We just upgraded our Vent to 3.0 and now we can't get a listing.

Anybody else having this problem?

I notice that it appears that the vent tracking thing is down at the moment. It's not a 3.0 thing, it's just an inconvenient timing. I'm looking into it right now.

--
It's all in the reflexes.

Yesterday, I was getting weird feedback, also.

It would show one person on the vent's root and no chans. The one person's name was "XXXXXXXXXXX" - no, we don't have a guildie w/ that sign-in.

Just to test, I downloaded the newest ventrilo_status program for linux (the officialy provided one) to test if the response was different between the old program and the new one (the responses were identical, so I guess the new protocol is somewhat backward compatible).

But this is the response I get:

./ventrilo_status -c2 -tv23.darkstarllc.com:26037
NAME: Inconclusive - Proudmoore
PHONETIC: Inconclusive
COMMENT: Ventrilo Server
AUTH: 0
MAXCLIENTS: 50
VOICECODEC: 3,Speex
VOICEFORMAT: 26,32 KHz%2C 16 bit%2C 4 Qlty
UPTIME: 397238
PLATFORM: Linux-i386
VERSION: 3.0.0
CLIENTCOUNT: 4
CLIENTFIELDS: ADMIN,CID,PHAN,PING,SEC,NAME,COMM
CLIENT: ADMIN=0,CID=176,PHAN=0,PING=70,SEC=7795,NAME=XXXXXXXX
CLIENT: ADMIN=1,CID=176,PHAN=0,PING=57,SEC=7793,NAME=XXXXXXXX
CLIENT: ADMIN=0,CID=176,PHAN=0,PING=14,SEC=5730,NAME=XXXXXXXX
CLIENT: ADMIN=0,CID=176,PHAN=0,PING=96,SEC=4779,NAME=XXXXXXXX

Those XXXXXX's aren't put there by me, those are what's in the response. I'm not sure exactly what this means yet, but I'm inclined to think that your host has some configuration different here than what was originally there.

I can look into this further, but one thing to note is that my own vent host also upgraded to 3.0 and mine has continued to run without a hitch.

--
It's all in the reflexes.