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. Problems after upgrade

Problems after upgrade

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

    Hi Nicolas,

    I have updated to latest fop2 version to try fixing Chrome's issues that were getting people crazy here. As I use port eth1, I went inside the Makefile and added the -i eth1 to the reactivate command and was able to install it. I have also ran the FreePBX script to update the buttons as instructed by README file.

    I checked the two config files that were before compared to the new ones and I saw no major changes and then I restarted the fop2 service to get things on the new version. This was the first surprise, the service doesn't start up anymore using init.d script and I couldn't find logs to see what is going on.

    I started then using '/usr/local/fop2/fop2_server -i eth1 -d' and it started ok but then when I visit the page and all my panel is gone with only a NO BUTTONS green box and even going to FreePBX and re-applying all settings won't work.

    Before I had couple complaining users. Now I have all users unable to work. Can you please help?

    Thanks.

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

      Hi,

      I think the problem was that fop2admin was not updated, right? I will update the README file..

      for other users, if you use fop2admin and there is an updated fop2 and updated fop2admin, you will need to update both.

      Best regards,

      1 Reply Last reply
      0
      • F
        F
        fagiani
        wrote on last edited by
        #3

        Thanks! How about the service startup with eth1 on init.d script issue?

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

          You can edit the options file in /etc/sysconfig/fop2 to add whatever parameters necessary, as any other service in a redhat/centos box. That way you do not have to modify the init script itself, and an upgrade will not break your custom parameters.

          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