I upgraded from 6.x-2.2 to 6.x-2.4, and the count of anonymous users in my (plain, vanilla) who's online block kept rising (our avg is ~50, and this was 300+ before I disabled the module). I disabled the module, cleared my sessions table for uid=0 and all was normal again. I re-enabled the module the next day, and saw the same behavior (and no we haven't been slashdotted or anything; traffic is actually normal). One oddity: autologout is writing to the sessions field of the sessions table for uid=0, data like "autologout_hits|a:2:{i:0;i:1266075276;i:1;i:1266075323;}". Shouldn't autologout be ignoring sessions with uid=0? Thanks for insight.
AD

Comments

mygumbo’s picture

mygumbo commented

Noone else had this problem?

jvandervort’s picture

jvandervort commented

Not that we know of, but I don't know how many people that happen to use autologout also use the who's online block.
Give the latest dev snapshot a try and see if the issue changes. I think this may be related to
#342781: Notify logged out user what happened.

jvandervort’s picture

jvandervort commented
Status: Active » Fixed

Let me know...

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

yan’s picture

yan commented
Status: Closed (fixed) » Active

Same here with the anonymous user count in admin menu. It was usually ~20, after enabling the module it raised to ~100.

roball’s picture

roball commented

Also with v6.x-2.5? If so please increase the version in this ticket.

yan’s picture

yan commented
Title: Upgrade to 6.x-2.4 breaks count of anon users in who's online block » Wrong count of anon users in who's online block and admin menu
Version: 6.x-2.4 » 6.x-2.5
yan’s picture

yan commented

No ideas what could cause this?

johnennew’s picture

johnennew commented
Version: 6.x-2.5 » 6.x-4.x-dev
Assigned: Unassigned » johnennew

Not seeing this behaviour in 7.x-4.x - setting to 6.x-4.x to check there when other issues with block timer are sorted:

johnennew’s picture

johnennew commented
Status: Active » Closed (won't fix)

I am not seeing this behaviour in the 6.x-4.x branch either. Closing old issue - please reopen if you feel this is a problem in the supported 6.x-4.x or 7.x-4.x branches.