OpenVZ Forum


Home » General » Support » "Holy crap" in kernel.log when using vzctl chkpnt xxx --dump
"Holy crap" in kernel.log when using vzctl chkpnt xxx --dump [message #46290] Thu, 10 May 2012 17:52 Go to next message
devnull is currently offline  devnull
Messages: 20
Registered: May 2012
Junior Member
Hello!

Please forgive my bad English, I am French.

I am using a little script to replicate OpenVZ containers on a different directory but sometimes, in kernel.log, there are strange messages :

kernel: Holy Crap 1 0 12176,1120(imap-login)
kernel: Holy Crap 1 0 4487,291(pdns_server)
kernel: Holy Crap 1 0 100278,14626(imap)
kernel: Holy Crap 1 0 8978,331(opendkim)
kernel: Holy Crap 1 0 8979,332(opendkim)
kernel: Holy Crap 1 0 7185,1420(mysqld)
kernel: Holy Crap 1 0 4485,289(pdns_server)
kernel: Holy Crap 1 0 8981,334(opendkim)
kernel: Holy Crap 1 0 399921,289(pdns_server)
kernel: Holy Crap 1 0 399924,292(pdns_server)
kernel: Holy Crap 1 0 8693,268(rsyslogd)
kernel: Holy Crap 1 0 8978,331(opendkim)
kernel: Holy Crap 1 0 719575,3799(master)


The script is simple (copied from vzmigrate) :

1) rsync --archive --delete --delete-excluded --hard-links --numeric-ids --sparse /var/lib/vz/private/xxx/ /home/backup/vz/xxx/ (first pass)
2) vzctl chkpnt xxx --suspend
3) vzctl chkpnt xxx --dump --dumpfile "xxx.dump"
1) rsync --archive --delete --delete-excluded --hard-links --numeric-ids --sparse /var/lib/vz/private/xxx/ /home/backup/vz/xxx/ (second pass)
5) vzctl chkpnt xxx --resume


I have found the source file where the error come from but I am unable to know if it is a severe error or not.

It is present on line 279 in cpt_dump.c but after the error a "continue" is called in a infinte loop so I am puzzled...

git.openvz.org/?p=linux-2.6.32-openvz;a=blob;f=kernel/cpt/cpt_dump.c


I am using Proxmox 2.1, everything is up to date.

EDIT : kernel & tools version :

pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1


Thank you for your help!

[Updated on: Fri, 11 May 2012 08:22]

Report message to a moderator

Re: "Holy crap" in kernel.log when using vzctl chkpnt xxx --dump [message #46355 is a reply to message #46290] Mon, 14 May 2012 03:34 Go to previous messageGo to next message
___jul is currently offline  ___jul
Messages: 2
Registered: May 2012
Junior Member
Hi,

I've the same problem :
Apr 9 01:19:41 xxxx kernel: Holy Crap 1 0 26466,22969(tlsmgr)
Apr 9 01:19:41 xxxx kernel: Holy Crap 2 0 26466,22969(tlsmgr)

seems to happen at the exact same moment of a vzdump.
Result 1 of my VE is blocked in Uninterruptible state.

root 3863 312351 0.0 10164 408 ? Ds Apr09 10557290:44 vzctl --skiplock chkpnt 100 --suspend

My version :
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1dso1

Did you find a solution and an explanation of this "Holy Crap" ?

Thks

jul
Re: "Holy crap" in kernel.log when using vzctl chkpnt xxx --dump [message #46384 is a reply to message #46290] Wed, 16 May 2012 09:48 Go to previous messageGo to next message
damswf is currently offline  damswf
Messages: 5
Registered: September 2009
Junior Member
I have the same problem:

May 14 16:51:01 wfsr010 kernel: Holy Crap 1 0 909551,469(apache2)
May 14 18:17:22 wfsr010 kernel: Holy Crap 1 0 979972,373(mysqld)
May 14 18:22:18 wfsr010 kernel: Holy Crap 1 2 979935,336(mysqld)
May 14 18:23:17 wfsr010 kernel: Holy Crap 1 0 989531,129(sshd)
May 14 18:23:17 wfsr010 kernel: Holy Crap 1 0 989776,374(mysqld)
May 15 17:19:45 wfsr010 kernel: Holy Crap 1 0 989776,374(mysqld)
May 15 17:54:43 wfsr010 kernel: Holy Crap 1 0 2455,40(init-logger)
May 15 18:40:50 wfsr010 kernel: Holy Crap 1 0 22862,374(mysqld)

I think this problem arises when I try to chkpnt a container.

my kernel:
Linux wfsr010 2.6.32-11-pve #1 SMP Wed Apr 11 07:17:05 CEST 2012 x86_64 GNU/Linux

my vzctl version:
vzctl version 3.0.30.2-11.git.aefc8ef

I use proxmox 2.1 and I am up to date.

[Updated on: Wed, 16 May 2012 09:50]

Report message to a moderator

Re: "Holy crap" in kernel.log when using vzctl chkpnt xxx --dump [message #46386 is a reply to message #46355] Wed, 16 May 2012 10:38 Go to previous message
devnull is currently offline  devnull
Messages: 20
Registered: May 2012
Junior Member
Hello!

___jul wrote on Mon, 14 May 2012 05:34
Did you find a solution and an explanation of this "Holy Crap" ?

Nope...

I have read the source of cpt_dump.c but I am unable to understand why the error is triggered.

The patch including this error was posted by Alexey Kuznetsov in August 2006.

git.openvz.org/?p=linux-2.6.16-openvz;a=commitdiff_plain;h=c691647ba91d87e1d79f8eb7cda31d698f782a14


Cheers.

Previous Topic: scapy filters / tcpdump
Next Topic: Crossover Cable Connected, now what?
Goto Forum:
  


Current Time: Sat Apr 27 20:47:27 GMT 2024

Total time taken to generate the page: 0.02641 seconds