<div>Hi, </div>
<div> </div>
<div>Unfortunately , I cannot recreate that issue and now everything seems fine.</div>
<div>But, I have a similar issue on an RHEL4 machine . I am trying to configure this as a central server.</div>
<div>But the central logging does not seem to work as expected. </div>
<div>When I check the 514 port everything seems fine.</div>
<div> </div>
<div>lsof -i:514<br>COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME<br>syslog-ng 23505 root 3u IPv4 72737 TCP *:514 (LISTEN)<br>syslog-ng 23505 root 9u IPv4 72792 TCP 20.5.68.39:514-><a href="http://20.5.68.225:56596">20.5.68.225:56596</a> (ESTABLISHED)</div>
<div> </div>
<div>But, as you suggested, running syslog_ng with "Fedv" options does report some errors.</div>
<div> </div>
<div> /opt/soe/local/syslog_ng/sbin/syslog-ng -Fedv<br>Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (98)'<br>Error initializing source driver; source='s_remote', id='s_remote#0'<br>
Error initializing message pipeline;<br></div>
<div>I executed the below commadn on the test machine .</div>
<div> </div>
<div>Please help me fix this.</div>
<div> </div>
<div>Thanks,</div>
<div>Rakesh</div>
<div><br> </div>
<div class="gmail_quote">On Thu, Dec 15, 2011 at 8:05 PM, Pal Tamas <span dir="ltr"><<a href="mailto:folti@balabit.hu">folti@balabit.hu</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div class="HOEnZb">
<div class="h5">On Wed, Dec 14, 2011 at 06:54:33PM +0530, Rakesh Rajasekharan wrote:<br>> Hi,<br>><br>> I am faced with a rather strange issue with syslog 3.0.7 version. The daemon<br>> does not start at all when I try to run it in the central server mode.<br>
> I though do not get any error messages .<br>> But, I noticed that after a reboot of the machine. Everything works fine. Can<br>> someone please suggest of any possible areas to check.<br>><br>> Thanks,<br>
> Rakesh<br></div></div>Hi,<br><br>We need more information about this.<br>What is your syslog-ng configuration?<br>If your syslog-ng listens on 514/tcp port (the default server port for tcp<br>transport):<br> - Did you disabled the rsh service in /etc/inetd.conf ? By default,<br>
it's the service that listens on 514/tcp.<br> - probably if you configured your system to start syslog-ng before<br> starting inetd, syslog-ng acquired the port before inetd could start.<br><br>Otherwise, did you tried to run syslog-ng with the -Fedv arguments added<br>
from the command line? It won't go to the background, but will display<br>all startup messages it may or may not be able/not configured to write out.<br><br>Regards,<br><span class="HOEnZb"><font color="#888888">--<br>
Pal Tamas/Folti<br><a href="mailto:folti@balabit.hu">folti@balabit.hu</a><br><br>______________________________________________________________________________<br>Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br></font></span></blockquote></div><br>