web interface not working

[lewissue]

root@v09:~# tail /var/log/daemon.log
Sep 25 02:51:57 v09 pveproxy[2906]: worker 97627 finished
Sep 25 02:51:57 v09 pveproxy[2906]: worker 99902 finished
Sep 25 02:51:57 v09 pveproxy[2906]: server stopped
Sep 25 02:59:04 v09 pveproxy[114844]: start failed - unable to create socket - IO::Socket::INET: Address already in use
Sep 25 02:59:11 v09 pveproxy[114873]: start failed - unable to create socket - IO::Socket::INET: Address already in use
Sep 25 02:59:31 v09 pveproxy[114939]: start failed - unable to create socket - IO::Socket::INET: Address already in use
Sep 25 02:59:46 v09 pveproxy[114984]: start failed - unable to create socket - IO::Socket::INET: Address already in use
Sep 25 03:00:39 v09 pveproxy[115085]: start failed - unable to create socket - IO::Socket::INET: Address already in use
Sep 25 03:02:15 v09 pveproxy[115264]: start failed - unable to create socket - IO::Socket::INET: Address already in use
Sep 25 03:05:13 v09 pveproxy[115566]: start failed - unable to create socket - IO::Socket::INET: Address already in use
root@v09:~#

 

[Q-wulf]

just shooting at ghosts here, but:

try

pveproxy --debug

shold give yo something like:

[COLOR=#333333]unable to create socket - IO::Socket::INET: Address already in use[/COLOR]

they advise to perform a pvecluster restart (http:/***/forum.proxmox.com/threads/14141-web-interface-not-working-in-Proxmox-3)

service pve-cluster restart

they also advise to check whether your ip can be resolved as a hostname

That is ensure that
listed hostname in /etc/hostname is listed in /etc/hosts with ipaddress

then there is also advise here:


https:/*****/188.165.151.221/threads/16521-Can-t-login-via-WebGUI
to do the following:

pvedaemon stop
pvedaemon start

and if it does not help to perform a

killall pvedaemon
/etc/init.d/pvedaemon start
reboot (as per the last posts comment)

alternatively you can post the output of

cat /etc/hostname
cat /etc/hosts
cat /etc/network/interfaces

and maybe we can spot a config error for you.


there are also a bunch of threads where the "webcache" seems to be the cuplrit and "clearing" it fixed the issue.

Hope that helps, while you wait for qualified help