FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Restart daemon after upgrade to version 3

Restart daemon after upgrade to version 3 31 Aug 2007 13:38 #23

  • P-M Lejon
  • P-M Lejon's Avatar Topic Author
  • Offline
  • 5th level - Black Belt
  • 5th level - Black Belt
  • Posts: 92
  • Karma: 3
  • Thank you received: 15
I've been testing XClient 3 for a few weeks and have found a different behavior than the previous versions.

Due to our users and their environment, using the 99.restartFW.sh isn't a valid option for us. Therefore we've been restarting the fwcld using an auto-activated script like this:
trigger_restart.sh -> runs the script restart_fwcld.sh
restart_fwcld.sh -> runs systemstarter restart fwcld

On version 2.x there's no problem, but on version 3 I get the following result:
Fri Aug 31 13:53:03 CEST 2007 [2964]: can't bind to port 20010 to listen for status messages... retryingFri Aug 31 13:53:05 CEST 2007 [2964]: can't bind to port 20010 to listen for status messages... retryingFri Aug 31 13:53:07 CEST 2007 [2964]: can't bind to port 20010 to listen for status messages... retryingFri Aug 31 13:53:09 CEST 2007 [2964]: can't bind to port 20010 to listen for status messages... retryingFri Aug 31 13:53:11 CEST 2007 [2964]: can't bind to port 20010 to listen for status messages... retryingFri Aug 31 13:53:13 CEST 2007 [2964]: can't bind to port 20010 to listen - exceeded retry count, aborting...Fri Aug 31 13:53:13 CEST 2007 [2964]: cannot start the status server, aborting...


If I on the other hand runs the systemstarter command directly from Terminal, there's no errors.

I've been testing a solution using a launchdaemon instead, but it seems like it's getting a bit too complicated that way.

Any suggestions/ideas/solutions?
P-M Lejon
System Administrator
BonnierNews
Sweden
  • Page:
  • 1