Its a local webserver on our LAN.
IE appears to be set properly... I have no other problems like this on other servers or sites.
Then entire site works fine and loads, its just after apache has ran awhile it gets worse and worse until the point it times out and/or never loads.
Nothing really in the apache logs at all... there is some SSL error logs about the CN being set to localhost.localdomain... but im not using SSL.
I also still do not have mod_perl running and cannot figure it out.
Ive tried running it in conf.d/perl.conf and/or otrs.conf.
I have apache setting the documentroot to /opt/otrs/bin/cgi-bin to make it the default page and no virtual hosts.
I have tried setting this in otrs.conf and keeping the default settings for mod_perl, but when I try the "test" to see if mod_perl is running
" /index.pl?Action=foo " to see in the error if it says its being ran by mod_perl, it is not...
Everything seems to work just fine, its just HORRIBLY slow and I cannot figure out why.
The system (cpu, ram, swap) is all fine and idle, the server has plenty of throughput... its gotta be mod_perl, apache, etc..
________________________________
From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Steve Morrey
Sent: Tuesday, March 11, 2008 2:37 PM
To: User questions and discussions about OTRS.org
Subject: Re: [otrs] Apache settings (besides mod_perl) to make OTRS run faster.
Might want to check for proxy and caching before you worry about apache settings.
Some ISPs will cache page data to "make it load faster", however with the dynamic nature of OTRS pages, this is ineffective and can actually slow things down.
The other thing to check is in the browser(s) that you are using.
Make sure you DO have at least 50-100MB of cache space set aside for internet usage.
Your browser will then load the cached images from the hard-drive, rather than request them from the server.
One way you can check to see if the images are being requested at each view or if they are being cached by the ISP's proxy servers is to locate your apache access logs and look to see if the same images are being requested by the same IP addresses frequently.
Finally one other thing that can slow you down, are simple stupid permissions errors, they may be something minor like a piece of javascript not having the perms set correctly.
The easiest way to check for this would be to look in your apache error logs and see what errors are popping up.
If apache has no errors it will tend to run 2-3 times faster than it will with even only a couple of relatively minor errors.
This is because each request will generate at least one and possibly 2 entries, an access entry and an error entry.
Some requests may happen 4 or 5 times for a single page load. If you can eliminate the error entry (by solving the error), you could see a dramatic speed up.
Sincerely,
Steve Morrey
On 3/11/08, Nielson, Adam