/dev/log is not a socket error on startup
Howdy. Doing some updates to my Linux box today when I noticed I still hadn't gotten around to setting up log rotation. It was then that I've noticed syslog-ng wasn't running. I tried to start it manually, but get the following: io.c: bind_unix_socket(): /dev/log not a socket Error initializing configuration, exiting. I just upgraded to latest libol (0.3.11) and syslog-ng (1.6.rc4) today, same results. Any ideas? Thanks -T
On Wed, Oct 22, 2003 at 02:12:55PM -0400, Tony Karakashian wrote:
Howdy. Doing some updates to my Linux box today when I noticed I still hadn't gotten around to setting up log rotation. It was then that I've noticed syslog-ng wasn't running. I tried to start it manually, but get the following:
io.c: bind_unix_socket(): /dev/log not a socket Error initializing configuration, exiting.
I just upgraded to latest libol (0.3.11) and syslog-ng (1.6.rc4) today, same results. Any ideas?
something probably changed the socket to a pipe or something. try removing /dev/log and restart syslog-ng so it will not refuse to start. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
io.c: bind_unix_socket(): /dev/log not a socket Error initializing configuration, exiting.
something probably changed the socket to a pipe or something. try removing /dev/log and restart syslog-ng so it will not refuse to start.
And, just like that, it's working. I had removed /dev/log and recreated it, not realizing syslog takes care of that. Cool. Thanks! -T -- Answering the age old question: Which is more painful, going to work or gouging your eye out with a spoon? www.workorspoon.com
participants (2)
-
Balazs Scheidler
-
Tony Karakashian