Andreas

Hi Can Dinh, what we find from jetty.log are missing lines of log output that prove that the service is started. At the same time we find joc.log reporting that it is busy cleaning up log files. Please, restart the JOC Cockpit container 1-2 times. Then check the number of log files in the JOC Cockpit's logs volume. Could be that you were running the container for a longer time and that cleanup of old log files now exceeds the 60s timeout for startup of JOC Cockpit. Best regards Andreas

Hi Lee, did you mean to say when running the jetty.sh file? Please check JOC Cockpit's log files in the js7-joc-primary-logs volume. The jetty.log file and joc.log file should indicate why the PID file could not be written (missing volume, missing permissions or other). Best regards Andreas

Hi Gregory, you are in the driver seat for both, the configuration of OIDC in the Keycloak Server and in JS7. You did not provide information about what you configured in Keycloak, but express frustration and blame the JS7 OIDC Client. This is not the perfect approach to request assistance. Did you read the log output of JS7? The account that was used to login was in fact authenticated with the LDAP UTB Identity Service,. However, for this service no roles have been configured in JS7: "Account has...

Hi Raj, for integration with Nagios please look up the https://kb.sos-berlin.com/display/JS7/JS7+-+Checks+with+System+Monitors node in the documentation. You will find scripts for download to perform active checks. For passive checks the https://kb.sos-berlin.com/display/JS7/JS7+-+Notifications can be used to send alerts by mail and to execute the Nagios command line client and send alerts from the Nagios Server. Best regards Andreas

Hi, as a redirect URL you can assign the JOC Cockpit URL from https://<host>:<port> as you would use it from your browser.</port></host> For references see https://kb.sos-berlin.com/display/JS7/JS7+-+OIDC+Identity+Service Best regards Andreas

Hi, in step 3 of https://kb.sos-berlin.com/display/JS7/JS7+-+LDAP+Identity+Service+Configuration you will find explanations about usign LDAP Authorization. Choose the Identity Service Type "LDAP" instead of "LDAP-JOC. Most probably the memberOf Attribute is available in your AD. You can activate the setting in the Identity Service settings. Make the "group search base" the same as the "search base" used for Authentication. Consider to use the distinguished name of a group (not the group name) for...

Hi, thank you for the feedback. It looks that some tables are missing that are created by the JOC Cockpit installer. If you operate JOC Cockpit from a container then please run the ./install/joc_install_tables.sh|.cmd script to install tables, for details see https://kb.sos-berlin.com/display/JS7/JS7+-+JOC+Cockpit+Installation+for+Containers#JS7JOCCockpitInstallationforContainers-CreateDatabaseObjects If you operate JOC Cockpit on premises, then please check for errors in your ./logs/Install*.log...

Hi, which release of JobScheduler are you using? The error message reported from your initial post hints at use of branch 1.x. This branch is at its end-of-life since August 2023. The current branch of JobScheduler is 2.7, see https://kb.sos-berlin.com/display/JS7/JS7+-+Download. If this is a fist time installation then it will be preferable to follow installation instructions available from https://kb.sos-berlin.com/display/JS7/JS7+-+Installation. Before you start please check the https://kb.sos-berlin.com/display/JS7/JS7+-+System+Architecture....