OpenVZ Forum


Home » General » Support » *SOLVED* No resolve inside one VE
Re: No resolve inside one VE [message #12837 is a reply to message #12832] Fri, 11 May 2007 08:38 Go to previous messageGo to previous message
3molo is currently offline  3molo
Messages: 13
Registered: April 2007
Junior Member
Ok so something has happened. What I did was change the othersockbuf, tcprcvbuf & tcpsndbuf parameters (set VEID --parameter value:value --save) and upon stoping the VE:

flop:/etc/vz/conf# vzctl stop 107
Stopping VE ...
flop kernel: Oops: 0000 [#1]
flop kernel: SMP
flop kernel: CPU: 1, VCPU: 0.1
flop kernel: EIP is at ipt_unregister_table+0xb/0x1b0 [ip_tables]
flop kernel: eax: 00000000 ebx: 00104007 ecx: f8bff770 edx: f6f61e80
flop kernel: esi: 00000000 edi: 00104007 ebp: 00000000 esp: e7d99f44
flop kernel: ds: 007b es: 007b ss: 0068
flop kernel: Process vzmond/107 (pid: 24906, veid: 0, ti=e7d99000 task=f62cb950 task.ti=e7d99000)
flop kernel: Stack: 00000282 c013f797 f6295600 00000000 c2337800 c22fc2c0 f8c00d28 00104007
flop kernel: 00000000 00104007 00000000 f8bff3fb 00000000 f8bff89d f8c00c80 00000006
flop kernel: f8b9158f f6143000 00000000 f6143000 f6143028 c0520700 00000000 f8b93ab6
flop kernel: Call Trace:
flop kernel: Code: 04 89 d0 5a c3 c7 04 24 02 00 00 00 e8 5f b0 ff ff 89 c2 89 d0 5a c3 89 f6 8d bc 27 00 00 00 00 55 57 56 53 83 ec 1c 8b 44 24 30 <8b> 50 34 89 04 24 89 54 24 14 e8 c6 ad ff ff 89 44 24 0c 89 e0
flop kernel: EIP: [<f89521ab>] ipt_unregister_table+0xb/0x1b0 [ip_tables] SS:ESP 0068:e7d99f44

Unable to stop VE: operation timed out
flop:~# cat /var/log/kernel
<snip>
May 11 10:16:28 flop kernel: CPU: 1, VCPU: 0.1
May 11 10:16:28 flop kernel: EIP: 0060:[<f89521ab>] Not tainted VLI
May 11 10:16:28 flop kernel: EFLAGS: 00010296 (2.6.18-028stab027 #1)
May 11 10:16:28 flop kernel: EIP is at ipt_unregister_table+0xb/0x1b0 [ip_tables]
May 11 10:16:28 flop kernel: eax: 00000000 ebx: 00104007 ecx: f8bff770 edx: f6f61e80
May 11 10:16:28 flop kernel: esi: 00000000 edi: 00104007 ebp: 00000000 esp: e7d99f44
May 11 10:16:28 flop kernel: ds: 007b es: 007b ss: 0068
May 11 10:16:28 flop kernel: Process vzmond/107 (pid: 24906, veid: 0, ti=e7d99000 task=f62cb950 task.ti=e7d99000)
May 11 10:16:28 flop kernel: Stack: 00000282 c013f797 f6295600 00000000 c2337800 c22fc2c0 f8c00d28 00104007
May 11 10:16:28 flop kernel: 00000000 00104007 00000000 f8bff3fb 00000000 f8bff89d f8c00c80 00000006
May 11 10:16:28 flop kernel: f8b9158f f6143000 00000000 f6143000 f6143028 c0520700 00000000 f8b93ab6
May 11 10:16:28 flop kernel: Call Trace:
May 11 10:16:28 flop kernel: [<c013f797>] ub_slab_uncharge+0x87/0xb0
May 11 10:16:28 flop kernel: [<f8bff3fb>] ip_nat_rule_cleanup+0x3b/0x80 [iptable_nat]
May 11 10:16:28 flop kernel: [<f8bff89d>] fini_iptable_nat+0x1d/0x60 [iptable_nat]
May 11 10:16:28 flop kernel: [<f8b9158f>] do_ve_iptables+0x3cf/0x14a0 [vzmon]
May 11 10:16:28 flop kernel: [<f8b93ab6>] env_cleanup+0xb6/0x180 [vzmon]
May 11 10:16:28 flop kernel: [<f8b93bc3>] vzmond_helper+0x43/0x60 [vzmon]
May 11 10:16:28 flop kernel: [<f8b93b80>] vzmond_helper+0x0/0x60 [vzmon]
May 11 10:16:28 flop kernel: [<c0100f35>] kernel_thread_helper+0x5/0x10
May 11 10:16:28 flop kernel: Code: 04 89 d0 5a c3 c7 04 24 02 00 00 00 e8 5f b0 ff ff 89 c2 89 d0 5a c3 89 f6 8d bc 27 00 00 00 00 55 57 56 53 83 ec 1c 8b 4 4 24 30 <8b> 50 34 89 04 24 89 54 24 14 e8 c6 ad ff ff 89 44 24 0c 89 e0
May 11 10:16:28 flop kernel: EIP: [<f89521ab>] ipt_unregister_table+0xb/0x1b 0 [ip_tables] SS:ESP 0068:e7d99f44


/proc/user_beancounters

107: kmemsize 211264 2444162 10485760 15728640 0
lockedpages 0 0 32 32 0
privvmpages 1 98451 98816 131072 5
shmpages 1 977 8192 8192 0
dummy 0 0 0 0 0
numproc 0 69 120 120 0
physpages 1 9761 0 2147483647 0
vmguarpages 0 0 65536 131072 0
oomguarpages 1 9761 6144 2147483647 0
numtcpsock 0 47 512 512 0
numflock 0 8 100 110 0
numpty 0 5 16 16 0
numsiginfo 0 13 256 256 0
tcpsndbuf 0 35520 319488 524288 0
tcprcvbuf 0 454392 319488 524288 238
othersockbuf 0 133032 132096 336896 16123
dgramrcvbuf 0 8364 132096 132096 0
numothersock 0 110 512 512 0
dcachesize 0 0 1048576 1097728 0
numfile 0 1272 2048 2048 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 0 10 128 128 0

Do I have to stop vz itself? Rather not since other VEs still run smooth.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: *SOLVED* unable to access VE
Next Topic: CPT ERR
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Jan 30 01:21:56 GMT 2026

Total time taken to generate the page: 0.48418 seconds
Powered by FUDforum Powered by Virtuozzo Containers