Open noodohs opened 7 years ago
Please try removing the --safe
option.
Will try that. I had added that so that we wouldn't have to worry about being kicked backward in time, but i guess if we are all signed off it might be fine.
If you are concerned, you can use --saveworld
, which will explicitly save the world to disk before restarting (rather than relying on a graceful shutdown saving the world).
I have the same problem and:
[root@h2725656 ~]# su -s /bin/bash steam
[steam@h2725656 root]$ arkmanager status @blueark2
Running command 'status' for instance 'blueark2'
Server running: No
Server listening: No
Server build ID: 2120726
[steam@h2725656 root]$ arkmanager start @blueark2
Running command 'start' for instance 'blueark2'
Checking for updates before starting
Checking for update; PID: 23880
Your server is already up to date! The most recent version is 2120726.
The server is now running, and should be up within 10 minutes
[steam@h2725656 root]$ arkmanager update --update-mods --warn @blueark2
Running command 'update' for instance 'blueark2'
Checking for update; PID: 24491
Your server is already up to date! The most recent version is 2120726.
[steam@h2725656 root]$ arkmanager stop --warn @blueark2
Running command 'stop' for instance 'blueark2'
This ARK server will shutdown in 10 minutes
**Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.**
There are -1 players connected
There are -1 players connected
There are -1 players connected
There are -1 players connected
There are -1 players connected
This ARK server will shutdown in 5 minutes
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 4 minutes
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 3 minutes
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 120 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 90 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 60 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 45 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 30 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 20 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
There are -1 players connected
This ARK server will shutdown in 15 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
This ARK server will shutdown in 10 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
This ARK server will shutdown in 5 seconds
Error connecting to server: Verbindungsaufbau abgelehnt at -e line 33.
Stopping server; reason: shutdown
The server has been stopped
[steam@h2725656 root]$
An here its crashing. If the crontab starts for update it just stop the server without warning. -.- /15 * /usr/local/bin/arkmanager update --warn --saveworld --update-mods @blueark
I cant find a solution. Tool is up to date. All other commands working so far. Please help...
@Aylja your issue is different to that of the OP.
If you look at the output, it is trying to warn, but it looks almost as if you are having the same problem as #849, where the server is binding only to the external IP address.
What are the contents of the arkserver.log file (with any sensitive data masked out), from the last start line to the end?
i continue in #849
I think I've got everything running pretty well now, but the server does not warn us before kicking us off for updates. Not always a huge deal, but sometimes we are in the middle of fighting an alpha wyvern in the air...
I have the update command specified via cron:
I modified that slightly from what using the install-cronjob command does, thinking that maybe removing @all and --cronjob would help (I only run one instance anyway), but it still does not give any warning. In my config, I have the following:
Am I doing something wrong? I would, ideally, like to also have it wait until everyone has signed off before doing the restart, but at least actually warning us would be a good start.