No webinterface after Updates

[hpcraith]

I initiated updates from the Proxmox webinterface.
After working for some time the console window disappeared.
I was able to access the server via ssh and realised (netstat -ltn) that no process was
listening on port 8006.
I issued apt-get update from the CLI. It told me that there was nothing new to install but 43 packages
were not installed correctly. An error was reported that grub was unable to write the boot block to /dev/sda.
A lot of things happened but finally the webinterface was there again and everything worked as expected.
I did not reboot as I fear that the system will not start. I am at home and not at the computing center.
pveversion -v
-------------

root@vwsrv2:/var/log# pveversion -v
proxmox-ve-2.6.32: 3.4-157 (running kernel: 2.6.32-34-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-2.6.32-34-pve: 2.6.32-140
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-2
pve-cluster: 3.0-18
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
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.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@vwsrv2:/var/log#

There is a new kernel availlable, but not running.

The disks are organized as follows:

root@vwsrv2:/boot# parted -l
Error: /dev/sda: unrecognised disk label
Model: IBM ServeRAID-MR10M (scsi)
Disk /dev/sda: 1168GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

Model: LSILOGIC Logical Volume (scsi)
Disk /dev/sdb: 146GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 537MB 536MB primary ext3 boot
2 537MB 146GB 145GB primary lvm


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/pve-swap: 18.1GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 18.1GB 18.1GB linux-swap(v1)


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/pve-ext: 91.1GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 91.1GB 91.1GB ext3


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/pve-data: 862GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 862GB 862GB ext3


Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/pve-root: 36.2GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:

Number Start End Size File system Flags
1 0.00B 36.2GB 36.2GB ext3


root@vwsrv2:/boot#


So the question is: how to proceed?

 

[udo]

Hi,
the disk-output shows, that your boot-disk isn't sda. sdb looks much better ;-)

What is the output of

pvs

I would do an "grub-install /dev/sdb"

Because the web-gui:
Restart pve-proxy and look if port 8006 is open.

Udo

 

[hpcraith]

"grub-install /dev/sdb" worked.
pvs output is:
root@vwsrv2:~# pvs
PV VG Fmt Attr PSize PFree
/dev/sda pve lvm2 a-- 1.06t 285.43g
/dev/sdb2 pve lvm2 a-- 135.47g 0
root@vwsrv2:~#

So far everything seems ok. I will restart the server this evening and see if the new kernel
vmlinuz-2.6.32-39-pve
is booted.
If that works the only remaining question is:
Why does the Proxmox web console started by the web update button disappear and the system is left in such disorder.
I have a subsciption for all production servers. So is it OK to start the update from the webinterface?

Dieter

 

[tom]

there was an issue with GUI updates (as the restart of the services also restarted the upgrade process).

but already fixed since some time, but probably you still had the old version before the upgrade.

 

[hpcraith]

there was an issue with GUI updates (as the restart of the services also restarted the upgrade process).

but already fixed since some time, but probably you still had the old version before the upgrade.

So would it be appropriate to log-in via ssh and then
apt-get update
apt-get upgrade
apt-get dist-upgrade

I understand that the enterprise repository is password protected.

 

[tom]

So would it be appropriate to log-in via ssh and then
apt-get update
apt-get upgrade
apt-get dist-upgrade

I understand that the enterprise repository is password protected.

yes, but as long as you have a subscription key, access is allows.

the update commands are ok (apt-get upgrade is not needed), also documented on:

http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.4