PVE Zwei Faktor funktioniert nicht mehr

achim22

Renowned Member
May 21, 2015
419
5
83
59
Dortmund
Hallo, habe zu Testzwecken den PVE 8.0 installiert und Google Authenticator eingerichtet, so wie bei allen Installationen von PVE.
Jetzt erhalte ich die Meldung: Anmeldung fehlgeschlagen. Bitte versuchen Sie es noch einmal.

Ich komme aber per SSH drauf kann aber die /etc/pve/user.cfg nicht bearbeiten um die Google Authenticator zu deaktivieren.

Habe im Log auch eine menge Fehler:

Jun 28 10:26:14 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:19 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:24 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:29 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:34 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:39 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:44 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:49 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:54 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:26:59 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:27:04 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:27:09 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:27:13 pve pvescheduler[29838]: jobs: cfs-lock 'file-jobs_cfg' error: got lock request timeout Jun 28 10:27:13 pve pvescheduler[29837]: replication: cfs-lock 'file-replication_cfg' error: got lock request timeout Jun 28 10:27:14 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:27:15 pve pvedaemon[2900]: <root@pam> successful auth for user 'root@pam' Jun 28 10:27:19 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:27:24 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:27:25 pve pvedaemon[3507934]: authentication failure; rhost=::ffff:134.3.44.88 user=root@pam msg=unable to open file '/etc/pve/priv/tfa.cfg.tmp.3507934' - Input/output error Jun 28 10:27:29 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:27:34 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error Jun 28 10:27:39 pve pve-ha-lrm[2929]: unable to write lrm status file - unable to delete old temp file: Input/output error
 
cluster? oder standalone?

was sagt

journalctl -b -u pve-cluster

?
 
  • Like
Reactions: achim22
cluster? oder standalone?

was sagt

journalctl -b -u pve-cluster

?
Standalone... Fehler gefunden :)

Jun 27 19:22:53 pve systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Jun 27 19:22:54 pve systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
Jun 28 02:23:16 pve pmxcfs[2558]: [database] crit: commit transaction failed: database or disk is full#010
Jun 28 02:23:16 pve pmxcfs[2558]: [database] crit: rollback transaction failed: cannot rollback - no transaction is active#010
 
:) gut dass die installation nur fuer testzwecke war ;)