On 24.02.2013 10:56, jbarwick wrote:
> It actually makes perfect sense.
>
> This issue is related to the proxy not getting a response in a timely fashion from the "guest".
>
> This can be related to a variety of issues. VM latency, load, etc.etc. Each guest is different. And, I hope you don't have too many guests on a host else you could have some serious performance problems. If you don't know where your guest are physically located (which host), you could have a variety of network issues.
>
> On the proxy, I would increase the timeout values to handle cases where the guest is slow to respond (if you have access to the proxy config).
>
> Good luck.
The lag I get before being informed about the"internal server error" is
approximately 15 seconds, the same as the timeout of my pound proxy. And
I confirm, that the error message itself is produced by the pound, not
bugzilla! Thanks a lot, jbarwick!
Does it mean, that if I walk around the proxy by forwarding the port 80
from the guest into real world the problem will vanish? I guess so.
As I said before, the problem is solved with downgrade. But if anyone
here @ bugzilla is interested in troubleshooting the problem I am ready
to assist (I don't know how program in Perl though).
--
P.S.
Although the cause of the problem seems to move away from being entirely
on the bugzilla's side, I still don't understand one thing: my bug
database is small at the moment (only ca 80 bugs), and it never should
take more than half a second to process any request on such database.
And the pound have worked for us for years with the default timeout. I
think, that there is a second culprit inside bugzilla, that tries to
contact something nonexistent on the network. Maybe the problem was in
the fact, that the bugzilla was installed with different network setup
(other IP address) than it is working right now? But I did sudo
./
checksetup.pl, so even if that was problem it should have been fixed.