Changes between Version 159 and Version 160 of FAQ

Timestamp:

Mar 16, 2026, 9:00:14 AM (2 hours ago)

Author:

Dimitar Misev

Comment:

—

FAQ

@@ -358 +358 @@
 ''Solution:'' when redeploying rasdaman, make sure to ''restart Tomcat''. This is required because petascope uses a native library from GDAL; further information in the [https://cwiki.apache.org/confluence/display/tomcat/HowTo#HowTo-I'mencounteringclassloaderproblemswhenusingJNIunderTomcat Tomcat docs].
 
-=== Petascope is stuck to start
-
-When you see in `petascope.log` with the last line below in a few minutes
-
-{{{
-  INFO [2026-03-16 07:45:41] HikariDataSource@110: HikariPool-1 - Starting...
-  INFO [2026-03-16 07:45:41] HikariDataSource@123: HikariPool-1 - Start completed.
-  INFO [2026-03-16 07:45:42] HikariDataSource@110: HikariPool-2 - Starting...
-  INFO [2026-03-16 07:45:42] HikariDataSource@123: HikariPool-2 - Start completed.
-}}}
-
-After a few minutes, it may have this log below in `petascope.log`:
-
-{{{
- Caused by: liquibase.exception.LockException: Could not acquire change log lock.  
-}}}
-
-then it can be an issue with liquibase (it thinks a migration crashed or didn’t finish, it leaves locked = true. Then no new migrations will run until it’s unlocked). Then, you need to fix it manually:
-
-{{{
-sudo su - postgres
-psql
-\c petascopedb;
-update databasechangeloglock set locked = false
-
-}}}
-
-then restart petascope (either via `sudo service tomcat9 restart` if external petascope or `sudo service rasdaman restart` if embedded petascope) and it should work again.
-
-
-
-
-
-
-=== Modulor operation in WCPS ===
+=== Petascope fails to start due to failed/locked migration
+
+`petascope.log` contains the following error a few minutes after starting tomcat:
+
+{{{
+  INFO [2026-03-14 06:35:43] HikariDataSource@110: HikariPool-1 - Starting...
+  INFO [2026-03-14 06:35:43] HikariDataSource@123: HikariPool-1 - Start completed.\
+ ERROR [2026-03-14 06:40:43] SpringApplication@821: Application run failed
+... Factory method 'targetDataSource' threw exception; nested exception is 
+liquibase.exception.LockException: Could not acquire change log lock.
+Currently locked by <host> (ip%interface) since 3/14/26, 6:35 AM
+}}}
+
+This is likely caused when liquibase, a library for database migration used in petascope, crashed or didn't finish before tomcat was restarted again. It marks the migration as locked in the `DATABASECHANGELOGLOCK` table in petascopedb, and no new migrations will run until it's manually unlocked:
+
+{{{
+$ sudo -u postgres psql -d petascopedb
+
+UPDATE DATABASECHANGELOGLOCK SET LOCKED = FALSE
+}}}
+
+Then restart tomcat (`sudo service tomcat9 restart` if external deployment, or `sudo service rasdaman restart` if embedded).
+
+
+=== Modulo operation in WCPS ===
 
 In WCPS, `%` character is used for decoding UTF-8 encoded characters, for example,