The VPS was down for 1 hour again. But now I think I understand what's going on.
At 12:01 all VPS'es (except mine) begin to process 24-hour logs thus overloading the disk.
A ticket has been logged. Waiting for a response.
BTW, they replaced a disk on Saturday.
Have you switched of the code 'validation' for comments against your Blog?
....or is this another feature designed to challange your mighty bug fixing talent?
😁
MJ
Finally I've got some attention from the provider! They are going to change the other VPSes' crontabs to distribute the load. Yeeeehhaaaa!!!! Took me 8 months to convince them.
Something happened with DNS today. The likera.com was not resolvable. Had to restart named several times.
Don't get it:
Nov 18 04:09:38 likera named[18781]: listening on IPv4 interface lo, 127.0.0.1#53
Nov 18 04:09:38 likera named[18781]: could not listen on UDP socket: address family not supported
Nov 18 04:09:38 likera named[18781]: creating IPv4 interface lo failed; interface ignored
Nov 18 04:09:38 likera named[18781]: listening on IPv4 interface seth0, x.x.x.x#53
Nov 18 04:09:38 likera named[18781]: could not listen on UDP socket: address family not supported
Nov 18 04:09:38 likera named[18781]: creating IPv4 interface seth0 failed; interface ignored
Nov 18 04:09:38 likera named[18781]: listening on IPv4 interface seth0:cp1, y.y.y.y#53
Nov 18 04:09:38 likera named[18781]: could not listen on UDP socket: address family not supported
Nov 18 04:09:38 likera named[18781]: creating IPv4 interface seth0:cp1 failed; interface ignored
Nov 18 04:09:38 likera named[18781]: not listening on any interfaces
Never seen that before. It was not working since 5 hours ago. Nice ...
(This post was last modified: 18 Nov 2011, 09:33 by Like Ra.)
Looks like another bug in either kernel or named. Had to explicitly set the maximum open files limit. Weird ...