JOC Cockpit - Troubleshooting

Installation Errors

Installer raises error "Validating data for panel jetty was not successful"

I tried to install JOC Cockpit, but got an error as below:

[scheduler@jos11rc2 joc.1.11.0-RC2]$ ./setup.sh -u joc_install.xml
java -Dizpack.mode=privileged -jar "./joc.1.11.0-RC2.jar" joc_install.xml

[ Starting automated installation ]
numOfPrevInstallations=0
com.izforge.izpack.installer.InstallerException: Validating data for panel jetty was not successful
com.izforge.izpack.installer.InstallerException: Validating data for panel jetty was not successful
at com.izforge.izpack.installer.AutomatedInstaller.validatePanel(Unknown Source)
at com.izforge.izpack.installer.AutomatedInstaller.installPanel(Unknown Source)
at com.izforge.izpack.installer.AutomatedInstaller.doInstall(Unknown Source)
at com.izforge.izpack.installer.Installer.main(Unknown Source) [
Automated installation FAILED! ]

By using the -u switch the user requested the installer not to switch to the root account in order to acquire privileges that allow to create folders. At the same time the user scheduler does not have the permissions to create a folder in the /opt/sos-berlin.com directory.

Admittedly the error message that is presented by IZPack installer is confusing, however, missing permissions are the cause for this error.

Use ./setup.sh joc_install.xml without the -u switch to install JOC Cockpit with correct permissions.

Operations Errors

Database Connection to MySQL unavailable after idle timeout

If a MySQL DBMS is being used by the JobScheduler, then the MySQL wait_timeout that rules the max. lifetime of idle connections should be checked and if necessary modified. 

• The default wait_timeout for MySQL is relatively short and the JOC Cockpit does not have a mechanism for keeping the connection open over longer periods of time such as overnight. 
• See the following article for instructions about how to change the MySQL DBMS timeout variable:
  • Database Connections to MySQL get lost
• If the DBMS wait_timeout is too short users will get an "Unauthorized to access JOC Cockpit" message together with a JOC-407 error message after submitting their credentials. However, restarting the JOC Cockpit web service / daemon will create a new database connection and allow authorized users to log in again.