Monroe down for 7 hours now

[the_ancient]

NM , looks like back online

[JPC-Anoop]

Thanks for the update. Please feel free to open a ticket with support if you're facing any issue with the server.

[the_ancient]

Am I looking at another 8 hour downtime????

I almost lost all of the clients on that server last time this happen to have it occur AGAIN in the same month is unacceptable...

Further when is the Grid Hosting, that should stop these node level FS errors if done correctly, going to be a service? For the Money I am Paying JPC I can get a grid Hosted VPS that will not be down for 8+ Hours while FDisk is run

[the_ancient]

15 hours of down time this month so far , 5 hours down under this outage, 3 hours since last JPC Update.....

Wonderful

[JPC-Nasir]

Hi,

Please accept our sincere apologies for the extended downtime. File system check is still in progress, currently 2nd pass is being done, there are three passes in total.

[pacoflaco]

I am in the some node and i'm very tired about this kind of problem, the most fun is that passing hours and hours and we do not update anything

[the_ancient]

I understand that this happens, my problem is

1> JPC had told me and other many many many times it was taken steps to ensure fsck did not take hours and hours and hours, this seems to be an empty promise year after year...

2> More importantly for over a year now I have been asking about and have been told "hang in there i is coming" for a "cloud" / grid or for web hosting, only it never comes....


I dont have a Problem with small outages, that is the nature of budget hosting, however there is a viable solution to stop these hours/days long fsck and I wish JPC would implement something even if its not a full ontrue Cloud, Some kind of Redunant SAN, or other offerings that would enable people to move VPS to another node to only have a few minutes or 1 hour of downtime vs hours and hours.... I would pay extra for that.

[the_ancient]

Another thing, when you have a downtime of this length it should be common and automatic practice to run a date/time update on the node, every time this happens I get warnings out the rear from Lic Managers and other scripts that depend on proper time sync with the real word......

Someone please update the hardware nodes time

[JPC-Nasir]

Sincere apologies, time has been synchronized now.

[the_ancient]

Here we go again, 3rd time in he same month

I am really getting tired of this

[pacoflaco]

10 hours more

[JPC-Zishan]

We had already setup a Node for Monroe replacement and VPSs were being migrated to new Node when Monroe crashed. We are performing File System Check on Monroe and in parallel restoring the VPSs from backup to a new Node that was setup for replacement. The backup that we will be using is of 29th July.

[the_ancient]

21 hours of down time this month so far , 5 hours down under this outage, 3 hours since last JPC Update.....

Wonderful

[Ron]

I know that you know these bare metal restores take 2 to 3 days...

[Ron]

Oh.... they have Monroe up and running -- I guess that's the old Monroe. Will they still be migrating to the new Monroe as of the 29th, or will they attempt an rsync when the new Monroe is up and running with 29th data.... what if the old Monroe crashes again, this time during the rsync? That'll leave the state of some files in the 29th and some current. Wow, what a hard decision to make (for me). Glad I don't have to make it!