nagiosxi cookie

[eltrasimaco]

When browsing two nagiosxi instances (such as production and tests) , I get lots of session timeouts and, i suspect it has to do with the "nagiosxi" cookie, which overwrites last settings; is there any way to name this cookie in a "variable" fasion? (something like uname, or such)?
Thanks in advance

[tmcdonald]

Cookies should be tied to a specific domain, so unless you have your two XI servers on the same FQDN but different subdirectories, there is something else going on.

[eltrasimaco]

Actually, it's as you say, there are two nagios instances in the same domain, listening to different ports;I would be happy to know if there is any hint, trick or workaround, related to this subject.
Thanks!

[mcapra]

Separate domains is the W3C compliant (§2) way of handling this particular case. Separate paths would also be a W3C compliant solution, but I don't think it will work in Nagios XI.

Shy of a re-write of how Nagios XI handles persistence, I believe it's a limitation of mod_php in this particular case. I think you could use connection pools in FPM to work around this, but Nagios XI isn't tested/developed against FPM. You'd also need to be relatively familiar with how FPM works as I doubt there's a convenient HowToForge article for this particular case.

[tmcdonald]

We generally recommend against running XI on the same server as our other software, but we might not have anything published specifically for running two XI instances on the same server. The same advice would apply here though, you are going to see issues like this at the very least. It's not something we support, and would require a rewrite of XI as @mcapra mentioned.