<div dir="ltr"><div>Hi,<br><br></div>syslog-ng-ctl requires the same control file that you supplied to the 2nd syslog-ng instance, so this should work:<br><div><div><br>$ syslog-ng-ctl --control=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.ctl<br><br></div><div>If it started up, it should work though. Can you start syslog-ng in the foreground (-F) and request debug logs using -de, so it should look like this:<br><br>$ syslog-ng -Fed --cfgfile=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.conf --persist-file=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.persist --pidfile=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.pid --control=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.ctl<br><br></div><div>This should display a couple of debugging messages during startup and also whenever a message is received. You might find a clue there.<br></div><div><br></div><div>Also, this may or may not have a relation to the problem you are seeing, but 3.3.4 is pretty old, probably more than 5 years old. Our current version is 3.7.3.<br></div><div><br></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">-- <br>Bazsi<br></div></div></div>
<br><div class="gmail_quote">On Wed, Jun 29, 2016 at 3:33 PM, David Campeau <span dir="ltr">&lt;<a href="mailto:David.Campeau@tn.gov" target="_blank">David.Campeau@tn.gov</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I&#39;m not sure of the syntax needed to connect to the socket or how to prepare the system.<br>
<br>
Below is just a blind attempt to connect to a socket.  The 2nd instance of syslog-ng is running and listening on port 518.<br>
<br>
I created a directory under /run called &quot;syslog-ng-Second-Instance&quot; and tried to connect...  However Connection is refused.<br>
<br>
Command Used:<br>
root@syslog-ng:# syslog-ng-ctl verbose --set=on --control=/run/syslog-ng-Second-Instance<br>
Error connecting control socket, socket=&#39;/run/syslog-ng-Second-Instance&#39;, error=&#39;Connection refused&#39;<br>
<br>
<br>
Any thoughts on the correct syntax and preparation needed?<br>
<span class="im HOEnZb"><br>
<br>
Best Regards,<br>
<br>
<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:jrhendri@roadrunner.com">jrhendri@roadrunner.com</a> [mailto:<a href="mailto:jrhendri@roadrunner.com">jrhendri@roadrunner.com</a>]<br>
</span><div class="HOEnZb"><div class="h5">Sent: Tuesday, June 28, 2016 3:00 PM<br>
To: Syslog-ng users&#39; and developers&#39; mailing list; David Campeau<br>
Subject: RE: [syslog-ng] Syslog-ng Multiple Instances<br>
<br>
Maybe this?<br>
<br>
If you need to use a non-standard control socket to access syslog-ng,<br>
       use the syslog-ng-ctl &lt;command&gt; --set=on --control=&lt;socket&gt; command to<br>
       specify the socket to use.<br>
<br>
<br>
<br>
---- David Campeau &lt;<a href="mailto:David.Campeau@tn.gov">David.Campeau@tn.gov</a>&gt; wrote:<br>
&gt; Jim,<br>
&gt;<br>
&gt; No errors as the instance starts normally and listens on port 518. However, no logs are received or forwarded.<br>
&gt;<br>
&gt; root@syslog-ng1:/usr/local/bin/syslog-ng-Second-Instance# netstat -an |grep 518<br>
&gt; udp        0      0 <a href="http://0.0.0.0:518" rel="noreferrer" target="_blank">0.0.0.0:518</a>             0.0.0.0:*<br>
&gt;<br>
&gt; The test device is on the same subnet as syslog-ng listening on port 518, so there aren&#39;t any firewall issues. I&#39;ve verified the test device is configured for port 518.<br>
&gt;<br>
&gt; However, when I check ctl stats, it&#39;s seeing the stats of the production syslog-ng instance.  So, it appears this is improperly configured, but it&#39;s unknown what needs to be changed.<br>
&gt;<br>
&gt; Best Regards,<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <a href="mailto:jrhendri@roadrunner.com">jrhendri@roadrunner.com</a> [mailto:<a href="mailto:jrhendri@roadrunner.com">jrhendri@roadrunner.com</a>]<br>
&gt; Sent: Tuesday, June 28, 2016 12:53 PM<br>
&gt; To: Syslog-ng users&#39; and developers&#39; mailing list<br>
&gt; Cc: David Campeau<br>
&gt; Subject: Re: [syslog-ng] Syslog-ng Multiple Instances<br>
&gt;<br>
&gt; The only thing that would limit the number of instances that I am aware of are conflicts for opening things like network ports, connections to databases, maybe FIFOs, etc.<br>
&gt;<br>
&gt; I would look at that as a place to start.<br>
&gt;<br>
&gt; What kind of errors are you getting when you try to start the second instance?<br>
&gt;<br>
&gt; Jim<br>
&gt;<br>
&gt; ---- David Campeau &lt;<a href="mailto:David.Campeau@tn.gov">David.Campeau@tn.gov</a>&gt; wrote:<br>
&gt; &gt; Hello,<br>
&gt; &gt;<br>
&gt; &gt; I&#39;ve been using syslog-ng to filter syslog before forwarding on to a log collector. However, I need to spin up a second instance for testing purposes. I&#39;ve found a little bit of information on-line, but it hasn&#39;t completed the entire picture.<br>
&gt; &gt;<br>
&gt; &gt; This is the command used to start up the 2nd instance. I&#39;m pointing to separate .conf .persist .pid and .ctl files -- However, it&#39;s still not working. I suspect the issue is due to OS log sources. How do a change log sources?<br>
&gt; &gt;<br>
&gt; &gt; syslog-ng --cfgfile=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.conf --persist-file=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.persist --pidfile=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.pid --control=/usr/local/bin/syslog-ng-Second-Instance/syslog-ng.ctl &amp;<br>
&gt; &gt;<br>
&gt; &gt; This is the upper part of the syslog-ng.conf file for the 2nd instance I wish to run.<br>
&gt; &gt;<br>
&gt; &gt; @version: 3.3.4<br>
&gt; &gt; @include &quot;scl.conf&quot;<br>
&gt; &gt;     options {<br>
&gt; &gt;         time-reap(30);<br>
&gt; &gt;         mark-freq(10);<br>
&gt; &gt;         keep-hostname(yes);<br>
&gt; &gt;         chain-hostnames(no);<br>
&gt; &gt;         use-dns(no);<br>
&gt; &gt; ##       log-fifo-size(500000);                ## Tuning Options<br>
&gt; &gt; ##      flush_lines(10000);                   ## Tuning Options<br>
&gt; &gt; ##       flush_timeout(10000);                ## Tuning Options<br>
&gt; &gt;     };<br>
&gt; &gt;<br>
&gt; &gt;         source s_second_instance {<br>
&gt; &gt;         syslog(transport(&quot;udp&quot;) port(&quot;518&quot;));       #### Will receive test syslog on port 518<br>
&gt; &gt;         };<br>
&gt; &gt;<br>
&gt; &gt;     destination d_syslog_udp {<br>
&gt; &gt;         syslog(&quot;10.X.X.X&quot;<br>
&gt; &gt;             transport(&quot;udp&quot;)<br>
&gt; &gt;             port(&quot;514&quot;)<br>
&gt; &gt;             throttle(4000)<br>
&gt; &gt;         );<br>
&gt; &gt;     };<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; I&#39;m hoping someone has experience or has seen information on how to run a 2nd instance on the same box.<br>
&gt; &gt;<br>
&gt; &gt; Best Regards,<br>
&gt; &gt;<br>
&gt; &gt; David<br>
&gt;<br>
<br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" rel="noreferrer" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" rel="noreferrer" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
</div></div></blockquote></div><br></div>