ReadPacket got an error
Posted: Fri Feb 27, 2004 6:49 am
Hi,
I'm new to Crossfire. I set up a 1.5.0 server on my Debian box and have been playing on my local network with a 1.5.0 gtk client. I have been using the old Apartment in Scorn and now am running into a situation where whenever I get close to the exit, the server cuts the connection, and I get logged out. The server messages are:
We have not sent item quiver (10043)
ReadPacket got an error.: Connection reset by peer
ReadPacket got error 104, returning 0
Received SIGPIPE, ignoring...
New socket write failed WTS (32: Broken pipe).
Write_To_Socket called with dead socket
make_path_tofile /home/mph/games/crossfire/var/crossfire/players/dev/dev.pl...
LOGOUT: Player named dev from ip 127.0.0.1
Waiting for connections...
my guess is that this "item quiver" is the culprit, but I don't know how it got there and what to do about it. Suggestions?
-mph
I'm new to Crossfire. I set up a 1.5.0 server on my Debian box and have been playing on my local network with a 1.5.0 gtk client. I have been using the old Apartment in Scorn and now am running into a situation where whenever I get close to the exit, the server cuts the connection, and I get logged out. The server messages are:
We have not sent item quiver (10043)
ReadPacket got an error.: Connection reset by peer
ReadPacket got error 104, returning 0
Received SIGPIPE, ignoring...
New socket write failed WTS (32: Broken pipe).
Write_To_Socket called with dead socket
make_path_tofile /home/mph/games/crossfire/var/crossfire/players/dev/dev.pl...
LOGOUT: Player named dev from ip 127.0.0.1
Waiting for connections...
my guess is that this "item quiver" is the culprit, but I don't know how it got there and what to do about it. Suggestions?
-mph