Fo pe EN verry slow on upgrade plesk 10 systems
Fo pe EN verry slow on upgrade plesk 10 systems
Ive change the title because i cant add a message with F O p-en in title. The forums blocks me for a while
It does work but over 20 seconds to get a small file.
Also posted on Parallels support forum, cause this is a urgetn problem for me.
On separate upgraded systems ive this problem.
Some crons use fopen to trigger some actions.
This always worked fine in psa 7,8 and 9.
Since ive upgrade from 9.3 to 10.1 fopen works extremely slow.
The cron / wget process still leave, so the maxclients was reached and apache crached serveral times now.
Does some one have a idea how to solve this, this problem is verry annoying for me.
Log files doest show any errors, just:
[Fri Dec 24 13:27:40 2010] [error] server reached MaxClients setting, consider raising the MaxClients setting
I use php-5.2.16-1.el5.art.
This is not the problem, on another server running same versions with plesk 9 no problem with fopen.
Also checked the resolv.conf. The nameservers are correct set. Same settings as the plesk 9 server.
Trace or ping works good.
It does work but over 20 seconds to get a small file.
Also posted on Parallels support forum, cause this is a urgetn problem for me.
On separate upgraded systems ive this problem.
Some crons use fopen to trigger some actions.
This always worked fine in psa 7,8 and 9.
Since ive upgrade from 9.3 to 10.1 fopen works extremely slow.
The cron / wget process still leave, so the maxclients was reached and apache crached serveral times now.
Does some one have a idea how to solve this, this problem is verry annoying for me.
Log files doest show any errors, just:
[Fri Dec 24 13:27:40 2010] [error] server reached MaxClients setting, consider raising the MaxClients setting
I use php-5.2.16-1.el5.art.
This is not the problem, on another server running same versions with plesk 9 no problem with fopen.
Also checked the resolv.conf. The nameservers are correct set. Same settings as the plesk 9 server.
Trace or ping works good.
Re: Fo pe EN verry slow on upgrade plesk 10 systems
This is very curious.
Is PHP running differently in 10 than in 9? (e.g. fastcgi or something)
What about the firewall? Could there be a problem there?
Maxclients increasing is particularly interesting, as I would not have thought that fopen would cause any issues here - but obviously it is.
Sorry not to have any ideas other than the above.
Is PHP running differently in 10 than in 9? (e.g. fastcgi or something)
What about the firewall? Could there be a problem there?
Maxclients increasing is particularly interesting, as I would not have thought that fopen would cause any issues here - but obviously it is.
Sorry not to have any ideas other than the above.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
Re: Fo pe EN verry slow on upgrade plesk 10 systems
Ive around 10 vpsses with exactly the same software.
Just plesk 9 and 10 are different. On the two ive upgrade this problem still is.
Increasing the maxclients only delay a crash, the fopen processes also cause a heavvy load.
I have turn off all fopen crontabs.
Ive checked logs, resolvers. Try fopen different domains, turn off firewall, still the same problem
Any idea would be verry welcome.
Thnx
Just plesk 9 and 10 are different. On the two ive upgrade this problem still is.
Increasing the maxclients only delay a crash, the fopen processes also cause a heavvy load.
I have turn off all fopen crontabs.
Ive checked logs, resolvers. Try fopen different domains, turn off firewall, still the same problem
Any idea would be verry welcome.
Thnx
Re: Fo pe EN verry slow on upgrade plesk 10 systems
After my final option (reboot) the problem looks solved. Now the fopen works fast withoud any config change.
I keep an extra eye on the problem server, if i find anything i will post it here.
Im happy the f-o-p-e-n-s are back. Thx, Bob
I keep an extra eye on the problem server, if i find anything i will post it here.
Im happy the f-o-p-e-n-s are back. Thx, Bob
Re: Fo pe EN verry slow on upgrade plesk 10 systems
It just solve the problem for a short time.
I still have problems with plesk 10.1.
Ftp doesnt work, and the fopen / apache crash problem still a live
[root@vps conf.d]# /usr/sbin/lsof -i | grep http | more
wget 1531 root 4u IPv4 318687324 TCP domains.nl:37708->domains.nl:http (ESTABLISHED)
httpd 5579 apache 79u IPv4 318704334 TCP vps.myserver.nl:46271->domain.com:http (SYN_SENT)
And 50 more processes like this
Ftp error in messages.log:
Dec 25 00:58:33 vps proftpd[24005]: Fatal: unknown configuration directive 'ClamAV' on line 1 of '/etc/proftp-asl.conf'
Also getting a lot of this:
Dec 25 01:00:20 vps named[19937]: network unreachable resolving '1.0.0.127.virbl.dnsbl.bit.nl/TXT/IN': 2001:7b8:3:1f:0:3:53:1#53
I still have problems with plesk 10.1.
Ftp doesnt work, and the fopen / apache crash problem still a live
[root@vps conf.d]# /usr/sbin/lsof -i | grep http | more
wget 1531 root 4u IPv4 318687324 TCP domains.nl:37708->domains.nl:http (ESTABLISHED)
httpd 5579 apache 79u IPv4 318704334 TCP vps.myserver.nl:46271->domain.com:http (SYN_SENT)
And 50 more processes like this
Ftp error in messages.log:
Dec 25 00:58:33 vps proftpd[24005]: Fatal: unknown configuration directive 'ClamAV' on line 1 of '/etc/proftp-asl.conf'
Also getting a lot of this:
Dec 25 01:00:20 vps named[19937]: network unreachable resolving '1.0.0.127.virbl.dnsbl.bit.nl/TXT/IN': 2001:7b8:3:1f:0:3:53:1#53
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
Re: Fo pe EN verry slow on upgrade plesk 10 systems
The Plesk upgrade probably reinstalled the Plesk version of psa-proftpd, which has no support for ClamAV. Reinstall the package from ART. I think a simple 'yum update' would offer that since ART's 1.3.3d is more recent than the version distributed by Plesk. (Or are they on 1.3.3d as well with Plesk 10?)bob83 wrote:Ftp error in messages.log:
Dec 25 00:58:33 vps proftpd[24005]: Fatal: unknown configuration directive 'ClamAV' on line 1 of '/etc/proftp-asl.conf'
Lemonbit Internet Dedicated Server Management
Re: Fo pe EN verry slow on upgrade plesk 10 systems
breun wrote:The Plesk upgrade probably reinstalled the Plesk version of psa-proftpd, which has no support for ClamAV. Reinstall the package from ART. I think a simple 'yum update' would offer that since ART's 1.3.3d is more recent than the version distributed by Plesk. (Or are they on 1.3.3d as well with Plesk 10?)bob83 wrote:Ftp error in messages.log:
Dec 25 00:58:33 vps proftpd[24005]: Fatal: unknown configuration directive 'ClamAV' on line 1 of '/etc/proftp-asl.conf'
Outline the 3 lines in /etc/proftp-asl.conf solve this. I used the latets asl version.
Remove 127.0.0.1 from resolv.conf solve the fopen problem. For some reason this entry makes trouble in plesk 10.
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
Re: Fo pe EN verry slow on upgrade plesk 10 systems
You mean you commented out the ClamAV statements? Yes, that will probably get FTP to work again as well, but you won't be using the latest version of ProFTPD with all security fixes and the ClamAV scanning integration provided by ASL.bob83 wrote:Outline the 3 lines in /etc/proftp-asl.conf solve this. I used the latets asl version.
Are you sure named was running and functioning correctly? Using a local resolver yields much better performance, so I'd recommend against this unless there really is no other way. I'd try a service named restart and using 127.0.0.1 in /etc/resolv.conf and seeing if you still have problems. (You could also fire some DNS queries at your local resolver using dig to see if it's functioning correctly.)Remove 127.0.0.1 from resolv.conf solve the fopen problem. For some reason this entry makes trouble in plesk 10.
Lemonbit Internet Dedicated Server Management
Re: Fo pe EN verry slow on upgrade plesk 10 systems
The fopen problem does now sound like a DNS issue. I'm wondering if the Plesk 10 upgrade has somehow broken the DNS config?
Regarding optimal configurations, what we do (and I'm not saying it is the best option) is to have 127.0.0.1, 208.67.220.220 and 208.67.222.222 in resolve.conf and then set 208.67.222.222 and 208.220.220 in the forwarders section in named.conf
The idea is that most lookups will be to the local DNS, but external lookups will be via the 222/220 Ips which are OpenDNS.com's.
Because we also have the OpenDNS servers in resolve.conf there will obviously be times when the system uses those instead of the local named even for local lookups but this is the way I prefer things to be - just in case: should named die then at least the system will still be able to use the OpenDNS servers, at least in theory.
Faris.
Regarding optimal configurations, what we do (and I'm not saying it is the best option) is to have 127.0.0.1, 208.67.220.220 and 208.67.222.222 in resolve.conf and then set 208.67.222.222 and 208.220.220 in the forwarders section in named.conf
The idea is that most lookups will be to the local DNS, but external lookups will be via the 222/220 Ips which are OpenDNS.com's.
Because we also have the OpenDNS servers in resolve.conf there will obviously be times when the system uses those instead of the local named even for local lookups but this is the way I prefer things to be - just in case: should named die then at least the system will still be able to use the OpenDNS servers, at least in theory.
Faris.
--------------------------------
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
<advert>
If you want to rent a UK-based VPS that comes with friendly advice and support from a fellow ART fan, please get in touch.
</advert>
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
Re: Fo pe EN verry slow on upgrade plesk 10 systems
I prefer to use 127.0.0.1 exclusively and monitor availability.
Lemonbit Internet Dedicated Server Management
Re: Fo pe EN verry slow on upgrade plesk 10 systems
Still weired.
If i add 127.0.0.1 as nameserver in resolv.conf f o p en is slow and apache crash.
[root@vps ~]# dig www.nu.nl
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> www.nu.nl
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38648
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;www.nu.nl. IN A
;; ANSWER SECTION:
www.nu.nl. 84820 IN CNAME gl.nu.nl.
gl.nu.nl. 30 IN A 62.69.184.21
;; AUTHORITY SECTION:
gl.nu.nl. 2020 IN NS gl2.nu.nl.
gl.nu.nl. 2020 IN NS gl1.nu.nl.
;; Query time: 9 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Dec 26 20:16:22 2010
;; MSG SIZE rcvd: 96
If i remove 127.0.0.1 from resolv.conf f o p en is working normal:
[root@vps ~]# dig www.nu.nl
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> www.nu.nl
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51879
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;www.nu.nl. IN A
;; ANSWER SECTION:
www.nu.nl. 20275 IN CNAME gl.nu.nl.
gl.nu.nl. 6 IN A 62.69.179.15
;; AUTHORITY SECTION:
gl.nu.nl. 2723 IN NS gl1.nu.nl.
gl.nu.nl. 2723 IN NS gl2.nu.nl.
;; ADDITIONAL SECTION:
gl1.nu.nl. 3178 IN A 62.69.179.251
gl2.nu.nl. 3178 IN A 62.69.184.251
;; Query time: 1 msec
;; SERVER: 83.149.80.123#53(83.149.80.123)
;; WHEN: Sun Dec 26 20:17:55 2010
;; MSG SIZE rcvd: 128
[root@vps ~]#
/etc/resolv.conf now looks like:
search vps.mycompname.com
#nameserver 127.0.0.1
nameserver 83.149.80.123
nameserver 85.17.150.123
nameserver 85.17.96.69
For info, proftp ans asl versions:
[root@vps ~]# rpm -q psa-proftpd
psa-proftpd-1.3.3d-1.el5.art
[root@vps ~]# rpm -q asl
asl-2.2.11-1.el5.art
If i add 127.0.0.1 as nameserver in resolv.conf f o p en is slow and apache crash.
[root@vps ~]# dig www.nu.nl
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> www.nu.nl
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38648
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;www.nu.nl. IN A
;; ANSWER SECTION:
www.nu.nl. 84820 IN CNAME gl.nu.nl.
gl.nu.nl. 30 IN A 62.69.184.21
;; AUTHORITY SECTION:
gl.nu.nl. 2020 IN NS gl2.nu.nl.
gl.nu.nl. 2020 IN NS gl1.nu.nl.
;; Query time: 9 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Dec 26 20:16:22 2010
;; MSG SIZE rcvd: 96
If i remove 127.0.0.1 from resolv.conf f o p en is working normal:
[root@vps ~]# dig www.nu.nl
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_5.3 <<>> www.nu.nl
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51879
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;www.nu.nl. IN A
;; ANSWER SECTION:
www.nu.nl. 20275 IN CNAME gl.nu.nl.
gl.nu.nl. 6 IN A 62.69.179.15
;; AUTHORITY SECTION:
gl.nu.nl. 2723 IN NS gl1.nu.nl.
gl.nu.nl. 2723 IN NS gl2.nu.nl.
;; ADDITIONAL SECTION:
gl1.nu.nl. 3178 IN A 62.69.179.251
gl2.nu.nl. 3178 IN A 62.69.184.251
;; Query time: 1 msec
;; SERVER: 83.149.80.123#53(83.149.80.123)
;; WHEN: Sun Dec 26 20:17:55 2010
;; MSG SIZE rcvd: 128
[root@vps ~]#
/etc/resolv.conf now looks like:
search vps.mycompname.com
#nameserver 127.0.0.1
nameserver 83.149.80.123
nameserver 85.17.150.123
nameserver 85.17.96.69
For info, proftp ans asl versions:
[root@vps ~]# rpm -q psa-proftpd
psa-proftpd-1.3.3d-1.el5.art
[root@vps ~]# rpm -q asl
asl-2.2.11-1.el5.art