FOP2 2.30 Beta

[sbasan]

Hello,

Just upgraded to the new fop server via the management GUI.
Can't login any more.
fop2 log show all logins as FAILED LOGIN (non existant user).
/autoconfig-users.sh show correct users and passwords but using same credentials fail.

Any idea?

[nicolas]

If you use the users listed in the output from autoconfig-users.sh and it does not work, either your fop2.cfg is not using that script as a base for configuration or has some other conflicting config entries, or perhaps FOP2 just needs to be reloaded.

Best regards,

[sbasan]

It using that script (it's exactly as it was before the upgrade).
Notice something else, when pressing submit changes and not pressing the reload I can login but see no buttons.
When press the reload after the submit changes I can't login.

As stated before, the fop server was upgraded from the management GUI alone.
Verify all configuration files and they as they were before.

[nicolas]

You upgraded only the FOP2 Manager, not the fop2 server. Anyways, a manager upgrade should not leave you with no service. Please try restarting the fop2 service from the command line.. did you try that?

service fop2 restart

Best regards,

[sbasan]

First thing I've done.
There's no one online to take a look?

[sbasan]

It's a production server so all users can't access the FOP.
Don't know what cause this but every upgrade I have some issues and/or changes need to be done in a code related to the upgrade.

[nicolas]

Are you using custom function for the manager due to multi tenant? You should avoid upgrading if that is the case. I am online if you want to chat.

[nicolas]

I am online at the live help now.

[sbasan]

Solved in a flash by Nicolas.
I'm sure he can give a few words for other future users with same symptoms.

[nicolas]

Ok.. problem was due to the usage of a multi tenant system with FOP2 version 2.30.00 (old). The latest FOP2 Manager allows the selection of individual tenants to enable the service, so you can select which tenants will have access to the FOP2 service. That way you can use the standard license with no extra costs to give service for up to 5 tenants. sbasan had much more than 5 tenants, but not an extended license, and the Tenant selection in the newer FOP2 Manager works only with the updated autoconfiguration scripts in more recent FOP2 versions. By using an older FOP2 version, the previous autoconfiguration scripts just printed out all tenants, not only the selected ones from the FOP2 Manager, and reached the 5 tenant limit making some tenants unavailable.

So, if you use an older FOP2 with a multi tenant system and plan to use the tenant selection via the FOP2 Manager, then go ahead and upgrade everything: fop2 and the fop2 manager. If you upgrade only the fop2 manager you have the change of having features that won't work with the server, like this tenant selection.

In this particular case, updating just autoconfig-users.sh in his installation with the latest version fixed the issue.