DragonFly bugs List (threaded) for 2004-04
This is one of those things that has got to be a trivial fix if only
we can isolate the actual system call that is failing.
Is is something that started recently or has it never (or not for a long
time) worked on DragonFly?
If this is running under linux emulation then try using 'ktrace -i'
to run the server and record a failed connection attempt from the client.
You should be able to use /usr/ports/devel/linux_kdump to dump the ktrace
output (for linux compatibility mode the normal 'kdump' will produce
I'm guessing it's a bug that was introduced in the linux syscall
separation work or something minor in Jeff's networking work, but
we need just a tad more information to track it down.
The output is likely going to be a lot, so don't post it, instead put it
up somewhere and post the ftp/http URL that we can fetch the dump from.
:Just so you know; You're not alone.
:I had this exact same problem when I was setting up ~16 gameservers for a
:gamecompo in q3. I wanted to use DragonFly but I got that error all the
:Never found a solution..
:> won't run under DragonFly? It uses Linux compatibility, starts OK but when
:> a client tries to connect the server logs:
:> NET_SendPacket ERROR Protocol not available to xxx.xxx.xxx.xxx:27960
:> where xxx.xxx.xxx.xxx is the IP address of the client that tries to
:> Under FreeBSD 4.9 everything runs fine.