search

mr-guard / dayz-server-manager

A server installer and watch-dog for dayz standalone with built-in Discord and RCon bot
MIT License
158 stars 43 forks source link

Under Ubuntu 22 system：Error trying to scan for ingame report file #157

Open zhangchuangshi opened 3 months ago

zhangchuangshi commented 3 months ago

LOG： @2024-08-20T00:21:54.907Z | IMPORTANT | Manager | User 'admin' executed: login - [] @2024-08-20T00:21:54.908Z | IMPORTANT | Manager | User admin logged in - [] @2024-08-20T00:22:24.507Z | IMPORTANT | Manager | User 'admin' executed: login - [] @2024-08-20T00:22:24.508Z | IMPORTANT | Manager | User admin logged in - [] @2024-08-20T00:22:26.776Z | INFO | Monitor | Server running... - [] @2024-08-20T00:22:27.782Z | IMPORTANT | RCON | Listening on 0.0.0.0:42814 - [] @2024-08-20T00:22:27.811Z | IMPORTANT | RCON | Log-In Successful. RCON Connected - [] @2024-08-20T00:22:27.815Z | WARN | RCON | Command 'say -1 Big Brother Connected.' (0) failed - [] @2024-08-20T00:22:27.816Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:22:27.821Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:22:51.805Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:22:52.432Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:22:52.903Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:22:54.265Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:22:57.258Z | INFO | Monitor | Server running... - [] @2024-08-20T00:23:19.476Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:23:27.300Z | INFO | Monitor | Server running... - [] @2024-08-20T00:23:35.946Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:23:37.136Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:23:38.449Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:23:57.320Z | INFO | Monitor | Server running... - [] @2024-08-20T00:24:02.136Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:24:02.902Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:24:12.746Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:24:19.540Z | WARN | Discord | Queueing message because client did not start or is not yet ready - [false] @2024-08-20T00:24:27.349Z | INFO | Monitor | Server running... - [] @2024-08-20T00:24:57.853Z | INFO | Monitor | Server running... - [] @2024-08-20T00:24:58.840Z | ERROR | IngameReport | Error trying to scan for ingame report file - [{}] @2024-08-20T00:25:27.904Z | INFO | Monitor | Server running... - [] @2024-08-20T00:25:28.859Z | ERROR | IngameReport | Error trying to scan for ingame report file - [{}] @2024-08-20T00:25:57.924Z | INFO | Monitor | Server running... - [] @2024-08-20T00:25:58.904Z | ERROR | IngameReport | Error trying to scan for ingame report file - [{}]

zhangchuangshi commented 3 months ago

I found that the DZSM-TICK.json file is damaged,Every time he is deleted, it can be restored, but after a while, the file becomes damaged again。

code end: "id": 2996397, "id2": "", "position": "3799.474609 190.410690 12985.645508", "speed": "0.000000 0.000000 0.000000", "damage": 0.0 } ] }}

rklxmok commented 1 month ago

I am having this exact issue sadly. but it is with every additional spawnable type, not just the closing entry.