Failed to start Proxmox VE firewall on fresh install

W

worian

New Member
Apr 7, 2020
8
0
1
44
Hey there,

I was using Proxmox 4 on a single computer that I use as a personal server, and decided that corona lockdown was the perfect occasion to switch to v6.1

I downloaded the image from Proxmox website, burnt it on a usb stick, and totally reinstalled it on the PC hard drive. Install went fine.
After the reinstall, I was not able to access the GUI though I did nothing more than installing.
I tried to reinstall again (downloading the image again to reject the theory of a possible corruption, used another usb drive,...).
Still unable to access GUI. Even from the machine with curl on localhost:8006.

In short, systemctl status 'pve*' says (full version in file attached):

Failed to start Proxmox VE firewall.
pve-firewall.service: Failed with result 'timeout'.

pve systemd[1]: Failed to start PVE Status Daemon.
Process: 740 ExecStart=/usr/bin/pvestatd start (code=killed, signal=TERM)

Apr 07 14:23:27 pve systemd[1]: Failed to start PVE Cluster Resource Manager Daemon.
Process: 937 ExecStart=/usr/sbin/pve-ha-crm start (code=killed, signal=TERM)
Click to expand...

I did some googling and forum lookup, tried all the tips I found. I made all the updates with aptitude. No success. I have had temporary success where I've been able to access GUI but it was gone again after reboot. I think this success happened when I reduced /etc/hosts to the following, though I'm not sure since I tried other tricks, since host file was not changed since then while I lost GUI access again, and since I'm not able to retrieve GUI access when I replay the commands I sent...

127.0.0.1 localhost
192.168.1.50 pve

# 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
Click to expand...

If you have any clue please let me know,
Thanks for your time,
Julien
 

Attachments

Last edited:
could you post the journal boot output as well? journalctl -b
 
can you access /etc/pve ? do you see directories and files in there?
 
Yes

root@pve:/etc/pve# ls
authkey.pub local nodes priv pve-www.key storage.cfg vzdump.cron
datacenter.cfg lxc openvz pve-root-ca.pem qemu-server user.cfg
Click to expand...
 
could you try the following
Code: 
systemctl stop pveproxy pvedaemon
pveproxy start -d

and post the output?[/code]
 
No output after 10 min if I just keep waiting, but after this command I can kind of connect the web gui url, then text appears (see blow)
But when the URL finishes loading I get a blank webpage, but with the right title though "pve - Proxmox Virtual Environment", there's some progress :)
(tried to empty cache and another browser, page still blank)

Code: 
root@pve:/home# pveproxy start -d
4359: ACCEPT FH10 CONN1
4361: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x565434ee6e60)
4361: CLOSE FH10 CONN0
close connection AnyEvent::Handle=HASH(0x565434ee6e60)
4359: CLOSE FH10 CONN0
4359: ACCEPT FH10 CONN1
4361: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x565435883ec0)
4361: CLOSE FH10 CONN0
close connection AnyEvent::Handle=HASH(0x56543588a440)
4359: CLOSE FH10 CONN0
4360: ACCEPT FH10 CONN1
4361: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x565434ee4198)
4361: CLOSE FH10 CONN0
4359: ACCEPT FH10 CONN1
4361: ACCEPT FH10 CONN1
4361: ACCEPT FH11 CONN2
4361: ACCEPT FH12 CONN3
4361: ACCEPT FH14 CONN4
4359: ACCEPT FH12 CONN2
close connection AnyEvent::Handle=HASH(0x565435b54778)
4359: CLOSE FH12 CONN1
close connection AnyEvent::Handle=HASH(0x5654358bae50)
4359: CLOSE FH10 CONN0
4359: ACCEPT FH10 CONN1
close connection AnyEvent::Handle=HASH(0x565434ee4150)
4361: CLOSE FH10 CONN3
close connection AnyEvent::Handle=HASH(0x5654306f8de0)
4361: CLOSE FH11 CONN2
close connection AnyEvent::Handle=HASH(0x565435889d98)
4361: CLOSE FH12 CONN1
close connection AnyEvent::Handle=HASH(0x5654358bb440)
 
okay - can you kill that foreground process and run systemctl start pveproxy pvedaemon and look at the journal again?
 
I get this
Code: 
root@pve:~# systemctl start pveproxy pvedaemon
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xe" for details.

Code: 
Apr 09 08:28:56 pve pveproxy[13410]: start failed - can't acquire lock '/var/run/pveproxy/pveproxy.pid.lock' - daemon already started (pid = 4478)
Apr 09 08:28:56 pve pveproxy[13410]: start failed - can't acquire lock '/var/run/pveproxy/pveproxy.pid.lock' - daemon already started (pid = 4478)
Apr 09 08:28:56 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
Apr 09 08:28:56 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Apr 09 08:28:56 pve systemd[1]: Failed to start PVE API Proxy Server.
Apr 09 08:28:56 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Apr 09 08:28:56 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 1.
Apr 09 08:28:56 pve systemd[1]: Stopped PVE API Proxy Server.
Apr 09 08:28:56 pve systemd[1]: Starting PVE API Proxy Server...
Apr 09 08:29:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 08:29:50 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 08:29:50 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 08:30:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 08:30:39 pve pveproxy[13451]: start failed - can't acquire lock '/var/run/pveproxy/pveproxy.pid.lock' - Resource temporarily unavailable
Apr 09 08:30:39 pve pveproxy[13451]: start failed - can't acquire lock '/var/run/pveproxy/pveproxy.pid.lock' - Resource temporarily unavailable
Apr 09 08:30:39 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
Apr 09 08:30:39 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Apr 09 08:30:39 pve systemd[1]: Failed to start PVE API Proxy Server.
Apr 09 08:30:39 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Apr 09 08:30:39 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 2.
Apr 09 08:30:39 pve systemd[1]: Stopped PVE API Proxy Server.
Apr 09 08:30:40 pve systemd[1]: Starting PVE API Proxy Server...
Apr 09 08:30:49 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 08:30:49 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 08:31:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 08:31:50 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 08:31:50 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 08:32:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 08:32:17 pve pveproxy[13495]: start failed - can't acquire lock '/var/run/pveproxy/pveproxy.pid.lock' - Resource temporarily unavailable
Apr 09 08:32:17 pve pveproxy[13495]: start failed - can't acquire lock '/var/run/pveproxy/pveproxy.pid.lock' - Resource temporarily unavailable
Apr 09 08:32:18 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
Apr 09 08:32:18 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Apr 09 08:32:18 pve systemd[1]: Failed to start PVE API Proxy Server.
Apr 09 08:32:18 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Apr 09 08:32:18 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
Apr 09 08:32:18 pve systemd[1]: Stopped PVE API Proxy Server.
Apr 09 08:32:18 pve systemd[1]: Starting PVE API Proxy Server...
Apr 09 08:32:45 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 08:32:45 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 08:32:51 pve smartd[631]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 69 to 70
Apr 09 08:33:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 08:33:53 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 08:33:53 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 08:34:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 08:34:03 pve pveproxy[13519]: start failed - can't acquire lock '/var/run/pveproxy/pveproxy.pid.lock' - Resource temporarily unavailable
Apr 09 08:34:03 pve pveproxy[13519]: start failed - can't acquire lock '/var/run/pveproxy/pveproxy.pid.lock' - Resource temporarily unavailable
Apr 09 08:34:03 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
Apr 09 08:34:03 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Apr 09 08:34:03 pve systemd[1]: Failed to start PVE API Proxy Server.
Apr 09 08:34:03 pve systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Apr 09 08:34:03 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 4.
Apr 09 08:34:03 pve systemd[1]: Stopped PVE API Proxy Server.
Apr 09 08:34:04 pve systemd[1]: Starting PVE API Proxy Server...
 
you need to kill the other process first - e.g. with 'killall pveproxy'
 
Here is the result
(at IP:8006 still a blank webpage, with the right page title)

Code: 
root@pve:~# systemctl stop pveproxy pvedaemon
root@pve:~# date ; killall pvedaemon ; killall pveproxy ; systemctl start pveproxy pvedaemon ; date
Thu 09 Apr 2020 08:54:09 PM CEST
pvedaemon: no process found
pveproxy: no process found
Thu 09 Apr 2020 08:57:14 PM CEST

Code: 
root@pve:~# journalctl
...
Apr 09 20:54:05 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 20:54:05 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 20:54:05 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 20:54:10 pve systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Apr 09 20:54:10 pve systemd[1]: Starting PVE API Daemon...
Apr 09 20:54:10 pve systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Apr 09 20:54:52 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 20:54:52 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 20:55:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 20:55:23 pve pvedaemon[27175]: starting server
Apr 09 20:55:23 pve pvedaemon[27175]: starting 3 worker(s)
Apr 09 20:55:23 pve pvedaemon[27175]: worker 27176 started
Apr 09 20:55:23 pve pvedaemon[27175]: worker 27177 started
Apr 09 20:55:23 pve pvedaemon[27175]: worker 27178 started
Apr 09 20:55:25 pve systemd[1]: Started PVE API Daemon.
Apr 09 20:55:25 pve systemd[1]: Starting PVE API Proxy Server...
Apr 09 20:55:53 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 20:55:53 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 20:56:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 20:56:51 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 20:56:51 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 20:57:00 pve systemd[1]: Starting Proxmox VE replication runner...
Apr 09 20:57:07 pve pveproxy[27213]: starting server
Apr 09 20:57:07 pve pveproxy[27213]: starting 3 worker(s)
Apr 09 20:57:07 pve pveproxy[27213]: worker 27214 started
Apr 09 20:57:07 pve pveproxy[27213]: worker 27215 started
Apr 09 20:57:08 pve pveproxy[27213]: worker 27216 started
Apr 09 20:57:09 pve systemd[1]: Started PVE API Proxy Server.
Apr 09 20:57:30 pve systemd[1]: pvesr.service: Succeeded.
Apr 09 20:57:30 pve systemd[1]: Started Proxmox VE replication runner.
Apr 09 20:58:00 pve systemd[1]: Starting Proxmox VE replication runner...
 
can you try reloading with cleared cache? do the developer tools in the browser say anything when you refresh? that kind of sounds like missing JS files...
 
You're right, it fails loading ext-all.js because of connection loss
It used display the GUI correctly previously, when it did display. So I guess the file is here but there are still difficulties for the browser to reach it through pveproxy or so

Code: 
[Error] Failed to load resource: La connexion réseau a été perdue. (ext-all.js, line 0)
[Error] ReferenceError: Can't find variable: Ext
    Code général (charts.js:1)
[Error] ReferenceError: Can't find variable: Ext
    Code général (proxmoxlib.js:2)
[Error] ReferenceError: Can't find variable: Ext
    Code général (pvemanagerlib.js:396)
[Error] ReferenceError: Can't find variable: Ext
    Code général (locale-en.js:1)
[Error] ReferenceError: Can't find variable: Ext
    Code général (192.168.1.50:37)
 
could you check pveproxy logs for those requests? maybe they provide a hint..
 
After days looking out, still the issue here. I give up for now, maybe I'll come back to Proxmox at the next major version. Thanks for your time helping me trying to find out.
 
I had same problem. Make sure you use https://your IP:port
Don't blow off the FDQN entry on setup even if you don't "need" one. Use 'pve.home' if you must.
Chromium nagged me a little still.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom