[pve-devel] Error: unable to connect to socket
Oleg Kostyuk
cub.uanic at gmail.com
Tue Dec 6 11:08:31 CET 2011
Hello Alexandre,
Yes, I'm pretty sure about dns:
# hostname
tux
# hostname -f
tux.cub.org.ua
# host `hostname`
tux.cub.org.ua is an alias for humster.cub.org.ua.
humster.cub.org.ua has address 172.16.17.3
humster.cub.org.ua has address 172.16.29.3
# host `hostname -f`
tux.cub.org.ua is an alias for humster.cub.org.ua.
humster.cub.org.ua has address 172.16.17.3
humster.cub.org.ua has address 172.16.29.3
# host 172.16.17.3
3.17.16.172.in-addr.arpa domain name pointer tux.cub.org.ua.
# host 172.16.29.3
3.29.16.172.in-addr.arpa domain name pointer tux.cub.org.ua.
As I found, error is triggered in /usr/sbin/qm, line 53, because in line 51:
my $s = IO::Socket::UNIX->new(Peer => $path, Timeout => 120);
returned value is undef. At the time of call $path is set to
"/var/run/qemu-server/100.vnc".
Do you need some other information?
Is there opssibility to chat somewhere, like IRC, and when everything
will be solved, then post result here?
Thanks!
2011/12/6 Alexandre DERUMIER <aderumier at odiso.com>:
> Hi,
>
> it's working fine for me, but maybe can I help you.
>
> are you sure your dns configuration is ok ? ("failed: Unknown host" seems to be a dns resolv error)
>
> can you resolve your hostname ?
>
>
>
>
> ----- Mail original -----
>
> De: "Oleg Kostyuk" <cub.uanic at gmail.com>
> À: pve-devel at pve.proxmox.com
> Envoyé: Mardi 6 Décembre 2011 10:31:51
> Objet: [pve-devel] Error: unable to connect to socket
>
> Hello,
>
> I'm using Proxmox VE 2.0. It installed well, and I was able to create
> new VM and run it. But when I'm trying to look at VM console, I see
> error. As I found, it's because of some error with vncproxy. I tried
> to run manually same command as I found in log, and got:
>
> # /bin/nc -l -p 5903 -w 10 -c /usr/sbin/qm vncproxy 100
> vncproxy: forward host lookup failed: Unknown host
>
>
> I did small debug, and seems that's because of problem in /usr/sbin/qm:
>
> unable to connect to socket '/var/run/qemu-server/100.vnc' -
> Connection refused at /usr/sbin/qm line 53.
> at /usr/share/perl5/PVE/RESTHandler.pm line 488
> PVE::RESTHandler::cli_handler('main', 'qm vncproxy',
> 'vncproxy', 'ARRAY(0x2287080)', 'ARRAY(0x40d44a8)', undef, undef)
> called at /usr/share/perl5/PVE/CLIHandler.pm line 189
> PVE::CLIHandler::handle_cmd('HASH(0x40d5778)', 'qm',
> 'vncproxy', 'ARRAY(0x2287080)', undef, '/usr/sbin/qm') called at
> /usr/sbin/qm line 452
>
> How this can be solved?
> Thanks in advance!
>
> --
> Sincerely yours,
> Oleg Kostyuk (CUB-UANIC)
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
>
> --
>
> --
>
>
>
>
>
> Alexandre Derumier
> Ingénieur système
> e-mail : aderumier at odiso.com
> Tél : +33 (0)3 20 68 88 90
> Fax : +33 (0)3 20 68 90 81
> 45 Bvd du Général Leclerc
> 59100 ROUBAIX - FRANCE
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Sincerely yours,
Oleg Kostyuk (CUB-UANIC)
More information about the pve-devel
mailing list