It sounds like you might have some database corruption, basically  
bogus entries that aren't really still online, but still exist in the  
DB.  You might have to bite the bullet and clear everybody in order  
to get back to a known state.

Of course, it could also be a problem with the CCA code.

Michael Grinnell
Network Security Administrator
The American University


On Apr 19, 2007, at 9:14 AM, Kyle Evans wrote:

> This past weekend, there was network maintenance here that caused a  
> lot
> of communication trouble between the CAM and the CASes.  Since then
> we've had trouble with login sessions not timing out properly after
> their time is up.  If we try to delete somebody out of online users  
> who
> is supposed to have expired, it just does not work.  We allow a  
> login to
> last a week, and we don't use the heartbeat timer to time users out.
> This issue only arises with some CASes but not all CASes.  A strange
> error started showing up in perfigo-log0.log.0 this week too:
>
> SEVERE: AC - getRoamingHostTable: Invalid remote object!!
> Apr 16, 2007 6:49:31 PM com.perfigo.wlan.web.admin.AccessConf
> getRoamingHostTable
>
>
> This error shows up if you search online users or if you try to delete
> someone out of online users.  We do not have roaming enabled.
>
> Anybody have ideas?
>
>
> Kyle