syslog-ng 1.4.13 on solaris 5.6 and 5.8
Hi, I'm running syslog-ng on Solaris machines. So far I have two machines with will not start syslog-ng properly. ----- root@mimas:/etc/local/syslog-ng-1.4.13/etc$ /etc/init.d/syslog-ng start Starting Syslog-NG Error creating AF_INET socket (Error 0) Error initializing configuration, exiting. root@mimas:/etc/local/syslog-ng-1.4.13/etc$ uname -a SunOS mimas 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-80 ----- The Solaris 5.8 machine has the same problem. Funny thing is - other Solaris 5.8 machines do run syslog-ng just fine. Idea's anyone? Thanks, Jasper 12:07pm up 20 day(s), 16:01, 20 users, load average: 0.14, 0.14, 0.13
On Tue, Oct 02, 2001 at 12:11:28PM +0200, Jasper Jans wrote:
Hi,
I'm running syslog-ng on Solaris machines. So far I have two machines with will not start syslog-ng properly.
----- root@mimas:/etc/local/syslog-ng-1.4.13/etc$ /etc/init.d/syslog-ng start Starting Syslog-NG Error creating AF_INET socket (Error 0) Error initializing configuration, exiting.
root@mimas:/etc/local/syslog-ng-1.4.13/etc$ uname -a SunOS mimas 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-80 -----
The Solaris 5.8 machine has the same problem. Funny thing is - other Solaris 5.8 machines do run syslog-ng just fine.
run syslog-ng with truss, e.g.: truss syslog-ng -dv and check the output why the socket(AF_INET...) call fails -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
On Tue, Oct 02, 2001 at 12:31:23PM +0200, Balazs Scheidler wrote:
On Tue, Oct 02, 2001 at 12:11:28PM +0200, Jasper Jans wrote:
Hi,
I'm running syslog-ng on Solaris machines. So far I have two machines with will not start syslog-ng properly.
----- root@mimas:/etc/local/syslog-ng-1.4.13/etc$ /etc/init.d/syslog-ng start Starting Syslog-NG Error creating AF_INET socket (Error 0) Error initializing configuration, exiting.
root@mimas:/etc/local/syslog-ng-1.4.13/etc$ uname -a SunOS mimas 5.6 Generic_105181-23 sun4u sparc SUNW,Ultra-80 -----
The Solaris 5.8 machine has the same problem. Funny thing is - other Solaris 5.8 machines do run syslog-ng just fine.
run syslog-ng with truss, e.g.:
truss syslog-ng -dv
and check the output why the socket(AF_INET...) call fails
as it seems syslog-ng succeeded to create a socket, but failed to resolve some kind of hostname. what is your config file like? -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
Balazs Scheidler
-
Jasper Jans