Users get logged in as someone else

[TommyBoi]

Hi,

I am running vbulletin 4.2.2 patch level 4. Encountering these two issues:

1. Sometimes a user becomes logged in as another user. Say I login to vbulletin but instead of showing my name in the top right corner, its showing another registered members name! I have had a few users complain about this (also have a screenshot if someone wants to see). This is an urgent problem!


2. Cant see the last couple of replies in active threads. I can see that someone has replied to the thread and that the thread has 30 replies but when I browse the thread its only showing the first 25 replies. This is happening quite often, I tried clearing the system cache and rebuilding thread info but no luck. One thing that seems to work sometimes is changing the number of posts that I see per page, in my usercp. This only seems to fix the issue temporarily though.

Is these any fix to these issues?

Regards.

[Guest]

It seems that this could be webserver related. On what type of server is youer forum running? For example on IIS (Microsoft) incorrect settings for the 'Output Caching' will result in mix ups: suddenly you are another user, posts disappear and so on.

[TommyBoi]

Its a LAMP server.

[Guest]

I think you need to look at server side caching issues. Exclude caching php outputs to begin with.

[Wayne Luke]

Are you using a proxy server?

[TommyBoi]

No I am not using any proxy, and php caching is already off. I spoke to my host and he says the server has something called ramcache.

[Guest]

Big chance that the 'ramcache' is causing the issues.

[TommyBoi]

Like I said its not caching PHP. Wayne, do you have any solution for this?

Btw you can ignore the second issue, it was caused by my browser caching the thread (no idea why it would cache php tho).

[Guest]

It only can be related to caching. Because it mixes up php outputs. The server reuses php output from other users, this isn't something vBulletin does.

BTW did he mention MemCached perhaps?

Correct me if I'm wrong Wayne.

[Wayne Luke]

Turn off the ramcache for 24-48 hours. It is probably acting as a psuedo-proxy server and preventing each user from seeing the results of their own execution. See if the issue continues.