Oct 6 23:37:30 F-04 traccar: # Compiler replay data is saved as: Oct 6 23:37:30 F-04 traccar: # An error report file with more information is saved as: To enable core dumping, try "ulimit -c unlimited" before starting Java again Oct 6 23:37:30 F-04 traccar: # No core dump will be written. Oct 6 23:37:30 F-04 traccar: # Problematic frame: Oct 6 23:37:30 F-04 traccar: # Java VM: OpenJDK 64-Bit Server VM (11.0.5+10-LTS, mixed mode, tiered, compressed oops, serial gc, linux-amd64) Oct 6 23:37:30 F-04 traccar: # A fatal error has been detected by the Java Runtime Environment: Oct 6 23:37:08 F-04 systemd: Started traccar. Oct 6 23:37:08 F-04 systemd: Stopped traccar. The syslog output of the crash is: Oct 6 23:37:08 F-04 systemd: rvice: Scheduled restart job, restart counter is at 2. Looking into the syslog I found that traccar was started 3 times because it crashed and was restarted by the service. 23:39:14 INFO: Waiting for changelog lock. 23:39:14 INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1 23:39:04 INFO: Waiting for changelog lock. 23:39:04 INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1 23:38:54 INFO: Waiting for changelog lock. 23:38:54 INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1 23:38:44 INFO: Waiting for changelog lock. 23:38:44 INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1 23:38:34 INFO: Waiting for changelog lock. 23:38:34 INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1 23:38:34 INFO: SELECT COUNT(*) FROM PUBLIC.DATABASECHANGELOGLOCK 23:38:33 INFO: Clearing database change log checksums 23:38:29 INFO: HikariPool-1 - Start completed. 23:38:08 INFO: HikariPool-1 - Start completed. 23:37:48 INFO: HikariPool-1 - Start completed. 23:37:23 INFO: Can not use class .YamlChangeLogParser as a Liquibase service because .BaseConstructor is not in the classpath 23:37:23 INFO: Can not use class .JsonChangeLogParser as a Liquibase service because .BaseConstructor is not in the classpath 23:37:23 INFO: Successfully acquired change log lock 23:37:23 INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1 23:37:23 INFO: SELECT COUNT(*) FROM PUBLIC.DATABASECHANGELOGLOCK 23:37:23 INFO: Successfully released change log lock 23:37:23 INFO: UPDATE PUBLIC.DATABASECHANGELOG SET MD5SUM = NULL 23:37:23 INFO: SELECT MD5SUM FROM PUBLIC.DATABASECHANGELOG WHERE MD5SUM IS NOT NULL 23:37:21 INFO: Successfully acquired change log lock 23:37:21 INFO: SELECT LOCKED FROM PUBLIC.DATABASECHANGELOGLOCK WHERE ID=1 23:37:21 INFO: SELECT COUNT(*) FROM PUBLIC.DATABASECHANGELOGLOCK 23:37:20 INFO: Clearing database change log checksums 23:37:16 INFO: HikariPool-1 - Start completed. 23:36:38 INFO: HikariPool-1 - Start completed. The log file output is: 23:36:35 INFO: HikariPool-1 - Starting. I can easily reproduce the issue by running systemctl stop rvice and then systemctl start rvice The database migration is long done and I did not kill the process manually. I don't know what I would be doing wrong.
0 Comments
Leave a Reply. |