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 Stopped after restart Elastix server

Fop2 Stopped after restart Elastix server

Scheduled Pinned Locked Moved Support
5 Posts 3 Posters 112 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.
  • S
    S
    specomm
    wrote on last edited by
    #1

    Dear ,

    Every Time Server restarted FOP2 dosnot work automatically like before ...

    I have to start it manually & (pgrep fop2 )..

    Kindly help how we can make it autmatically..

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

      Run this:

      chkconfig --list | grep fop2

      Do you see output? Does it say in the output "3:on" ? If so, fop2 is configured to start at boot. If not, you might need to add the service.

      chkconfig --add fop2

      Best regards,

      1 Reply Last reply
      0
      • S
        S
        specomm
        wrote on last edited by
        #3

        After Checking 3 is on ..

        What to do ?

        1 Reply Last reply
        0
        • A
          A
          AlexRS
          wrote on last edited by
          #4

          Sorry for me, Im not @admin, but fop2 doesnt started after restart server or restart elastix? Which OS do you use? Did you try 'service fop2 status'? Or debud fop2 (add -X 511 and 'log dir' key for fop2)? It was written there how to debug fop2. I havnt fop2 server now to give you direct way, try to search here.
          Sorry for my English(

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

            Perhaps you have the old FOP1 starting and taking the tcp/4445 port... so FOP2 is unable to start because of it.

            After a restart, try this command:

            netstat -lnp | grep 4445

            If you see a line of output with the process name "perl", it means you have FOP1 enabled. In that case you must disable it or change its port:

            http://members.asternic.biz/knowledge_base/how-to-disable-fop1-on-elastix-systems

            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