Hi,
 
Unfortunately , I cannot recreate that issue and now everything seems fine.
But, I have a similar issue on an RHEL4 machine . I am trying to configure this as a central server.
But the central logging does not seem to work as expected.
When I check the 514 port everything seems fine.
 
lsof -i:514
COMMAND     PID USER   FD   TYPE DEVICE SIZE NODE NAME
syslog-ng 23505 root    3u  IPv4  72737       TCP *:514 (LISTEN)
syslog-ng 23505 root    9u  IPv4  72792       TCP 20.5.68.39:514->20.5.68.225:56596 (ESTABLISHED)
 
But, as you suggested, running syslog_ng with "Fedv" options does report some errors.
 
 /opt/soe/local/syslog_ng/sbin/syslog-ng -Fedv
Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (98)'
Error initializing source driver; source='s_remote', id='s_remote#0'
Error initializing message pipeline;
I executed the below commadn on the test machine .
 
Please help me fix this.
 
Thanks,
Rakesh

 
On Thu, Dec 15, 2011 at 8:05 PM, Pal Tamas <folti@balabit.hu> wrote:
On Wed, Dec 14, 2011 at 06:54:33PM +0530, Rakesh Rajasekharan wrote:
> Hi,
>
> I am faced with a rather strange issue with syslog 3.0.7 version. The daemon
> does not start at all when I try to run it in the central server mode.
> I though do not get any error messages .
> But, I noticed that after a reboot of the machine. Everything works fine. Can
> someone please suggest of any possible areas to check.
>
> Thanks,
> Rakesh
Hi,

We need more information about this.
What is your syslog-ng configuration?
If your syslog-ng listens on  514/tcp port (the default server port for tcp
transport):
 - Did you disabled the rsh service in /etc/inetd.conf ? By default,
  it's the service that listens on 514/tcp.
 - probably if you configured your system to start syslog-ng before
  starting inetd, syslog-ng acquired the port before inetd could start.

Otherwise, did you tried to run syslog-ng with the -Fedv arguments added
from the command line? It won't go to the background, but will display
all startup messages it may or may not be able/not configured to write out.

Regards,
--
Pal Tamas/Folti
folti@balabit.hu

______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq