Manager: "FOP2 Server is not responding. Be sure the service is running!"

[xeper]

I've built a new FOP2 server in order to use 2.28 and because our current one was built in a hurry some time ago and just doesn't seem to work very well (mainly our fault, not FOP2's fault)

So I've got FOP2 installed and have configured the manager so that it can communicate with the database. I can log into the manager, but I see this message on most pages: "FOP2 Server is not responding. Be sure the service is running!"

FOP2 is running, I can log in using a user created with the manager, or a user created manually.

Because of this (I assume) I can't get the manager to upgrade from 1.0.3 to 1.0.4 and I can't install any plugins.

Could this perhaps be a file or folder permissions issue? Could it be because I'm running a trail license on this server? (I don't want to de-activate our production server as I test this new one)

Also, this may be related, it may not... when I log into FOP2, I don't see anything but the "Filter", "Dial", 'Availability' and 'Logout' items. The rest is white. Is there a PHP file I need to configure somewhere? (maybe PHP short tags issue? I think I'd seen that before with either FOP2 or another similar app.)

[nicolas]

Hi,

The fop2 manager is a php application. To check if fop2 is running it opens a socket connection to the fop2 port (tcp/4445). May installations prevent php from initiating socket connections, for security reasons. That will prevent the sevice check, it might also prevent retrieving/downloading new versions or plugins from the manager itself. Those restrictions might be done with selinux, or some php.ini settings like (allow_url_fopen).

Also, the manager directory must be ownded by the same user the web server (or php) is running as.

What you can see then is a result of the output from the scripts:

autoconfig-users.sh

and

autoconfig-buttons.sh

You should execute those scripts on the server command line (in /usr/local/fop2) and inspect the output. There might be some other error with database connections for example, that might prevent the scripts from generating proper configuration data.

Best regards,