Troubleshooting - Revision history

Craig at 21:31, 17 May 2023

2023-05-17T21:31:05Z

← Older revision		Revision as of 21:31, 17 May 2023
Line 65:		Line 65:
	You need to let Winstone, the servlet container that is used for the Quick Start method, know about the JDK. It needs a JDK to be able to compile the JSPS. The installer tries to find one to configure Winstone properly, but isn't always able to do so.		You need to let Winstone, the servlet container that is used for the Quick Start method, know about the JDK. It needs a JDK to be able to compile the JSPS. The installer tries to find one to configure Winstone properly, but isn't always able to do so.

	Usually, a global environment variable called <code>JAVA_HOME</code> will do the trick - see [~~http~~://docs.oracle.com/cd/E19182-01/820-7851/inst_cli_jdk_javahome_t/ Setting JAVA_HOME].		Usually, a global environment variable called <code>JAVA_HOME</code> will do the trick - see [https://docs.oracle.com/cd/E19182-01/820-7851/inst_cli_jdk_javahome_t/ Setting JAVA_HOME].

	Another option is to use a directive that points to your JDK only for winstone. You can either add the <code>--javaHome=...</code> directive in the <code>webObsidian.sh</code> or </code>webObsidian.bat</code> command following the last of other directives (--config=%file% or --config=$file). Or you can add the <code>--javaHome=...</code> directive the <code>winstone.properties</code> and/or <code>winstoneAdminOnly.properties</code> file(s).		Another option is to use a directive that points to your JDK only for winstone. You can either add the <code>--javaHome=...</code> directive in the <code>webObsidian.sh</code> or </code>webObsidian.bat</code> command following the last of other directives (--config=%file% or --config=$file). Or you can add the <code>--javaHome=...</code> directive the <code>winstone.properties</code> and/or <code>winstoneAdminOnly.properties</code> file(s).
Line 110:		Line 110:
	</pre>		</pre>

	If you encounter an error like the one above and are using MySQL (particularly version 5.0), there is a chance you are hitting a [~~http~~://bugs.mysql.com/bug.php?id=20932 MySQL bug]. This problem seems to occur mainly on new Obsidian instances, so once corrected, there is a good chance you will never see the issue again.		If you encounter an error like the one above and are using MySQL (particularly version 5.0), there is a chance you are hitting a [https://bugs.mysql.com/bug.php?id=20932 MySQL bug]. This problem seems to occur mainly on new Obsidian instances, so once corrected, there is a good chance you will never see the issue again.

	Two approaches have been used with success:		Two approaches have been used with success:
	# In MySQL's my.cnf file, temporarily change (or add) the following line, and then restart mysqld: <pre>innodb_lock_wait_timeout = 600</pre><br />This appears to only be an issue when Obsidian first gets running, and it can typically be reverted after a while.<br /><br />		# In MySQL's my.cnf file, temporarily change (or add) the following line, and then restart mysqld: <pre>innodb_lock_wait_timeout = 600</pre><br />This appears to only be an issue when Obsidian first gets running, and it can typically be reverted after a while.<br /><br />
	# At a MySQL prompt, run the following command: <pre>optimize table semaphore;</pre><br /> If this resolves your issue, we suggest optimizing all your tables using [~~http~~://dev.mysql.com/doc/refman/5.0/en/mysqlcheck.html mysqlcheck].		# At a MySQL prompt, run the following command: <pre>optimize table semaphore;</pre><br /> If this resolves your issue, we suggest optimizing all your tables using [https://dev.mysql.com/doc/refman/8.0/en/mysqlcheck.html mysqlcheck].

	= I am running Obsidian on Oracle but I'm seeing the error "ORA-00942: table or view does not exist" =		= I am running Obsidian on Oracle but I'm seeing the error "ORA-00942: table or view does not exist" =

Craig: /* When I try to enter my job's class name in the UI, I get the message "Could not locate the class [MyJob]". What's the problem? */

2023-05-17T21:29:32Z

When I try to enter my job's class name in the UI, I get the message "Could not locate the class [MyJob]". What's the problem?

← Older revision		Revision as of 21:29, 17 May 2023
Line 16:		Line 16:

	# If you are running a combined scheduler and web application, the JAR file containing the job is not on the classpath of the servlet container (Tomcat/Jetty/etc). JARs are placed under <code>WEB-INF/lib</code> in the web application.		# If you are running a combined scheduler and web application, the JAR file containing the job is not on the classpath of the servlet container (Tomcat/Jetty/etc). JARs are placed under <code>WEB-INF/lib</code> in the web application.
	# If you are running a standalone web application with no scheduler running, your other Obsidian instance which includes the scheduler has not had its [[Implementing_Jobs#Classpath_Scanning\|Classpath Scanning]] configuration set, or has not been started with the appropriate classpath required for it to save the job metadata the web application uses to validate jobs. See [[Implementing_Jobs#~~Classpath_for_Building_and_Deploying~~\|Classpath for Building ~~and Deploying~~]].		# If you are running a standalone web application with no scheduler running, your other Obsidian instance which includes the scheduler has not had its [[Implementing_Jobs#Classpath_Scanning\|Classpath Scanning]] configuration set, or has not been started with the appropriate classpath required for it to save the job metadata the web application uses to validate jobs. See [[Implementing_Jobs#Classpath_for_Building\|Classpath for Building]].
	# Obsidian has not been restarted after updating the classpath with a new JAR.		# Obsidian has not been restarted after updating the classpath with a new JAR.
	# Job does not implement <code>com.carfey.ops.job.SchedulableJob</code>.		# Job does not implement <code>com.carfey.ops.job.SchedulableJob</code>.

Craig: /* Why isn't my job showing up? */

2023-05-17T21:28:20Z

Why isn't my job showing up?

← Older revision		Revision as of 21:28, 17 May 2023
Line 27:		Line 27:
	= Why isn't my job showing up? =		= Why isn't my job showing up? =

	Out of the box, Obsidian will display any previously scheduled jobs and Obsidian's bundled jobs. You can type in your class name as described in [[Admin_Jobs#~~Job_Nickname_and_Class~~\|Admin Jobs]].		Out of the box, Obsidian will display any previously scheduled jobs and Obsidian's bundled jobs. You can type in your class name as described in [[Admin_Jobs#Nickname.2C_Class_and_Folder\|Admin Jobs]].

	If you are using Obsidian's [[Implementing_Jobs#Classpath_Scanning\|classpath scanning]] and don't see your job pre-populated, make sure you set appropriate the "packageScannerPrefix" value in the [[Admin Scheduler Settings\|scheduler settings]] screen, and ensure the user account running Obsidian has read privileges to the <code>WEB-INF</code> directory of Obsidian's deployment directory.		If you are using Obsidian's [[Implementing_Jobs#Classpath_Scanning\|classpath scanning]] and don't see your job pre-populated, make sure you set appropriate the "packageScannerPrefix" value in the [[Admin Scheduler Settings\|scheduler settings]] screen, and ensure the user account running Obsidian has read privileges to the <code>WEB-INF</code> directory of Obsidian's deployment directory.

Carfey: /* My job isn't running when expected. Why not? */

2016-07-01T17:47:06Z

My job isn't running when expected. Why not?

← Older revision		Revision as of 17:47, 1 July 2016
Line 5:		Line 5:
	This may be a case where your schedule isn't correct for the execution times you want, or the job may be failing.		This may be a case where your schedule isn't correct for the execution times you want, or the job may be failing.

	# First, you should confirm that your job isn't actually running. You can check for the [[~~Admin_Job_History~~\|Job ~~History~~]] screen to see if there are any scheduled or completed jobs. You may see that a job failed; to see details on it, simply expand the row to see an exception stack trace and the option to resubmit the job. If your job is failing, you may wish to set up [[Admin_Notifications\|notifications]] so that you know of future problems quickly.		# First, you should confirm that your job isn't actually running. You can check for the [[Admin_Job_Activity\|Job Activity]] screen to see if there are any scheduled or completed jobs. You may see that a job failed; to see details on it, simply expand the row to see an exception stack trace and the option to resubmit the job. If your job is failing, you may wish to set up [[Admin_Notifications\|notifications]] so that you know of future problems quickly.
	# If you don't see any jobs listed there, you can confirm what execution times your schedule will result in. To see what times your job will execute, check the [[Admin_Job_Run_Time_Preview\|Run Time Preview]] screen.		# If you don't see any jobs listed there, you can confirm what execution times your schedule will result in. To see what times your job will execute, check the [[Admin_Job_Run_Time_Preview\|Run Time Preview]] screen.
	# Next, you can check for any general server health issues. To do so, first you can search the [[Admin_Logs\|Logs]] screen for any errors or warnings that may indicate a server issue.		# Next, you can check for any general server health issues. To do so, first you can search the [[Admin_Logs\|Logs]] screen for any errors or warnings that may indicate a server issue.

Carfey at 17:46, 1 July 2016

2016-07-01T17:46:50Z

← Older revision		Revision as of 17:46, 1 July 2016
Line 95:		Line 95:
	</pre></li>		</pre></li>
	<li> Obsidian was not shut down properly, and was started in another location before the old license lease expired. Obsidian works by leasing a license for a specified amount of time, and refreshing it before it expires. When shut down gracefully, Obsidian will release this lease and make it available to any other node using the same key. If it is shut down non-gracefully, the lease will stay active, and only the same server will be able to refresh that same license before it expires. By default, a lease lasts an hour or two to gracefully handle sporadic connectivity.</li>		<li> Obsidian was not shut down properly, and was started in another location before the old license lease expired. Obsidian works by leasing a license for a specified amount of time, and refreshing it before it expires. When shut down gracefully, Obsidian will release this lease and make it available to any other node using the same key. If it is shut down non-gracefully, the lease will stay active, and only the same server will be able to refresh that same license before it expires. By default, a lease lasts an hour or two to gracefully handle sporadic connectivity.</li>
	<li> You are using the wrong license key. Check the license key set in the [[Admin ~~System~~\|~~System~~]] ~~tab~~ of the web application. This is the value Obsidian is using to verify its licensing status. Note that the value in your properties file is only used to initialize the Obsidian database, so once it is set, you must update the value in the [[Admin ~~System~~\|~~System~~]] ~~tab~~.</li>		<li> You are using the wrong license key. Check the license key set in the [[Admin Scheduler Settings\|scheduler settings]] screen of the web application. This is the value Obsidian is using to verify its licensing status. Note that the value in your properties file is only used to initialize the Obsidian database, so once it is set, you must update the value in the [[Admin Scheduler Settings\|scheduler settings]] screen.</li>
	<li> You may have runaway background Obsidian processes which are using a license that you are unaware of.</li>		<li> You may have runaway background Obsidian processes which are using a license that you are unaware of.</li>
	</ol>		</ol>

Carfey: /* Why isn't my job showing up? */

2016-07-01T17:46:33Z

Why isn't my job showing up?

← Older revision		Revision as of 17:46, 1 July 2016
Line 29:		Line 29:
	Out of the box, Obsidian will display any previously scheduled jobs and Obsidian's bundled jobs. You can type in your class name as described in [[Admin_Jobs#Job_Nickname_and_Class\|Admin Jobs]].		Out of the box, Obsidian will display any previously scheduled jobs and Obsidian's bundled jobs. You can type in your class name as described in [[Admin_Jobs#Job_Nickname_and_Class\|Admin Jobs]].

	If you are using Obsidian's [[Implementing_Jobs#Classpath_Scanning\|classpath scanning]] and don't see your job pre-populated, make sure you set appropriate the "packageScannerPrefix" value in the [[Admin ~~System~~\|~~System~~]] ~~tab~~, and ensure the user account running Obsidian has read privileges to the <code>WEB-INF</code> directory of Obsidian's deployment directory.		If you are using Obsidian's [[Implementing_Jobs#Classpath_Scanning\|classpath scanning]] and don't see your job pre-populated, make sure you set appropriate the "packageScannerPrefix" value in the [[Admin Scheduler Settings\|scheduler settings]] screen, and ensure the user account running Obsidian has read privileges to the <code>WEB-INF</code> directory of Obsidian's deployment directory.

	In addition, some users have had issues with classpath scanning not locating jobs in JARs created by tools which don't include directory entries, such as Eclipse. Scanning relies on these directory entries, so please ensure they are included. For example, in Eclipse, if you choose to export a JAR, make sure the ''Add Directory Entries'' option is selected.		In addition, some users have had issues with classpath scanning not locating jobs in JARs created by tools which don't include directory entries, such as Eclipse. Scanning relies on these directory entries, so please ensure they are included. For example, in Eclipse, if you choose to export a JAR, make sure the ''Add Directory Entries'' option is selected.

Craig: /* I'm seeing an error in the logs about a time zone conflict. What's going on? */

2015-11-28T21:32:25Z

I'm seeing an error in the logs about a time zone conflict. What's going on?

← Older revision		Revision as of 21:32, 28 November 2015
Line 158:		Line 158:
	<pre>		<pre>
	-- Add table prefix as required.		-- Add table prefix as required.
	DELETE FROM OPERATIONS_PARAMETER WHERE NAME LIKE '%~~timezone~~';		DELETE FROM OPERATIONS_PARAMETER WHERE NAME LIKE '%time%one%';
	</pre>		</pre>

Craig at 18:04, 19 November 2015

2015-11-19T18:04:25Z

@@ Line 56: / Line 56: @@
 ** If using the Ant script, change the <code>deployPort</code> setting: <code>ant run.war -DdeployPort=8080 -Dspawn=true</code>
 ** If using the command line to start Winstone, edit <code>winstone.properties</code> by setting the <code>httpPort</code> property to the desired value (e.g. 8080).
 = I tried running Obsidian in Jetty 9, but encountered the error "There is an error in invoking javac.  A full JDK (not just JRE) is required" =

Carfey: /* I'm seeing an error in the logs about a time zone conflict. What's going on? */

2015-11-10T22:09:52Z

I'm seeing an error in the logs about a time zone conflict. What's going on?

← Older revision		Revision as of 22:09, 10 November 2015
Line 143:		Line 143:
	If you start multiple schedulers with different JVM time zones, Obsidian will abort startup to prevent inconsistent scheduling behaviour. The error will look something like "Cannot start scheduler in timezone [PST] since it conflicts with currently running node in timezone [EST]".		If you start multiple schedulers with different JVM time zones, Obsidian will abort startup to prevent inconsistent scheduling behaviour. The error will look something like "Cannot start scheduler in timezone [PST] since it conflicts with currently running node in timezone [EST]".

	Normally, if a scheduler is shut down, it can be started again with a new time zone setting. However, if a scheduler is not gracefully shut down, the stored time zone may persist. In this case, the following sample ~~query~~ can be used while all schedulers are stopped to clear out ~~the~~ time zone state:		Normally, if a scheduler is shut down, it can be started again with a new time zone setting. However, if a scheduler is not gracefully shut down, the stored time zone may persist. In this case, the following sample SQL can be used while all schedulers are stopped to clear out all time zone state:
	<pre>		<pre>
	-- Add table prefix as required.		-- Add table prefix as required.
	DELETE FROM OPERATIONS_PARAMETER WHERE NAME LIKE '%timezone';		DELETE FROM OPERATIONS_PARAMETER WHERE NAME LIKE '%timezone';
	</pre>		</pre>

Carfey at 22:05, 10 November 2015

2015-11-10T22:05:44Z

← Older revision		Revision as of 22:05, 10 November 2015
Line 138:		Line 138:

	To change this and eliminate deadlocks, enable the [[Getting_Started#MS_SQL_Server_Snapshot_Isolation\|read committed snapshot isolation]] on your database.		To change this and eliminate deadlocks, enable the [[Getting_Started#MS_SQL_Server_Snapshot_Isolation\|read committed snapshot isolation]] on your database.

			= I'm seeing an error in the logs about a time zone conflict. What's going on? =

			If you start multiple schedulers with different JVM time zones, Obsidian will abort startup to prevent inconsistent scheduling behaviour. The error will look something like "Cannot start scheduler in timezone [PST] since it conflicts with currently running node in timezone [EST]".

			Normally, if a scheduler is shut down, it can be started again with a new time zone setting. However, if a scheduler is not gracefully shut down, the stored time zone may persist. In this case, the following sample query can be used while all schedulers are stopped to clear out the time zone state:
			<pre>
			-- Add table prefix as required.
			DELETE FROM OPERATIONS_PARAMETER WHERE NAME LIKE '%timezone';
			</pre>