XF 2.2 Members Online dropping to zero

[Global96]

Hi I consistently have 60+ online. Just today it has begun dropping to 0, then rising to over a hundred in minutes. I have no idea what's going on.

 

[Chris D]

I've moved this out of bugs for now as I'm pretty sure it isn't one.

The online statistics come from the session activity table. There isn't really any expectation for this to drop to zero.

Disabling all add-ons to see if the issue persists may be worthwhile but currently looking at the site on your license it seems to be working fine so it might be worth just keeping an eye on it and see if you notice any pattern and keep us updated.

 

[Global96]

I've moved this out of bugs for now as I'm pretty sure it isn't one.

The online statistics come from the session activity table. There isn't really any expectation for this to drop to zero.

Disabling all add-ons to see if the issue persists may be worthwhile but currently looking at the site on your license it seems to be working fine so it might be worth just keeping an eye on it and see if you notice any pattern and keep us updated.

I've had the exact same add-ons for a while now. It just suddenly happened yesterday. For some reason I feel like the solution probably involves a cron job.

 

[Global96]

Looks like a MySQL database repair may have fixed it. Will update it later when confirmed.

 

[Global96]

Nope, it's happening again.

 

[mjda]

It could be that your server is rebooting for some reason. I know any time my server reboots my online stats reset too.

 

[Global96]

It could be that your server is rebooting for some reason. I know any time my server reboots my online stats reset too.

Yep, it's confirmed!

 

[Masetrix]

Yep, it's confirmed!

The format of the xf_session_activity table is memory.
If you convert this table to Innodb, the contents are retained even after a restart.

However, you seem to have a memory error that should first be fixed by replacing the memory modules.

 

[Global96]

The format of the xf_session_activity table is memory.
If you convert this table to Innodb, the contents are retained even after a restart.

However, you seem to have a memory error that should first be fixed by replacing the memory modules.

Restarted Apache, that fixed the memory issue!

 

[Masetrix]

Restarted Apache, that fixed the memory issue!

With this error description I'm very sure that Apache was only the symptom, but the actual error lurks in the background until the faulty memory area is used again. In that case it was even lucky that the error only affected an in-memory table.