[Fixed in 2.1.0] Syslog messages show as diffs in Juniper backups

Unimus support forum
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Wed Jun 08, 2022 4:53 am

Hi Tomas,

I have tried logging in to a device that routinely fails backup due to terminal syslog output (as confirmed by debug logs).
It seems that the "monitor stop" command stops any actively started log monitoring, but ESC-q pauses all terminal syslog output.
A lot of our devices have the line

set system syslog user * any warning

which maximises terminal syslog output, without having to start a log monitor. I think that is why the "monitor stop" command currently implemented in the Unimus Junos driver does not help on these devices.
I realise that a workaround could be to remove the previously mentioned line, but we would really like to keep syslog output visible as a default.
User avatar
Tomas
Posts: 1109
Joined: Sat Jun 25, 2016 12:33 pm

Wed Jun 08, 2022 12:37 pm

ptorbjornsson wrote:
Wed Jun 08, 2022 4:53 am
Hi Tomas,

I have tried logging in to a device that routinely fails backup due to terminal syslog output (as confirmed by debug logs).
It seems that the "monitor stop" command stops any actively started log monitoring, but ESC-q pauses all terminal syslog output.
A lot of our devices have the line

set system syslog user * any warning

which maximises terminal syslog output, without having to start a log monitor. I think that is why the "monitor stop" command currently implemented in the Unimus Junos driver does not help on these devices.
I realise that a workaround could be to remove the previously mentioned line, but we would really like to keep syslog output visible as a default.
Edit: please see later post for updates

Unimus currently sends ESC+Q. The suggested change in this topic was to change this to "monitor stop". Can you please send us both the Debug Log as well as the Device Output Log files so we can analyze what is going on?

Thanks!
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Wed Jun 08, 2022 12:52 pm

Tomas wrote:
Mon Jun 28, 2021 4:19 pm
Just an update: we have added handling for this to our JunOS driver. This will be available in 2.1.0 stable release. Before backup, a "monitor stop" command will be sent (this is the same as ESC+Q). Since this is a per-session setting, the device will not be affected in any way.

You can also deal with this using the new Backup Filters: https://unimus.net/blog/backup-filters-unimus-210. These are available in the 2.1 Betas already if you want to test this.
Ah, I was under impression (due to your earlier reply that I quoted), that Unimus sent "monitor stop". I am currently running 2.2.0-Beta3.
I will find a device where I can reproduce the error and send you the logs.
User avatar
Tomas
Posts: 1109
Joined: Sat Jun 25, 2016 12:33 pm

Wed Jun 08, 2022 12:54 pm

ptorbjornsson wrote:
Wed Jun 08, 2022 12:52 pm
Ah, I was under impression (due to your earlier reply that I quoted), that Unimus sent "monitor stop". I am currently running 2.2.0-Beta3.
I will find a device where I can reproduce the error and send you the logs.
Actually you are right - I just checked our JunOS driver and we currently do send "monitor stop". Sorry for the confusion :(
I will talk with the team why we chose "monitor stop" instead of CTRL+Q ESC+Q, and see if we can change it.
ptorbjornsson
Posts: 23
Joined: Tue Aug 11, 2020 12:08 pm

Wed Jun 08, 2022 1:03 pm

Tomas wrote:
Wed Jun 08, 2022 12:54 pm
ptorbjornsson wrote:
Wed Jun 08, 2022 12:52 pm
Ah, I was under impression (due to your earlier reply that I quoted), that Unimus sent "monitor stop". I am currently running 2.2.0-Beta3.
I will find a device where I can reproduce the error and send you the logs.
Actually you are right - I just checked our JunOS driver and we currently do send "monitor stop". Sorry for the confusion :(
I will talk with the team why we chose "monitor stop" instead of CTRL+Q, and see if we can change it.
Ah, that's great thanks. And just to be sure, it's ESC+Q, not CTRL+Q ;)
Post Reply