What is 3.0 using in place of Apache2

[Kaanha]

What service is ProxMox 3.0 using in place of Apache2? Right now I have a totally dead web interface and the first thing I want to try is to see if the service itself is running, but I'm not sure what service it's using.

Also, what would be the appropriate command to start that service?

 

[Kaanha]

Okay, I posted a little too soon, the very next search I did I found my answer. it's PVEProxy. So I'm good there, the interface is back...

However I'm not able to log into the web interface now, it tells me wrong password. Though my password works fine to log in to SSH and I've not made any changes.

 

[tom]

post your '/etc/hosts'

 

[Kaanha]

Here you go Tom:

127.0.0.1 localhost.localdomain localhost
152.8.134.205 silverdragon.ncat.edu silverdragon


# The following lines are desirable for IPv6 capable hosts


::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

 

[Kaanha]

Actually I seem to be having even more problems.

I've made no changes to the system at all, since the upgrade to 3.0 it was running happily till today when I got an email that someone couldn't access their webserver that's running on there.

That's how I identified I had no web interface access...

Now I'm trying to enter a container and I get this:

root@silverdragon:~# vzctl enter 100
enter into CT 100 failed

If I try to stop the Container I get:

root@silverdragon:~# qm stop 100
unable to find configuration file for VM 100 - no such machine

root@silverdragon:~# vzctl stop 100
Stopping container ...
Child 350820 exited with status 7
Killing container ...
Child 350822 exited with status 7
Unable to stop container

Now I've had this to happen before and restarting has fixed it with no issues. If i attempt to restart with either shutodwn -r now, reboot or reboot -f it does absolutely nothing. The system will NOT restart.

 

[Kaanha]

Also, Tom, I thought you might want my pveversion -v output.

pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-19-pve: 2.6.32-95
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-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.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1

Sorry, I meant to post that in my last post but doing multiple things and just forgot1

 

[tom]

pveversion and /etc/hosts looks ok.

- do you have the right time on your server?
- is this a single host or a cluster node?

 

[Kaanha]

It's a single machine and the time and date are spot on

root@silverdragon:~# date
Sun Jun  2 11:53:50 EDT 2013

 

[tom]

any hint in the syslog? (/var/log/syslog)

 

[Kaanha]

I don't see anything suggesting what could be causing an issue. Here is a small snippet, I tried to get as much information in it as possible that I thought might be helpful...

Jun  2 10:48:26 silverdragon pvedaemon[23795]: server closing
Jun  2 10:48:26 silverdragon rrdcached[2774]: caught SIGTERM
Jun  2 10:48:26 silverdragon rrdcached[2774]: starting shutdown
Jun  2 10:48:26 silverdragon rrdcached[2774]: clean shutdown; all RRDs flushed
Jun  2 10:48:26 silverdragon rrdcached[2774]: removing journals
Jun  2 10:48:26 silverdragon rrdcached[2774]: removing old journal /var/lib/rrdcached/journal/rrd.journal.$
Jun  2 10:48:26 silverdragon rrdcached[2774]: removing old journal /var/lib/rrdcached/journal/rrd.journal.$
Jun  2 10:48:26 silverdragon rrdcached[2774]: goodbye
Jun  2 11:06:48 silverdragon pveproxy[350690]: starting server
Jun  2 11:06:48 silverdragon pveproxy[350690]: starting 3 worker(s)
Jun  2 11:06:48 silverdragon pveproxy[350690]: worker 350691 started
Jun  2 11:06:48 silverdragon pveproxy[350690]: worker 350692 started
Jun  2 11:06:48 silverdragon pveproxy[350690]: worker 350693 started
Jun  2 11:17:01 silverdragon /USR/SBIN/CRON[350749]: (root) CMD (   cd / && run-parts --report /etc/cron.h$
Jun  2 11:19:02 silverdragon qm[350761]: <root@pam> starting task UPID:silverdragon:00055A2A:0291DF6D:51AB$
Jun  2 11:19:02 silverdragon qm[350762]: shutdown VM 100: UPID:silverdragon:00055A2A:0291DF6D:51AB6266:qms$
Jun  2 11:19:02 silverdragon qm[350762]: unable to find configuration file for VM 100 - no such machine
Jun  2 11:19:02 silverdragon qm[350761]: <root@pam> end task UPID:silverdragon:00055A2A:0291DF6D:51AB6266:$
Jun  2 11:19:11 silverdragon qm[350763]: <root@pam> starting task UPID:silverdragon:00055A2C:0291E2B2:51AB$
Jun  2 11:19:11 silverdragon qm[350764]: stop VM 100: UPID:silverdragon:00055A2C:0291E2B2:51AB626F:qmstop:$
Jun  2 11:19:11 silverdragon qm[350764]: unable to find configuration file for VM 100 - no such machine
Jun  2 11:19:11 silverdragon qm[350763]: <root@pam> end task UPID:silverdragon:00055A2C:0291E2B2:51AB626F:$
Jun  2 11:19:22 silverdragon shutdown[350766]: shutting down for system reboot
Jun  2 11:29:24 silverdragon qm[350817]: <root@pam> starting task UPID:silverdragon:00055A62:0292D232:51AB$
Jun  2 11:29:24 silverdragon qm[350818]: stop VM 100: UPID:silverdragon:00055A62:0292D232:51AB64D4:qmstop:$
Jun  2 11:29:24 silverdragon qm[350818]: unable to find configuration file for VM 100 - no such machine
Jun  2 11:29:24 silverdragon qm[350817]: <root@pam> end task UPID:silverdragon:00055A62:0292D232:51AB64D4:$
Jun  2 11:36:06 silverdragon kernel: CT: 105: started
Jun  2 11:36:07 silverdragon kernel: device veth105.0 entered promiscuous mode
Jun  2 11:36:07 silverdragon kernel: vmbr0: port 2(veth105.0) entering forwarding state
Jun  2 11:36:09 silverdragon ntpd[343168]: Listen normally on 15 veth105.0 fe80::b06d:52ff:fe2c:fb38 UDP 1$
Jun  2 11:36:09 silverdragon ntpd[343168]: peers refreshed
Jun  2 11:36:17 silverdragon kernel: veth105.0: no IPv6 routers present
Jun  2 11:40:30 silverdragon shutdown[350998]: shutting down for system reboot

The system never shut down after that last line, no restart command works at all.

I can't remember what I time I have my system backup happen on the weekend but could it be possible that it's performing a backup is the reason the reboot commands won't wor

 

[tom]

just to note, qm is a command for KVM, not for containers. therefore you get

unable to find configuration file for VM 100 - no such machine

but before you debug the CT, find out why you can´t login to the web interface. But I am out of ideas.

 

[Kaanha]

Yeah, I've been trying to figure that out myself....

Is there a separate method to change the password for the web interface? I've done passwd and changed the root password, but still no luck. So I was curious if there was a way to independently change the web interface password so I could reset it.

 

[tom]

the root account is the same for console or web (and yes, passwd is the right way to change)

 

[dietmar]

Maybe a problem with the proxmox file system. What is the output of

# ls -l /etc/pve