After installing proxmox 6 and restarting the server. Page not working and files disappear.

[Devanger]

Hello.
They disappear after installing proxmox 6 from the template and also manually through your iso, files from the /etc/pve directory.
It's possible that they disappeared somewhere else but I can't detect it.

Please help.
I installed promox 6, then I did a standard server update, and when the server has started and responds to ping, my server's proxmox page no longer works and these files disappear from /etc/pve



photo after fresh installation





and here the photo after reboot.



files are gone





- As something sorry i use google translate

 

[t.lamprecht]

I installed promox 6, then I did a standard server update,

I'd guess that you did not had any valid Package repositories setup, and possible did not looked what the upgrade proposed and thus removed some packages. Please ensure you have a valid repository setup.. https://pve.proxmox.com/wiki/Package_Repositories

and here the photo after reboot.

They are not gone, the pve-cluster service isn't running/had an error and thus it doesn't provides the mountpoint on /etc/pve.
systemctl status pve-cluster.service

 

[Devanger]

@t.lamprecht
After updating your repositories, there is still the same problem as I wrote above.

 

[t.lamprecht]

After updating your repositories, there is still the same problem as I wrote above.

Yeah, removed packages do not automatically get back, this needs to be done before the first upgrade...

Check the full log, journalctl -b -u pve-cluster and please post the output in text format, e.g., in [code] content here [/code] tags...

As said, you did some upgrades with incomplete repositories, and we have no idea what you changes from apt you accepted on the upgrade...

You can also check [/icode]less /var/log/apt/history.log.1[/icode] or if that got rotated then zless /var/log/apt/history.log.1.gz for what was done on the upgrade.

 

[lps90]

Using a soyoustart (OVH) dedicated server?
same problem already reported yesterday: https://forum.proxmox.com/threads/ovh-proxmox-6-no-web-gui-access.70644/#post-317085

 

[Devanger]

Generally there were standard repositories from ovh and we changed to what you provided on the site.

## Note, this file is written by cloud-init on first boot of an instance
## modifications made here will not survive a re-bundle.
## if you wish to make changes you can:
## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg
##     or do the same in user-data
## b.) add sources in /etc/apt/sources.list.d
## c.) make changes to template file /etc/cloud/templates/sources.list.debian.tmpl
###

# See http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.html
# for how to upgrade to newer versions of the distribution.
deb http://deb.debian.org/debian buster main
deb-src http://deb.debian.org/debian buster main

## Major bug fix updates produced after the final release of the
## distribution.
deb http://security.debian.org/ buster/updates main
deb-src http://security.debian.org/ buster/updates main
deb http://deb.debian.org/debian buster-updates main
deb-src http://deb.debian.org/debian buster-updates main

## Uncomment the following two lines to add software from the 'backports'
## repository.
##
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
deb http://deb.debian.org/debian buster-backports main
deb-src http://deb.debian.org/debian buster-backports main
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

Check the full log, journalctl -b -u pve-cluster and please post the output in text format, e.g.,.

root@ns3134046:~# journalctl -b -u pve-cluster
-- Logs begin at Tue 2020-06-02 18:27:51 UTC, end at Tue 2020-06-02 18:29:03 UTC. --
Jun 02 18:28:03 ns3134046 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 02 18:28:03 ns3134046 pmxcfs[1073]: [main] crit: Unable to get local IP address
Jun 02 18:28:03 ns3134046 pmxcfs[1073]: [main] crit: Unable to get local IP address
Jun 02 18:28:03 ns3134046 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 02 18:28:03 ns3134046 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 02 18:28:03 ns3134046 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 02 18:28:03 ns3134046 systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jun 02 18:28:03 ns3134046 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
Jun 02 18:28:03 ns3134046 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 02 18:28:03 ns3134046 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 02 18:28:03 ns3134046 pmxcfs[1227]: [main] crit: Unable to get local IP address
Jun 02 18:28:03 ns3134046 pmxcfs[1227]: [main] crit: Unable to get local IP address
Jun 02 18:28:03 ns3134046 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 02 18:28:03 ns3134046 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 02 18:28:03 ns3134046 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
Jun 02 18:28:04 ns3134046 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 02 18:28:04 ns3134046 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 02 18:28:04 ns3134046 pmxcfs[1229]: [main] crit: Unable to get local IP address
Jun 02 18:28:04 ns3134046 pmxcfs[1229]: [main] crit: Unable to get local IP address
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 02 18:28:04 ns3134046 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
Jun 02 18:28:04 ns3134046 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 02 18:28:04 ns3134046 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 02 18:28:04 ns3134046 pmxcfs[1234]: [main] crit: Unable to get local IP address
Jun 02 18:28:04 ns3134046 pmxcfs[1234]: [main] crit: Unable to get local IP address
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 02 18:28:04 ns3134046 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.
Jun 02 18:28:04 ns3134046 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 02 18:28:04 ns3134046 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 02 18:28:04 ns3134046 pmxcfs[1238]: [main] crit: Unable to get local IP address
Jun 02 18:28:04 ns3134046 pmxcfs[1238]: [main] crit: Unable to get local IP address
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 02 18:28:04 ns3134046 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Jun 02 18:28:04 ns3134046 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Start request repeated too quickly.
Jun 02 18:28:04 ns3134046 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jun 02 18:28:04 ns3134046 systemd[1]: Failed to start The Proxmox VE cluster filesystem.

 

[lps90]

I already told you a "solution"
(not a full solution, but it solves the problem if you edit your hosts file..)
check the link i told you before..

 

[lps90]

There's another solution too (a better one).
You can install Proxmox 5 template and update / upgrade using this tutorial:
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0#Known_upgrade_issues

After restarting, it will boot the Web Gui with no problems

 

[t.lamprecht]

Jun 02 18:28:03 ns3134046 pmxcfs[1073]: [main] crit: Unable to get local IP address

OK, better than what I thought. You have to just fix your /etc/hosts file, i.e., add an entry for your nodename and the public (or cluster) IP and drop entries to loopback addresses for the nodename (localhost has to stay)