Update auf 1.2.5.4 >> stündliches Email

[t_heinrich]

Hallo,

ich habe heute auf meinen Pi3 ein Update auf Version 1.2.5.4 gemacht.
Unter "System Information" kann ich als Laie nichts ungewöhnliches, auffälliges entdecken.

Seit dem Update erhalte ich stündlich eine Email vom Loxberry mit folgendem Betreff:

Cron <root@loxberry> cd / && run-parts --report /etc/cron.hourly

und folgendem Inhalt:

/etc/cron.hourly/logrotate:
error: skipping "/var/log/apt/term.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/apt/history.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/aptitude" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/alternatives.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/lighttpd/*.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mail.info" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mail.warn" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mail.err" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/mail.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/daemon.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/kern.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/auth.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/user.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/lpr.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/cron.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/debug" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/messages" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/samba/log.smbd" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/samba/log.nmbd" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/samba/log.samba" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/unattended-upgrades/unattended-upgrades.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/unattended-upgrades/unattended-upgrades-dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/unattended-upgrades/unattended-upgrades-shutdown.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
run-parts: /etc/cron.hourly/logrotate exited with return code 1

Hab ich irgendwas falsch gemacht?

Gruß Thomas

[t_heinrich]

Hallo,
anbei mal noch die Übersicht aus den Systeminformationen, evtl. erkennt man da mehr ... ich leider nicht.

[Christian Fenzl]

Prof.Mobilux Kannstvdu das mit den Rechten im skel(?)-Ordner aufklären. Ich weiß auch nicht genau, wo wie was gesetzt sein sollte.

t_heinrich Du hast jedenfalls nichts falsch gemacht - das AlexaLox Plugin (und/oder vielleicht noch ein anderes) ist hier bei der Installation mit chmod 777 rekursiv durch Systemordner genagelt, und darüber beschweren sich nun die Systemdienste (cron, logrotate).

Welche Plugins hast du drauf?

[t_heinrich]

Hallo,
ach das tut gut, sonst bekomme ich immer nur gesagt "du bist schuld" :-P

Anbei ein Screenshoots meiner PlugIns.

[svethi]

Ja, mit dem Alexa gabs da mal Probleme

[Gast]

Ich habe das gleiche Problem. Das Update auf die, in nem anderen Threat hingewiesene Version 0.10b, habe ich gemacht. Hat aber nix geholfen......
Grüße,
Michael

[Christian Fenzl]

t_heinrich Wenn du das Alexa4Lox Update vom 27.10. noch nicht eingespielt hast, musst du das zuerst machen: https://www.loxforum.com/forum/proje...0968-alexa-lox

t_heinrich Gast Das Alexa4Lox Update behebt das Problem nicht. Dieses chmod 777 wurde in den Vorgänger-Versionen vom Daemon, also bei jedem Systemstart, ausgeführt - damit wird es nach manuellem Fixen beim nächsten Start gleich wieder umgestellt. Deswegen ist das Update Grundvoraussetzung.

So, und dann (ohne Gewähr!):

Als root an der Shell anmelden
umount /var/log -l
Dann wechselt dorthin: cd /var/log
Zum Prüfen, ob ungemounted wurde: df -h . (mit Punkt)

- Wenn ihr als Size die Größe eurer SD seht, hat's funktioniert, sonst nochmal aus dem Ordner raus und nochmal umount /var/log -l (oder -f), und nochmal mit df -h . prüfen.

Wenn das die SD ist, dann schauen, was in /var/log auf der SD liegt. Aus meiner Sicht sollte der Ordner leer sein.

Zeigt mal mit ls -l -a was da drin ist.

PS: Danach rebooten, damit der Mount wieder stimmt.

[Prof.Mobilux]

Zum Reparieren müsst ihr folgende Befehle (als root) in Putty durchführen:

chown -R daemon:daemon /var/log
chmod 0755 /var/log
chown -R loxberry:loxberry /opt/loxberry/log/skel_syslog/*
chown -R root:root /opt/loxberry/log/skel_syslog/apt
chown -R root:adm /opt/loxberry/log/skel_syslog/samba
chmod -R 0750 /opt/loxberry/log/skel_syslog/*
chmod -R 0755 /opt/loxberry/log/skel_syslog/apt
chmod -R 0755 /opt/loxberry/log/skel_syslog/fsck
chown -R loxberry:loxberry /opt/loxberry/log/skel_system/*
chmod -R 0755 /opt/loxberry/log/skel_system/*

Danach rebooten. Dann sollte es wieder passen.

[weitho]

Guten Abend, habt ihr bitte ein to do dafür. Bin kein Programmierer, Dankeschön

[t_heinrich]

Prof.Mobilux und Gast Fenzl: danke für eure Unterstützung, hab's mal ausgeführt und melde mich, wenn ich keine Mails mehr bekomme.

@weitho: kurzes Stöbern im Loxberry-Wiki bringt dich hierhin:

https://www.loxwiki.eu/pages/viewpage.action?pageId=12091660

[Gast]

Zum Reparieren müsst ihr folgende Befehle (als root) in Putty durchführen:

chown -R daemon:daemon /var/log
chmod 0755 /var/log
chown -R loxberry:loxberry /opt/loxberry/log/skel_syslog/*
chown -R root:root /opt/loxberry/log/skel_syslog/apt
chown -R root:adm /opt/loxberry/log/skel_syslog/samba
chmod -R 0750 /opt/loxberry/log/skel_syslog/*
chmod -R 0755 /opt/loxberry/log/skel_syslog/apt
chmod -R 0755 /opt/loxberry/log/skel_syslog/fsck
chown -R loxberry:loxberry /opt/loxberry/log/skel_system/*
chmod -R 0755 /opt/loxberry/log/skel_system/*

Danach rebooten. Dann sollte es wieder passen.

Hallo,
hat funktioniert. Seit gestern Abend bekomme ich keine Mails mehr!!!
Vielen Dank!!!!!!

Grüße,
Michael

[t_heinrich]

Hat auch bei mir funktionniert, vielen Dank für eure schnelle Unterstützung!!

[weitho]

Hallo, leider hat es bei mir nicht geklappt! Habe alles wie laut Anleitung als "root"durchgeführt. Die besagten Mails kommen laufend ... Vielleicht hat jemand einen anderen Vorschlag für mich. Dankeschön

[Christian Fenzl]

Das Alexa-Plugin, sofern im Einsatz, hast du aktualisiert?

[weitho]

Servus, habe ich nicht installiert

[weitho]

Schönen Tag, ich habe einmal alle nicht verwendeten Plugin´s deinstalliert. Jetzt bekomme ich keine Mails mehr. Danke nochmals für eure Unterstützung.

[Christian Fenzl]

Weißt du noch, was du alles deinstalliert hast?
Das wäre ein Anhaltspunkt, ob vielleicht noch ein anderes Plugin außer die alte Version von Alexa hier einen "Bock abschließt".