Hi, this has nothing to do with the RE actually (and nothing to do with the router configuration). These messages come from the embedded Linux inside the MPC in slot 1 («fpc1»), when its logrotates is executed. This kind of infra inside the MPCs (a Linux running a Juniblob) exists since MPC7 I think. This bug is described in PR1471006 and not harmful («Two cronjobs on fpc are executed at the same time.»).
To see the original logs by logging inside the embedded Linux on an MPC7 from the CLI of an RE: > start shell user root # rsh -Ji fpc3 # tail -n 5 /var/log/user.log 2021-05-31T04:02:01.064586+02:00 cr-co-01-pareq2-re1-fpc3 logrotate: ALERT exited abnormally with [1] 2021-06-02T04:02:01.491175+02:00 cr-co-01-pareq2-re1-fpc3 logrotate: ALERT exited abnormally with [1] 2021-06-06T04:02:01.404865+02:00 cr-co-01-pareq2-re1-fpc3 logrotate: ALERT exited abnormally with [1] 2021-06-12T04:02:01.262606+02:00 cr-co-01-pareq2-re1-fpc3 logrotate: ALERT exited abnormally with [1] 2021-06-13T04:02:01.455588+02:00 cr-co-01-pareq2-re1-fpc3 logrotate: ALERT exited abnormally with [1] > Le 15 juin 2021 à 15:51, Thomas Mann <[email protected]> a écrit : > > Hi Alexandre, > > The log files on the active RE are rotated periodically and there are > more than 45% available on the /.mount/var fs (5G free). > I read the syslog messages as they are generated by FPC1, or I'm wrong ? > > Thank you > Thomas > > > On Tue, Jun 15, 2021 at 3:25 PM Alexandre Guimaraes > <[email protected]> wrote: >> >> Hello Thomas, >> >> Probably, there ir no space to allocate new files from logrotate service. >> Remove all files > request system storage cleanup >> >> Check this configuration lines to keep log files under control: >> >>> show configuration system syslog >> user * { >> any emergency; >> } >> file messages { >> any notice; >> authorization info; >> } >> file interactive-commands { >> interactive-commands any; >> } >> file LINKS-UP-DOWN { >> daemon info; >> match "(SNMP_TRAP|VCCPD_PROTOCOL)"; >> archive size 1m files 10; >> <===================================<================ >> } >> file LOGS-DE-CLI { >> interactive-commands info; >> match .*CMDLINE.*; >> archive size 1m files 10; >> <===================================<================ >> } >> >> Att >> Alexandre >> >> Em 15/06/2021 10:07, "juniper-nsp em nome de Thomas Mann" >> <[email protected] em nome de >> [email protected]> escreveu: >> >> Hi, >> >> Today one of our fpcs started throwing every minute logrotate syslog >> alerts. >> Did you faced something like this before ? >> >> Jun 15 12:38:01 core1-re1 fpc1 user.notice logrotate: ALERT exited >> abnormally with [1] >> Jun 15 12:39:01 core1-re1 fpc1 user.notice logrotate: ALERT exited >> abnormally with [1] >> Jun 15 12:40:01 core1-re1 fpc1 user.notice logrotate: ALERT exited >> abnormally with [1] >> Jun 15 12:41:01 core1-re1 fpc1 user.notice logrotate: ALERT exited >> abnormally with [1] >> >> Thank you >> Thomas _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
