Bug Vboptimise issue when enabling with VBSecurity

[Mick]

Hi Fillip H.,

My server is nginx, php-fpm/fastCGI (I have read a few issues with fastCGI)

I have a small issue which happens only when I enable VBoptimise.

Ok even though I have read the 2nd login does not work with FastCGI - it actually does work for me somehow, it works very well infact and I have emailed the admins there passwords and they have all confirmed it works too.

However the issue I have is as soon as I enable VBOptimise the login works but it will just keep asking for the login if you try to SAVE anything ?

But with VBoptimise off, I login with the 2nd login and everything works fantastic!

I really need both of these working, as your vboptimise saves my forum like 4-5 million queries a day!!!

Thanks Fillip H. for any advice or help

Mick

 

[Mick]

Small update,

This seems to be an Xcache issue.

I changed it to file cache because all php files get picked up by xcache anyway...

But when on filecache it is working fine, not really sure if I should worry about it or not as I believe xcache will cache the php files anyway???

Regards
Mick

 

[Fillip H.]

Well, even with XCache caching files Filecache's gonna be less efficient than XCache, as you're still dealing with disk I/O rather than reading from and writing to RAM.

We can't support the Password Auth system on FastCGI for the same reason why opcode cachers like XCache don't work properly: It's a stateless system, where each process is completely oblivious to the previous ones.
It's like after each page load, you restart Apache, that's a simplified way of looking at it.

 

[Mick]

Just to satisfy my curiosity as I am not sure how it works 100%

I thought that VBoptimise would write the files to disk (FIleSystem) but once written then xcache would then store them in memory until the TTL?

I completely understand that written direct into memory would be better of course!

I think I will enable memcached (I have it installed) if that would be a better option

Mick

 

[Fillip H.]

From my understanding, the files are still read in order to determine whether they've been changed. I could be wrong, I've not done extensive research into this as the Filecache option was only really designed for people that does not have the ability to alter their server configuration to use a "proper" opcode cacher

To be honest I think you'd get a gain in performance switching to DSO+APC over FCGI+Memcache, but that varies greatly on a server-by-server basis so you might want to run some comparison tests on your system

 

[Mick]

Hi Fillip H.,

Thanks for the reply that actually makes allot of sense, I only ask these things to increase my knowledge (not to be a pain lol)

Anyway I managed to get it to work in turned on the feature:

Alternate Flushing

But I am not sure that it is a good idea to carry on with xcache now?

Regards
Mick

 

[Fillip H.]

To be honest I've no experience running XCache under FastCGI (other than the fact that it flat out didn't work for us so I gave up, and switched to APC & DSO ) so I can't say

 

[Mick]

I just installed APC which is running fine with FastCGI.

Both Products are now working together with no issues.

Regards
Mick

 

[andrewsimm84]

So you got the second login to work with fastcgi? I run Apache + Nginx, APC, Memcahce and use FastCGI and I can not get it to work.