El servidor dejo de funcionar

ERICK SOTO GARCIA3 years ago

Buen día comunidad tengo un problema con mi servidor, no recibe los reportes de los gps el log dice lo siguiente:

2022-03-28 06:58:37  INFO: Shutting down server...
2022-03-28 06:58:41  INFO: HikariPool-1 - Starting...
2022-03-28 06:58:42 ERROR: HikariPool-1 - Exception during pool initialization. - The file is locked: C:/Program Files/Traccar/data/database.mv.db [2.0.206/7] - MVStoreException (... < DataManager:131 < *:90 < Context:298 < Main:120 < ...)
2022-03-28 06:58:42 ERROR: Main method error - The file is locked: C:/Program Files/Traccar/data/database.mv.db [2.0.206/7] - MVStoreException (... < DataManager:131 < *:90 < Context:298 < Main:120 < ...)
2022-03-28 06:58:42  WARN: JNA: Callback org.traccar.WindowsService$ServiceMain@4f4c4b1a threw the following exception - The file is locked: C:/Program Files/Traccar/data/database.mv.db [2.0.206/7] - MVStoreException (... < DataManager:131 < *:90 < Context:298 < Main:120 < ...)
2022-03-28 07:53:02  INFO: HikariPool-1 - Starting...
2022-03-28 07:53:06  INFO: HikariPool-1 - Added connection conn0: url=jdbc:h2:./data/database user=SA
2022-03-28 07:53:06  INFO: HikariPool-1 - Start completed.
2022-03-28 07:53:08  INFO: Set default schema name to PUBLIC
2022-03-28 07:53:09  INFO: Clearing database change log checksums
2022-03-28 07:53:10  INFO: Successfully acquired change log lock
2022-03-28 07:53:10  INFO: Successfully released change log lock
2022-03-28 07:53:10  INFO: Successfully acquired change log lock
2022-03-28 07:53:11  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-03-28 07:53:11  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2022-03-28 07:53:14  INFO: Reading from PUBLIC.DATABASECHANGELOG
2022-03-28 07:53:14  INFO: Reading from PUBLIC.DATABASECHANGELOG
2022-03-28 07:53:15  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2022-03-28 07:53:15  INFO: Successfully released change log lock
2022-03-28 07:53:19  INFO: Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system instability.
2022-03-28 07:53:21  INFO: Operating system name: Windows 10 version: 10.0 architecture: amd64
2022-03-28 07:53:21  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: ojdkbuild version: 11.0.13+8-LTS
2022-03-28 07:53:21  INFO: Memory limit heap: 4080mb non-heap: 0mb
2022-03-28 07:53:21  INFO: Character encoding: Cp1252 charset: windows-1252
2022-03-28 07:53:21  INFO: Version: 4.15
2022-03-28 07:53:21  INFO: Starting server...
2022-03-28 07:53:23  WARN: Port disabled due to conflict - Address already in use: bind - BindException (...)
2022-03-28 07:53:23  INFO: jetty-10.0.7; built: 2021-10-06T19:34:02.766Z; git: da8a4553af9dd84080931fa0f8c678cd2d60f3d9; jvm 11.0.13+8-LTS
2022-03-28 07:53:27  INFO: Started o.t.w.@dbfb905{/,null,AVAILABLE}
2022-03-28 07:53:27  INFO: Session workerName=node0
2022-03-28 07:53:31  WARN: JAXBContext implementation could not be found. WADL feature is disabled.
2022-03-28 07:53:32  INFO: Started o.e.j.s.ServletContextHandler@5985df7a{/,null,AVAILABLE}
2022-03-28 07:53:32  INFO: Started ServerConnector@693b618b{HTTP/1.1, (http/1.1)}{0.0.0.0:8082}
2022-03-28 07:53:32  INFO: Started Server@6f8d1bab{STARTING}[10.0.7,sto=0] @31487ms
2022-03-28 08:16:19  INFO: HikariPool-1 - Starting...
2022-03-28 08:16:19  INFO: HikariPool-1 - Added connection conn0: url=jdbc:h2:./data/database user=SA
2022-03-28 08:16:19  INFO: HikariPool-1 - Start completed.
2022-03-28 08:16:19  INFO: Set default schema name to PUBLIC
2022-03-28 08:16:19  INFO: Clearing database change log checksums
2022-03-28 08:16:20  INFO: Successfully acquired change log lock
2022-03-28 08:16:20  INFO: Successfully released change log lock
2022-03-28 08:16:20  INFO: Successfully acquired change log lock
2022-03-28 08:16:20  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.json.JsonChangeLogParser Unable to get public no-arg constructor
2022-03-28 08:16:20  INFO: Cannot load service: liquibase.parser.ChangeLogParser: liquibase.parser.core.yaml.YamlChangeLogParser Unable to get public no-arg constructor
2022-03-28 08:16:21  INFO: Reading from PUBLIC.DATABASECHANGELOG
2022-03-28 08:16:21  INFO: Reading from PUBLIC.DATABASECHANGELOG
2022-03-28 08:16:21  INFO: Cannot load service: liquibase.hub.HubService: Provider liquibase.hub.core.StandardHubService could not be instantiated
2022-03-28 08:16:21  INFO: Successfully released change log lock
2022-03-28 08:16:22  INFO: Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system instability.
2022-03-28 08:16:22  INFO: Operating system name: Windows 10 version: 10.0 architecture: amd64
2022-03-28 08:16:22  INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: ojdkbuild version: 11.0.13+8-LTS
2022-03-28 08:16:22  INFO: Memory limit heap: 4080mb non-heap: 0mb
2022-03-28 08:16:22  INFO: Character encoding: Cp1252 charset: windows-1252
2022-03-28 08:16:22  INFO: Version: 4.15
2022-03-28 08:16:22  INFO: Starting server...
2022-03-28 08:16:23  WARN: Port disabled due to conflict - Address already in use: bind - BindException (...)
2022-03-28 08:16:23  INFO: jetty-10.0.7; built: 2021-10-06T19:34:02.766Z; git: da8a4553af9dd84080931fa0f8c678cd2d60f3d9; jvm 11.0.13+8-LTS
2022-03-28 08:16:23  INFO: Started o.t.w.@5f7a995f{/,null,AVAILABLE}
2022-03-28 08:16:23  INFO: Session workerName=node0
2022-03-28 08:16:24  WARN: JAXBContext implementation could not be found. WADL feature is disabled.
2022-03-28 08:16:24  INFO: Started o.e.j.s.ServletContextHandler@7ebd1a56{/,null,AVAILABLE}
2022-03-28 08:16:24  INFO: Started ServerConnector@50677bc5{HTTP/1.1, (http/1.1)}{0.0.0.0:8082}
2022-03-28 08:16:24  INFO: Started Server@9f92d99{STARTING}[10.0.7,sto=0] @7904ms

Espero puedan ayudarme.

gracias y buen dia.

Anton Tananaev3 years ago

Seems to be working fine based on the log.

Track-trace3 years ago

Check the Port...

2022-03-28 08:16:22  INFO: Starting server...
2022-03-28 08:16:23  WARN: Port disabled due to conflict - Address already in use: bind - BindException (...)

It seems the port is already used. SO check what is running on the port and kill that process.