Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. FOP2 suddenly stopped working

FOP2 suddenly stopped working

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 36 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    R
    rob69
    wrote on last edited by
    #1

    Hi FOP2 has been working great for months then today suddenly it stops, ran yum updates and freepbx updates (Using Elastix 2)

    Getting this:
    [root@elastixv2 fop2]# /usr/local/fop2/fop2_server --test
    /usr/local/fop2/autoconfig-buttons-freepbx.sh: line 15: [: too many arguments
    Connection to manager OK!

    but its saying that its connection to the manager is OK

    and this

    [root@elastixv2 fop2]# netstat -lnp | grep 444
    tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN 3044/perl

    which i fear is the problem as 4445 should be fop2 not perl but if that is the case how did this change happen and how can i correct it? this happened before any updates were done too

    Thanks
    Robert

    1 Reply Last reply
    0
    • N
      N
      nicolas
      wrote on last edited by
      #2

      The update re-enabled or changed fop1 port back to 4445, preventing FOP2 from starting. You can disable fop1 by setting

      FOPRUN=false
      

      in /etc/amportal.conf . So it does not start on the next reboot. Then stop the current running fop1:

      /usr/sbin/amportal stop_fop
      

      and start fop2

      service fop2 start
      
      1 Reply Last reply
      0
      • R
        R
        rob69
        wrote on last edited by
        #3

        Thanks,

        I had already managed to set the FOPRUN=false but had not stopped it afterwards!!!

        So that fixed the issue

        😄

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups