Drivers disappearing from live timing

Assetto Corsa Server Manager v2 Support
1

Please describe the issue in as detailed a way as possible
8 to 10 minutes after the start of an event, some or all drivers connected to the servers disappears from the live timing. They’re still connected to the Assetto Corsa Server and are visible by the other drivers on the map but they seem to be disconnected from ACSM live timing / race control and their lap times are not registered by ACSM anymore.
The problem always occurs like ten minutes after the start of an event but not during the looping practices.

For exemple:
A championship event is scheduled for the sunday at 8pm.
Event format is 2 hours practice, 10 minutes qualifying and 1 hour race.
The looping practice is started on the monday.
All week long, there is no problem whatsoever, the drivers connected to the practice can stay connected for any amount of time without disappearing from the live timing.
But on sunday the event starts.
Everyone connects at the start of the event at 8pm.
At 8:10, some drivers disappears at the same time from the live timing and the server-manager.log spams me with error message like

time="2025-02-25T21:55:29+01:00" level=error msg="Unable to handle event: 53" error="racecontrol: could not find connected driver for DriverGUID: XXXXXXXXXXX"

Then we tell everyone who isn’t on the live timing to deconnect and reconnect and the error messages disappear and everything is fine after.

When people deconnects we have those kind of error messages:

time="2025-02-25T21:55:31+01:00" level=error msg="Unable to handle event: 52" error="racecontrol: client disconnected without ever being connected: Driver Name (XXXXXXXXXXXXX)"

The problem only occurs at the start of the event for the first session (generally practice) but not on the next session (qualify or race).
It’s always 10 minutes after the event’s start.

Thanks for your help,
Kind regards,

Karmeliet
Which version of Server Manager are you using?
2.4.5 but it was happening on the previous version as well

What OS are you running Server Manager on?
Ubuntu 24.04

Any extra information about the problem
Native install, not dockerized, everything up to date.

2

Hi,

We haven’t had any other reports of an issue like this, so unfortunately I don’t have any immediate idea of what the issue might be here.

Do you have a debug bundle exported from the server from after one of these incidents? If you don’t it would be very useful to export one (from the Server → Logs page) the next time this happens so we can look through the logs. It would be best if you could email that to us at support@emperorservers.com, debug bundles do redact most sensitive information but there is still some information in there that you may not want to share publicly.

The timing seems particularly odd, out of interest have you tried refreshing the Live Timings page after this happens? Based on the error I wouldn’t expect that to help, but it would be good to know for certain.

With issues like this I think it’s always helpful to double check your server configuration as well, make sure that none of your ports are clashing, especially if you run multiple ACSM instances.

I hope that helps, again if you can provide a debug bundle that should help a lot here.

Thanks.

3

Hi and thanks for your response.

I did indeed refresh the page after this happens but no changes.

Sadly the report bundle files are not covering the last incident.
I’ll email you the bundle from the next event in two weeks or try to reproduce the problem before that.

I checked my port mapping, we do run 10 server instances and there is no clash between ports.

I’ll try to run ACSM on a different host with a similar OS config to see if the problem is present as well which could indicate an OS related problem.

I’ll keep you informed.

Thx again.

1 Like