updating plugin, can't restart service fop2

8 years ago

kelmore
4 Feb 2016

Each time I try to restart fop2 using stop or restart it fails. I've restarted the entire freepbx server and I get the same message.
[root@lion2 ~]# service fop2 stop
Shutting down Flash Operator Panel 2: [FAILED]
I'm using FOP2 Server Status: OK - Version: 2.30.04 with FreePBX 13.0.49
Anything I can check?
Thanks

Answered by admin
See post in context

I notice that the process name is missing the last letter (fop2_serve) instead of fop2_server, that might confuse the init script. You can edit /etc/rc.d/init.d/fop2 and replace
killproc fop2_server
with
killproc fop2_serve
admin
6 Feb 2016 Administrator

stop fails... it might be because FOP2 is not started? Did you try that?
service fop2 start
wait a while
service fop2 status
what does it say?
kelmore
8 Feb 2016

Everything seems to be running fine, except the Call History plugin which I have found a few posts about but haven't tackled yet. When I want to install a new licensed plugin, I do need to restart the service from the command line in this way to activate it, correct?
[root@XX ~]# service fop2 status
fop2_server dead but subsys locked
[root@XX ~]# service fop2 start
Starting Flash Operator Panel 2: [ OK ]
[root@XX ~]# service fop2 status
fop2_server dead but subsys locked
[root@XX ~]# service fop2 stop
Shutting down Flash Operator Panel 2: [FAILED]
kelmore
9 Feb 2016

Edited 8 years ago by admin

[root@lion2 ~]# /usr/local/fop2/fop2_server -X 1
Flash Operator Panel 2 - White Label Version
unable to initialize libusb: -99
EV: error in callback (ignoring): bind: Address already in use at script/fop2_server.pl line 14203.
127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: 1
127.0.0.1 <- Challenge: 181433702
127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: 2
127.0.0.1 <- Message: Authentication accepted
127.0.0.1 <- Event: FullyBooted
127.0.0.1 <- Privilege: system,all
127.0.0.1 <- Status: Fully Booted
127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: 3
127.0.0.1 <- Message: Mailbox Message Count
127.0.0.1 <- Mailbox: 6603@default
127.0.0.1 <- UrgMessages: 0
127.0.0.1 <- NewMessages: 0
127.0.0.1 <- OldMessages: 0
127.0.0.1 <- Event: VarSet
127.0.0.1 <- Privilege: dialplan,all
127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
127.0.0.1 <- ChannelState: 4
127.0.0.1 <- ChannelStateDesc: Ring
127.0.0.1 <- CallerIDNum: 0
127.0.0.1 <- CallerIDName: 0
127.0.0.1 <- ConnectedLineNum: 0
127.0.0.1 <- ConnectedLineName: 0
127.0.0.1 <- Language: en
127.0.0.1 <- AccountCode:
127.0.0.1 <- Context: timeconditions
127.0.0.1 <- Exten: 3
127.0.0.1 <- Priority: 4
127.0.0.1 <- Uniqueid: 1454976540.16105
127.0.0.1 <- Linkedid: 1454976540.16104
127.0.0.1 <- Variable: DB_RESULT
127.0.0.1 <- Value:
127.0.0.1 <- Event: Newexten
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
127.0.0.1 <- ChannelState: 4
127.0.0.1 <- ChannelStateDesc: Ring
127.0.0.1 <- CallerIDNum: 0
127.0.0.1 <- CallerIDName: 0
127.0.0.1 <- ConnectedLineNum: 0
127.0.0.1 <- ConnectedLineName: 0
127.0.0.1 <- Language: en
127.0.0.1 <- AccountCode:
127.0.0.1 <- Context: timeconditions
127.0.0.1 <- Exten: 3
127.0.0.1 <- Priority: 5
127.0.0.1 <- Uniqueid: 1454976540.16105
127.0.0.1 <- Linkedid: 1454976540.16104
127.0.0.1 <- Extension: 3
127.0.0.1 <- Application: ExecIf
127.0.0.1 <- AppData: 0?Set(DB(TC/3)=)
127.0.0.1 <- Event: Newexten
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
127.0.0.1 <- ChannelState: 4
127.0.0.1 <- ChannelStateDesc: Ring
127.0.0.1 <- CallerIDNum: 0
127.0.0.1 <- CallerIDName: 0
127.0.0.1 <- ConnectedLineNum: 0
127.0.0.1 <- ConnectedLineName: 0
127.0.0.1 <- Language: en
127.0.0.1 <- AccountCode:
127.0.0.1 <- Context: timeconditions
127.0.0.1 <- Exten: 3
127.0.0.1 <- Priority: 6
127.0.0.1 <- Uniqueid: 1454976540.16105
127.0.0.1 <- Linkedid: 1454976540.16104
127.0.0.1 <- Extension: 3
127.0.0.1 <- Application: Set
127.0.0.1 <- AppData: DEVICE_STATE(Custom:TC3)=INUSE
127.0.0.1 <- Event: VarSet
127.0.0.1 <- Privilege: dialplan,all
127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
127.0.0.1 <- ChannelState: 4
127.0.0.1 <- ChannelStateDesc: Ring
127.0.0.1 <- CallerIDNum: 0
127.0.0.1 <- CallerIDName: 0
127.0.0.1 <- ConnectedLineNum: 0
127.0.0.1 <- ConnectedLineName: 0
127.0.0.1 <- Language: en
127.0.0.1 <- AccountCode:
127.0.0.1 <- Context: timeconditions
127.0.0.1 <- Exten: 3
127.0.0.1 <- Priority: 6
127.0.0.1 <- Uniqueid: 1454976540.16105
127.0.0.1 <- Linkedid: 1454976540.16104
127.0.0.1 <- Variable: DB_RESULT
127.0.0.1 <- Value:
127.0.0.1 <- Event: Newexten
127.0.0.1 <- Privilege: call,all
127.0.0.1 <- Channel: Local/s@tc-maint-00001db3;2
127.0.0.1 <- ChannelState: 4
127.0.0.1 <- ChannelStateDesc: Ring
127.0.0.1 <- CallerIDNum: 0
127.0.0.1 <- CallerIDName: 0
127.0.0.1 <- ConnectedLineNum: 0
127.0.0.1 <- ConnectedLineName: 0
127.0.0.1 <- Language: en
127.0.0.1 <- AccountCode:
127.0.0.1 <- Context: timeconditions
127.0.0.1 <- Exten: 3
127.0.0.1 <- Priority: 7
127.0.0.1 <- Uniqueid: 1454976540.16105
127.0.0.1 <- Linkedid: 1454976540.16104
127.0.0.1 <- Extension: 3
127.0.0.1 <- Application: ExecIf
127.0.0.1 <- AppData: 0?Set(NOT_INUSE)
admin
9 Feb 2016 Administrator

netstat -lnp | grep 444
What do you see? If you see "perl" as using the socket, it is the old FOP1 that is taking the port and does not let FOP2 to start. You must disable FOP1 in that case, so FOP2 can run an keep running after it is started.
kelmore
9 Feb 2016

Last month I installed a FreePBX distro and then added FOP2, never used FOP1, unless it's bundled with FreePBX.
[root@XX ~]# netstat -lnp | grep 444
tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN 1520/fop2_serve
unix 2 [ ACC ] STREAM LISTENING 10598 1444/gam_server @/tmp/fam-root-
admin
10 Feb 2016 Administrator

So, you have fop2 running... then it seems your problem is only with the init script? That is super strange as the init script is used widely on centos based distributions like the FreePBX distro. Are you sure you are not starting FOP2 from any other script/place? How do you start FOP2 normally? Does it start at boot with no issue?
kelmore
10 Feb 2016

Yes, starts at boot with no issue, all automatically. I don't believe I made any odd changes to the init script.
admin
10 Feb 2016 Administrator

Are you running the service commands as root?
What is the output from:
service fop2 status
?
kelmore
10 Feb 2016

Here's what I just tried:
Please note most tasks should be handled through the GUI.
You can access the GUI by typing one of the above IPs in to your web browser.
For support please visit:
http://www.freepbx.org/support-and-professional-services
[root@lion2 ~]# service fop2 status
fop2_server is stopped
[root@lion2 ~]# service fop2 start
Starting Flash Operator Panel 2: [ OK ]
[root@lion2 ~]# service fop2 status
fop2_server dead but subsys locked
[root@lion2 ~]# ps aux | grep fop2
root 1520 0.0 7.8 309524 150680 ? Ss Feb04 6:38 /usr/local/fop2 /fop2_serve -d
root 4261 0.0 6.3 307804 121236 ? Ss Feb08 1:21 /usr/local/fop2 /fop2_serve -d
root 29325 0.3 5.4 307188 104020 ? Ss 10:14 0:00 /usr/local/fop2 /fop2_serve -d
root 31209 0.0 0.0 103248 872 pts/0 S+ 10:15 0:00 grep fop2
[root@lion2 ~]# service fop2 stop
Shutting down Flash Operator Panel 2: [FAILED]
[root@lion2 ~]# kill 29325
[root@lion2 ~]# ps aux | grep fop2
root 1520 0.0 7.8 309524 150680 ? Ss Feb04 6:38 /usr/local/fop2/fop2_serve -d
root 4261 0.0 6.3 307804 121236 ? Ss Feb08 1:21 /usr/local/fop2/fop2_serve -d
root 31258 0.0 0.0 103248 876 pts/0 S+ 10:16 0:00 grep fop2
[root@lion2 ~]# kill 4261
[root@lion2 ~]# kill 1520
[root@lion2 ~]# service fop2 start
Starting Flash Operator Panel 2: [ OK ]
[root@lion2 ~]# ps aux | grep fop2
root 656 0.0 0.0 103244 864 pts/0 R+ 10:17 0:00 grep fop2
root 31282 3.4 5.3 307188 103796 ? Ss 10:17 0:00 /usr/local/fop2/fop2_serve -d
[root@lion2 ~]# service fop2 restart
Shutting down Flash Operator Panel 2: [FAILED]
Starting Flash Operator Panel 2: [ OK ]
[root@lion2 ~]# ps aux | grep fop2
root 896 2.4 5.4 308256 104176 ? Ss 10:17 0:00 /usr/local/fop2/fop2_serve -d
root 2797 0.0 0.0 103244 864 pts/0 S+ 10:17 0:00 grep fop2
root 31282 3.2 5.6 307188 108932 ? Ss 10:17 0:01 /usr/local/fop2/fop2_serve -d
[root@lion2 ~]#
admin
10 Feb 2016 Administrator Answer

I notice that the process name is missing the last letter (fop2_serve) instead of fop2_server, that might confuse the init script. You can edit /etc/rc.d/init.d/fop2 and replace
killproc fop2_server
with
killproc fop2_serve
kelmore
11 Feb 2016

This seemed to do the trick! Thanks!!!!

updating plugin, can't restart service fop2

Answered by admin