Skip to content

Possible Solutions

Here, you find some problems which might occur with your installation and their solutions.

No Dashboard After Updating to 5.3.2

With PLOSSYS 5.3.2, the dashboard of PLOSSYS Administrator has been secured. In order that the user can see the dashboard, the dashbord area has to be specified in the ALLOWED_OIDC_CLIENTS key. For more information, refer to ALLOWED_OIDC_CLIENTS.

Wrong Order of the Log Messages

Make sure that the times are synchronous among all PLOSSYS 5 servers in your cluster.

Flickering Browser When Opening PLOSSYS Administrator

If you cannot open the user interface, PLOSSYS Administrator, and the browser is flickering, the reason could be be one of the following situations:

  • Check the configuration for the OIDC identity provider. Check if the AUTH_ISSUER_URL and the ID_PROVIDER_NAME environment variables are specified correctly. For more information, refer to Configure the PLOSSYS Administrator Environment.

  • The HTTP code 304 (Not Modified) is returned erroneously by the services. This is shown in the log messages. Then deactivate the ETag handling by setting USE_ETAG to N.

Loading Browser When Opening PLOSSYS Administrator

If Loading... is the only thing you get when opening the user interface, PLOSSYS Administrator, the reason could be the following situation:

  • You do not have the permission to do anything with PLOSSYS Administrator. In the OIDC identity provider, check if you have a role assigned that has permissions for PLOSSYS Administrator.

Authentication Error With PLOSSYS CLI

If the call of PLOSSYS CLI returns the Access denied, please specify valid authentication error message, the reason could be that the environment variables for the OIDC identity provider have been misconfigured.

  • Check the environment variables for the OIDC identity provider. Check if the AUTH_ISSUER_URL and the ID_PROVIDER_NAME environment variables are specified correctly. For more information, refer to Configure the PLOSSYS CLI Environment.

Export from easyPRIMA to PLOSSYS 5 Does Not Work

When updating to PLOSSYS 5.1.0 and using easyPRIMA as of version 1.3.1, the 20181204_perl_soap-lite_1.27_part.zip package has to be installed for easyPRIMA. Otherwise, the export from easyPRIMA to PLOSSYS 5 does not work and the 500 SSL negotiation failed error message is output to the logfile of easyPRIMA (edc.log).

Hint - stop the system

Before installing the 20181204_perl_soap-lite_1.27_part.zip package for easyPRIMA, stop the system and all Perl processes completely (sysstop -full). Otherwise, the Perl environment will break.

Back to top