Closed LotekHeavy closed 1 month ago
maybe aborted (core dumped) is not that wrong (I found this https://github.com/arkmanager/ark-server-tools/issues/1030#issuecomment-513593977), but iwhy then it show this things: "$arkserverroot/$arkserverexec" "$arkserveropts" "${arkextraopts[@]}"
thanks for clarify... :)
maybe aborted (core dumped) is not that wrong (I found this #1030 (comment)), but iwhy then it show this things: "$arkserverroot/$arkserverexec" "$arkserveropts" "${arkextraopts[@]}"
thanks for clarify... :)
bash prints out the raw unexpanded command that launched the child process that was terminated by a signal.
I can start and stop my ark instances without any problem, but after every arkmanager stop --saveworld @island I will see an error in the logfile of the arkmanager:
line 1318: 100721 Aborted (core dumped) "$arkserverroot/$arkserverexec" "$arkserveropts" "${arkextraopts[@]}"
Im running Ubuntu 24.04 LTS, but had this also with my old Ubuntu 20.04 LTS...I use a systemd for initial starting my 8 ark instances, but for updating and restarting I use cronjobs with arkmanager directly.
Full Logfile from a start to stop: