Unable to open pty [message #10796] |
Fri, 02 March 2007 17:15 |
Romeo Theriault
Messages: 20 Registered: December 2006
|
Junior Member |
|
|
Hi, I created a new VE today, and was configuring it and all was going well
until I restarted it and I am now unable to either enter it with:
vzctl enter 107
Or ssh into the VE.
When I try to enter the VE I get this error.
Enter into VE 107 failed
Unable to open pty: No such file or directory
When I try to ssh into the VE I get this error:
ssh: connect to host academic.umfk.maine.edu port 22: Connection refused
I found the bug in bugzilla with someone with a similar issue with Ubuntu.
http://bugzilla.openvz.org/show_bug.cgi?id=398
I am running CentOS with all the VE¹s also CentOS. All completely updated
with the latest kernels, etc...
In Bugzilla it says the issue has to do with showconsole, but I searched the
/etc/ directory for showconsole and did not find any init scripts with a
reference to showconsole.
Everything else on the VE seems to be running just fine, but I need to get
access to it.
I also tried: vzctl set 107 ‹devices c:5:2:rw ‹save
And this did not allow me to access it.
The problem seemed to arise after I configured winbind and smb to start on
boot. I tried disabling them on boot but I still can¹t log in.
Does anyone know how to fix this problem.
Thanks,
Romeo
|
|
|
Re: Unable to open pty [message #10798 is a reply to message #10796] |
Fri, 02 March 2007 17:29 |
|
http://wiki.openvz.org/VPS_enter_failed should help.
Romeo Theriault wrote:
> Hi, I created a new VE today, and was configuring it and all was going
> well until I restarted it and I am now unable to either enter it with:
>
> /vzctl enter 107
>
> /Or ssh into the VE.
>
> When I try to enter the VE I get this error.
>
> Enter into VE 107 failed
> Unable to open pty: No such file or directory
http://wiki.openvz.org/VPS_enter_failed should help.
>
>
> When I try to ssh into the VE I get this error:
>
> ssh: connect to host academic.umfk.maine.edu port 22: Connection refused
Perhaps ssh is not running or firewalled.
|
|
|
|
Re: Unable to open pty [message #10801 is a reply to message #10799] |
Fri, 02 March 2007 18:09 |
Romeo Theriault
Messages: 20 Registered: December 2006
|
Junior Member |
|
|
Yes, copying the /dev directory from a working VE to the non-working VE
fixed the problem. I can now login to the VE successfully.
Thank you,
Romeo
On 3/2/07 12:47 PM, "Kirill Korotaev" <dev@sw.ru> wrote:
> Romeo,
>
> most likely some /dev files were deleted inside your VE.
> to check:
> # ls -la /vz/root/<VEID>/dev
>
> try searching forum for "ptmx" and "pty".
> http://forum.openvz.org/index.php?t=tree&th=1282&mid =7149&&rev=&reveal=
>
>
> Kirill
>
>
>> Hi, I created a new VE today, and was configuring it and all was going
>> well until I restarted it and I am now unable to either enter it with:
>>
>> /vzctl enter 107
>>
>> /Or ssh into the VE.
>>
>> When I try to enter the VE I get this error.
>>
>> Enter into VE 107 failed
>> Unable to open pty: No such file or directory
>>
>>
>> When I try to ssh into the VE I get this error:
>>
>> ssh: connect to host academic.umfk.maine.edu port 22: Connection refused
>>
>>
>> I found the bug in bugzilla with someone with a similar issue with Ubuntu.
>> _http://bugzilla.openvz.org/show_bug.cgi?id=398
>> _
>> I am running CentOS with all the VE¹s also CentOS. All completely
>> updated with the latest kernels, etc...
>>
>> In Bugzilla it says the issue has to do with showconsole, but I searched
>> the /etc/ directory for showconsole and did not find any init scripts
>> with a reference to showconsole.
>>
>> Everything else on the VE seems to be running just fine, but I need to
>> get access to it.
>>
>> I also tried: vzctl set 107 ‹devices c:5:2:rw ‹save
>>
>> And this did not allow me to access it.
>>
>> The problem seemed to arise after I configured winbind and smb to start
>> on boot. I tried disabling them on boot but I still can¹t log in.
>>
>> Does anyone know how to fix this problem.
>>
>> Thanks,
>>
>> Romeo
>>
>>
>> ------------------------------------------------------------ ------------
>>
|
|
|