Some applications started multiple times at boot



  • I'm running 2.0-RC1 (i386)
    built on Mon Mar 7 12:03:17 EST 2011

    The system log shows two attempts to start siproxd; the second failing apparently because siproxd was already running:

    clog /var/log/system.log | grep siproxd

    Mar 10 17:10:12 pfsense siproxd[57223]: siproxd.c:247 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 starting up
    Mar 10 17:10:12 pfsense siproxd[58384]: siproxd.c:295 INFO:daemonized, pid=58384
    Mar 10 17:10:12 pfsense siproxd[58384]: plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40
    Mar 10 17:10:12 pfsense siproxd[58384]: sock.c:131 INFO:bound to port 5060
    Mar 10 17:10:12 pfsense siproxd[58384]: register.c:119 WARNING:registration file corrupt, starting with empty table
    Mar 10 17:10:12 pfsense siproxd[58384]: siproxd.c:349 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 started
    Mar 10 17:10:15 pfsense siproxd[10308]: siproxd.c:247 INFO:siproxd-0.8.0-5472 i386-portbld-freebsd8.1 starting up
    Mar 10 17:10:15 pfsense siproxd[11219]: siproxd.c:295 INFO:daemonized, pid=11219
    Mar 10 17:10:15 pfsense siproxd[11219]: plugins.c:112 INFO:Plugin 'plugin_logcall' [Logs calls to syslog] loaded with success, exemask=0x40
    Mar 10 17:10:15 pfsense siproxd[11219]: sock.c:543 ERROR:bind failed: Address already in use
    Mar 10 17:10:15 pfsense siproxd[11219]: siproxd.c:337 ERROR:unable to bind to SIP listening socket - aborting


  • Rebel Alliance Developer Netgate

    Was that at boot time? Or when you saved the siproxd settings?

    It's always been an issue that certain packages try to start twice at boot time, but it's usually harmless.



  • @jimp:

    Was that at boot time? Or when you saved the siproxd settings?

    Boot time.


  • Rebel Alliance Developer Netgate

    Did it actually affect the service in some way? Or was it running OK? It may be harmless.



  • @jimp:

    Did it actually affect the service in some way? Or was it running OK? It may be harmless.

    I haven't tested any calls, so as best I can tell, the only harm is wasting CPU cycles at boot time, which can mount up if replicated across a number of applications or packages. For example, it appears bandwidthd is also started twice at boot time:

    clog /var/log/system.log | grep -i bandwidthd

    Mar 10 17:10:07 pfsense bandwidthd: Monitoring subnet 192.168.211.128 with netmask 192.168.211.128
    Mar 10 17:10:07 pfsense bandwidthd: Syntax Error "syntax error" on line 17
    Mar 10 17:10:07 pfsense bandwidthd: Syntax Error "syntax error" on line 17
    Mar 10 17:10:15 pfsense bandwidthd: Monitoring subnet 192.168.211.128 with netmask 192.168.211.128
    Mar 10 17:10:15 pfsense bandwidthd: Syntax Error "syntax error" on line 17
    Mar 10 17:10:15 pfsense bandwidthd: Syntax Error "syntax error" on line 17

    I'll change the topic and start another topic for the "syntax error".


  • Rebel Alliance Developer Netgate

    The actual packages themselves need to check if they are being run at bootup and account for that.

    http://redmine.pfsense.org/issues/53


Log in to reply