DomDom3333

I see. An I guess there's nothing we can really do about it?

I dont think its stuck on the lobby registration. When i set the "registerToLobby" config to 0, it STILL gets stuck there. I dont think this is networking related.... It seems to fail to initialize the first session (bases on what a normal local server writes into the console compared to this). Given my LIMITED knowledge on the matter, i would guess its a Wine compatibility issue of some sort? Here is what a working server on my windows machine writes. Server starting with version 255 Starting server Doms Server FileToStruct cfg/eventRules.json maxCarSlots 50 exceeds the pit count for nurburgring. Setting car slots to 50 Translated realtime interval hzToMiliseconds(18)=54 SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.929515 Track nurburgring was set and updated Event changed Reading custom event rules FileToStruct cfg/eventRules.json SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.891939 Significant change detected, updating lobby (1|1) maxCarSlots 50 exceeds the pit count for nurburgring. Setting car slots to 50 Resetting weekend to friday night Reset time to friday night: 0 -> 0 Reset time to first session: 0 -> 43200 SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.918487 Listening to TCP 9601 | UDP 9600 Trying to connect to lobby (0 times, interval 10000 s) Session changed: Practice -> Practice 0 Detected sessionPhase <waiting for drivers> -> <waiting for drivers> (Practice) TCP connect returns: -1 ==ERR: RegisterToLobby TCP connection failed, couldn't connect to the lobby server Trying to connect to lobby (1 times, interval 13000 s) TCP connect returns: 0 RegisterToLobby succeeded Lobby accepted connection Lobby accepted connection Sent lobby registration request for nurburgring TCPQueue now: 4 New TCP incoming pakSizeMax, 0 => 2 Updated lobby with 0 drivers As yous see, it tries to reset the session before it connects to the lobby system. It gets stuck there tho. Also thank you for your fast help and effort. It is really appreciated.

So i left the server run overnight and today it was avaliable to join. No additional error messages which were out of the ordinary. So i guess it just takes multiple hours to get past that line? While the server was idling it was repeatetly writing "Server was running late for 1 step(s), not enough CPU power", which doesnt make sense since it is running on an AMD 3900X with 48GB of ram and no other MAJOR applications to compete with. Upon restarting the server to apply changes, it sticks on the "Reset time to friday night: 0 -> 0" line Attatched another server log as far as it let me go back after i restarted it Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power New connection received 172 1 client(s) online TCPQueue now: 208 ==ERR: Uninitialized Connection 0 timed out (31134627 - 31132626 = 2000) ==ERR: Uninitialized Connection 0 timed out (31134627 - 31132626 = 2000) Removing dead connection 0 (last lastUdpPaketReceived 31134627) ==ERR: Uninitialized Connection 0 timed out (31134627 - 31132626 = 2000) Alive connections: 0 0 client(s) online Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power Server was running late for 1 step(s), not enough CPU power New connection received 172 1 client(s) online TCPQueue now: 434 New TCP incoming pakSizeMax, 0 => 432 Located entryListId -1 for connection 1 S76561198077727714 New connection request: id 1 Dominik Essenhofer S76561198077727714 on car model 25 Creating new car connection: carId 1001, carModel 25, raceNumber #87 Special Rules for carid 1001: max_total_driving_time is -1 (from -1), pitCount 0 startingTime is not set? Starting stint for car 1001 driver 0 at 66757015.548500 Updated lobby with 1 drivers Assigning gridNumber 1 to new carId 1001 Sent handshake response for car 1001 connection 1 with 1228 bytes 1 Driver(s) detected, starting session SessionManager::randomizeGreenFlagTriggers: s:0.991555 e:0.999999 r:0.993187 Detected sessionPhase <waiting for drivers> -> <pre session> (Practice) Sent session update to lobby Updated leaderboard for 1 clients (Practice-<pre session> 20 min) Detected sessionPhase <session> -> <session> (Practice) Sent session update to lobby Tcp message count (1 clients): Udp message count (1 clients): 23=1, Associated: connId 1, now 66765907 Reset time offset for connection 1, new offset 66765902, diff 8887 Receives driver stint reset for car 1001 Ending stint: new total time for car 1001 driver 0 is 9094.951500 List of Stints for car 1001 driver 0 Stint 1 car 1001 driver 0 started 66757015.548500 ended 66766110.500000 Receives driver stint reset for car 1001 startingTime is not set? Updated 0 clients with new carSystem for car 1001 (67108864l) Updated 0 clients with new carSystem for car 1001 (67108880l) Updated 0 clients with new carSystem for car 1001 (67108864l) Updated 0 clients with new carSystem for car 1001 (67108880l) Receives driver stint reset for car 1001 startingTime is not set? Starting stint for car 1001 driver 0 at 66793633.500000 Updated 0 clients w---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Checking if 'accServer.exe' is present--- ---'accServer.exe' found, continuing...--- ---Prepare Server--- ---Checking if config files are present--- ---Checking if WINE workdirectory is present--- ---WINE workdirectory found--- ---Checking if WINE is properly installed--- ---WINE properly set up--- ---Server ready--- ---Start Server--- 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 009c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 009c:err:winediag:nodrv_CreateWindow L"The explorer process failed to start." 009c:err:systray:initialize_systray Could not create tray window 0024:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000007E970 1 C) semi-stub 0024:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000007E740 1 C) semi-stub 0024:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000007E6A0 1 C) semi-stub Server starting with version 255 Starting server ACC Docker Server FileToStruct cfg/eventRules.json Translated realtime interval hzToMiliseconds(18)=54 SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.915965 Track monza was set and updated Event changed Reading custom event rules FileToStruct cfg/eventRules.json SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.945944 Significant change detected, updating lobby (1|1) Resetting weekend to friday night Reset time to friday night: 0 -> 0 0120:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0000000002F3F760 1 C) semi-stub 0120:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0000000002F3F760 1 C) semi-stub 0120:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0000000002F3F760 1 C) semi-stub

So ive just did a clean reinstall of the server (including removing the appdata folder) and reset my portforwarding rules accordingly. Still gets stuck on the "Reset tiume to friday night: 0 -> 0

That's great news. I've forwarded the ports and I don't see any errors or strange notifications in the log but the server just never shows up. When I leave the log open, it eventually just closes (unlike other containers) and when I reopen it, nothing has changed. Here is a block out of the logs. Other than those MaxCarSlots config being off i dont see anything wrong and it ALWAYS gets stuck there ---Checking if UID: 99 matches user--- usermod: no changes ---Checking if GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Checking if 'accServer.exe' is present--- ---'accServer.exe' found, continuing...--- ---Prepare Server--- ---Checking if config files are present--- ---Checking if WINE workdirectory is present--- ---WINE workdirectory found--- ---Checking if WINE is properly installed--- ---WINE properly set up--- ---Server ready--- ---Start Server--- Server starting with version 255 Starting server Doms Server FileToStruct cfg/eventRules.json maxConnections 30 is smaller than maxCarSlots 99, reducing car slots to 30 Translated realtime interval hzToMiliseconds(18)=54 SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.901446 Track nurburgring was set and updated Event changed Reading custom event rules FileToStruct cfg/eventRules.json SessionManager::randomizeGreenFlagTriggers: s:0.890000 e:0.950000 r:0.925428 Significant change detected, updating lobby (1|1) maxConnections 30 is smaller than maxCarSlots 99, reducing car slots to 30 Resetting weekend to friday night Reset time to friday night: 0 -> 0

Hi. I was wondering if this is still the case. There seems to be no alternative to hosting an ACC server in Docker as far as i know which is a real shame.