OpenVZ Forum


Home » General » Support » Strange behavior when starting container - hostname.
Strange behavior when starting container - hostname. [message #35120] Tue, 03 March 2009 10:19 Go to next message
Genicode is currently offline  Genicode
Messages: 2
Registered: March 2009
Junior Member
Hello,

I installed openvz on Debian eth system.
Im using kernel fzakernel-2.6.18-686-bigmem ( I tried other kernels ovzkernel-* but i got some problems with networking and vmalloc ).

I created container 102, set ip and hostname. When system starts everything is ok - container is going up, i can log on it.

When im trying to start and stop container, im getting this:

arch:~# vzctl stop 102
Stopping container ...
Container was stopped
Container is unmounted
arch:~# vzctl start 102
Starting container ...
Container is mounted
Adding IP address(es): 192.168.1.1
Setting CPU units: 1000
Configure meminfo: 65536
File resolv.conf was modified
Container start in progress...
arch:~#

bash: line 384:  9473 Segmentation fault      hostname ${hostname}

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: invalid opcode: 0000 [#1]

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: SMP

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: CPU:    0, VCPU: 102.0

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: EIP is at sys_sethostname+0x5d/0x91

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: eax: f7e78a20   ebx: 00000004   ecx: 00000001   edx: f2e22000

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: esi: f2e23f6c   edi: ec100000   ebp: f2e22001   esp: f2e23f6c

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: ds: 007b   es: 007b   ss: 0068

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: Process hostname (pid: 8449, veid: 102, ti=f2e22000 task=f2e18190 task.ti=f2e22000)

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: Stack: 61707564 b7f44808 c0110cac c0110d24 0000804b 00021000 00000004 f2e23fbc

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel:        f2e18190 0804b000 00021000 f7854540 0806c000 c01550d0 f7854574 0804b008

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel:        0804b008 0804b008 00000002 c0102963 0804b008 00000004 0804b008 0804b008

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel:  Call Trace:

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: Code: d9 8b 54 24 50 89 e0 89 e6 e8 0d a6 08 00 85 c0 75 38 89 e2 89 d9 81 e2 00 e0 ff ff 8b 02 c1 e9 02 8b 80 58 04 00 00 8b 78 8b 45 <f0> 3b 45 f4 7c e1 8b 45 ec 89 45 dc 8b 45 dc c9 c3 8b 80 58 04

Message from syslogd@arch at Tue Mar  3 10:57:08 2009 ...
arch kernel: EIP: [<c01296f5>] sys_sethostname+0x5d/0x91 SS:ESP 0068:f2e23f6c


After that a lot of system processes going down and system is not responsible. Only way is hard reboot.

I tried to create my own kernel - the same.
I tried without bigmem - the same.
When im using ovzkernel-* it looks good, but as i said - im getting network problems - sometimes eth0 is timeouting, then i can only reboot the system.

Any ideas what is wrong and what can i do to correct it?
Perhaps its a bug?

Kernel and tools version:
arch:~# dpkg -l |grep fza
ii  fzakernel-2.6.18-686-bigmem          028stab056.1dso1                         OpenVZ - Meta kernel 2.6.1814-fza-686-bigmem
ii  linux-image-2.6.18-14-fza-686-bigmem 028stab056.1dso1                         OpenVZ Linux kernel binary image for version
arch:~# dpkg -l |grep vz
ii  linux-patch-openvz                   2.6.24-ovz004.1d3                        server virtualization solution - linux patch
ii  vzctl                                3.0.23-1dso1~etch0                       OpenVZ - server virtualization solution - co
ii  vzquota                              3.0.12-1dso1~etch0                       OpenVZ - server virtualization solution - qu


[Updated on: Tue, 03 March 2009 10:22]

Report message to a moderator

Re: Strange behavior when starting container - hostname. [message #35122 is a reply to message #35120] Tue, 03 March 2009 10:59 Go to previous message
Genicode is currently offline  Genicode
Messages: 2
Registered: March 2009
Junior Member
New info:

Problem is when trying to set hostname. After reboot i enter the container and i tired to change hostname. Effect here:
arch:/etc/vz/conf# vzctl enter 102
entered into CT 102
arch:/# ls
bin  boot  dev  etc  home  initrd  lib  media  mnt  opt  proc  root  sbin  srv  sys  tmp  usr  var
arch:/# hostname
arch
arch:/# hostname d
Segmentation fault

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: invalid opcode: 0000 [#1]
arch:/#
Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: SMP

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: CPU:    5, VCPU: 102.1

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: EIP is at sys_sethostname+0x5d/0x91

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: eax: f55f2c40   ebx: 00000001   ecx: 00000000   edx: f63a4000

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: esi: f63a5f6c   edi: 00000000   ebp: f63a4001   esp: f63a5f6c

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: ds: 007b   es: 007b   ss: 0068

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: Process hostname (pid: 8520, veid: 102, ti=f63a4000 task=dfbf2cb0 task.ti=f63a4000)

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: Stack: dfa33764 b7f92808 c0110cac c0110d24 0000804b 00021000 00000004 f63a5fbc

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel:        dfbf2cb0 0804b000 00021000 dfa337c0 0806c000 c01550d0 dfa337f4 0804b008

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel:        0804b008 0804b008 00000002 c0102963 0804b008 00000001 0804b008 0804b008

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel:  Call Trace:

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: Code: d9 8b 54 24 50 89 e0 89 e6 e8 0d a6 08 00 85 c0 75 38 89 e2 89 d9 81 e2 00 e0 ff ff 8b 02 c1 e9 02 8b 80 58 04 00 00 8b 78 8b 45 <f0> 3b 45 f4 7c e1 8b 45 ec 89 45 dc 8b 45 dc c9 c3 8b 80 58 04

Message from syslogd@arch at Tue Mar  3 11:56:42 2009 ...
arch kernel: EIP: [<c01296f5>] sys_sethostname+0x5d/0x91 SS:ESP 0068:f63a5f6c
Previous Topic: OpenVZ Clustering
Next Topic: Do you know how to put /vz on a different hard drive?
Goto Forum:
  


Current Time: Sun Apr 28 17:59:38 GMT 2024

Total time taken to generate the page: 0.03002 seconds