status command seems not working about ark-server-tools HOT 33 CLOSED

the serverport is hardcoded in the script (7779) but the server is running on an other port..

it looks like the arkserveropts (?Port=$arkserverport) doesn't work

the function should be:

function isTheServerUp(){
  PORT=$arkserverport
  lsof -i |grep $PORT > /dev/null
  result=$?
  return $result
}

its crazy, i've set the serverport to "7777" in the arkmanager.cfg
lsof -i says its running on 7779
and arkservers.net says its running on 7778
WTF?!

from ark-server-tools.

Same for me. I'am on it.

from ark-server-tools.

• Port not defined in launch options.
• lsof -i reports port 7778.
• Server browser reports 7777.
• Arkservers.net reports 7777.

from ark-server-tools.

Same for me, port. If i check with "netstat -lputen" i can see the port is listenning on 7778. And it appear on 7777 on the steam server browser . And set the port in the command line seems to not change anything.
So wath the plan?

I purpose to tell our user to set the port in Ark settings and set the same port in arkmanager config to allow us to check the server is online.

from ark-server-tools.

To check if is one line we have to check our local listenning port. Whatever the steam broswer say.

It's fixed in my last PR

from ark-server-tools.

"The inconsistancy is caused by the unreal engine and how it is setup. In the BaseEngine config file it has the ports set on a +1 offset of each other.

Port=7777
PeerPort=7778"

from ark-server-tools.

Yeah as Atriusftw quoted from my post on steam community. From what I understand unreal engine has a public port and a peer port.
The "Port" config option is what the server reports when the it communicates with steam through the steamapi. (ie hense why people get "STEAMPS3 - AsyncTCPSocket created" and "STEAMPS3 - AsncTCPSocket destroyed" errors)
The "PeerPort" is the actual port that the server is listening to.
For the sake of is being confusing, I have set my Port and PeerPort in BaseEngine.ini to the exact same thing.

from ark-server-tools.

Im currently graphing the mentioned ports for results. Will post them when they're filled up.

from ark-server-tools.

[steam@ns322377 ~]$ lsof -i |grep 27016; echo $?
ShooterGa 30686 steam   11u  IPv4 1190052      0t0  UDP *:27016
0
[steam@ns322377 ~]$ lsof -i |grep 27015; echo $?
1

Looks like lsof returns 1 if nothing is found and 0 if foud.. should we fix the script?

from ark-server-tools.

Haha, that is so opposite of what it should be. Totally f*cks with my mind.

My graphing results for the listening port though;

7777, UDP
http://atrius.net/~random/UDP-7777.png

7778, UDP
http://atrius.net/~random/UDP-7778.png

These are results without defining port in launch options, and with only me on the server for 30~ minutes.

Furthermore, some bindings:

steam@natrium:~$ netstat -tulpn | grep ShooterGame
udp        0      0 0.0.0.0:27016           0.0.0.0:*                           21382/ShooterGameSe
udp        0      0 0.0.0.0:7778             0.0.0.0:*                           21382/ShooterGameSe

from ark-server-tools.

The script work for me like that. Are you testing the dev1.1? I have fixed
this part. Now we get the port number from the configuration file. And its
7778 by default.
Le 22 juin 2015 11:30 AM, "Fez Vrasta" [email protected] a écrit :

[steam@ns322377 ~]$ lsof -i |grep 27016; echo $?
ShooterGa 30686 steam 11u IPv4 1190052 0t0 UDP *:27016
0
[steam@ns322377 ~]$ lsof -i |grep 27015; echo $?
1

Looks like lsof returns 1 if nothing is found and 0 if foud.. should we
fix the script?

—
Reply to this email directly or view it on GitHub
#31 (comment)
.

from ark-server-tools.

So, the script is actualy working by default? No?

from ark-server-tools.

Not working in dev1.1, as the start function subtracts 1 from the port defined in config.

from ark-server-tools.

Correct me if I am wrong, we subtract 1 from port because the server then starts on port+1 so we have to check port once the server is started, because it is listening on (port-1)+1

no?

from ark-server-tools.

The port defined in the configuration file should be the one that is up
when the server is up.

Not working in dev1.1, as the run function subtracts 1 from the port
defined in config.

—
Reply to this email directly or view it on GitHub
#31 (comment)
.

from ark-server-tools.

Yes, that is correct @FezVrasta.
Unreal Engine is stupid like that.

Basically, Unreal Engine adds 1 to the specified port in our config.
What i find is funny though - in the server browser it still shows the port in the config.

@Sispheor - That is weird. I have port 27015 in my configuration files, and the server comes up at 27014.

atrius@natrium:/home/steam$ arkmanager status
 Server running:  Yes
 Server online:   No
 Server version:  668810

atrius@natrium:/home/steam$ sudo netstat -tulpn | grep ShooterGame
udp        0      0 0.0.0.0:27015           0.0.0.0:*                           562/ShooterGameServ
udp        0      0 0.0.0.0:27016           0.0.0.0:*                           562/ShooterGameServ

from ark-server-tools.

I don't get where is the problem then

If we annul the Unreal Engine problem providing him port-1 why should we check port-1 when we look for the server status?

Unreal Engine has set the server to (port-1)+1 (= port) so we should check port, and this is what we are currently doing in 1.1

from ark-server-tools.

Absolutly. I don't get why you play with that port. It's simple. What you
get with netstat is what you have to set in the configuration file to check
it.

2015-06-23 15:51 GMT+02:00 Fez Vrasta [email protected]:

I don't get where is the problem then

If we annul the Unreal Engine problem providing him port-1 why should we
check port-1 when we look for the server status?

Unreal Engine has set the server to (port-1)+1 (= port) so we should
check port, and this is what we are currently doing in 1.1

—
Reply to this email directly or view it on GitHub
#31 (comment)
.

Nicolas MARCQ

from ark-server-tools.

Looks like there is some confusion here...

from ark-server-tools.

Now all fine, u can closed the bug xD

from ark-server-tools.

I don't understand how it's fine? I'm still showing as not online

from ark-server-tools.

@FezVrasta So what the plan? I suggest the port in the cfg be the real one listtening on the server. And we remove math from the function. And we explain how to get the port for the first time to set it correctly in the cfg.

from ark-server-tools.

@Sispheor sorry I don't get what you mean, if we want the server to listen to the given port, we have to do math.

from ark-server-tools.

this is the latest issue before the 1.1 release.

on my machine everything seems good honestly.

from ark-server-tools.

I will test in a few minutes on my Ubuntu and I'll give you a feedback if it's ok

from ark-server-tools.

@Sispheor we are going to merge a PR which replaces lsof with netstat, probably is better wait for it before test.

from ark-server-tools.

I didn't use netstat because it seems to need root privilege to work. Are
you sure you can get the port as steam user with netstat?

2015-06-24 18:04 GMT+02:00 Fez Vrasta [email protected]:

@Sispheor https://github.com/Sispheor we are going to merge a PR which
replaces lsof with netstat, probably is better wait for it before test.

—
Reply to this email directly or view it on GitHub
#31 (comment)
.

Nicolas MARCQ

from ark-server-tools.

It works with non root user, but the output is very different from BSD to Linux, I'm waiting to see what @klightspeed will push.

By the way running netstat -taupen | grep 27016 you will get the ARK process, so it should work.

from ark-server-tools.

Nothing works

steam@nas:~$ arkmanager status
 Server running:   Yes 
Utilisation : grep [OPTION]... MOTIF [FICHIER]...
Exécutez « grep --help » pour obtenir des renseignements complémentaires.
 Server online:   Yes 
 Server version:   666499

I have a tooltip about the use case of grep (in french sorry) in the middle of the output.

And the script return the port is up. But no.

from ark-server-tools.

have you updated the configuration?

I had the same problem because my configuration was not updated (the port variable changed)

from ark-server-tools.

Yep, I've updated it. I work on a fix for this issue. PR incoming.

2015-06-24 21:12 GMT+02:00 Fez Vrasta [email protected]:

have you updated the configuration?

I had the same problem because my configuration was not updated (the port
variable changed)

—
Reply to this email directly or view it on GitHub
#31 (comment)
.

Nicolas MARCQ

from ark-server-tools.

Have you tested it? Ok for you @FezVrasta ?

from ark-server-tools.

@Sispheor

Netstat only needs root privileges to show all active connections.
Can be run on normal user - shows their active connections.

from ark-server-tools.