Author Topic: Server Crash hang of at leas 30 secoonds server Beta 0.29.6  (Read 60 times)

gibnieauf

  • Newbie
  • *
  • Status:
    Offline
    Posts:
    4
    • View Profile
Avorion server Beta 0.29.6 r19037 60436ea95a15 running on Debian GNU/Linux 9 (stretch) starting up in "/home/zap475614/g203234/avorion/imperium"
CPU: AMD Ryzen 7 1700X Eight-Core Processor 16 Cores
RAM: 62GB




sector (-413:135) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-413_135"
Player WasIstSeifee moved to sector (-413:135)from (-412:134) server time taken for change: 0ms
scheduled save for sector (-413:135), 0x7f3a25271000, entities: 562
saving sector (-413:135)
sector (-413:135) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-413_135"
scheduled save for sector (-412:134), 0x7f3a282f00a0, entities: 2
saving sector (-412:134)
sector (-412:134) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-412_134"
scheduled save for sector (-412:140), 0x7f3a096a8270, entities: 768
saving sector (-412:140)
sector (-412:140) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-412_140"
scheduled save for sector (-413:126), 0x7f3a659211e0, entities: 1118
saving sector (-413:126)
sector (-413:126) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-413_126"
scheduled save for sector (-412:128), 0x7f3a1d2fd4c0, entities: 0
saving sector (-412:128)
sector (-412:128) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-412_128"
scheduled save for sector (-411:130), 0x7f3a244b9550, entities: 2
saving sector (-411:130)
sector (-411:130) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-411_130"
scheduled save for sector (-412:131), 0x7f3a72327f40, entities: 509
saving sector (-412:131)
sector (-412:131) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-412_131"
scheduled save for sector (-412:134), 0x7f3a282f00a0, entities: 2
saving sector (-412:134)
sector (-412:134) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-412_134"
Triggered saving of all server data.
scheduled save for sector (0:0), 0x7fff3b129630, entities: 64
saving sector (0:0)
sector (0:0) saved to "/home/zap475614/g203234/avorion/imperium/jumps.dat"
scheduled save for sector (-424:148), 0x7f3a274f1de0, entities: 1716
saving sector (-424:148)
sector (-424:148) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-424_148"
scheduled save for sector (-413:135), 0x7f3a25271000, entities: 633
saving sector (-413:135)
sector (-413:135) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-413_135"
<> You cannot build this. The block overlaps too much with another block.
Triggered saving of all server data.
scheduled save for sector (0:0), 0x7fff3b129630, entities: 64
saving sector (0:0)
sector (0:0) saved to "/home/zap475614/g203234/avorion/imperium/jumps.dat"
scheduled save for sector (-424:148), 0x7f3a274f1de0, entities: 1712
saving sector (-424:148)
sector (-424:148) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-424_148"
scheduled save for sector (-413:135), 0x7f3a25271000, entities: 739
saving sector (-413:135)
sector (-413:135) saved to "/home/zap475614/g203234/avorion/imperium/sectors/-413_135"
<> You cannot edit a damaged ship.
<> You cannot edit a damaged ship.
<> You cannot edit a damaged ship.
<> You cannot edit a damaged ship.
<> You cannot edit a damaged ship.
Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!

Hang of at least 30 seconds detected, sending stack traceSending crash report ...
Crash report sent successfully!


and this continues after restart, this starts again after 10 minutes or after 2 hours



unbekannt1984

  • Full Member
  • ***
  • Status:
    Offline
    Posts:
    183
    • View Profile
on: January 13, 2020, 04:17:11 PM
Hi,

you are using Debian? Could you provide some information about System-Load and so on? Even if that server doesn't have a graphical user interface, you could use "screen" to get (another) terminal and "htop" to get some information about Memory-Usage and CPU-Load.

Please also provide information about the HDD/SDD and the Partitions on that drive.



Hammelpilaw

  • Hero Member
  • *****
  • Status:
    Offline
    Posts:
    561
    • View Profile
    • Scrap Yard - Avofactory
on: January 13, 2020, 05:04:38 PM
Did you configure the cores/threads correctly in server.ini file? Should be 16/8/8 (worker/generator/scriptBackground) for your machine.

Please watch wiki to understand the numbers above:
https://avorion.gamepedia.com/Setting_up_a_server#Multithreading
Scrap Yard Galaxy
My mods and tools
My Workshop

If you find a bug in my mods please contact me.



Savagetda@gmail.com

  • Newbie
  • *
  • Status:
    Offline
    Posts:
    1
    • View Profile
My server is hanging as well. Seems to happen more often when we have just 3 players online. The hang for me is lasting much longer than 30 seconds, it never seems to go back to normal. I end up restarting the server to fix it.