[SOLVED] PVE does not accept root passwd anymore

DrillSgtErnst

Active Member
Jun 29, 2020
91
6
28
Hi,
since this weekend my PVE Server does not accept my rott Password anymore.
I even set it again via passwd, but PVE does not accept it
<pre>root@pvetest:~# pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.4: 6.4-4
pve-kernel-helper: 6.4-4
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve4~bpo10
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.3-1
proxmox-backup-client: 1.1.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
</pre>

I don't know where to look. I have root access to the physical machine.
 
Hi,
do you mean the web UI or via ssh? In the first case, please check that the correct realm (PAM) is selected. In the latter case, is PermitRootLogin set in /etc/ssh/sshd_config?
 
And via ssh it works? To rule out some keyboard config issue or something along those lines, please try typing out the password in the username field first to see if it's what you expect to be typing. Is Wrong Password the full error message?
 
Well SSH does work.

the complete message says "Login failed. Please try again"

I saw a little timedrift and setup the ntp. But still the same error. The backups meanwhile fail too
100 VM 100 FAILED 00:00:00 unable to open file '/etc/pve/nodes/hostname/qemu-server/100.conf.tmp.117814' - Input/output error
 
sounds like an issue with pmxcfs.. is it quorate (pvecm status / systemctl status pve-cluster corosync)?
 
isn't corosync only for clusters?
I have a standalone machine

pvecm does say similar
root@pvetest:~# pvecm status
Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?

root@pvetest:~# systemctl status pve-cluster corosync
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-06-23 09:04:27 CEST; 3 weeks 1 days ago
Main PID: 5817 (pmxcfs)
Tasks: 7 (limit: 19660)
Memory: 54.8M
CGroup: /system.slice/pve-cluster.service
└─5817 /usr/bin/pmxcfs

Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/100: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/124: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/136: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/135: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/123: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pvetest/local: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pvetest/pbstest: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pvetest/backup: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pvetest/local-zfs: -1
Jul 13 09:06:03 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pvetest/backup_usb: -1

● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2021-06-23 09:04:27 CEST; 3 weeks 1 days ago
Docs: man:corosync
man:corosync.conf
man:corosync_overview

Jun 23 09:04:27 pvetest systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
 
can you touch a file on pmxcfs? like touch /etc/pve/test? if not, anything visible in the logs?
 
can you post journalctl -b -u pve-cluster?
 
-- Logs begin at Wed 2021-06-23 09:04:16 CEST, end at Thu 2021-07-15 14:23:17 CEST. --
Jun 23 09:04:26 pvetest systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 23 09:04:27 pvetest systemd[1]: Started The Proxmox VE cluster filesystem.
Jul 10 01:07:30 pvetest pmxcfs[5817]: [database] crit: commit transaction failed: database or disk is full#010
Jul 10 01:07:30 pvetest pmxcfs[5817]: [database] crit: rollback transaction failed: cannot rollback - no transaction is active#010
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-node/pvetest: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-node/pvetest: /var/lib/rrdcached/db/pve2-node/pvetest: illegal attempt to u
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/204: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/204: /var/lib/rrdcached/db/pve2-vm/204: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/131: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/131: /var/lib/rrdcached/db/pve2-vm/131: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/199: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/199: /var/lib/rrdcached/db/pve2-vm/199: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/201: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/201: /var/lib/rrdcached/db/pve2-vm/201: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/102: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/102: /var/lib/rrdcached/db/pve2-vm/102: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/100: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/100: /var/lib/rrdcached/db/pve2-vm/100: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/126: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/203: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/203: /var/lib/rrdcached/db/pve2-vm/203: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/205: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/205: /var/lib/rrdcached/db/pve2-vm/205: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/118: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/113: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/113: /var/lib/rrdcached/db/pve2-vm/113: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/121: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/121: /var/lib/rrdcached/db/pve2-vm/121: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/111: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/200: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/202: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/202: /var/lib/rrdcached/db/pve2-vm/202: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/119: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/119: /var/lib/rrdcached/db/pve2-vm/119: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/120: -1
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/120: /var/lib/rrdcached/db/pve2-vm/120: illegal attempt to update using
Jul 13 09:02:33 pvetest pmxcfs[5817]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/135: -1
 
possibly it was full on the 10th? can you try restarting pve-cluster (and check the logs again after that for any errors/warnings)?
 

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!

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!