SSH only after IP change

tl5k5

New Member
Jul 28, 2017
19
0
1
47
Hello all,
My test server, soon to be in production, won't allow me to access the web interface after I recently changed it's IP address. I've changed this servers IP twice...this time there's a problem.
I started with changing the IP in the web interface and after I reboot I changed the /etc/hosts file followed by a 2nd reboot. I should have changed them at the same time, but I forgot to change hosts before I rebooted.
Hosts and /etc/network/interfaces look correct. I assume there's a service config that is not happy.

This is a non-HA config.
interfaces:
auto vmbr0
iface vmbr0 inet static
address 10.x.x.20
netmask 255.255.255.0
gateway 10.x.x.254
bridge_ports enp5s0
bridge_stp off
bridge_fd 0


hosts:
127.0.0.1 localhost.localdomain localhost
10.x.x.20 name.local name pvelocalhost



Any guidance?

Thanks!
 

tl5k5

New Member
Jul 28, 2017
19
0
1
47
Apparently /etc/pve is now an empty directory. How does that happen???
 

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
3,798
345
83
31
Vienna
what does
Code:
systemctl status pve-cluster
say?
 

tl5k5

New Member
Jul 28, 2017
19
0
1
47
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-09-07 14:10:09 CDT; 18h ago
Process: 3403 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)

Sep 07 14:10:09 name systemd[1]: Starting The Proxmox VE cluster filesystem...
Sep 07 14:10:09 name pmxcfs[3403]: [database] crit: found entry with duplicate name (inode = 00000000001FAA62,
Sep 07 14:10:09 name pmxcfs[3403]: [database] crit: found entry with duplicate name (inode = 00000000001FAA62,
Sep 07 14:10:09 name pmxcfs[3403]: [database] crit: DB load failed
Sep 07 14:10:09 name pmxcfs[3403]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-clust
Sep 07 14:10:09 name pmxcfs[3403]: [main] notice: exit proxmox configuration filesystem (-1)
Sep 07 14:10:09 name systemd[1]: pve-cluster.service: Control process exited, code=exited status=255
Sep 07 14:10:09 name systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Sep 07 14:10:09 name systemd[1]: pve-cluster.service: Unit entered failed state.
Sep 07 14:10:09 name systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
 

tl5k5

New Member
Jul 28, 2017
19
0
1
47
Rebuilding. Wish I knew what happened so I can avoid it happening again!
 

About

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

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 your own in 60 seconds.

Buy now!