Page History

Table of Contents

Installation Errors

...

Observation

A user tries to install JOC Cockpit, but gets 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! ]

Explanation

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.

JOC Cockpit Windows Service does not start

Observation

A user tries to install the JOC Cockpit and gets an error when tryng to start the Windows service.

+------------------------------------------------------------------------------------------------------------------------

| Start Jetty service for JOC (JobScheduler Operations Center)
+------------------------------------------------------------------------------------------------------------------------
Le service SOS JOC (JobScheduler Operations Center) démarre.
Le service SOS JOC (JobScheduler Operations Center) n'a pas pu êté lancé

Une erreur spécifique … un service s'est produit: 5.

Vous obtiendrez une aide supplémentaire en entrant NET HELPMSG 3547.

The log file joc.YYYY-MM-DD.log shows the following information:

[2016-12-26 14:08:11] [info] [10424] Commons Daemon procrun (1.0.15.0 32-bit) started
[2016-12-26 14:08:11] [info] [10424] Service sos_joc name SOS JOC (JobScheduler Operations Center)
[2016-12-26 14:08:12] [info] [10424] Service 'sos_joc' installed
[2016-12-26 14:08:12] [info] [10424] Commons Daemon procrun finished
[2016-12-26 14:08:12] [info] [8708] Commons Daemon procrun (1.0.15.0 32-bit) started
[2016-12-26 14:08:12] [info] [8708] Running 'sos_joc' Service ...
[2016-12-26 14:08:12] [info] [3988] Starting service ...
[2016-12-26 14:08:13] [error] [3988] Failed to execute process
[2016-12-26 14:08:13] [error] [3988] Invalid directory name.
[2016-12-26 14:08:13] [error] [3988] ServiceStart returned 5
[2016-12-26 14:08:13] [error] [3988] Invalid directory name.
[2016-12-26 14:08:13] [info] [8708] Run service finished.

Explanation

The Windows Service tries to locate the Java Virtual Machine from a non-existing directory. This happens due to the fact that the JVM is not found from the PATH - as e.g. the installer - but from the Windows Registry or JAVA_HOME environment variable. If the JAVA_HOME environment variable points to a non-existent directory then the above error "Invalid directory name" is raised and the Windows Service will not tart.

Operations Errors

...

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.