Plesk slow! big pain

[IG0R]

Hi,

I recently upgraded one of my servers to the last plesk version 7.6.1 and my problemas started.


1.
I made a full backup of my sites using the plesk utility, everything is fine at this time..

2.
I get a new server Pentium 4 3.4 HT 1gb ddr, with a fresh install of plesk 7.6.1

3. I started the plesk restore of my old backup from plesk 7.5.6 ( 400 sites)

This process take almost 2 ( TWOOO DAYS ) to setup my plesk from .psa backup

I lost some clients.. but ok .. i think that this is the only problem.


Now i see that the new plesk is very slow to add and remove new sites. When i try to add, remove or modify one website i saw the process list the process dnsmng.exe taking minutes and minutes to process the operation. This happened too when i was restoring my websites.


What can i do to improve the dnsmng.exe performace and get my plesk running good like when he was the old version ??

Thank you everyone

 

[Skeeter]

To improve the DNSmng performance, you should go to Plesk -> Server -> Components management and switch to Bind DNS. If it is not installed, you can go to Add/Remove programs -> Plesk -> change-> modify -> DNS management and add the Plesk DNS server (bind)

We are working on investigating the problem with slow DNS performance with MSDNS.

 

[Bogdan]

I'm having a similar issue on a server, but it's caused by websrvmng.exe.

The server is a Windows Server 2003 x64 and whenever anyone uses websrvmng to add domains, hosting or change any hosting settings, it takes about 3 minutes for the command to execute and it takes abou 20-30% CPU time when running.

The server is a dual opteron with 2GB DDR2 and about 100 small domains on it. It has been running Plesk 7.6.0 when I set it up, and it worked fine, but after I upgraded to 7.6.1 websrvmng got very very slow. Except this, the server works like a charm, including Plesk.

I run several other Plesk 7.6.1 servers, both x64 and x86 which were upgraded in the same way, but none of them are behaving like this.

The bad thing here is that I don't have the slightest idea what can cause this problem and how to torubleshoot it. I tried running wbsrvmng from the command line to add domains or change hosting settings and runs just as slow.

If anyone has any suggestions...

 

[Skeeter]

Actually, you can do the following:

1. Run websrvmng --remove-all

2. After it finishes, run
websrvmng --reconfigure-vhost --vhost-name=<domain-name>

for each website (do not run reconfigure-all, if it fails, you`ll have to reconfigure all domains again)

Most of the time, complete reconfiguration resolves the problem.

Please, note, that your websites will be offline during this reconfiguration.
For your 100 domains reconfiguration should take approx 1-1,5 hour.

If you get any errors, they will most probably be related to some missing folders, you would need to recreate the folders and run websrvmng again to create the website. You can use reconfigurator /check-permissions=<domain-name> to recreate folders.

 

[Bogdan]

Skeeter,

Reconfiguring the vhosts will not do any good! The IIS metabase is fine and is in sync with the settigs from the PSA database. The only problem I have is that when I run websrvmng, it runs very very slow.

 

[ataab]

Originally posted by Bogdan
Skeeter,

Reconfiguring the vhosts will not do any good! The IIS metabase is fine and is in sync with the settigs from the PSA database. The only problem I have is that when I run websrvmng, it runs very very slow.

What i have learned, "websrvmng calls dnsmng (or some thing like that, while using microsoft DNS) and that causes it to hang or go damn slow." I have been monitoring the process colsely, and it will hang when it comes to dnsmng.

 

[mattridings]

One of the things we've noticed from the Plesk control panel that really slows things down is when modifying sites with frontpage support turned on. When we trace out the server processes it seems that it's hanging for a while on the frontpage processes.

-matt

 

[Bogdan]

I switched to BIND on one of 7.6.1 servers hoping this will finally solve our problem... but with no luck.

Plesk is extremely fast except when it has to call on websrvmng, but unfortuantely this is not helping at all, especially with new clients who lose their confidence is us from day one after they spend 10 to 15 minutes setting up a new domain.

I'm not sure how this is affecting your business, but personally, I am sick and tired of losing new clients because of this damn thing, and not being to do anything about this!

Apparently, everytime SWsoft releases a new Plesk version, we install it to get rid of old bugs and we come across new ones!

SWsoft really needs to fire their project manager for Plesk, as he doesn't seem to know anything about application development lifecycle.

 

[Webplus]

I use MS DNS, and I feel Plesk is very slow.
When creating new mail accounts, Plesk sometimes is veeeery slow!!

Another strange thing is that I'm having some DNS Bad Gateway erros on some domains.

If I change to BIND, it will work better?
The "bad gateway" is associated with MS DNS? What do you think?

If you answer yes to all question, I can change to BIND, and BIND will be configured with all settings of MS DNS (all domains DNS will be auto-configured on BIND)?

Thank you.

 

[Webplus]

Sorry, I'm getting Gateway Timeout, and not Bad Gateway.

 

[adrianodalpra]

I did change MS-DNS to BIND and have no success either.

Plesk still slow on websvrmng.exe process using MS-DNS or BIND DNS.

After checking that I reverted to MS-DNS.

Adriano.

 

[Webplus]

Why didn't you keep the BIND running?

MS-DNS is better?

 

[adrianodalpra]

Hi,

I think Microsoft software is better running on a Windows Server.

It has some advantages:

1) Patches are applied automatically by Microsoft Update
2) There is a graphical interface for MS-DNS
3) MS-DNS is part of Operating System

I just changed to BIND to try the solution for Plesk. Without success I reverted to MS-DNS.

Adriano.

 

[mattridings]

I definitely like working with the microsoft interface better since I'm proficient with it.

However, depending upon your circumstances the big problem with microsoft dns is that recursive dns is either on, or off. But if it's on it's open to everyone. That's a big problem for some of us.

-matt