Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Terminated
Stopping server, it is restarting too quickly.
rm: ne peut enlever `/var/run/armagetronad-dedicated-starter.pid': Permission no
n accordée
rm: ne peut enlever `/var/run/armagetronad-dedicated.pid': Permission non accord
ée
Last edited by epsy on Thu Nov 09, 2006 10:31 pm, edited 2 times in total.
How did you build and install? Did you start from a binary or the source? On first glance, it seems like it is a client pretending to be a server; a yet unknown build error could cause that.
Options selected are:
Build Regular Game Client: false
Build Dedicated Server: true
Build Master Server: false
Installation options:
Prefix: /usr/local
Build with Krawall authentication support (server): no
Init scripts will be installed in : /etc/init.d
Dynamic data will be kept in : /var/games/armagetronad-dedicated
PID files will be kept in : /var/run
Log files will be kept in : /var/log
Add user to run server : yes
Binaries will be installed in : ${prefix}/bin
Static data will be installed in : ${prefix}/share/games/armagetronad-ded
icated
Configuration will be installed in : ${prefix}/etc/games/armagetronad-dedic
ated
Documentation will be installed in : ${datadir}/doc/games/armagetronad-dedi
cated
Link to configuration will go to : /etc/armagetronad-dedicated
Music support: no
Build with Krawall authentication support: no
Use dirty SDL initialization: no
Call sysinstall: yes
Generate uninstall: yes
Allow multiple versions: yes (slot "0.2.8.2.1")
Use custom memory manager: no
Debug level: 0
Code level: 0
cat /var/log/armagetronad.log
/var/games/armagetronad-dedicated /home/epsy/armagetronad-0.2.8.2.1
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Not sure, I never knew about the --enable-multiver switch, it could be that it broke over time and noone noticed.
Could you try without it and just use --prefix if you need multiple versions?
And please post the contents of the file config.h in your build directory. Something very strange is happening for you. I tested your exact configure command line and nothing unusual happened.
Another thing to try: in your server build directory, do
Ok, the important line there is the "#define DEDICATED", that should disable the graphics. Unless for some reason another config.h is included instead. Could you, in the build directory, do
make
make all-recursive
make[1]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1'
Making all in src
make[2]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/src'
Making all in first
make[3]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/src/first'
make[3]: Rien à faire pour « all ».
make[3]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/src/first'
Making all in doc
make[3]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/src/doc'
Making all in net
make[4]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/src/doc/net'
make[4]: Rien à faire pour « all ».
make[4]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/src/doc/net'
make[4]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/src/doc'
make[4]: Rien à faire pour « all-am ».
make[4]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/src/doc'
make[3]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/src/doc'
Making all in thirdparty
make[3]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/src/thirdparty'
make[4]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/src/thirdparty'
make[4]: Rien à faire pour « all-am ».
make[4]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/src/thirdparty'
make[3]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/src/thirdparty'
make[3]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/src'
make[3]: Rien à faire pour « all-am ».
make[3]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/src'
make[2]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/src'
Making all in resource
make[2]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/resource'
make[2]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/resource'
Making all in batch
make[2]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/batch'
make[2]: Rien à faire pour « all ».
make[2]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/batch'
Making all in config
make[2]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/config'
make[2]: Rien à faire pour « all ».
make[2]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/config'
Making all in desktop
make[2]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1/desktop'
make[2]: Rien à faire pour « all ».
make[2]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1/desktop'
make[2]: Entering directory `/home/epsy/armagetronad-0.2.8.2.1'
make[2]: Rien à faire pour « all-am ».
make[2]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1'
make[1]: Leaving directory `/home/epsy/armagetronad-0.2.8.2.1'
or you want that i make clean before?
I wonder where the /* eeehhhh???? -> */ comes from. It's not in the 0.2.8 sources I've got.
i was just surprised because it's saying i dont have the standart libs...
did you enter the touch command? The intent of the make invocation would have been to get the actual compilation flags so we can see where files are included from. If touching doesn't help, yes, please do a make clean.
And the purpose of the locate command was to get a list of all config.h files that may have been included. I didn't realize the list could get that long Since you obviously know what you're doing, could you do the check yourself? Look for the -I compiler flags in the make output and look for config.h files there.
Another thing to try: look for a random #ifndef DEDICATED block in the sources and add an error in there. Check whether it compiles. In a working setup, it should; for you, if everything we think we know actually is true, it should fail.
[0] sn_SetNetState: can't setup listening sockets. Reason given:
[0] Permanent network error: Unable to bind to 82.227.65.72:4534 because that is not an address of the local machine.
you can try to connect to it...it works... but he shjows me that warning
Ah, starting from scratch fixed it? I just remembered that the 0.2.8.1 tarball doesn't ship with dependency tracking by default, so if you configure your build directory first for the client, then build, then reconfigure for the server, it won't get done properly.
To the problem at hand, you can either ignore it, or look for appearances of SERVER_IP in your config files. Remove them, they are only required if your server can listen to multiple IPs and you want to select a specific one.
Another possible reason, although I don't think AA is affected by it any more, could be a strange name configuration. At least in the past, AA would try to bind to whatever IP $HOSTNAME resolved to. So $HOSTNAME should resolve to your server's IP.