[Gelöst] Hilfe Fhem startet dauernd.

Begonnen von Hackstall, 30 Juli 2021, 21:21:27

Vorheriges Thema - Nächstes Thema

Hackstall

Hilfe,

nach einem Spannungseinbruch auf meinem Raspberry passieren
nun scheinbar schlimmer Dinge in meinem Containter

Er wiederholt ständig die folgende Sequenz und FHEM reboot ständig
Kann man das weider reparieren?
Bitte um Hilfe


Preparing configuration ... done
Starting FHEM ...
su: user fhem does not exist
Unable to start FHEM process - errorcode 1
Preparing user environment ...
1. Creating group 'fhem' with GID 1000 ...
groupadd: existing lock file /etc/group.lock without a PID
groupadd: cannot lock /etc/group; try again later.
2. Enforcing GID for group 'bluetooth' to 6001 ...
3. Creating user 'fhem' with UID 1000 ...
useradd: existing lock file /etc/passwd.lock without a PID
useradd: cannot lock /etc/passwd; try again later.
usermod: group '1000' does not exist
adduser: The user `fhem' does not exist.
adduser: The user `fhem' does not exist.
adduser: The user `fhem' does not exist.
adduser: The user `fhem' does not exist.
adduser: The user `fhem' does not exist.
adduser: The user `fhem' does not exist.
4. Creating log directory /opt/fhem/./log ...
5. Enforcing user and group ownership for /opt/fhem to fhem:fhem ...
6. Enforcing file and directory permissions for /opt/fhem ...
7. Correcting group ownership for /dev/tty* ...
/entry.sh: line 328: [[: /dev/gpiomem
/dev/gpiochip2
/dev/gpiochip1
/dev/gpiochip0: syntax error: operand expected (error token is "/dev/gpiomem
/dev/gpiochip2
/dev/gpiochip1
/dev/gpiochip0")
8. Found GPIO: Correcting group permissions in /dev and /sys to 'gpio' with GID 6002 ...
groupadd: existing lock file /etc/group.lock without a PID
groupadd: cannot lock /etc/group; try again later.
adduser: The user `fhem' does not exist.
chown: invalid user: '.gpio'
9. Found I2C: Correcting group permissions in /dev to 'i2c' with GID 6003 ...
adduser: The user `fhem' does not exist.
10. Updating /etc/sudoers.d/fhem-docker ...
/entry.sh: line 414: [: too many arguments
/entry.sh: line 421: [: too many arguments
11. Pre-authorizing SSH to Docker host for user 'fhem' ...
12. Updating SSH key pinning and SSH client permissions for user 'fhem' ...
chown: invalid user: 'fhem.fhem'


Hackstall

Habs gefunden.

es waren einige Files unter /etc gelockt und daher war kein Update möglich.

Gruss Andreas