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. Can't connect after updates

Can't connect after updates

Scheduled Pinned Locked Moved Support
4 Posts 2 Posters 63 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.
  • J
    J
    jdhatch
    wrote on last edited by
    #1

    I installed the following updates via Yum and now the FOP2 is not getting past "Connecting to server, attempt number : 1" ... 2 ... 3 ........

    Is anyone else seeing this? (I suspect that freePBX 2.8.0-2 is the culprit)

    Thanks, Jason

    Updating:
    RoundCubeMail noarch 0.3.1-9 elastix-beta 2.0 M

    Updating:
    elastix noarch 2.0.4-16 elastix-beta 10 M

    Updating:
    elastix-a2billing noarch 1.8.1-14beta elastix-beta 7.6 M

    Updating:
    elastix-firstboot noarch 2.0.4-6 elastix-beta 92 k

    Updating:
    elastix-pbx noarch 2.0.4-17 elastix-beta 4.5 M

    Updating:
    freePBX noarch 2.8.0-2 elastix-beta 26 M

    Updating:
    perl-Mail-IMAPClient noarch 3.28-1.el5 epel 229 k

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

      Hi,

      Disable FOP1, edit /etc/amportal.conf and be sure that FOPRUN is set to false.

      1 Reply Last reply
      0
      • J
        J
        jdhatch
        wrote on last edited by
        #3

        That did it.

        When I reboot the VM FOP2 is not auto starting. Anywhere I can fix that?

        Thanks, Jason

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

          fop2 init script should not be touched by any updates, you can see if its installed and enabled with the command:

          chkconfig --list | grep fop2
          

          If you see that runlevel 3 is on (3:on), then fop2 will start on boot. If it is not there you have to add it with the command

          chkconfig --add fop2
          

          and then be sure it is enabled

          chkconfig fop2 on
          

          Best regards,

          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