DarkJester Posted December 11, 2018 Share Posted December 11, 2018 After about 8 hours of play all cores start to peak, server reports on Steam it is up. All players kicked and cannot reconnect. Happened on last beta version and this weeks release. Extended play can reproduce. Link to comment Share on other sites More sharing options...
BenWinston Posted December 12, 2018 Share Posted December 12, 2018 Oddly enough, my single player game just did the same thing. Lost connection to the server.... the one running on the same machine as the game. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 12, 2018 Boxelware Team Share Posted December 12, 2018 Posting such things only really help us if you include the server logs from that session - otherwise there's not much we can do except say: "oh, okay, looks like this happens for some reason." So please post the server logs from that session :) Link to comment Share on other sites More sharing options...
DarkJester Posted December 12, 2018 Author Share Posted December 12, 2018 The log file is 7.5mb how much do you want? Link to comment Share on other sites More sharing options...
DarkJester Posted December 12, 2018 Author Share Posted December 12, 2018 Please see attached. It is a 7-Zip file, so you will need to change the file extension to 7z. The forum prevented me from uploading it with a 7z extension, and as a zip file I could not compress it enough. serverlog_2018-12-11_11-29-21.zip Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 12, 2018 Boxelware Team Share Posted December 12, 2018 A good place to share this is pastebin for example. I'll take a look at the logs! Link to comment Share on other sites More sharing options...
Kamo Posted December 12, 2018 Share Posted December 12, 2018 I have the same problem, but happening when transferring cargo for a while (I was loading and unloading stuff from a destroyed shipyard scattered along a waaagh fleet). The second serverlog, happening just after the first, almost only shows one thing 2018-12-12 23-51-45| error constructing ivec3: not enough arguments, expected a value of type 'int' at stack position 3 at 2018-12-12 23-51-45| stack traceback: 2018-12-12 23-51-45| [C]:-1: in function ivec3 2018-12-12 23-51-45| data/scripts/entity/ai/dock.lua:82: in function flyToDock 2018-12-12 23-51-45| data/scripts/entity/ai/trade.lua:81: in function updateServerAI 2018-12-12 23-51-45| data/scripts/entity/merchants/tradeship.lua:63: in function ? 2018-12-12 23-51-45| 2018-12-12 23-51-45| error constructing ivec3: not enough arguments, expected a value of type 'int' at stack position 3 at 2018-12-12 23-51-45| stack traceback: 2018-12-12 23-51-45| [C]:-1: in function ivec3 2018-12-12 23-51-45| data/scripts/entity/ai/dock.lua:82: in function flyToDock 2018-12-12 23-51-45| data/scripts/entity/ai/trade.lua:81: in function updateServerAI 2018-12-12 23-51-45| data/scripts/entity/merchants/tradeship.lua:63: in function ? 2018-12-12 23-51-45| Every 2 to 6 seconds. Apparently a change in ivec3 caused several scripts to break :(. Link to comment Share on other sites More sharing options...
DarkJester Posted December 14, 2018 Author Share Posted December 14, 2018 Had another server lockup last night. 4 players online half a dozen ships moving about with reasonable use of fighters. The server just stopped responding kicked all the players. The server process did not crash itself had to force it closed. No excessive CPU usage this time. Log attached its a 7z file again renamed as a .zip (No pastebin account and RDP on the server atm. easier to post it this way). serverlog_2018-12-13_14-38-58.zip Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 14, 2018 Boxelware Team Share Posted December 14, 2018 From what we've gotten in reports so far, it's some kind of lockup, not a hard crash per se. The clients don't get kicked, they lose connection because the server hangs and stops responding. We're currently looking into the issue, but we haven't managed to reproduce it yet. The script errors from the dock.lua script are unrelated by the way. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 14, 2018 Boxelware Team Share Posted December 14, 2018 If any of you have a reliable method of at least provoking the hang, that would be incredibly helpful! Link to comment Share on other sites More sharing options...
DarkJester Posted December 14, 2018 Author Share Posted December 14, 2018 Not sure what is triggering it, last night we were raiding a local alliance for cargo, cleaning it at a smuggler and selling it on. After that we did some mining and general stuff, fighters deployed no more than 100. I was salvaging a wreck at the time and it just froze up. The time before it was a marathon mining session in preparation for a station deployment. It just seems to occur after about 5 hours of general play with 4 or 5 players. Nothing I can point at and say that's what did it 🤨. Link to comment Share on other sites More sharing options...
BenWinston Posted December 14, 2018 Share Posted December 14, 2018 If any of you have a reliable method of at least provoking the hang, that would be incredibly helpful! For me, it's only the second time it's happened, both times I had been playing for extended periods, with a lot of long periods on Pause. Honestly, I wasn't even going to report it, since it was most likely something I induced. Link to comment Share on other sites More sharing options...
unbekannt1984 Posted December 14, 2018 Share Posted December 14, 2018 Hi, I'm also experiencing problems with the server crashing on singleplayer games. I already posted the serverlog in the Releasenotes-Thread for 0.20.1, but once more: 2018-12-13 15-01-16| Triggered saving of all server data. 2018-12-13 15-01-16| scheduled save for sector (-1:0), 0x7fbd200017a0, entities: 44 2018-12-13 15-01-16| saving sector (-1:0) 2018-12-13 15-01-16| sector (-1:0) saved to "/home/torsten/.avorion/galaxies/avorion_galaxy/sectors/-1_0" 2018-12-13 15-01-16| scheduled save for sector (0:0), 0x7fbd206e3550, entities: 121 2018-12-13 15-01-16| saving sector (0:0) 2018-12-13 15-01-16| sector (0:0) saved to "/home/torsten/.avorion/galaxies/avorion_galaxy/sectors/0_0" 2018-12-13 15-01-16| scheduled save for sector (114:-164), 0x7fbd20372740, entities: 79 2018-12-13 15-01-17| saving sector (114:-164) 2018-12-13 15-01-17| sector (114:-164) saved to "/home/torsten/.avorion/galaxies/avorion_galaxy/sectors/114_-164" 2018-12-13 15-14-57| Received valid shutdown message, shutting down. 2018-12-13 15-16-15| RCON[127.0.0.1] Logged in. 2018-12-13 15-19-37| RCON[127.0.0.1] Logged in. 2018-12-13 15-21-54| RCON[127.0.0.1] Logged in. Well, I was able to log-in using RCON, but commands were not executed. And here is the clientlog of those few minutes: 2018-12-13 15-00-38| <> (114:-164) Solar Cell Factory XXL verkaufte 273 Solarzellen für 126.863 Credits. 2018-12-13 15-00-38| (114:-164) Solar Cell Factory XXL verkaufte 273 Solarzellen für 126.863 Credits. 2018-12-13 15-01-07| <> (114:-164) Solar Power Plant S verkaufte 278 Energiezellen für 6.968 Credits. 2018-12-13 15-01-07| (114:-164) Solar Power Plant S verkaufte 278 Energiezellen für 6.968 Credits. 2018-12-13 15-14-56| Starting thread [OnlineServerQueries WorkerPool Thread 0]... 2018-12-13 15-14-56| Started thread [OnlineServerQueries WorkerPool Thread 0] with id 140346677294848 2018-12-13 15-14-56| Starting thread [OnlineServerQueries WorkerPool Thread 1]... 2018-12-13 15-14-56| Started thread [OnlineServerQueries WorkerPool Thread 1] with id 140346668902144 2018-12-13 15-14-56| Refreshing servers 0 2018-12-13 15-14-57| Starting thread [MainMenu Plan]... 2018-12-13 15-14-57| Started thread [MainMenu Plan] with id 140346386380544 2018-12-13 15-14-57| Error sending message of type: 2: can't send a when not connected 2018-12-13 15-14-57| Starting thread [server Shutdown]... 2018-12-13 15-14-57| Started thread [server Shutdown] with id 140346299066112 2018-12-13 15-14-57| Starting thread [uDP Connection Receive]... 2018-12-13 15-14-57| Started thread [uDP Connection Receive] with id 140346290673408 2018-12-13 15-14-58| Thread [uDP Connection Receive] with id 140346455602944 exiting... 2018-12-13 15-14-58| Thread [uDP Connection Receive] with id 140346455602944 exited 2018-12-13 15-14-58| UDP closed 2018-12-13 15-14-58| Client UDP: Connection closed 2018-12-13 15-14-58| Thread [uDP Connection Receive] with id 140346685687552 exiting... 2018-12-13 15-14-58| Thread [uDP Connection Receive] with id 140346685687552 exited 2018-12-13 15-14-58| UDP closed 2018-12-13 15-14-58| Client UDP: Connection closed 2018-12-13 15-15-02| Serverbrowser refresh complete: Responded 2018-12-13 15-15-02| Not responded: 2018-12-13 15-15-58| Unable to shutdown server. 2018-12-13 15-15-58| Thread [uDP Connection Receive] with id 140346290673408 exiting... 2018-12-13 15-15-58| Thread [uDP Connection Receive] with id 140346290673408 exited 2018-12-13 15-15-58| UDP closed 2018-12-13 15-15-58| Client UDP: Connection closed 2018-12-13 15-15-58| Thread [server Shutdown] with id 140346299066112 exiting... 2018-12-13 15-15-58| Thread [server Shutdown] with id 140346299066112 exited 2018-12-13 15-15-58| Thread [MainMenu Plan] with id 140346386380544 exiting... 2018-12-13 15-15-58| Thread [MainMenu Plan] with id 140346386380544 exited 2018-12-13 15-15-59| Startup successful. It just took me just about 2 hours to crash the server, I've beaten the wormhole-guardian at 0:0 and had a Salvager (with 12 Salvaging-Fighters) recycling it. Link to comment Share on other sites More sharing options...
DarkJester Posted December 18, 2018 Author Share Posted December 18, 2018 Locked up again right after todays update, did not crash. Stopped responding. serverlog_2018-12-18_19-22-02.zip Link to comment Share on other sites More sharing options...
DarkJester Posted December 19, 2018 Author Share Posted December 19, 2018 Hmm something has made this worse 6 server lockups in a space of 8 hours. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 19, 2018 Boxelware Team Share Posted December 19, 2018 Can you share the galaxy with us? We cannot reproduce the issue at all. For multiple days we've had Avorion running nonstop on our machines, nothing happened. Are you playing on vanilla or modded? Link to comment Share on other sites More sharing options...
DarkJester Posted December 19, 2018 Author Share Posted December 19, 2018 Vanilla, no mods. I will share as soon as I can. May consider starting a new Galaxy. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 19, 2018 Boxelware Team Share Posted December 19, 2018 We'll release a small update in the upcoming days with a hang detector, which should hopefully get us some more data about the issue. I'll notify you here once the update is live. Link to comment Share on other sites More sharing options...
DarkJester Posted December 19, 2018 Author Share Posted December 19, 2018 ;D Link to comment Share on other sites More sharing options...
DarkJester Posted December 20, 2018 Author Share Posted December 20, 2018 I get the feeling this is related to moving massive amounts of cargo around after invading sectors and wiping out stations or the overuse of fighters. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 20, 2018 Boxelware Team Share Posted December 20, 2018 Thanks for the input, we'll keep trying to reproduce the error. In the meantime, the update with the hang detector has gone live, we should be able to see the error now (but make sure you have crash sending enabled). Link to comment Share on other sites More sharing options...
DarkJester Posted December 20, 2018 Author Share Posted December 20, 2018 Done, thanks. I hope we crash again. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 21, 2018 Boxelware Team Share Posted December 21, 2018 So, any news? Link to comment Share on other sites More sharing options...
DarkJester Posted December 21, 2018 Author Share Posted December 21, 2018 Not yet, we took the night off last night from Avorion 😂. Will see if we can get everyone on tonight and blow a lot of stuff up. Link to comment Share on other sites More sharing options...
unbekannt1984 Posted December 21, 2018 Share Posted December 21, 2018 Hi koonschi, Thanks for the input, we'll keep trying to reproduce the error. In the meantime, the update with the hang detector has gone live, we should be able to see the error now (but make sure you have crash sending enabled). in the system.ini [system] sendCrashReports=true ? Let me go for the guardian, usually I crash the server within 2 hours then :) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now