Menu

How to start save_opserver automatically?

Help
tomelaine
2007-02-23
2013-05-02
  • tomelaine

    tomelaine - 2007-02-23

    Hello,
    until now I didn't discover how to run the fop (flash-operator-panel) after booting the system.
    I tried to follow the instructions in the HowTo from sylverboss (look at the end of this page: http://www.howtoforge.com/voip_xorcom_rapid_asterisk_starshop_oss_p4 )
    but when I do this, the system halts on boottime and I only can repair it by booting in recovery - mode and delete the related script from /etc/init.d/.....

    There should be a way to initialize the fop a short time AFTER the complete system booted up.

    Thanks for help
    Thomas

     
    • RazaMetaL

      RazaMetaL - 2007-02-25

      You need to add a script at the init time.

      If you are using debian you can make it with:

      cd /etc/init.d
      vi fop

      Edit fop to have the following line (replace the location of op_server.pl with your location):

      /var/www/starshop-oss/op_server.pl

      Finally type at the console:

      update-rc.d fop defaults

      Hope this help, it works for me.

       
    • RazaMetaL

      RazaMetaL - 2007-02-25

      I forgot,

      chmod a+x /etc/init.d/fop

       
    • tomelaine

      tomelaine - 2007-02-27

      Hello,
      the precedure discribed above is nearly the same as in the mentioned HowTo. Anyway I tried but made the same experience:
      The system halts at boottime.....repairing only with recovery console...
      so this doen't wor for me. I don't know why.. Anybody hava an idea?

      thanks
      thomas

       
    • Sylver BOSS

      Sylver BOSS - 2007-04-10

      Hi

      If you experience such issues at boot time, you may try the following after recovering the system :

      update-rc.d -f fop-starshop remove

      I will update the howto, but in short you have 2 FOP running at the same time - i would suggest that you change the port of the FOP instance running from the starshop folder.

      open op_server.cfg, locate line 27, change listen_port=4445 to listen_port=4446

      after reboot, you should have everything ok.

      AB.

       

Log in to post a comment.

MongoDB Logo MongoDB