1083: After replacement still Print/phpMyAdmin server problem
Although the hardware of the server was replaced, the server didn’t react for unknown reasons. A reboot of the machine solved the problem. We will think about ways to tackle this problem.
CPK messages are initially sent to the CPK mailing list, you can (un)subscribe via this link. You can also follow the service interruption messages via RSS using the link in the title under the RSS icon. If the CPK takes more time to resolve, any updates are published on this website.
For RU wide service interruption see meldingen.ru.nl.
Although the hardware of the server was replaced, the server didn’t react for unknown reasons. A reboot of the machine solved the problem. We will think about ways to tackle this problem.
Because of the recent problems with this server, we are going to replace the server, in order to prevent further service interruptions.
The server had a problem with one partition, which had started during the creation of new snapshots. We waited with the reboot untill after working hours. A reboot of the machine solved the problem. To prevent these problems in the future, we will no longer make local snapshots of homeservers, but of course the daily backups of the homeservers by the backup server will be continued.
Just like four days ago, the server didn’t react for unknown reasons. A reboot of the machine solved the problem. We plan to replace the server next Thursday 08:30-09:00 hours, in order to prevent further service interruptions.
Just like two weeks ago, the server didn’t react for unknown reasons. A reboot of the machine solved the problem. Together with the supplier we will try to find out what to replace to prevent this in the future.
From the moment of yesterday’s snapshots (13:00 hours), more and more processes were hung at the server. The first complaints arrived at C&CZ ca. 11:15 hours this morning. Therefore we decided ca. 11:35 to restart the server. The reboot resolved the problem. The number of snapshots will be reduced in order to try to prevent problems due to snapshots in the future.
Probably due to a too large printjob, the printer queue on the server (printto/printsmb/ooievaar) for the pr-hg-00-002 printer got stuck onWednesday morning. C&CZ was only informed of this problem at the end of Thursday. Friday morning this has been fixed by emptying the printqueue with old jobs.
The server didn’t react for unknown reasons. A reboot of the machine solved the problem.
The server had a problem with one partition. A reboot of the machine solved the problem.
The Linux login server lilo3 didn’t have the homedirectories of some users. It took a reboot to fix this.