file log enormi su solarstrech

Discussioni relative al software di monitoraggio energetico METERN
megamarco83
Messaggi: 246
Iscritto il: 22/08/2016, 14:13

file log enormi su solarstrech

Messaggioda megamarco83 » 08/10/2018, 11:45

ciao con la solarstretch 3.1 su raspberry pi 2
con versione del kernel è:

Codice: Seleziona tutto

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.14.62-v7+ #1134 SMP Tue Aug 14 17:10:10 BST 2018 armv7l GNU/Linux


il lancio di cleanlog non funziona:

Codice: Seleziona tutto

pi@raspberrypi:~ $ cleanlog
Pulizia cartella \var\log
Pulizia cartella \var\log\apache2
Aggiornamento file RamLog
[....] RAMLOG: Write files to disk..tar: var/log/syslog: file modificato mentre                                                                              era in lettura
tar: var/log/auth.log: file modificato mentre era in lettura
tar: var/log/daemon.log: file modificato mentre era in lettura
. ok
pi@raspberrypi:~ $

infatti dopo averlo lanciato si ha:
andando a vedere i file contenuti in /var/log ci sono ancora i XXX.1 con dimensioni enormi

Codice: Seleziona tutto

pi@raspberrypi:/var/log $ ls
apache2   auth.log.1  btmp    daemon.log  debug.1   messages    rpimonitor.log  syslog.1  user.log.1  wtmp.1
auth.log  boot.log    btmp.1  debug


inoltre riguardo ai log della stretch:

in /var/log mi trovo:

1) file auth.log enorme da circa 45mb

Codice: Seleziona tutto

Sep 13 13:46:46 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Sep 13 13:46:46 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/eflowlive selfc
Sep 13 13:46:46 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 13 13:46:47 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Sep 13 13:46:47 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/eflowlive whin
Sep 13 13:46:47 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 13 13:46:47 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Sep 13 13:46:48 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/eflowlive whout grep ^4\(.*W\)
Sep 13 13:46:48 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 13 13:46:48 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Sep 13 13:46:51 raspberrypi CRON[792]: pam_unix(cron:session): session closed for user root
Sep 13 13:46:53 raspberrypi CRON[795]: pam_unix(cron:session): session closed for user root
Sep 13 13:46:56 raspberrypi sshd[3712]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.31.116.15  user=root
Sep 13 13:46:58 raspberrypi sshd[3712]: Failed password for root from 116.31.116.15 port 11881 ssh2


2) file btm da 4.6mb

Codice: Seleziona tutto

L  ssh:notty                           root                            116.31.xxx                                                                                                                                                                                                                                                          -Dš[    tt                                   ™Z  ssh:notty                           root                            116.31.xxx                                                                                                                                                                                                                                                        gDš[    tt                                   ™Z  ssh:notty                           root                            116.31.xxx                                                                                                                                                                                                                                                           jDš[    tt                                   ™Z  ssh:notty                           root                            116.31..XXX                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     >Oš[    tt                               


3) file daemon.log enorme da 74,3mb

Codice: Seleziona tutto

Sep 13 13:53:50 raspberrypi cron[384]: sendmail: authentication failed (method PLAIN)
Sep 13 13:53:50 raspberrypi cron[384]: sendmail: server message: 535-5.7.8 Username and Password not accepted. Learn more at
Sep 13 13:53:50 raspberrypi cron[384]: sendmail: server message: 535 5.7.8  https://support.google.com/mail/?p=BadCredentials k63-v6sm6512282wmd.46 - gsmtp
Sep 13 13:53:50 raspberrypi cron[384]: sendmail: could not send mail (account default from /etc/msmtprc)
Sep 13 13:53:51 raspberrypi fail2ban-client[27408]: ERROR  No file(s) found for glob /var/log/domoticz.log
Sep 13 13:53:51 raspberrypi fail2ban-client[27408]: ERROR  Failed during configuration: Have not found any log file for domoticz jail
Sep 13 13:53:52 raspberrypi systemd[1]: fail2ban.service: Control process exited, code=exited status=255
Sep 13 13:53:52 raspberrypi systemd[1]: Failed to start Fail2Ban Service.
Sep 13 13:53:52 raspberrypi systemd[1]: fail2ban.service: Unit entered failed state.
Sep 13 13:53:52 raspberrypi systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Sep 13 13:53:52 raspberrypi systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Sep 13 13:53:52 raspberrypi systemd[1]: Stopped Fail2Ban Service.
Sep 13 13:53:52 raspberrypi systemd[1]: Starting Fail2Ban Service...



4) syslog da 10mb

Codice: Seleziona tutto

Sep 13 13:56:28 raspberrypi systemd[1]: Failed to start Fail2Ban Service.
Sep 13 13:56:28 raspberrypi systemd[1]: fail2ban.service: Unit entered failed state.
Sep 13 13:56:28 raspberrypi systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Sep 13 13:56:28 raspberrypi systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Sep 13 13:56:28 raspberrypi systemd[1]: Stopped Fail2Ban Service.
Sep 13 13:56:28 raspberrypi systemd[1]: Starting Fail2Ban Service...
Sep 13 13:56:28 raspberrypi cron[384]: sendmail: authentication failed (method PLAIN)
Sep 13 13:56:28 raspberrypi cron[384]: sendmail: server message: 535-5.7.8 Username and Password not accepted. Learn more at
Sep 13 13:56:28 raspberrypi cron[384]: sendmail: server message: 535 5.7.8  https://support.google.com/mail/?p=BadCredentials j75-v6sm4833997wmj.8 - gsmtp
Sep 13 13:56:28 raspberrypi cron[384]: sendmail: could not send mail (account default from /etc/msmtprc)
Sep 13 13:56:28 raspberrypi CRON[2899]: (root) MAIL (mailed 59 bytes of output but got status 0x004d from MTA#012)


ed infine in /var/log/apache2

ho access.log e error.log ma sono piccolini da circa 90kb

in totale, come memoria siamo a:
Used: 1.98GB (87.19%) Free: 298.53MB Total: 2.28GB
ed ho già fatto pulizia dei due log da 40mb e 70mb (nel senso che nel conto sopra li ho già tolti)


Avatar utente
Flane
Messaggi: 2470
Iscritto il: 16/01/2016, 15:02

Re: file log enormi su solarstrech

Messaggioda Flane » 08/10/2018, 15:58

Hai il fail2ban che non si avvia e crea un sacco di errori perchè hai cancellato il file /var/log/domoticz.log
Intanto crea un file vuoto /var/log/domoticz.log con proprietario root e permessi 640 e riavvia.

Poi hai il sendmail non configurato che ti crea anche quello errori....
... basta leggere quello che c'è nel log ed un passo alla volta risolvere i problemi :roll:

Poi ferma MeterN e 123Solar e fai la pulizia con cleanlog.

e poi cerca di capire che cosa ancora intasa il log....

megamarco83
Messaggi: 246
Iscritto il: 22/08/2016, 14:13

Re: file log enormi su solarstrech

Messaggioda megamarco83 » 08/10/2018, 18:05

ciao, come si disabilita il send mail?

il file di domoticz lo avevo creato, forse c'era qualche problema per i permessi...ora ho riprovato con i permessi 640

questo è il file auth.log

Codice: Seleziona tutto

Oct  8 17:59:08 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/virtmeter 4 0 0 exppower 0 grep ^4\(.*W\)
Oct  8 17:59:08 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:08 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:11 raspberrypi CRON[21276]: pam_unix(cron:session): session closed for user root
Oct  8 17:59:11 raspberrypi CRON[21279]: pam_unix(cron:session): session closed for user root
Oct  8 17:59:21 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/poolerconsumi 1 energy
Oct  8 17:59:22 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:22 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:22 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/poolerconsumi 1 power
Oct  8 17:59:22 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/poolerconsumi 1 power
Oct  8 17:59:22 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:22 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:22 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:22 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:23 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/pool123s energy
Oct  8 17:59:23 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:23 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/pool123s power
Oct  8 17:59:23 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:23 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:23 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/pool123s power
Oct  8 17:59:23 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:23 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:24 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:24 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/virtmeter 3 0 0 imppower 0
Oct  8 17:59:24 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:24 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/eflow whin
Oct  8 17:59:24 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:24 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:24 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:24 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/virtmeter 3 0 0 imppower 0
Oct  8 17:59:24 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:24 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/virtmeter 4 0 0 exppower 0 grep ^4\(.*W\)
Oct  8 17:59:25 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:25 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:25 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/eflow whout
Oct  8 17:59:25 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:25 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:25 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:25 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/virtmeter 4 0 0 exppower 0
Oct  8 17:59:25 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:26 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:26 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/eflow selfc
Oct  8 17:59:26 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:26 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:26 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/virtmeter 5 0 0 selfcpower 0
Oct  8 17:59:26 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:27 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  8 17:59:27 raspberrypi CRON[21275]: pam_unix(cron:session): session closed for user root
Oct  8 17:59:32 raspberrypi CRON[21278]: pam_unix(cron:session): session closed for user root
Oct  8 17:59:38 raspberrypi sshd[24162]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.31.116.15  user=root
Oct  8 17:59:41 raspberrypi sshd[24162]: Failed password for root from 116.31.116.15 port 31924 ssh2
Oct  8 17:59:41 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/poolerconsumi 1 energy
Oct  8 17:59:41 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  8 17:59:42 raspberrypi sudo: pam_unix(sudo:session): session closed for user root


questo è il syslog

Codice: Seleziona tutto

Oct  8 18:04:01 raspberrypi CRON[13070]: (root) CMD (sleep 20; /var/www/MyScripts/lcd.sh)
Oct  8 18:04:01 raspberrypi CRON[13063]: (root) CMD (sleep 40; /var/www/MyScripts/lcd.sh)
Oct  8 18:04:01 raspberrypi CRON[13073]: (root) CMD (sleep 20; /var/www/MyScripts/domoticz.sh)
Oct  8 18:04:01 raspberrypi CRON[13072]: (root) CMD (/usr/local/bin/ds18b20 00000746702d 14 > /dev/null 2>&1  #meter 14 = mandata caldaia)
Oct  8 18:04:01 raspberrypi CRON[13074]: (root) CMD (          /var/www/MyScripts/lcd.sh)
Oct  8 18:04:01 raspberrypi CRON[13079]: (root) CMD (/var/www/MyScripts/domoticz.sh)
Oct  8 18:04:01 raspberrypi CRON[13094]: (root) CMD (/usr/local/bin/ds18b20 0000074881f9 13 > /dev/null 2>&1  #meter 13 = mandata riscaldamento)
Oct  8 18:04:07 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:04:07 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. b139-v6sm24002033wmd.36 - gsmtp
Oct  8 18:04:07 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:04:07 raspberrypi CRON[13031]: (root) MAIL (mailed 59 bytes of output but got status 0x0041 from MTA#012)
Oct  8 18:04:12 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:04:12 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. e67-v6sm11314447wmd.41 - gsmtp
Oct  8 18:04:12 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:04:12 raspberrypi CRON[13034]: (root) MAIL (mailed 583 bytes of output but got status 0x0041 from MTA#012)
Oct  8 18:04:29 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:04:29 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. 20-v6sm14517810wml.10 - gsmtp
Oct  8 18:04:29 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:04:29 raspberrypi CRON[13030]: (root) MAIL (mailed 59 bytes of output but got status 0x0041 from MTA#012)
Oct  8 18:04:31 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:04:31 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. q16-v6sm14030239wrn.41 - gsmtp
Oct  8 18:04:31 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:04:31 raspberrypi CRON[13033]: (root) MAIL (mailed 583 bytes of output but got status 0x0041 from MTA#012)
Oct  8 18:04:35 raspberrypi systemd[1]: Started Session c4 of user root.

perchè ad esempio registra le attività di cron in cui lancio /var/www/MyScripts/lcd.sh ??


questo è il daemonlog

Codice: Seleziona tutto

Oct  8 18:05:08 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:05:08 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. z12-v6sm5132619wrv.46 - gsmtp
Oct  8 18:05:08 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:05:11 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:05:11 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. k63-v6sm11516044wmd.46 - gsmtp
Oct  8 18:05:11 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:05:30 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:05:30 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. 126-v6sm13010837wme.48 - gsmtp
Oct  8 18:05:30 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:05:32 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:05:32 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. z2-v6sm13552030wrh.8 - gsmtp
Oct  8 18:05:32 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:05:48 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:05:48 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. c24-v6sm5907754wre.44 - gsmtp
Oct  8 18:05:48 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:05:52 raspberrypi cron[383]: sendmail: recipient address root not accepted by the server
Oct  8 18:05:52 raspberrypi cron[383]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. a5-v6sm10433334wmh.8 - gsmtp
Oct  8 18:05:52 raspberrypi cron[383]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  8 18:06:01 raspberrypi systemd[1]: Started Session c5 of user root.

Avatar utente
Flane
Messaggi: 2470
Iscritto il: 16/01/2016, 15:02

Re: file log enormi su solarstrech

Messaggioda Flane » 09/10/2018, 8:49

QUI trovi come disabilitare il log di cron in syslog
Il file per la configurazione dovrebbe essere /etc/rsyslog.conf


Per sendmail hai qualcosa che cerca continuamente di inviare mail.
Cerca di capire cosa è. Eventualmente configuralo correttamente e vedi che email arrivano.
Per disabilitare il log di sendmail prova ad editare il file di configurazione /etc/msmtprc ed aggiungere la riga:

Codice: Seleziona tutto

syslog off

QUI trovi tutte le indicazioni sulla configurazione

Sempre in questo file di configurazione puoi anche abilitare un log specifico di questo servizio aggiungendo la riga (che forse trovi anche già commentata ... )

Codice: Seleziona tutto

logfile /var/log/msmtp.log

in questo modo puoi forse capire che cosa cerca di inviare tutte quelle email.
Naturalmente poi commenta questa riga per disabilitare questo inutile log.

megamarco83
Messaggi: 246
Iscritto il: 22/08/2016, 14:13

Re: file log enormi su solarstrech

Messaggioda megamarco83 » 09/10/2018, 10:31

ciao dopo le modifiche al file rsyslog che è in /etc

Codice: Seleziona tutto

###############
#### RULES ####
###############

#
# First some standard log files.  Log by facility.
#
auth,authpriv.*         /var/log/auth.log
*.*;auth,authpriv.none,cron.nome      -/var/log/syslog
#cron.*            /var/log/cron.log
daemon.*         -/var/log/daemon.log
kern.*            -/var/log/kern.log
lpr.*            -/var/log/lpr.log
mail.*            -/var/log/mail.log
user.*            -/var/log/user.log
cron.*              /dev/null

ed il file msmtprc

Codice: Seleziona tutto

# Impostazioni account
defaults
tls on
tls_starttls on
tls_trust_file /etc/ssl/certs/ca-certificates.crt

account default
host smtp.gmail.com
port 587
auth on
user via.XXX@gmail.com
password XXXXXX
from via.XXX@gmail.com
#logfile /var/log/msmtp.log
#rimuovere per attivare i log
syslog off


ovviamente dopo aver modificato i file ho riavviato il raspberry in modo da riavviare tutti i servizi

dopo il riavvio questi sono i log

questo è il file auth.log

Codice: Seleziona tutto

Oct  9 10:20:23 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/eflow whin
Oct  9 10:20:23 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/pool123s power
Oct  9 10:20:23 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  9 10:20:23 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  9 10:20:24 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  9 10:20:24 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  9 10:20:24 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/virtmeter 3 0 0 imppower 0
Oct  9 10:20:24 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  9 10:20:24 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  9 10:20:24 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/eflow whout
Oct  9 10:20:24 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct  9 10:20:24 raspberrypi sshd[27383]: Accepted password for root from 192.168.0.4 port 53234 ssh2
Oct  9 10:20:24 raspberrypi sshd[27383]: pam_unix(sshd:session): session opened for user root by (uid=0)
Oct  9 10:20:24 raspberrypi systemd-logind[309]: New session c5 of user root.
Oct  9 10:20:25 raspberrypi sudo: pam_unix(sudo:session): session closed for user root
Oct  9 10:20:25 raspberrypi sudo:     root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/local/bin/virtmeter 4 0 0 exppower 0
Oct  9 10:20:25 raspberrypi sudo: pam_unix(sudo:session): session opened for user root by (uid=0)

continua ad avere questi log

questo è daemon.log

Codice: Seleziona tutto

Oct  9 10:23:08 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. y19-v6sm11118171wra.60 - gsmtp
Oct  9 10:23:08 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:23:11 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:23:11 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. m136-v6sm4996308wmb.4 - gsmtp
Oct  9 10:23:11 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:23:29 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:23:29 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. h64-v6sm11002445wmh.27 - gsmtp
Oct  9 10:23:29 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:23:31 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:23:31 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. y138-v6sm10408845wmd.2 - gsmtp
Oct  9 10:23:31 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:23:41 raspberrypi systemd[1]: Started Session c6 of user root.



questo è il syslog

Codice: Seleziona tutto

Oct  9 10:24:51 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:24:51 raspberrypi CRON[11767]: (root) MAIL (mailed 59 bytes of output but got status 0x0041 from MTA#012)
Oct  9 10:25:01 raspberrypi CRON[16442]: (root) CMD (sleep 20; /var/www/MyScripts/domoticz.sh)
Oct  9 10:25:01 raspberrypi CRON[16444]: (root) CMD (sleep 40; /var/www/MyScripts/lcd.sh)
Oct  9 10:25:01 raspberrypi CRON[16448]: (root) CMD (sleep 40; /var/www/MyScripts/domoticz.sh)
Oct  9 10:25:01 raspberrypi CRON[16451]: (root) CMD (sleep 20; /var/www/MyScripts/lcd.sh)
Oct  9 10:25:01 raspberrypi CRON[16453]: (root) CMD (/var/www/MyScripts/domoticz.sh)
Oct  9 10:25:01 raspberrypi CRON[16457]: (root) CMD (          /var/www/MyScripts/lcd.sh)
Oct  9 10:25:07 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:25:07 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. e196-v6sm2059092wmf.43 - gsmtp
Oct  9 10:25:07 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:25:07 raspberrypi CRON[16419]: (root) MAIL (mailed 59 bytes of output but got status 0x0041 from MTA#012)
Oct  9 10:25:11 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:25:11 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. x139-v6sm23483711wme.3 - gsmtp
Oct  9 10:25:11 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:25:11 raspberrypi CRON[16422]: (root) MAIL (mailed 583 bytes of output but got status 0x0041 from MTA#012)
Oct  9 10:25:30 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:25:30 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. z2-v6sm15518640wrh.8 - gsmtp
Oct  9 10:25:30 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:25:30 raspberrypi CRON[16418]: (root) MAIL (mailed 59 bytes of output but got status 0x0041 from MTA#012)
Oct  9 10:25:31 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:25:31 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. y125-v6sm8771260wme.12 - gsmtp
Oct  9 10:25:31 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:25:31 raspberrypi CRON[16421]: (root) MAIL (mailed 583 bytes of output but got status 0x0041 from MTA#012)
Oct  9 10:25:49 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:25:49 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. r128-v6sm10015590wma.40 - gsmtp
Oct  9 10:25:49 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:25:49 raspberrypi CRON[16417]: (root) MAIL (mailed 59 bytes of output but got status 0x0041 from MTA#012)
Oct  9 10:25:51 raspberrypi cron[369]: sendmail: recipient address root not accepted by the server
Oct  9 10:25:51 raspberrypi cron[369]: sendmail: server message: 553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. m12sm12525900wrx.75 - gsmtp
Oct  9 10:25:51 raspberrypi cron[369]: sendmail: could not send mail (account default from /etc/msmtprc)
Oct  9 10:25:51 raspberrypi CRON[16420]: (root) MAIL (mailed 583 bytes of output but got status 0x0041 from MTA#012)
Oct  9 10:26:01 raspberrypi CRON[21090]: (root) CMD (sleep 40; /var/www/MyScripts/lcd.sh)
Oct  9 10:26:01 raspberrypi CRON[21096]: (root) CMD (          /var/www/MyScripts/lcd.sh)
Oct  9 10:26:01 raspberrypi CRON[21100]: (root) CMD (sleep 20; /var/www/MyScripts/lcd.sh)
Oct  9 10:26:01 raspberrypi CRON[21101]: (root) CMD (sleep 20; /var/www/MyScripts/domoticz.sh)
Oct  9 10:26:01 raspberrypi CRON[21105]: (root) CMD (/var/www/MyScripts/domoticz.sh)
Oct  9 10:26:01 raspberrypi CRON[21106]: (root) CMD (sleep 40; /var/www/MyScripts/domoticz.sh)
Oct  9 10:26:05 raspberrypi systemd[1]: Started Session c7 of user root.


dopo aver attivato brevemente il log delle mail questo è il risultato del file msmtp.log

Codice: Seleziona tutto

ott 09 09:47:57 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. t198-v6sm7632051wmd.9 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:48:00 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. 67-v6sm11514601wmd.1 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:48:09 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. f1-v6sm11768385wme.23 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:48:11 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. 62-v6sm24260374wra.48 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:48:30 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. y4-v6sm18870389wrd.25 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:48:31 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. b143-v6sm23880082wma.28 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:48:50 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. u191-v6sm14176137wmd.31 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:48:50 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. g15-v6sm13374403wrp.56 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:49:09 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. b1-v6sm12067578wrt.43 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:49:13 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. 67-v6sm11519037wmd.1 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:49:31 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. y7-v6sm10853991wmy.27 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:49:32 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. j46-v6sm31691712wre.91 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:49:50 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. x8-v6sm33872228wrd.54 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR
ott 09 09:49:51 host=smtp.gmail.com tls=on auth=on user=via.XXXXX@gmail.com from=via.XXXXX@gmail.com recipients=root smtpstatus=553 smtpmsg='553 5.1.2 The recipient address <root> is not a valid RFC-5321 address. q200-v6sm15154301wmd.2 - gsmtp' errormsg='recipient address root not accepted by the server' exitcode=EX_DATAERR



anche con quelle modifiche sembra che cron vada a scrivere il log

Avatar utente
Flane
Messaggi: 2470
Iscritto il: 16/01/2016, 15:02

Re: file log enormi su solarstrech

Messaggioda Flane » 09/10/2018, 11:27

Ho controllato nel mio auth.log ed io non ho nessun log di pool123s, virtmeter, etc.... io ho solo i pam_unix.
Io però al momento ho ancora il kernel 4.9.80, devo fare qualche prova se questi log sono legati dall'ultimo aggiornamento del kernel ...

megamarco83
Messaggi: 246
Iscritto il: 22/08/2016, 14:13

Re: file log enormi su solarstrech

Messaggioda megamarco83 » 09/10/2018, 11:29

ok grazie, puoi farmi sapere?
grazie mille!!
p.s. eventualmente si può fare un downgrade del kernel? anche se mi sembra strano che sia colpa del kernel...

Avatar utente
Flane
Messaggi: 2470
Iscritto il: 16/01/2016, 15:02

Re: file log enormi su solarstrech

Messaggioda Flane » 09/10/2018, 18:05

Sono quasi certo che sia il Kernel se guardi nelle note della Solarstretch ho dovuto mettere dei filtri anche per altre cose presenti nel nuovo kernel e che intasavano il log e mandavano in blocco il Raspi.

NOTA KERNEL:
Nella presente versione 3.1 è stato aggiornato il Kernel alla vers. 4.14 in cui ed è stato introdotto un controllo sulla tensione di alimentazione
dell'RPI. Ho però rilevato con un RPI2 nel file syslog continue false segnalazioni di "under Voltage" che intasavano il file di log.
Per questo motivo ho deciso di aggiungere un filtraggio messaggi di log "Under Voltage" in /etc/rsyslog.d/ignore-underpowering.conf
Potete eventualmente eliminare il filtraggio semplicemente cancellando il file /etc/rsyslog.d/ignore-underpowering.conf

dolam
Messaggi: 222
Iscritto il: 15/08/2016, 23:08

Re: file log enormi su solarstrech

Messaggioda dolam » 09/10/2018, 23:22

megamarco hai ancora la versione di gianfrdp per la gestione dei carichi?
Perché se c’è l’hai ancora potrebbe dipendere da questo .
Di recente ho dovuto cancellarne uno da 650Mb e complessivamente avevo 3.7 Gb di. file .log e naturalmente il raspberry andava il blocco

megamarco83
Messaggi: 246
Iscritto il: 22/08/2016, 14:13

Re: file log enormi su solarstrech

Messaggioda megamarco83 » 09/10/2018, 23:48

Ciao, no ho cambiato tutto il sistema aggiornando a strech :)


Torna a “MeterN”

Chi c’è in linea

Visitano il forum: Nessuno e 15 ospiti