Server Health High after Update 12.0.18 #8

[Graphrix]

Since the update our Server Health has been very high and is playing up with email and probably other services.

OS CentOS 6.5 (Final)
Plesk version 12.0.18 Update #8, last updated at July 16, 2014 11:20 AM

The system is up-to-date; last checked at July 19, 2014 04:41 AM

Services !Problem
Disk OK
Memory OK
CPU !Problem
Network


This is the log from /var/log/plesk/health-alarm.log


##################################################

2014-06-24T10:01:15+11:00 INFO (6): Server health parameter "Services > Panel CPU usage" changed its status from "green" to "red".
2014-06-24T10:21:16+11:00 INFO (6): Server health parameter "Services > Apache CPU usage" changed its status from "red" to "green".
2014-06-24T10:21:16+11:00 INFO (6): Server health parameter "Services > nginx CPU usage" changed its status from "red" to "green".
2014-06-24T10:21:16+11:00 INFO (6): Server health parameter "Services > Mail server CPU usage" changed its status from "red" to "green".
2014-06-24T10:21:16+11:00 INFO (6): Server health parameter "Services > MySQL CPU usage" changed its status from "red" to "green".
2014-06-24T10:21:16+11:00 INFO (6): Server health parameter "Services > Panel CPU usage" changed its status from "red" to "green".
2014-06-24T10:21:17+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "red" to "green".
2014-07-02T11:56:51+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "red" to "green".
2014-07-02T13:02:47+11:00 INFO (6): Server health parameter "Services > Apache CPU usage" changed its status from "red" to "green".
2014-07-02T13:02:47+11:00 INFO (6): Server health parameter "Services > nginx CPU usage" changed its status from "red" to "green".
2014-07-02T13:02:47+11:00 INFO (6): Server health parameter "Services > Mail server CPU usage" changed its status from "red" to "green".
2014-07-02T13:02:47+11:00 INFO (6): Server health parameter "Services > MySQL CPU usage" changed its status from "red" to "green".
2014-07-02T13:02:47+11:00 INFO (6): Server health parameter "Services > Plesk CPU usage" changed its status from "red" to "green".
2014-07-02T13:02:47+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "red" to "green".
2014-07-18T10:06:02+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "red" to "green".
2014-07-21T12:59:09+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "green" to "red".
2014-07-21T13:19:11+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "red" to "green".
2014-07-24T05:24:34+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "red" to "green".
2014-07-24T05:42:03+11:00 INFO (6): Server health parameter "Services > Apache CPU usage" changed its status from "green" to "red".
2014-07-24T05:42:03+11:00 INFO (6): Server health parameter "Services > nginx CPU usage" changed its status from "green" to "red".
2014-07-24T05:42:04+11:00 INFO (6): Server health parameter "Services > Plesk CPU usage" changed its status from "green" to "red".
2014-07-24T05:42:04+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "green" to "red".
2014-07-24T05:52:05+11:00 INFO (6): Server health parameter "Services > Mail server CPU usage" changed its status from "green" to "red".
2014-07-24T05:52:05+11:00 INFO (6): Server health parameter "Services > MySQL CPU usage" changed its status from "green" to "red".
2014-07-24T05:57:06+11:00 INFO (6): Server health parameter "Services > Apache CPU usage" changed its status from "red" to "green".
2014-07-24T05:57:06+11:00 INFO (6): Server health parameter "Services > nginx CPU usage" changed its status from "red" to "green".
2014-07-24T05:57:06+11:00 INFO (6): Server health parameter "Services > Mail server CPU usage" changed its status from "red" to "green".
2014-07-24T05:57:06+11:00 INFO (6): Server health parameter "Services > MySQL CPU usage" changed its status from "red" to "green".
2014-07-24T05:57:06+11:00 INFO (6): Server health parameter "Services > Plesk CPU usage" changed its status from "red" to "green".
2014-07-24T05:57:06+11:00 INFO (6): Server health parameter "CPU > Total usage" changed its status from "red" to "green".




This is the log from /var/log/nginx/error.log
##################################################

2014/07/24 03:19:35 [emerg] 21095#0: open() "/var/www/vhosts/system/######.com.au/logs/proxy_access_log" failed (13: Permission denied)
2014/07/24 03:19:35 [emerg] 21095#0: open() "/var/www/vhosts/system/######.com.au/logs/proxy_error_log" failed (13: Permission denied)
2014/07/24 04:06:09 [error] 21095#0: *26932 connect() failed (111: Connection refused) while connecting to upstream, client: 203.45.176.192, server: roundcube.webmail, request: "POST /services/ajax.php/horde/topbarUpdate HTTP/1.1", upstream: "http://###.###.21.241:7080/services/ajax.php/horde/topbarUpdate", host: "webmail.######.com.au", referrer: "http://webmail.######.com.au/passwd/"
2014/07/24 04:07:09 [emerg] 1104#0: bind() to ###.252.21.243:80 failed (99: Cannot assign requested address)
2014/07/24 04:29:50 [error] 3609#0: *212 connect() failed (111: Connection refused) while connecting to upstream, client: #.###.253.60, server: ######.com.au, request: "GET /robots.txt HTTP/1.1", upstream: "http://127.0.0.1:7080/robots.txt", host: "www.######.com.au"
2014/07/24 04:29:52 [error] 3609#0: *212 connect() failed (111: Connection refused) while connecting to upstream, client: #.###.253.60, server: ######.com.au, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:7080/", host: "www.5.255.253.60.com.au"
2014/07/24 04:30:48 [emerg] 1081#0: bind() to ###.###.21.243:80 failed (99: Cannot assign requested address)

 

[IgorG]

Please check the following KB and let me know if it doesn’t help - http://kb.parallels.com/en/114245