Starting the FOP2 Process - Error

[arainero]

Hello,

I had FOP2 setup on my clients PBX for over a month with no problems. My client notified me the other day that they can't log into FOP2. I tried to restart FOP2 and I was given this error message:

root@pbx:~ $ service fop2 restart
Shutting down Flash Operator Panel 2:                      [FAILED]
Starting Flash Operator Panel 2: XSLoader.pm did not return a true value at -e line 344.
                                                           [FAILED]

Do you know what is causing this and how to correct it? My client does not have root access so I know they didn't change anything.

Thanks,

-Alonzo

[nicolas]

Hi,

Try removing the /tmp/par-root directory and try starting fop2 again:

rm -rf /tmp/par-root
service fop2 start

[arainero]

That seems to let FOP2 start now. However, when I try to do:

root@pbx:~ $ service fop2 restart
Shutting down Flash Operator Panel 2:                      [FAILED]
Starting Flash Operator Panel 2:                           [  OK  ]

Shutting down FOP2 now fails. Also, when I try to log into FOP2 when it is running I am stuck at "Connecting to server, attempt number : 'X' "

[nicolas]

Perhaps you cannot stop it becuase it is not running, and perhaps it is not running because when you start it FOP1 is already running binding to port 4445 and then makes fop2 shut down.

Try this:

netstat -lnp | grep 444

What is the output?

[arainero]

root@pbx:~ $ netstat -lnp | grep 444 tcp        0      0 0.0.0.0:4445                0.0.0.0:*                   LISTEN 2085/perl

[nicolas]

As I have guessed, you have FOP1 running. You must stop it in order to let FOP2 run. To stop it run

amportal stop_fop

To disable it, edit /etc/amportal.conf and set

FOPRUN=false

Also, be sure you do not have a line like amportal start_fop in /etc/rc.d/rc.local, if you do, remove it.

After stopping FOP1 you will be able to start FOP2 normally:

service fop2 start

And check after 10 seconds or so that it is still running

pgrep fop2

Best regards,

[arainero]

I had the FOP framework disabled in Module Admin. I thought that would stop FOP from running. I guess I was wrong. I don't know why everything worked as of recently? Do you have any idea why that may be so?

Thanks for the help!

[nicolas]

Perhaps something was updated via yum re-enabling FOP1, and upon the next reboot, FOP1 won the race by being started first.

[arainero]

Hmm, this is odd. I made the change to amportal.conf as you suggest and when I do a 'amportal restart' I see that FOP is started up again and causes problems with FOP2.

Is there another way to disable FOP so when the server is restarted or the amportal restart command is issued there wont be a problem?

[nicolas]

I have never seen the problems you are having. The drastic way is to edit /var/www/html/panel/op_server.pl and put on line 2:

exit;

Do the same to this file:

/var/www/html/panel/safe_opserver

Be sure to modify the correct amportal.conf file or search for other FOP parameters there might be. Anyways, the above change will just exit

[arainero]

The reason why that kept happening is because the amportal.conf file was be regenerated. If I made changes directly to amportal.conf they would be discarded the next time the file was recreated. I believe I solved my problem by uninstalling FOP (not disabling) from Module Admin and rebooting the server. I did a fop2 restart and everything seems to be working now.