[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 257
  • Last Modified:

Plesk 8.2 VPS continuously stops serving HTTP for 20-30 seconds.

We are having some problems with Plesk on Virtuozzo.

Plesk 8.2
Red Hat 5 64

Virtuozzo 3.0 sp1
Red Hat 4 64

Every 15-30 minutes or so I get a dns error when surfing either the control panel or a website running from the plesk box.  I can't seem to see any traces to what would cause this in the logs.  During this 20 second or so "outage" I am still able to ping the machine and remain SSH connected to the VE.  Basically I cann't load an web page or refresh the current page for about 20 seconds or so then all seems normal after that.  No logged events, system does not reboot, apache does not go down.  

Plesk runs its own Apache build independant of the ones serving domains under plesk, so I can't believe it is an apache problem.  

Any suggestions?
0
CharlieBeBop
Asked:
CharlieBeBop
1 Solution
 
Kamran ArshadCommented:
Hi,

Is there any load on the server. You can increase the VM value as well as other parameters. Also open a ticket with Plesk.
0
 
CharlieBeBopAuthor Commented:
0.00 load on a quad core process with 15k drives and 4GB of ram, I allocated 2048 ram to the VE and burstable to 4GB, as well as 1/3rd of the CPU guarantee, with max being the limit.

I don't have a current support contract with plesk, I'm about to open a ticket if i can't find the solution, luckily there really isn't anything on the server, but it is delaying getting it launched.
0
 
mhgromCommented:
It may be worth running top on both the VE and the Hardware node and as soon as you get the freeze have  a look at what is running.

I wouldn't think it is a DNS error as your browser would still be ok as it keep the IP address is record.  I am guessing your browser is getting a timeout.

I saw this problem on one of our servers and it turned out to be a hard disk controller.  It would freeze up for around 30 seconds and no data could be read from the hard disk.  Applications would continue operating and the data would be returned after the freeze was over.  However during the freeze some applications will time out the read request...

To check it is not a hard disk problem,  when it freezes open a file via ssh,  for example
cat /etc/hosts
If you can read the file it is not a hard disk freeze.

Can you create another VPS with no software installed except the base linux and apache?  Assign it another IP and enter this in your browser.  When the main VE freezes check to see if the new one does as well.  This would help either rule out a hardware node problem or confirm it.

0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now