Backupmng CPU high load

[Micm_welker79]

Hi forum,

since the upgrade to Plesk 9.3 I've a problem with the Backup Manager. Every time I start a scheduled backup to the server repository, the CPU get a high load from 99,8% and the backupmng hangs up. On the console you can see, that there was a broken pipe for the backup job.
Following steps I test before I start a thread:
- remove and reinstall psa-backupmanager. --> nothing changes
- check the disk space in /var/lib/psa/dumps. --> there're 5 GB free space and I need only 150MB for a backup
- install newest versions of perl and python.

Does anyone have other ideas??

Greets,
Michael

 

[IgorG]

Need more details. Did you tried to find a most of hardloaded process during backup procedure?

 

[Micm_welker79]

actually Load during backup-process

ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 1868 652 ? Ss Feb07 0:00 init [2]
root 17470 0.0 0.0 1556 588 ? Ss Feb07 0:00 /sbin/syslogd
bind 17485 0.0 0.1 36328 2768 ? Ssl Feb07 0:00 /usr/sbin/named -t /var/named/run-root -c /etc/named.conf -u bind
root 17557 0.0 0.0 2600 1332 ? S Feb07 0:00 /bin/sh /usr/bin/mysqld_safe
mysql 17601 0.0 1.1 127048 23696 ? Sl Feb07 0:05 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/r
root 17602 0.0 0.0 1480 504 ? S Feb07 0:00 logger -p daemon.err -t mysqld_safe -i -t mysqld
root 17681 0.0 0.0 4172 744 ? S Feb07 0:00 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -std
root 17683 0.0 0.0 2964 716 ? S Feb07 0:00 /usr/sbin/courierlogger imapd
root 17693 0.0 0.0 4172 744 ? S Feb07 0:00 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -std
root 17695 0.0 0.0 2964 716 ? S Feb07 0:00 /usr/sbin/courierlogger imapd-ssl
root 17708 0.0 0.0 4172 760 ? S Feb07 0:00 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -std
root 17710 0.0 0.0 3096 868 ? S Feb07 0:00 /usr/sbin/courierlogger pop3d
root 17731 0.0 0.0 4172 744 ? S Feb07 0:00 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -std
root 17733 0.0 0.0 2964 716 ? S Feb07 0:00 /usr/sbin/courierlogger pop3d-ssl
root 17752 0.0 0.0 8752 972 ? Ssl Feb07 0:00 /usr/sbin/nscd
root 17778 0.0 0.0 2324 780 ? Ss Feb07 0:00 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive
root 17873 0.0 2.0 44968 41132 ? Ss Feb07 0:01 /usr/sbin/spamd --username=popuser --daemonize --nouser-config --helper-home-dir=/var/q
popuser 17929 0.0 1.9 44968 39996 ? S Feb07 0:00 spamd child
qmails 17971 0.0 0.0 1540 388 ? Ss Feb07 0:00 qmail-send
qmaill 17973 0.0 0.0 1492 456 ? S Feb07 0:00 splogger qmail 2
root 17974 0.0 0.0 1524 352 ? S Feb07 0:00 qmail-lspawn | /usr/bin/deliverquota ./Maildir
qmailr 17975 0.0 0.0 1520 360 ? S Feb07 0:00 qmail-rspawn
qmailq 17976 0.0 0.0 1488 332 ? S Feb07 0:00 qmail-clean
root 18053 0.0 0.6 34164 13192 ? Ss Feb07 0:03 /usr/sbin/apache2 -k start
www-data 18054 0.0 0.1 18768 2224 ? S Feb07 0:00 /usr/sbin/apache2 -k start
www-data 18060 0.0 0.5 36284 11948 ? S Feb07 0:07 /usr/sbin/apache2 -k start
10004 18109 0.0 0.0 4772 1872 ? S Feb07 0:00 /usr/sbin/sw-cp-serverd -f /etc/sw-cp-server/config
root 18152 0.0 0.0 4948 880 ? Ss Feb07 0:00 /usr/sbin/sshd
daemon 18212 0.0 0.0 1964 308 ? Ss Feb07 0:00 /usr/sbin/atd
root 18222 0.0 0.0 2136 680 ? Ss Feb07 0:00 /usr/sbin/cron
www-data 30327 0.0 0.5 36296 11920 ? S Feb07 0:04 /usr/sbin/apache2 -k start
root 17900 0.0 0.7 18336 15264 ? SN 08:11 0:00 /usr/bin/perl /opt/psa/admin/bin/plesk_agent_manager domains-id --owner-uid=6565f56f-4b
root 17902 0.0 0.3 12020 8092 ? SN 08:11 0:00 python /opt/psa/admin/share/pmmcli/pmmcli_daemon_runner.py
root 17910 99.8 0.6 18376 13472 ? RN 08:11 22:18 /usr/bin/perl /opt/psa/admin/bin/plesk_agent_manager domains-id --owner-uid=6565f56f-4b
root 17911 0.0 0.0 2240 744 ? SN 08:11 0:00 /bin/tar -f - -c technik webmaster
root 17912 0.0 0.0 0 0 ? ZN 08:11 0:00 [perl] <defunct>
www-data 21977 0.0 0.5 35824 10408 ? S 08:26 0:00 /usr/sbin/apache2 -k start
root 23770 0.0 0.1 10432 2780 ? Ss 08:32 0:00 sshd: root@pts/0
root 23778 0.0 0.0 4280 1616 pts/0 Ss 08:32 0:00 -bash
root 23891 0.0 0.0 3584 868 pts/0 R+ 08:33 0:00 ps aux

strace -p 17910:
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144) = -1 EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
write(1, "././@LongLink\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 6144Process 17910 detached

 

[Micm_welker79]

System info

and here the system infos:
Virtuozzo
Debian etch
15GB HDD
1,5 GB RAM

If you need more infos, please tell me what you need.

Greets,
Michael

 

[IgorG]

Well. As I see it is plesk_agent_manager process. Did you tried to find something suspicious in migration logs?

 

[Micm_welker79]

I've checked the migration.log, the psadump.log & the stderr in the session directory. In the migration.log there is no error or warning, but in the psadump.log und the stderr there is an entry "gzip: stdout: Broken pipe".
Can it be, that the gzip-package have an error?

Greets,
Michael

 

[IgorG]

There are can be different reasons of "gzip: stdout: Broken pipe"message. Is there are any error messages before "gzip: stdout: Broken pipe"?

 

[Micm_welker79]

there is no other message before the gzip-error pops up. I also reinstall the the gzip-package but there is no change at the error. :-(

 

[IgorG]

Seems investigation by support team is required there.

 

[Micm_welker79]

I find a workaround. I just remove the migration manager und reinstall the backup-manager. Now it work without any problems.