Over 5 year old critical error?


(Robert Wooden) #1

This morning on “Dashboard” I clicked “show all” in the “System Overview” and this over five year old error appeared:

Could not reload the FOP operator panel server using killall -HUP op_server.pl. Configuration changes may not be reflected in the panel display. If the FOP module was just installed you may have to retart Asterisk with the “amportal restart” command for the FOP server to run.

Below the error it says “5 years, 9 months, 1 week, 3 days, 56 minutes, 51 seconds, ago

Could this just be “hanging around” since then?

What can I do about it?

I cannot find any evidence that FOP is NOT running. Odd?

One of the 5 year old posts I found suggested doing a “fwconsole restart”, which I did but, error is still present.

Suggestions?


(Dave Burgess) #2

Use the X option to delete it.


#3

Yes, it means you had the error at that time and had yet to acknowledge it.