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. PIAF Reload Warning

PIAF Reload Warning

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 149 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.
  • L
    L
    loonsailor
    wrote on last edited by
    #1

    I've installed FOP2 and the admin module in my PIAF system. It works great, except that whenever I do a freepbx reload (after changing something) I get the following warning message:

    Error Could not reload FOP server
    
    Could not reload the FOP operator panel server using killall -HUP op_server.pl. Configuration changes may not be reflected in the panel display.
    Added 19 hours ago
    (freepbx.reload_fop)
    

    Looks like it's still trying to reload fop, even though I've moved on to fop2. It looks like fop2 is not being reloaded (the PID remains the same after a reload), though I haven't seen that causing any trouble.

    Have I missed something in the installation? How should I clean this up?

    Thanks.

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

      FOP2 is a standalone application, it has its own init scripts and it does not depend on FreePBX or any other external scripts.

      The error you see is for FOP(1), not sure what you did to disable (or not) FOP1, the best way is to set FOPRUN=false in /etc/amportal.conf , that should prevent the amportal scripts to try to start/restart/reload FOP(1) and prevent that error from showing. But that is a freepbx issue, not a fop2 issue.

      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