34SP.com System Status History

bishop.34sp.com plesk issues (bishop.34sp.com)

resolved

Description

We are currently investigating an issue with plesk on the bishop server. This will also impact on database services.

The issue was related to an incorrect restart of the database server and has now been resolved.

Start Time

24th January 2006, at 11:29PM

Resolution Time

24th January 2006, at 11:50PM

server3.xenserve.com

resolved

Description

server3.xenserve.com is presently refusing connections.

The machine has been power cycled and we are now waiting on the results from this.

The machine has now been restored.

Start Time

24th January 2006, at 4:42PM

Resolution Time

24th January 2006, at 4:48PM

Oversoul.34SP.com server (oversoul.34sp.com)

resolved

Description

An issue on the oversoul server is currently being looked into.

This matter is being looked into further after a repeat.

Steps have been taken to stop the problem on the server. We are monitoring the situation but the matter should be resolved.

Start Time

20th January 2006, at 9:12AM

Resolution Time

20th January 2006, at 10:35AM

business1.34sp.com reboot (business1.34sp.com)

resolved

Description

Business1.34sp.com is now fully restored.

The business1.34sp.com server has been rebooted due to failure.

The server has failed to recover from the reboot and an engineer has been dispatched to the data center to investigate the nature of the failure.

We anticipate their arrival within 60 minutes.

Start Time

18th January 2006, at 3:34PM

Resolution Time

18th January 2006, at 5:40PM

earth www failure (earth.34sp.com)

resolved

Description

This has now been resolved.

We are presently investigating the failure of www services on earth.34sp.com.

Other services are unaffected.

Start Time

10th January 2006, at 6:58PM

Resolution Time

10th January 2006, at 7:08PM

lothos.34sp.com unavailable (lothos.34sp.com)

resolved

Description

The lothos.34sp.com server is currently unavailable. An engineer is on the way to investigate. We will post any further information as soon as we have it.

The problem has been traced to a corrupt password database which has now been fixed. All services are now available on lothos.34sp.com.

Start Time

9th January 2006, at 10:59AM

Resolution Time

9th January 2006, at 1:01PM

phpMyAdmin on Lothos (lothos.34sp.com)

resolved

Description

We have become aware of an issue with phpMyAdmin giving the following error:

'phpMyAdmin tried to connect to the MySQL server, and the server rejected the connection. You should check the host, username and password in config.inc.php and make sure that they correspond to the information given by the administrator of the MySQL server.
Error

MySQL said: Documentation
Cannot connect: invalid settings. '

We are currently looking into this and will resolve it as soon as possible.

Apologies for any inconvenience caused.

Start Time

8th January 2006, at 1:30PM

Resolution Time

9th January 2006, at 10:54AM

server3.xenserve.com (server3.xenserve.com)

resolved

Description

server3.xenserve.com is presently refusing connections and we are unable to reboot the machine using remote power controllers.

An engineer is now on their way to the datacenter to investigate the failure manually.

The server has now been restored, we will be looking at why access was being refused to the machine.

Start Time

4th January 2006, at 6:33PM

Resolution Time

4th January 2006, at 8:03PM

Network issues

resolved

Description

The 34SP.com network is running slowly at this time.

Apologies for the delayed update - this problem was fixed approximately 1 hour after the original posting, at 6:30pm on December 25th.

Start Time

25th December 2005, at 5:33PM

Resolution Time

29th December 2005, at 12:22PM

server3.xenserve.com outage (server3.xenserve.com)

resolved

Description

We are aware of a problem with server3.xenserve.com, and are working to resolve the issue as soon as possible.

An engineer has attended the server and it is now available again.

Start Time

21st December 2005, at 1:35PM

Resolution Time

21st December 2005, at 2:54PM