34SP.com System Status History

Description

Update at 17:28:04(BST): Update at 17:27:46(BST): All services are now back online and functioning - please do let us know if you do however find any issues.

---

Update at 15:15:16(BST): The migration of the server has now been mainly completed, we still have a few small bits to do, but please do contact us if you are experiencing issues with your site at this time.

---

Update at 12:03:06(BST): Access to the prohost6 server has now been stopped so we can sync up the files and databases to the new hardware.

---

Update at 07:54:24(BST): This server is being migrated today, please try to avoid making any changes in the siteadmin area.

The ftp service has been disabled to avoid any file system changes at this time.

We will update this post throughout the day as the migration proceeds.

---

The prohost6.34sp.com server has recently not been providing a sufficient level of service to sites held on it and we are taking action to rectify this. Affected users will shortly receive an e-mail regarding the work being undertaken, but in preparation for this it is likely that the poor performance will continue this afternoon.

We are doing our best to ensure problems are kept to a minimum and can only apologise for this work which is necessary to improve the service in the coming days.

Start Time

3rd October 2011, at 1:16PM

Description

Update at 11:35:29(BST): This has now been resolved.

---

At present Xenserve4 is running all services but Plesk is reporting an unknown error. We're working to resolve this as soon as possible.

Start Time

30th September 2011, at 10:41AM

Description

Update at 10:40:24(BST): This status outage is now resolved.

---

Update at 15:00:09(BST): Max has rebooted cleanly and all services are now running once again.

We will be investigating the cause of the outage that prompted the reboot and shall monitor the server from here.

---

Unfortunately, we have been forced to reboot the Personal hosting machine Max.

This will affect all services hosted on accounts there.

We apologise for the obvious inconvenience caused. The machine is being shutdown cleanly so there should be no danger to any data.

The reboot should take no longer than 10 minutes.

Start Time

27th September 2011, at 2:55PM

Description

Update at 10:05:49(BST): The issue has now been resolved with this server.We are currently experiencing issues with the mysql service. This will be affecting some websites but not all and any email connections. This has been raised to the engineers who will be investigating shortly.

This has now been resolver by our engineers and a full table repair has been performed to ensure all is as it should be.

Start Time

23rd September 2011, at 8:34AM

Description

Update at 17:43:24(BST): The issue has now been resolved with this server.

---

We are currently aware of an issue affecting the server4.xenserve.com server and are currently looking into this.

Start Time

22nd September 2011, at 3:49PM

Description

Update at 15:00:49(BST): No issues have been discovered since xenserve18 was upgraded, so this outage is being marked as resolved.

---

Update at 22:26:40(BST): With the upgrade completed successfully, xenserve18 is now back online and functioning with its extra memory.

Services may seem a little sluggish at first, but that is largely due to users hitting refresh/send & receive, etc.

Any customers experiencing any lingering issues following this work are urged to contact support@34sp.com as soon as possible.

---

Update at 22:01:38(BST): Work has begun.

---

Update at 21:58:14(BST): This work will be starting in the next few minutes.

Any legitimate mail to be delivered to the server during this time will be queued and re-tried by the sending MTA.

---

Customers are reminded that reseller accounts on xenserve18 will be affected by a reboot & memory upgrade starting in approx. 30 minutes (22:00 BST).

Updates will be posted to this page when the work is completed and/or if there are any unforeseen circumstances.

We hope to have this work completed in under the projected time span of 30 minutes.

Start Time

21st September 2011, at 9:31PM

Description

Update at 15:01:59(BST): At this time the migration has gone to plan and any lingering issues that customers may have should be raised via e-mail to support@34sp.com.

---

Update at 13:33:03(BST): All 4PSA products and crons were enabled on the server this morning, please let us know if you have any issues with your sites after this move.

---

Update at 14:13:24(BST): The IPs were migrated across a short while ago, and the sites should now be up and running.

If anyone is experiencing any issues please contact us.

---

Update at 13:05:11(BST): We are currently in the process of migrating the IPs across servers, everything should be back online in the next hour.

---

Update at 12:09:41(BST): All web services are now offline for reimports of databases and final sync up of files before the IPs are switched over.

---

Update at 11:35:44(BST): Ftp services now going offline.

---

Update at 11:06:53(BST): Mail (POP3/IMAP) access has now been disabled as well.

---

Update at 10:45:30(BST): Incoming mailservices on server2 have now been stopped for an initial sync up of the email on the server.

---

The server2.xenserve.com is undergoing migration to new hardware today as per the email sent to all clients.

Try to avoid making any changes on any websites now to minimize loss of data when transferred to the new server.

We will update this post with progress throughout the day

Start Time

20th September 2011, at 8:11AM

Description

Update at 21:32:38(BST): This status outage regarding xenserve9's DNS service is now marked as resolved following successful operation of the service for at least a few days.

---

Update at 17:53:55(BST): Apologies for the late update: xenserve9's DNS service has been running since approx. 17:22.

We will continue to monitor this machine for a short time.

---

At present, xenserve9 is experiencing a software issue with its local DNS service that may be causing an outage for customers that use the ns17/ns18.xenserve.com name server addresses.

We're working hard to get this resolved as soon as possible.

Start Time

19th September 2011, at 5:12PM

Description

Update at 21:29:47(BST): This outage is now resolved. Please see the current update regarding the planned maintenance to xenserve18.

---

Update at 18:01:12(BST): Upon further investigation, it appears that two faults were affecting xenserve18 at the time of the outage:

One is related to the RAID card. There is some updated firmware available for this and we shall be discussing downtime planning to have the RAID card updated, as soon as is possible.

The second is memory starvation. An upgrade to the system's memory has been planned recently, which we may have to bring forward.

Any 'final' details pertaining to this solution will be e-mailed to affected customers as soon as possible.

---

Update at 11:07:44(BST): Xenserve18 is now back up and running (and has been for a short while).

We have observed an error presented by the system's BIOS which required user interaction to boot correctly.

We will be checking all databases for consistency very shortly and shall continue to interrogate the hardware to see why this message was presented.

---

Update at 10:41:20(BST): Unfortunately xenserve18 has not booted cleanly. We have an Engineer on-site already to investigate.

As a result the machine will be down for another 15-20 minutes.

---

Update at 10:26:36(BST): We have been forced to reboot xenserve18. This will mean the machine should restart as normal. We'll be checking all databases as soon as the machine is up and running again.

---

We are experiencing very high loads with server18/xenserve18. This is causing an outage of all services.

We are working to recover the machine.

Start Time

19th September 2011, at 10:17AM

Description

Update at 16:12:06(BST): Update at 11:49:07(BST): All VPS containers are up and running again after the host restart.

At present it appears that this was caused by a live migration of a container from another VPS host (something that shouldn't cause such catastrophic behaviour in a host) but the logging after the migrated container started is notably sparse.

We will continue to investigate & monitor the server from this point.

---

VPS22 has rebooted itself, this will affect all current containers present on the machine.

We are investigating the cause of this and will provide updates ASAP.

Start Time

14th September 2011, at 11:34AM