The reason for this maintenance is that it has been detected that a hard drive in the raid-array is showing signs of being defective.

During the scheduled maintenance window, Node 1 will be taken offline and the defective hard drive will be replaced. When Node 1 is started up again, the raid-array will be rebuilt and then services should return to normal.

It will take approximately 30 minutes to change hard drive, and then the raid-array has to be rebuilt. It is hard to say how long the rebuild will take, but there will be at least a maintenance window set for 5 hours. However, it will most likely go faster than that.

Thank you for your understanding.

2010-12-20, 23:34 GMT+1
UPDATE: All seem to have gone well. The drive has been replaced, the server is back online and the raid-set is being re-synced. If you have any further questions, email info@henleg.com and a customer service representative will get back to you as soon as possible.

2010-12-21, 11:20 GMT+1
UPDATE: The raid-set is synced up and checked.

2010-11-27, 16:11 GMT+1
UPDATE: Services are restored. We have been working with the datacenter to bring the server back up. All services should be operational. If you have any questions, as always feel free to email info@henleg.com and we’ll answer them and help you when necessary.

Note that migration to a new server is starting during week 44. This new server is located in a better network as well as running cPanel as the control panel. Further information will be posted on here.

Our deep apologies for the inconvenience this outage may cause.

2010-10-28, 23:05 GMT+1
UPDATE: Services are restored. Datacenter confirmed DDOS saturating their up-links to the Internet rending the customers’ servers unable to go online.

2010-08-11, 00:38 GMT+1
UPDATE: Services are restored, however if you experience more issues please email support@henleg.com. Steps are being taken to avoid downtime similar to this.

In order to mitigate this bug, manual intervention is necessary and measures has been taken on all servers/services to fix this issue.

Reference: Apache Foundation bugreport

We apologize for the inconvenience.

2009-03-14, 13:46 GMT+1
UPDATE: The network seem to have been stabilized now. If you experience any issues apart from what is posted above, please email support@henleg.com

2009-03-14, 14:46 GMT+1
UPDATE: There are still some lingering network issues to certain locations, we do know that the datacenter is working on it. We have not received an ETA on when this issue will be totally over, but it shouldn’t take too much time. Once again we apologize for any inconvenience this might have caused you. We will keep this post updated as we get to know more.

2009-03-14, 15:10 GMT+1
UPDATE: Network connectivity seems to have been restored to all locations now. We’ll update this post as further information comes in. Naturally, getting the network up and running is the biggest priority for the technicians on site at the datacenter and a RFO (Reason For Outage) takes lower priority. To verify the server status from different locations than your own, go to http://host-tracker.com and put in your website’s full domain name there. Also see the Pingdom Status page for Node 3 to see if there are any issues currently. If you have any questions, please email support@henleg.com and your inquiry will be answered as soon as possible.

Thank you for your patience.

2009-03-03, 22:28 GMT+1
UPDATE: The web server is now functioning normally. If you experience any errors apart from this, please email support@henleg.com

We apologize for any inconvenience this has caused.

2009-02-13, 21:42 GMT+1
UPDATE: The reason to this outage was a so called DDOS attack against the Datacenter where Node 3 is located in. The issue is now labelled as resolved. Thank you for your patience

We are working diligently on this issue and will migrate your data to a new server as soon this server is deployed and put active by our datacenter. (No data should be lost and emails will be put in queue during the migration process.)

We apologize for any inconvenience this may have caused you.

Watch this post for updates on the issue.

2008-10-20, 00:31 GMT+1
UPDATE: We have ordered a new server and the payment has been processed. As soon as the new server is provisioned by the datacenter, then the old harddrive will be put into the new server and data will start to get migrated. However, the process will take a while. We will however work as quick as possible to get everything sorted.

The positive thing here is that the new hardware will both be more solid, but also give you much better performance for all your hosted services. (Plus that we’ll add an extra surprise for existing users.)

Once again, we would like to emphasize that no email should be lost during this server migration.

Thank you again for your patience.

2008-10-20, 11:49 GMT+1
UPDATE: The new server is now up and running and we are configuring it. We are still waiting for the datacenter to provide us with either access to the old server (get it back online again), or get access to the harddrive in order to restore data on it.

2008-10-21, 01:45 GMT+1
UPDATE: The datacenter has agreed to put in the old harddrive into the new server. This is taking a while for them to do, and until this is done – there is no access to old data. Old accounts will be rebuilt and then email accounts, webdata and databases will be restored manually. In other words, right now we are waiting for the local datacenter technicians to expedite the harddrive move.

2008-10-24, 15:20 GMT+1
UPDATE: We have exhausted every option to recover the content of the crashed harddrive, but it looks like the initial actions of the datacenter staff destroyed the metadata needed to recover any eventual data from the harddrive. We also took in a third party consultant to help us to recover data, but the drive was too damaged to lift anything from. We are however restoring data through other methods, and if you need assistance email info@henleg.com and we’ll help you.

Once again, our sincere apologies for the inconvenience this has caused you.