No pve proxmox web interface after full upgrade

  • Thread starter Thread starter philuser
  • Start date Start date
P

philuser

Guest
Hello !

after the full update 2.0 to 2.1 with 'aptitude update && aptitude full-upgrade', no way to run the web Interface pve Proxmox.
when do I start apache2
Code:
# service apache2 restart
Restarting web server: apache2[Tue Oct 02 17:14:21 2012] [warn] _default_ VirtualHost overlap on port 8006, the first has precedence
[Tue Oct 02 17:14:21 2012] [warn] _default_ VirtualHost overlap on port 8006, the first has precedence
[Tue Oct 02 17:14:21 2012] [warn] _default_ VirtualHost overlap on port 8006, the first has precedence
[Tue Oct 02 17:14:21 2012] [warn] _default_ VirtualHost overlap on port 8006, the first has precedence
(98)Address already in use: make_sock: could not bind to address [::]:8006
(98)Address already in use: make_sock: could not bind to address [::]:8006

But I have no trace on the use of port 8006 !!

Code:
#netstat -tlnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.2:25            0.0.0.0:*               LISTEN      2679/master     
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      2679/master     
tcp        0      0 0.0.0.0:39758           0.0.0.0:*               LISTEN      1445/rpc.mountd 
tcp        0      0 0.0.0.0:45007           0.0.0.0:*               LISTEN      -               
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      1153/portmap    
tcp        0      0 0.0.0.0:4369            0.0.0.0:*               LISTEN      1526/epmd       
tcp        0      0 127.0.0.1:85            0.0.0.0:*               LISTEN      1845/pvedaemon work
tcp        0      0 0.0.0.0:5269            0.0.0.0:*               LISTEN      1553/beam       
tcp        0      0 10.138.10.141:53        0.0.0.0:*               LISTEN      1484/named      
tcp        0      0 10.138.10.140:53        0.0.0.0:*               LISTEN      1484/named      
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      1484/named      
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1478/sshd       
tcp        0      0 0.0.0.0:3306            0.0.0.0:*               LISTEN      2672/mysqld     
tcp        0      0 0.0.0.0:199             0.0.0.0:*               LISTEN      2695/snmpd      
tcp        0      0 127.0.0.1:587           0.0.0.0:*               LISTEN      4010/sendmail: MTA:
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1719/master     
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      1484/named      
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      2374/mysqld     
tcp        0      0 0.0.0.0:10000           0.0.0.0:*               LISTEN      3971/perl       
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      3185/apache2    
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      2175/portmap    
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      2770/apache2    
tcp        0      0 0.0.0.0:5280            0.0.0.0:*               LISTEN      1553/beam       
tcp        0      0 10.138.10.140:7777      0.0.0.0:*               LISTEN      1553/beam       
tcp        0      0 0.0.0.0:33985           0.0.0.0:*               LISTEN      1553/beam       
tcp        0      0 0.0.0.0:2049            0.0.0.0:*               LISTEN      -               
tcp        0      0 10.138.10.171:53        0.0.0.0:*               LISTEN      2744/named      
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      2744/named      
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      2656/sshd       
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      3074/cupsd      
tcp        0      0 0.0.0.0:34468           0.0.0.0:*               LISTEN      1166/rpc.statd  
tcp        0      0 0.0.0.0:5432            0.0.0.0:*               LISTEN      2778/postgres   
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      4010/sendmail: MTA:
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      2744/named      
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      2269/sshd       
tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN      1553/beam       
tcp6       0      0 :::53                   :::*                    LISTEN      1484/named      
tcp6       0      0 :::22                   :::*                    LISTEN      1478/sshd       
tcp6       0      0 ::1:953                 :::*                    LISTEN      1484/named      
tcp6       0      0 :::53                   :::*                    LISTEN      2744/named      
tcp6       0      0 :::22                   :::*                    LISTEN      2656/sshd       
tcp6       0      0 ::1:631                 :::*                    LISTEN      3074/cupsd      
tcp6       0      0 :::5432                 :::*                    LISTEN      2778/postgres   
tcp6       0      0 ::1:953                 :::*                    LISTEN      2744/named      
tcp6       0      0 :::22                   :::*                    LISTEN      2269/sshd

Can someone help me

thank

Phil
 
Last edited by a moderator:
any error on the update?

post the output of 'pveversion -v'
 
any error on the update?

post the output of 'pveversion -v'

Code:
# pveversion -v
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-14-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-12-pve: 2.6.32-68
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1
 
Code:
# pveversion -v
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-14-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-12-pve: 2.6.32-68
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1


and the update is performed without error
 
see what is running on p80: fuser -v -n tcp 80 or fuser -v -n tcp 8006
then try to kill: fuser -k -n tcp 80 and restart apache.
 
see what is running on p80: fuser -v -n tcp 80 or fuser -v -n tcp 8006
then try to kill: fuser -k -n tcp 80 and restart apache.

thank you for your answers, here are the results of the latest tests

Code:
[root@virtdeve:~]# fuser -v -n tcp 8006 
[root@virtdeve:~]# fuser -v -n tcp 80
                     USER        PID ACCESS COMMAND
80/tcp:              root       2770 F.... apache2
                     www-data   2806 F.... apache2
                     www-data   2807 F.... apache2
                     root       3185 F.... apache2
                     www-data   3293 F.... apache2
[root@virtdeve:~]# fuser -k -n tcp 80
80/tcp:               2770  2806  2807  3185  3293
[root@virtdeve:~]# fuser -v -n tcp 80
[root@virtdeve:~]# service apache2 start
Starting web server: apache2[Wed Oct 03 09:03:15 2012] [warn] _default_ VirtualHost overlap on port 8006, the first has precedence
[Wed Oct 03 09:03:15 2012] [warn] _default_ VirtualHost overlap on port 8006, the first has precedence
(98)Address already in use: make_sock: could not bind to address [::]:8006
(98)Address already in use: make_sock: could not bind to address [::]:8006
.
[root@virtdeve:~]#

it is as if he had a dual boot of port services: 8006!
and still no web interface


phil
 
I have no idea...It can be anything i guess. What is output of: apache2ctl -S

Code:
:~# apache2ctl -S
VirtualHost configuration:
wildcard NameVirtualHosts and _default_ servers:
*:8006                 localhost (/etc/apache2/sites-enabled/pve.conf:33)
Syntax OK
 
Ok I found ;)

I had a old configuration file in the directory .. apache2/sites-enables/pve.conf.old

Thank you again for your assistance
 
I got same problem on one node. I updated perfect without any problems on other nodes, but now web interface no upgraded :(

root@:# pveversion -v
proxmox-ve-2.6.32: 3.2-136 (running kernel: 2.6.32-32-pve)
pve-manager: 3.3-1 (running version: 3.3-1/a06c9f73)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-30-pve: 2.6.32-130
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.1-34
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-9
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
I use this old thread, because I have a similar issue.
After the last upgrade, I can't login to my Proxmox 4.1 test machine:

# pveversion -v
proxmox-ve: 4.1-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.1-34 (running version: 4.1-34/8887b0fd)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-13
pve-container: 1.0-61
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie

Firefox shows:
Secure Connection Failed
The connection to the server was reset while the page was loading.

With Chrome I get:
This site can’t be reached
The connection was reset.

The logfiles doesn't show something special and SSH login works.
An i cleared allredy the browser cache.

Any hints to debug this issue?

BR
Jasmin
 
check the running services with 'systemctl status "pve*"' and the logs with 'journalctl -b'
 
In the meantime I have all keys regenerated according to this description, because I thought this could be the reason.
But it changed nothing.

Edit: I found it!
I had a file /etc/default/pveproxy, which did restrict the access to localhost. This is, because I use ssh with port forwarding to access the server. I deactivated this temporarily. Because of the key regeneration, Chrome asked me to add an exception and then I was able to access the WebGUI.
Even with the access restriction and my port forwarding it is working now. But it definitely didn't work before the key regeneration, because I always used the ssh tunnel to access the server before the update.
Firefox was able to connect, after I cleared the browser cache, too.

During the debugging, I tried to start pveproxy with -debug, but this seems not to work. It always started as normal service. How is the correct syntax to start pveproxy in debug mode?
 
Last edited: