Trunk nightly

[Cody]

<nods> Thanks, amigo. A summer spa vacation, eh... sounds delightful.

[Getafix]

...and it WILL be down for the next couple of weeks.
...
Until this is resolved, no new nightly will be built for windows and linux and oolite-update (via rsync) will not be available for both windows and linux.
...

You may have noticed that we managed to deliver new nightlies at github even though terrastorage had ongoing network operations and its nightly build log page as well as the oolite-update (via rsync) service were down.

The terrastorage services are now restored, however, some minor hiccups are still expected to be noticed during this week too.

Thank you for your patience!
Cheers!

[Cody]

Code: Select all

12:44:44.805 [WARNING]: Warning! Global namespace polluted by:
12:44:44.805 [WARNING]: ["getScreenBackgroundForKey","setScreenBackgroundForKey"]

[another_commander]

Code: Select all

12:44:44.805 [WARNING]: Warning! Global namespace polluted by:
12:44:44.805 [WARNING]: ["getScreenBackgroundForKey","setScreenBackgroundForKey"]

This is from the Library OXP and comes up because it needs to be updated with the two new methods introduced with the latest commits. It is not a trunk issue.

[Cody]

Ah... okay.

[Hajimoto]

Code: Select all

12:44:44.805 [WARNING]: Warning! Global namespace polluted by:
12:44:44.805 [WARNING]: ["getScreenBackgroundForKey","setScreenBackgroundForKey"]

This is from the Library OXP and comes up because it needs to be updated with the two new methods introduced with the latest commits. It is not a trunk issue.

Are you sure about this?

[another_commander]

Are you sure about this?

Are you not?

[Svengali]

Are you sure about this?

Are you not?

[Hajimoto]

Hahah:)

[Getafix]

Are you sure about this?

Are you not?

Guys you killed me with this one! Thank you both!

[Getafix]

Guys, I'm bringing down TerraStorage to attempt a HDD recovery.
Oolite-update service will be unavailable.
I'll post an update later tonight.

EDIT 2017-08-30
I have managed to take a backup of the VMs and the latest scripts. However, if I could get an image of the source disk, it would avoid me the trouble of reinstalling everything from scratch. If you are wondering about the previous backups I have taken, well, the first one is on a disk that died and the second one is currently being taken.

The rate of imaging is dramatically low; without errors but we are talking about less than 128KB/s.
Unfortunately all the disks I have are in the Methuselah age category.
I am trying to get my hands to another/younger target disk to check if the issue is there.
I hope it is not due to the source disk.

EDIT 2017-09-08
No available hdd found yet to pinpoint the issue.

EDIT 2017-09-15
Good news. Just got a spare hdd to proceed with the troubleshooting.
Due to R/L priorities, I will be taking over these tasks this Monday.

EDIT 2017-10-03
Better news! It seems that the problem was not with worn out hdd,
but with some faulty Molex to SATA power cable adapters.
Currently cloning the server's disk.

EDIT 2017-10-05
Not THAT much better news. I managed to make a clone of the system disk.
I left it this morning trying to take a second clone.
It seems that at some point it finds some difficulty reading the source.
This means that the main disk will be dead soon.
I will try the clones the next couple of days and then will most probably proceed to disk replacement.

EDIT 2017-10-05 - Part II
I estimate that it will take 12 more hours to complete the second cloning.
This time I will let it complete. In the meantime I am looking into getting a disk.
The worst case scenario (please don't!) will call for three disks; one live, the second for backup and
the third for disaster recovery, physically far away from the server.

EDIT 2017-10-06
Second clone finished faster. This gave me the opportunity to test it as a primary before last nightly execution.
Currently this clone is the live one and I'm validating it while performing some operational tasks.

EDIT 2017-10-09
OK. The two disk-clones seem to be healthy. Today the source disk has been restored as live and terrastorage will remain up till the new replacement disk comes in.

[Hajimoto]

Guys, I'm bringing down TerraStorage to attempt a HDD recovery.
Oolite-update service will be unavailable.
I'll post an update later tonight.

Ok let us know!

[Cody]

Don't know if this is trunk or an OXP - probably the latter. Had a short cruise, saved, went to the manager and removed an OXZ (Rings), then exited the game. Tried my customary log check, but Notepad++ couldn't open it as it's 1GB in size - WTF? After relaunching the game, the log is normal again.

[Norby]

If your previous.log still hold it then you can try to look into with a viewer like F3 in Total Commander.

[Cody]

Thanks, Norby - but even if I could open it, I've no wish to wade through 1GB of errors.
However, it's here if anyone wants to try (.zip 31.9MB) - and good luck.