OpenVZ Forum


Home » General » Support » Bash 4.2 problem?
Bash 4.2 problem? [message #41893] Thu, 24 February 2011 13:07 Go to next message
hvdkamer is currently offline  hvdkamer
Messages: 40
Registered: July 2006
Member
I've compiled and installed the new Bash 4.2 in a container. When I try to get access from the physical server I get:
hoefnix2:~# vzctl enter 50


Indeed, no errors, but also no prompt from the container. When I revert to Bash 4.1 and patchlevel 009 everything works again. From a different console on the physical server or from a SSH login in the virtual server I can see that in the container Bash is started and that there is a pts. However after that point it freezes and a Ctrl-c gives back the prompt on the physical server.

Any suggestions are appreciated...


Henk van de Kamer
auteur Het Lab
http://www.hetlab.tk/
Re: Bash 4.2 problem? [message #41915 is a reply to message #41893] Thu, 24 February 2011 14:22 Go to previous messageGo to next message
hvdkamer is currently offline  hvdkamer
Messages: 40
Registered: July 2006
Member
I've installed strace to investigate further:
hoefnix2:~# strace vzctl enter 60
...
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x2b65860859d0) = 29577
close(3)                                = 0
close(7)                                = 0
close(9)                                = 0
close(10)                               = 0
read(8, 


With bash 4.1 patchlevel 009 I get:

clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x2af2938ab9d0) = 2972
close(3)                                = 0
close(7)                                = 0
close(9)                                = 0
close(10)                               = 0
read(8, "", 4)                          = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
...


Hope that someone sees the problem and may be even a soultion Smile.


Henk van de Kamer
auteur Het Lab
http://www.hetlab.tk/
Re: Bash 4.2 problem? [message #42189 is a reply to message #41893] Wed, 16 March 2011 09:40 Go to previous messageGo to next message
hvdkamer is currently offline  hvdkamer
Messages: 40
Registered: July 2006
Member
After investigation by the maintainer of Bash it is decided that this is a bug in vzctl. Hope this wil be fixed soon Smile.

At the moment the owner of a virtual machine can block the owner of the physical machine to use the vzctl enter command to gain access. For some these coluld be nice, but it also blocks an easy way to help a problematic virtual machine to its feet again...


Henk van de Kamer
auteur Het Lab
http://www.hetlab.tk/
Re: Bash 4.2 problem? [message #42193 is a reply to message #42189] Wed, 16 March 2011 17:17 Go to previous messageGo to next message
curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany
Senior Member

Hi Henk,

have you tested the last git commit:

http://git.openvz.org/?p=vzctl;a=commitdiff;h=e7c40ee697606e43d6242fd3c124e370588ae26f

Bye,
Thorsten
Re: Bash 4.2 problem? [message #42194 is a reply to message #42193] Wed, 16 March 2011 17:53 Go to previous messageGo to next message
hvdkamer is currently offline  hvdkamer
Messages: 40
Registered: July 2006
Member
I've just found this patch and busy to setup a test for it Smile.

Henk van de Kamer
auteur Het Lab
http://www.hetlab.tk/
Re: Bash 4.2 problem? [message #42195 is a reply to message #41893] Wed, 16 March 2011 18:00 Go to previous message
hvdkamer is currently offline  hvdkamer
Messages: 40
Registered: July 2006
Member
hoefnix2:~# vzctl enter 60
entered into CT 60
ve60:/# pacman -Q bash
bash 4.2.008-1


This patch solves the problem.


Henk van de Kamer
auteur Het Lab
http://www.hetlab.tk/
Previous Topic: Start/stop VE
Next Topic: Mount bind to merge split shared disk?
Goto Forum:
  


Current Time: Wed Nov 06 07:40:10 GMT 2024

Total time taken to generate the page: 0.03625 seconds