Proxmox apache2 fails after adding to cluster

[hotwired007]

I have 3 servers setup for for a test Proxmox 2 cluster, but when i add the second two machines to the cluster they both work until they are restarted and then apache2 fails...

any suggestions on what i should check?

 

[tom]

error logs?

 

[hotwired007]

which error logs should I be looking at...

apache error logs have nothing relevant apart from an error with favicon...

the boot up error is something to do with a SSL certificate....


root@pve2-3:~# pveversion -v
pve-manager: 2.0-18 (pve-manager/2.0/16283a5a)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-55
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.8-3
pve-cluster: 1.0-17
qemu-server: 2.0-13
pve-firmware: 1.0-14
libpve-common-perl: 1.0-11
libpve-access-control: 1.0-5
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29-3pve8
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1

 

[dietmar]

which error logs should I be looking at...

Any hint in /var/log/syslog ?

 

[hotwired007]

nothing...

all i can find is whats displayed on the console screen: (hand copied - is there a way to access this directly?)


Starting OpenVZ ... done

Bringing up interface venet0 ... done

Container(s) not found/usr/share/cluster/cluster.rng:992: element ref: Relax-NG parser error : Reference PVEVM has no matching definition

/usr/share/cluster/cluster.rng:992: element ref: Relax-NG parser error : Internal found no define for ref PVEVM

Relax-NG schema /usr/share/cluster/cluster.rng failed to compile

[ OK ]

waiting for quorum... [ OK ]

starting fenced... [ OK ]

staring dlm_controld... [ OK ]

unfencing self... [ OK ]

Starting PVE Daemon: pvedaemon.

Starting web server: apache2Syntax error on line 13 of /etc/apache2/sites-enabled/pve-redirect.conf: SSLCertificateFile: file '/etc/pve/local/pve-ssl.pem' does not exist or is empty Action 'start' failed.

The Apache error log may have more information.

failed!

Starting PVE Status Daemon: pvestatd.

startpar: service(s) returned failure: apache2 ... failed!

 

[dietmar]

Does it help if you run:

# pvecm updatecerts

and then restart apache

# /etc/init.d/apache2 restart

 

[hotwired007]

ahah! many thanks

 

[impa_prox]

Does it help if you run:

# pvecm updatecerts

Hi,
I try create cluster, I change /etc/hosts on second node and restart server. After boot I run

/etc/init.d/apache2 restart
Syntax error on line 13 of /etc/apache2/sites-enabled/pve-redirect.conf:
SSLCertificateFile: file '/etc/pve/local/pve-ssl.pem' does not exist or is empty
Action 'configtest' failed.
The Apache error log may have more information.

Then I run:

# pvecm updatecerts
no quorum - unable to update files

How to solve this problem?

 

[dietmar]

Seems you run old version - you should update first.

 

[impa_prox]

This node I installed today.

# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# aptitude update && aptitude full-upgrade
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

pveversion -v
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-68
pve-kernel-2.6.32-12-pve: 2.6.32-68
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.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-16
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

# cat /etc/debian_version
6.0.5

What need update and how to?

Thank you.

 

[dietmar]

Oh, you hijacked that thread (missed that). Yes, your node is up to date.