instance console something went wrong, connection is closed | Wallaby DCN

Swogat Pradhan swogatpradhan22 at gmail.com
Thu Jun 22 08:08:01 UTC 2023


Hi,
Please find the below log:
[root at dcn01-hci-1 libvirt]# cat virtqemud.log
2023-06-22 07:40:01.575+0000: 350319: error : virNetSocketReadWire:1804 :
End of file while reading data: Input/output error
2023-06-22 07:40:01.575+0000: 350319: error : virNetSocketWriteWire:1844 :
Cannot write data: Broken pipe

I think this is causing the problem of not getting the instance console.

With regards,
Swogat Pradhan

On Fri, Jun 2, 2023 at 11:27 AM Swogat Pradhan <swogatpradhan22 at gmail.com>
wrote:

> Update:
> If the i am performing any activity like migration or resize of an
> instance whose console is accessible, the console becomes inaccessible
> giving out the following error : something went wrong, connection is closed
>
> The was 1 other instance whose console was not accessible and i did a
> shelve and unshelve and suddenly the instance console became accessible.
>
> This is a peculiar behavior and i don't understand where is the issue .
>
> With regards,
> Swogat Pradhan
>
> On Fri, Jun 2, 2023 at 11:19 AM Swogat Pradhan <swogatpradhan22 at gmail.com>
> wrote:
>
>> Hi,
>> I am creating instances in my DCN site and i am unable to get the console
>> sometimes, error: something went wrong, connection is closed
>>
>> I have 3 instances now running on my hci02 node and there is console
>> access on 1 of the vm's and the rest two i am not getting the console, i
>> have used the same flavor, same image same security group for the VM's.
>>
>> Please suggest what can be done.
>>
>> With regards,
>> Swogat Pradhan
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230622/c8d367ba/attachment.htm>


More information about the openstack-discuss mailing list