I'm trying to set up a dedicated OFP Linux server. I've searched and haven't found an answer to the following question: What does
No entry 'config.bin.CfgAddons'.
mean?
Here's its context, in the log.2302.txt file:
WATCHDOG (2173): [Thu Feb 24 13:55:30 CST 2011] Starting server (port 2302)...
No entry 'config.bin.CfgAddons'.
13:55:31 Dedicated server created, memory used: 3900 KB
Operation Flashpoint Console version 1.96: port 2302 - Sockets
13:55:33 Server identity created
WATCHDOG (2333): [Thu Feb 24 14:47:27 CST 2011] Starting server (port 2302)...
No entry 'config.bin.CfgAddons'.
14:47:28 Dedicated server created, memory used: 3900 KB
Operation Flashpoint Console version 1.96: port 2302 - Sockets
14:47:29 Server identity created
I'm not sure that the log is providing all the info it's supposed to, btw. . .
Anyways, as always, any help will be appreciated. Thanks!
Thanks! I think I've figured out the cause (hat tip to the Great Overlord) - the message is gone, now. However, I still cannot get it to show up in the server list (I do have the gamespy line in the config).
It is a straight-up vanilla copy of fully-updated-to-1.96 OFP GOTY I'm using as the basis. I'll work on mods when I can get vanilla running.
Anyone know issues involved with getting a server to show up in GameSpy?
Yes, I have forwarded those ports, and a few others.
I'm thinking I'm going to have to hunt down some small animals for a ritual offering to some Finnish and Czech spirits to get this Linux and BIS love-child up and running. . .
This is the reason I put my server project back on the shelf. I could not get it to show on gamespy, but I only forwarded port 2302. After reading dengibtsschon's post I reconfigured my modem and opened a range of ports 2300-2400 and any protocol just in case. Well it still doesn't show. It did work with my basic dsl modem, but on my router/modem it's a bust.
Ok then. Check if you can you see your server with OFPWatch and if you can connect to it. From within your local network and from outside.
Nobody told if these things work already, so go check them.
Alright, I'm checking into these things. Thanks for the help!
No, there is no \ in the server name. The name is ATS.
Edit - Okay, from within the local network, I am unable to see the server w/ ofpwatch. I've been using both the 192.169.xx.x:2302 and the regular 76.xx.xxx.xx:2302 ip addresses, to see what works (hopefully, those are what are meant to be used for such a check).
I tried DirectPlay - no luck there.
I haven't been able to test outside the local network, yet.
As I proceed, I'll post what I'm seeing:
Terminal feedback Spoiler:
ofp@ofpserver:~/ofp$ ./ofpserver start
No file-names were converted
Starting OFP server...
ofp@ofpserver:~/ofp$ nohup: redirecting stderr to stdout
./ofpserver check
OFP directory: /home/ofp/ofp OK
Server executable: /home/ofp/ofp/server OK
Port number: 2302
Config file: /home/ofp/ofp/server.cfg OK
PID file: /home/ofp/ofp/ofp_server.2302.pid
RUN file: /home/ofp/ofp/ofp_server.2302.run
ofp@ofpserver:~/ofp$ ./ofpserver status
Server should be running...
PID file exists (PID=4980)...
Server process seems to be running...
ofp@ofpserver:~/ofp$
Log Spoiler:
WATCHDOG (4978): [Fri Mar 4 10:29:20 CST 2011] Starting server (port 2302)...
10:29:20 Dedicated server created, memory used: 4124 KB
Operation Flashpoint Console version 1.96: port 2302 - Sockets
10:29:21 Server identity created
WATCHDOG (5017): [Fri Mar 4 10:34:52 CST 2011] Starting server (port 2302)...
10:34:53 Dedicated server created, memory used: 4124 KB
Operation Flashpoint Console version 1.96: port 2302 - Sockets
10:34:54 Server identity created
#!/bin/bash
#
# ofpserver: Operation Flashpoint Linux dedicated server control script
# (c) 2003 BIStudio
# OFP binary version must be 1.92 or later!
#
#================================================= ======================
#======== CONFIGURATION PARAMETERS ========
#======== MUST BE EDITED MANUALLY TO FIT YOUR SYSTEM PARAMETERS ========
#================================================= ======================
OFP_DIR=/home/ofp/ofp
CONFIG=${OFP_DIR}/server.cfg
PORT=2302
PIDFILE=${OFP_DIR}/ofp_server.${PORT}.pid
RUNFILE=${OFP_DIR}/ofp_server.${PORT}.run
LOGFILE=${OFP_DIR}/log.${PORT}.txt
SERVER=${OFP_DIR}/server
#MODS=""
#================================================= ======================
case "$1" in
start)
if [ -f ${RUNFILE} ]; then
$0 stop
fi
cd ${OFP_DIR}
./tolower
echo "Starting OFP server..."
# file to mark we want server running...
echo "go" >${RUNFILE}
# launch the background watchdog process to run the server
nohup </dev/null >/dev/null $0 watchdog &
;;
stop)
echo "Stopping OFP server..."
if [ -f ${RUNFILE} ]; then
# ask watcher process to exit by deleting its runfile...
rm -f ${RUNFILE}
fi
# and terminate OFP server process
if [ -f ${PIDFILE} ]; then
kill -TERM $(< ${PIDFILE})
if [ -f ${PIDFILE} ]; then
rm -f ${PIDFILE}
fi
fi
;;
status)
if [ -f ${RUNFILE} ]; then
echo "Server should be running..."
else
echo "Server should not be running..."
fi
if [ -f ${PIDFILE} ]; then
PID=$(< ${PIDFILE})
echo "PID file exists (PID=${PID})..."
if [ -f /proc/${PID}/cmdline ]; then
echo "Server process seems to be running..."
fi
fi
;;
check)
echo -n "OFP directory: ${OFP_DIR} "
if [ -d ${OFP_DIR} ]; then
echo "OK"
else
echo "MISSING!"
fi
echo -n "Server executable: ${SERVER} "
if [ -x ${SERVER} ]; then
echo "OK"
else
echo "ERROR!"
fi
echo "Port number: ${PORT}"
echo -n "Config file: ${CONFIG} "
if [ -f ${CONFIG} ]; then
echo "OK"
else
echo "MISSING!"
fi
If you need someone to test from outside, i can help. Just need your server's external IP.
Edit:
If you don't even see the server from within the local network, don't bother trying from outside, it won't work as well.
Looks like there's a firewall (like iptables) installed on the server machine which blocks incoming connections
Last edited by dengibtsschon; Mar 4 2011 at 16:35.
Looks like there's a firewall (like iptables) installed on the server machine which blocks incoming connections
Ok, I did a little more research - it looks like Ubuntu doesn't establish a firewall upon installation, but ports remain closed until specifically opened (different from port forwarding, if I'm understanding this correctly).
I've found a command for opening ports:
iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport (replaced with my port) -j ACCEPT
Should I use this, replacing tcp w/ udp and doing it for ports 2302 and 2303?
Edit: I've learned about ufw and have tested opening 2302 and 2303. Doesn't seem to have worked. Any advice on this? I've disabled ufw for the time being (hadn't been enabled earlier, when I started working on this stuff today). Thanks, again, for the help.
Hopefully, I'm not making things worse!
Edit: I opened udp 2302 and 2303. Here's what iptables -L produces: