<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Applications started multiple times]]></title><description><![CDATA[<p dir="auto">I'm running <em>2.0-RC1-IPv6 (i386)<br />
built on Fri Aug 26 18:54:18 EDT 2011</em></p>
<p dir="auto">I've noticed siproxd seems to get started multiple times:</p>
<blockquote>
<h1><a class="anchor-offset" name="clog-var-log-system.log-grep-siproxd"></a>clog /var/log/system.log | grep siproxd</h1>
<p dir="auto">Sep  1 08:26:12 pfsense siproxd[5662]: siproxd.c:247 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 starting up<br />
Sep  1 08:26:12 pfsense siproxd[6276]: siproxd.c:295 INFO:daemonized, pid=6276<br />
Sep  1 08:26:12 pfsense siproxd[6276]: plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40<br />
Sep  1 08:26:12 pfsense siproxd[6276]: sock.c:131 INFO:bound to port 5060<br />
Sep  1 08:26:12 pfsense siproxd[6276]: siproxd.c:349 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 started<br />
Sep  1 08:26:17 pfsense siproxd[35862]: siproxd.c:247 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 starting up<br />
Sep  1 08:26:17 pfsense siproxd[36560]: siproxd.c:295 INFO:daemonized, pid=36560<br />
Sep  1 08:26:17 pfsense siproxd[36560]: plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40<br />
Sep  1 08:26:18 pfsense siproxd[36560]: sock.c:543 ERROR:bind failed: Address already in use<br />
Sep  1 08:26:18 pfsense siproxd[36560]: siproxd.c:337 ERROR:unable to bind to SIP listening socket - aborting</p>
<h1><a class="anchor-offset" name="ps-ax-grep-siproxd"></a>ps ax | grep siproxd</h1>
<p dir="auto">6276  ??  S      0:00.20 /usr/local/sbin/siproxd -c /usr/local/etc/siproxd.conf<br />
4584  0  R+    0:00.01 grep siproxd</p>
<h1><a class="anchor-offset"></a></h1>
</blockquote>
<p dir="auto">and so does pfflowd:</p>
<blockquote>
<h1><a class="anchor-offset" name="clog-var-log-system.log-grep-pfflowd"></a>clog /var/log/system.log | grep pfflowd</h1>
<p dir="auto">Sep  1 08:26:18 pfsense pfflowd[38723]: pfflowd listening on pfsync0<br />
Sep  1 08:26:18 pfsense pfflowd[38723]: pfflowd listening on pfsync0<br />
Sep  1 08:26:18 pfsense pfflowd[38914]: pfflowd listening on pfsync0<br />
Sep  1 08:26:18 pfsense pfflowd[38914]: pfflowd listening on pfsync0</p>
<h1><a class="anchor-offset" name="ps-ax-grep-pfflowd"></a>ps ax | grep pfflowd</h1>
<p dir="auto">38723  ??  Ss    0:00.56 /usr/local/sbin/pfflowd -n sme.example.org:5678 -S any -v 5<br />
38914  ??  Ss    0:00.59 /usr/local/sbin/pfflowd -n sme.example.org:5678 -S any -v 5<br />
27488  0  R+    0:00.01 grep pfflowd</p>
<h1><a class="anchor-offset"></a></h1>
</blockquote>
<p dir="auto">In the case of siproxd it seems benign (apart from delaying the startup a little), but in the case of pfflowd it seems to result in duplicate flow records at the collector.</p>
<p dir="auto">This seems to have been happening for a while, at least since the Jun 20 snapshot build which I have just replaced.</p>
]]></description><link>https://forum.netgate.com/topic/36846/applications-started-multiple-times</link><generator>RSS for Node</generator><lastBuildDate>Wed, 15 Jul 2026 02:07:55 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/36846.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 31 Aug 2011 23:21:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Applications started multiple times on Fri, 02 Sep 2011 02:08:26 GMT]]></title><description><![CDATA[<p dir="auto">Due to another problem I went back to my Jun 21 snapshot build, upgraded to Aug 26 snapshot build then gitsync'd to get IPv6 support. On reboot after the gitsync, pfflowd appears to get started multiple times but only one copy is left running:</p>
<blockquote>
<h1><a class="anchor-offset" name="ps-ax-grep-pfflowd"></a>ps ax | grep pfflowd</h1>
<p dir="auto">52323  ??  SNs    0:00.24 /usr/local/sbin/pfflowd -n sme.example.org:5678 -S any -v 5<br />
39759  0  R+    0:00.01 grep pfflowd</p>
<h1><a class="anchor-offset" name="clog-var-log-system.log-grep-pfflowd"></a>clog /var/log/system.log | grep pfflowd</h1>
<p dir="auto">Sep  2 11:30:36 pfsense pfflowd[2924]: pfflowd listening on pfsync0<br />
Sep  2 11:30:36 pfsense pfflowd[2924]: pfflowd listening on pfsync0<br />
Sep  2 11:30:38 pfsense pfflowd[5216]: pfflowd listening on pfsync0<br />
Sep  2 11:30:38 pfsense pfflowd[5216]: pfflowd listening on pfsync0<br />
Sep  2 11:30:41 pfsense pfflowd[5216]: pfflowd exiting on signal 15<br />
Sep  2 11:30:41 pfsense pfflowd[2924]: pfflowd exiting on signal 15<br />
Sep  2 11:30:45 pfsense pfflowd[52323]: pfflowd listening on pfsync0<br />
Sep  2 11:30:45 pfsense pfflowd[52323]: pfflowd listening on pfsync0</p>
<h1><a class="anchor-offset"></a></h1>
</blockquote>
<p dir="auto">siproxd is still started multiple times with one copy left running:</p>
<blockquote>
<h1><a class="anchor-offset" name="clog-var-log-system.log-grep-siproxd"></a>clog /var/log/system.log | grep siproxd</h1>
<p dir="auto">Sep  2 11:30:28 pfsense siproxd[58103]: siproxd.c:247 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 starting up<br />
Sep  2 11:30:28 pfsense siproxd[58359]: siproxd.c:295 INFO:daemonized, pid=58359<br />
Sep  2 11:30:28 pfsense siproxd[58359]: plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40<br />
Sep  2 11:30:28 pfsense siproxd[58359]: sock.c:131 INFO:bound to port 5060<br />
Sep  2 11:30:28 pfsense siproxd[58359]: siproxd.c:349 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 started<br />
Sep  2 11:30:34 pfsense siproxd[62885]: siproxd.c:247 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 starting up<br />
Sep  2 11:30:34 pfsense siproxd[63269]: siproxd.c:295 INFO:daemonized, pid=63269<br />
Sep  2 11:30:34 pfsense siproxd[63269]: plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40<br />
Sep  2 11:30:34 pfsense siproxd[63269]: sock.c:131 INFO:bound to port 5060<br />
Sep  2 11:30:34 pfsense siproxd[63269]: siproxd.c:349 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 started<br />
Sep  2 11:30:36 pfsense siproxd[2489]: siproxd.c:247 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 starting up<br />
Sep  2 11:30:36 pfsense siproxd[2808]: siproxd.c:295 INFO:daemonized, pid=2808<br />
Sep  2 11:30:36 pfsense siproxd[2808]: plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40<br />
Sep  2 11:30:36 pfsense siproxd[2808]: sock.c:543 ERROR:bind failed: Address already in use<br />
Sep  2 11:30:36 pfsense siproxd[2808]: siproxd.c:337 ERROR:unable to bind to SIP listening socket - aborting<br />
Sep  2 11:30:41 pfsense siproxd[25686]: siproxd.c:247 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 starting up<br />
Sep  2 11:30:41 pfsense siproxd[26409]: siproxd.c:295 INFO:daemonized, pid=26409<br />
Sep  2 11:30:41 pfsense siproxd[26409]: plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40<br />
Sep  2 11:30:42 pfsense siproxd[26409]: sock.c:131 INFO:bound to port 5060<br />
Sep  2 11:30:42 pfsense siproxd[26409]: siproxd.c:349 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 started</p>
<h1><a class="anchor-offset" name="ps-ax-grep-siprox"></a>ps ax | grep siprox</h1>
<p dir="auto">26409  ??  SN    0:00.25 /usr/local/sbin/siproxd -c /usr/local/etc/siproxd.conf<br />
50356  0  S+    0:00.01 grep siprox</p>
<h1><a class="anchor-offset"></a></h1>
</blockquote>
]]></description><link>https://forum.netgate.com/post/294161</link><guid isPermaLink="true">https://forum.netgate.com/post/294161</guid><dc:creator><![CDATA[wallabybob]]></dc:creator><pubDate>Fri, 02 Sep 2011 02:08:26 GMT</pubDate></item></channel></rss>