Changes between Version 157 and Version 158 of FAQ

Timestamp:

Mar 16, 2026, 7:33:23 AM (7 hours ago)

Author:

Bang Pham Huu

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.
+}}}
+
+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 ===