I tested the worker bridge with the event MPM and it ran just fine, but
that could well be depending on the way the web server is being used
(meaning the workload structure can be critical)
What happens if you switch to the worker MPM? That would be a crucial
test...Also, what happens if you force the lazy bridge loaded?
-- Massimo
On 01/23/2018 04:27 PM, Georgios Petasis wrote:
Ok, I have changed MPM back to prefork, and I have changed my apache
configuration to:
<IfModule mpm_prefork_module>
LoadModule rivet_module modules/mod_rivet.so
RivetServerConf MpmBridge prefork
</IfModule>
<IfModule mpm_worker_module>
LoadModule rivet_module modules/mod_rivet.so
RivetServerConf MpmBridge worker
</IfModule>
<IfModule mpm_event_module>
Error "mod_rivet does not support the event mpm."
</IfModule>
And I think I am back to normal. And next time the OS changes the MPM, I
will get at least an error while loading apache...
Best regards,
George
Στις 23/1/2018 16:24, ο Georgios Petasis έγραψε:
I thought I was using worker, but now I see that Fedora 27 has
switched by default to event...
So, it is using event (which is a HUGE problem - tdbcmysql is NOT
multithreaded)
How can I check what mpm is rivet using?
George
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
