DrkCloudStrife / pi-heim

Valheim Server on Raspberry Pi 5
3 stars 0 forks source link

Server crashes after a few minutes after starting #6

Open DrkCloudStrife opened 9 months ago

DrkCloudStrife commented 9 months ago

Once the valheim server has started, it will only run for a couple of minutes. Some people have experienced similar issues and have reported this in https://github.com/ptitSeb/box64/issues/1182

As a system administrator, I want to configure the box64 wrapper library correctly in order for the valheim server not to crash.

nitroinferno commented 9 months ago

Does it always crash after a few minutes? Or has it run for some time? (This may take several restarts as seen below). My pi is s rpi4 only has 4gb.. so it could be a contributing issue. Curious to know though if it behaves the same for an 8gb.

Also on startup with regards to libparty.so i get:

Using emulated /home/nitro/valheim_server/valheim_server_Data/Plugins/libparty.so
Redirecting overridden malloc from symtab function for /home/nitro/valheim_server/valheim_server_Data/Plugins/libparty.so

For example here is a snapshot from todays logs:

nitro@raspberrypi:~ $ journalctl --since -24hour --no-pager -u valheim | grep -i 'consumed'
Feb 06 20:35:38 raspberrypi systemd[1]: valheim.service: Consumed 8h 40.848s CPU time.
Feb 06 21:49:30 raspberrypi systemd[1]: valheim.service: Consumed 1h 42min 36.878s CPU time.
Feb 07 00:28:22 raspberrypi systemd[1]: valheim.service: Consumed 5h 11min 16.792s CPU time.
Feb 07 00:45:05 raspberrypi systemd[1]: valheim.service: Consumed 22min 40.800s CPU time.
Feb 07 00:55:54 raspberrypi systemd[1]: valheim.service: Consumed 15min 5.313s CPU time.
Feb 07 01:05:30 raspberrypi systemd[1]: valheim.service: Consumed 13min 32.997s CPU time.
Feb 07 01:28:24 raspberrypi systemd[1]: valheim.service: Consumed 31min 42.041s CPU time.
Feb 07 01:41:44 raspberrypi systemd[1]: valheim.service: Consumed 18min 17.604s CPU time.
Feb 07 01:51:55 raspberrypi systemd[1]: valheim.service: Consumed 14min 13.524s CPU time.
Feb 07 02:20:04 raspberrypi systemd[1]: valheim.service: Consumed 38min 17.261s CPU time.
Feb 07 02:26:40 raspberrypi systemd[1]: valheim.service: Consumed 9min 37.163s CPU time.
Feb 07 02:39:06 raspberrypi systemd[1]: valheim.service: Consumed 17min 11.062s CPU time.
Feb 07 03:10:03 raspberrypi systemd[1]: valheim.service: Consumed 42min 47.586s CPU time.
Feb 07 05:53:56 raspberrypi systemd[1]: valheim.service: Consumed 3h 42min 19.219s CPU time.
DrkCloudStrife commented 9 months ago

@nitroinferno I haven't personally moved the server to a service yet. I've been using a tmux subshell where is currently running. I've only been able to get the server running by a few minutes. This time ranges from 5 minutes, up to an hour. This is from my personal experience because I get disconnected from the server while I'm on it.

Regarding the libparty.so, here's what my logs output:

Using emulated /home/steam/valheim_server/valheim_server_Data/Plugins/libparty.so                                                                                                                             
Redirecting overridden malloc from symtab function for /home/steam/valheim_server/valheim_server_Data/Plugins/libparty.so                                                                                     
Using native(wrapped) libatomic.so.1                                                                                                                                                                          
Using native(wrapped) libpulse.so.0                                                                                                                                                                           
Using native(wrapped) libpulse-simple.so.0                                                                                                                                                                    
Using native(wrapped) libpulse-mainloop-glib.so.0                                                                                                                                                             
Using emulated /lib/x86_64-linux-gnu/libstdc++.so.6                                                                                                                                                           
Warning: Global Symbol _ZN9__gnu_cxx21zoneinfo_dir_overrideEv not found, cannot apply R_X86_64_GLOB_DAT @0x3f0624e268 ((nil)) in /lib/x86_64-linux-gnu/libstdc++.so.6                                         
Warning: Weak Symbol _ITM_memcpyRtWn not found, cannot apply R_X86_64_JUMP_SLOT @0x3f0624f060 (0x9c0f6)                                                                                                       
Warning: Weak Symbol _ITM_RU1 not found, cannot apply R_X86_64_JUMP_SLOT @0x3f0624f6a0 (0x9cd76)                                                                                                              
Warning: Weak Symbol _ZGTtdlPv not found, cannot apply R_X86_64_JUMP_SLOT @0x3f0624fb00 (0x9d636)                                                                                                             
Warning: Weak Symbol _ITM_RU8 not found, cannot apply R_X86_64_JUMP_SLOT @0x3f0624fff8 (0x9e026)                                                                                                              
Warning: Weak Symbol _ITM_memcpyRnWt not found, cannot apply R_X86_64_JUMP_SLOT @0x3f062504a8 (0x9e986)                                                                                                       
Warning: Weak Symbol _ZGTtnam not found, cannot apply R_X86_64_JUMP_SLOT @0x3f06250c88 (0x9f946)                                                                                                              
Preloaded 'libparty.so'           

I know that the RBPI5 is more powerful over RBPI4, but also since is newer, the box64 wrapper has been having issues with it.