Re: [j-nsp] syslog is flooded with curious messages (MX5 / 14.2R2.8)

2016-02-24 Thread Chuck Anderson
At least for the "ifa for this rt" message, it is a bug that was
fixed:

https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1067484

   "When setting the syslog to debug level (any any), you may note
reoccurring messages of the form "ifa for this rt ia is not
present, consider ifa as ready". These messages are logged for
IPv6 enabled interfaces when receiving forwarded packets and cause
no harm. Set a higher debug level to avoid seeing them.

Resolved In  14.1R6 14.2R4 15.1R2"

On Fri, Jan 22, 2016 at 12:31:05PM +0100, Job Snijders wrote:
> On Fri, Jan 22, 2016 at 09:12:01AM -0200, Eduardo Schoedler wrote:
> > Same problem here...
> > 
> > Jan 22 09:05:04  router chassisd[1546]: Cannot read 
> > hw.chassis.startup_time: No such file or directory
> > Jan 22 09:05:14  router last message repeated 2 times
> > Jan 22 09:07:14  router last message repeated 24 times
> > Jan 22 09:08:59  router last message repeated 21 times
> 
> I upgraded to 15.1R2.9, and subsequently the above messages went away
> (hooray!) but in return I got the below:
> 
>   Jan 22 11:29:32  eunetworks-1.router.nl.coloclue.net tfeb0 
> cmtfpc_vtreg_npc_create: Invalid I2C ID 0x556
>   Jan 22 11:29:32  eunetworks-1.router.nl.coloclue.net tfeb0 
> cmtfpc_vtreg_npc_volt_get - Failed to create vtreg handle
>   Jan 22 11:29:32  eunetworks-1.router.nl.coloclue.net tfeb0 
> cmtfpc_collect_voltage_status: failed reading Volterra volt data
>   (endlessly)
> 
> Kind regards,
> 
> Job
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] syslog is flooded with curious messages (MX5 / 14.2R2.8)

2016-01-22 Thread Job Snijders
On Fri, Jan 22, 2016 at 09:12:01AM -0200, Eduardo Schoedler wrote:
> Same problem here...
> 
> Jan 22 09:05:04  router chassisd[1546]: Cannot read hw.chassis.startup_time: 
> No such file or directory
> Jan 22 09:05:14  router last message repeated 2 times
> Jan 22 09:07:14  router last message repeated 24 times
> Jan 22 09:08:59  router last message repeated 21 times

I upgraded to 15.1R2.9, and subsequently the above messages went away
(hooray!) but in return I got the below:

Jan 22 11:29:32  eunetworks-1.router.nl.coloclue.net tfeb0 
cmtfpc_vtreg_npc_create: Invalid I2C ID 0x556
Jan 22 11:29:32  eunetworks-1.router.nl.coloclue.net tfeb0 
cmtfpc_vtreg_npc_volt_get - Failed to create vtreg handle
Jan 22 11:29:32  eunetworks-1.router.nl.coloclue.net tfeb0 
cmtfpc_collect_voltage_status: failed reading Volterra volt data
(endlessly)

Kind regards,

Job
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] syslog is flooded with curious messages (MX5 / 14.2R2.8)

2016-01-22 Thread Olivier Benghozi
14.2R5, had frequent /kernel: hw.chassis.startup_time update to 
1449495334.808647 messages.

I just did something like
set sytem syslog file messages kernel warning
to drop them...


> Le 22 janv. 2016 à 12:12, Eduardo Schoedler  a écrit :
> 
> Same problem here...
> 
> Jan 22 09:05:04  router chassisd[1546]: Cannot read
> hw.chassis.startup_time: No such file or directory
> Jan 22 09:05:14  router last message repeated 2 times
> Jan 22 09:07:14  router last message repeated 24 times
> Jan 22 09:08:59  router last message repeated 21 times

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] syslog is flooded with curious messages (MX5 / 14.2R2.8)

2016-01-22 Thread Eduardo Schoedler
Same problem here...

Jan 22 09:05:04  router chassisd[1546]: Cannot read
hw.chassis.startup_time: No such file or directory
Jan 22 09:05:14  router last message repeated 2 times
Jan 22 09:07:14  router last message repeated 24 times
Jan 22 09:08:59  router last message repeated 21 times

--
Eduardo Schoedler


2015-02-22 13:19 GMT-03:00 Job Snijders :

> Hi list,
>
> Upgraded this morning to 14.2R2.8 and I noticed that /var/log/messages
> is being blasted with all kinds of messages which have no meaning to me.
>
> Other then high memory usage, the box seems to operate fine. It's a
> regular edge router with some peering sessions, ibgp & transit, no mpls,
> only plain ip routing, vrrp & ospf{,3}. My configuration is a tad large
> due to extensive prefix-filters (7.6 megabyte or so).
>
> Does anybody have a clue what the following three things mean?
>
> - /kernel: ifa for this rt ia is not present, consider ifa as ready
> - chassisd[1432]: Cannot read hw.chassis.startup_time: No such file or
> directory
> - /kernel: setsocketopts: setting SO_RTBL_INDEX to 1
>
> Kind regards,
>
> Job
>
> syslog:
>
> Feb 22 16:13:04  eunetworks-1.router.nl.coloclue.net chassisd[1432]:
> Cannot read hw.chassis.startup_time: No such file or directory
> Feb 22 16:13:04  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:04  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:05  eunetworks-1.router.nl.coloclue.net /kernel:
> setsocketopts: setting SO_RTBL_INDEX to 1
> Feb 22 16:13:09  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:09  eunetworks-1.router.nl.coloclue.net last message
> repeated 3 times
> Feb 22 16:13:09  eunetworks-1.router.nl.coloclue.net chassisd[1432]:
> Cannot read hw.chassis.startup_time: No such file or directory
> Feb 22 16:13:10  eunetworks-1.router.nl.coloclue.net /kernel:
> setsocketopts: setting SO_RTBL_INDEX to 1
> Feb 22 16:13:11  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:13  eunetworks-1.router.nl.coloclue.net last message
> repeated 78 times
> Feb 22 16:13:14  eunetworks-1.router.nl.coloclue.net chassisd[1432]:
> Cannot read hw.chassis.startup_time: No such file or directory
> Feb 22 16:13:15  eunetworks-1.router.nl.coloclue.net /kernel:
> setsocketopts: setting SO_RTBL_INDEX to 1
> Feb 22 16:13:15  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:19  eunetworks-1.router.nl.coloclue.net last message
> repeated 69 times
> Feb 22 16:13:19  eunetworks-1.router.nl.coloclue.net chassisd[1432]:
> Cannot read hw.chassis.startup_time: No such file or directory
> Feb 22 16:13:20  eunetworks-1.router.nl.coloclue.net /kernel:
> setsocketopts: setting SO_RTBL_INDEX to 1
> Feb 22 16:13:20  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:20  eunetworks-1.router.nl.coloclue.net last message
> repeated 18 times
> Feb 22 16:13:24  eunetworks-1.router.nl.coloclue.net chassisd[1432]:
> Cannot read hw.chassis.startup_time: No such file or directory
> Feb 22 16:13:24  eunetworks-1.router.nl.coloclue.net /kernel:
> setsocketopts: setting SO_RTBL_INDEX to 1
> Feb 22 16:13:27  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:28  eunetworks-1.router.nl.coloclue.net last message
> repeated 32 times
> Feb 22 16:13:29  eunetworks-1.router.nl.coloclue.net chassisd[1432]:
> Cannot read hw.chassis.startup_time: No such file or directory
> Feb 22 16:13:29  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:29  eunetworks-1.router.nl.coloclue.net last message
> repeated 8 times
> Feb 22 16:13:29  eunetworks-1.router.nl.coloclue.net /kernel:
> setsocketopts: setting SO_RTBL_INDEX to 1
> Feb 22 16:13:30  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:31  eunetworks-1.router.nl.coloclue.net last message
> repeated 26 times
> Feb 22 16:13:34  eunetworks-1.router.nl.coloclue.net chassisd[1432]:
> Cannot read hw.chassis.startup_time: No such file or directory
> Feb 22 16:13:34  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, consider ifa as ready
> Feb 22 16:13:34  eunetworks-1.router.nl.coloclue.net last message
> repeated 11 times
> Feb 22 16:13:34  eunetworks-1.router.nl.coloclue.net /kernel:
> setsocketopts: setting SO_RTBL_INDEX to 1
> Feb 22 16:13:37  eunetworks-1.router.nl.coloclue.net /kernel: ifa for
> this rt ia is not present, c

[j-nsp] syslog is flooded with curious messages (MX5 / 14.2R2.8)

2015-02-22 Thread Job Snijders
Hi list,

Upgraded this morning to 14.2R2.8 and I noticed that /var/log/messages
is being blasted with all kinds of messages which have no meaning to me. 

Other then high memory usage, the box seems to operate fine. It's a
regular edge router with some peering sessions, ibgp & transit, no mpls,
only plain ip routing, vrrp & ospf{,3}. My configuration is a tad large
due to extensive prefix-filters (7.6 megabyte or so).

Does anybody have a clue what the following three things mean?

- /kernel: ifa for this rt ia is not present, consider ifa as ready
- chassisd[1432]: Cannot read hw.chassis.startup_time: No such file or 
directory
- /kernel: setsocketopts: setting SO_RTBL_INDEX to 1 

Kind regards,

Job

syslog:

Feb 22 16:13:04  eunetworks-1.router.nl.coloclue.net chassisd[1432]: Cannot 
read hw.chassis.startup_time: No such file or directory
Feb 22 16:13:04  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:04  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:05  eunetworks-1.router.nl.coloclue.net /kernel: 
setsocketopts: setting SO_RTBL_INDEX to 1
Feb 22 16:13:09  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:09  eunetworks-1.router.nl.coloclue.net last message repeated 
3 times
Feb 22 16:13:09  eunetworks-1.router.nl.coloclue.net chassisd[1432]: Cannot 
read hw.chassis.startup_time: No such file or directory
Feb 22 16:13:10  eunetworks-1.router.nl.coloclue.net /kernel: 
setsocketopts: setting SO_RTBL_INDEX to 1
Feb 22 16:13:11  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:13  eunetworks-1.router.nl.coloclue.net last message repeated 
78 times
Feb 22 16:13:14  eunetworks-1.router.nl.coloclue.net chassisd[1432]: Cannot 
read hw.chassis.startup_time: No such file or directory
Feb 22 16:13:15  eunetworks-1.router.nl.coloclue.net /kernel: 
setsocketopts: setting SO_RTBL_INDEX to 1
Feb 22 16:13:15  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:19  eunetworks-1.router.nl.coloclue.net last message repeated 
69 times
Feb 22 16:13:19  eunetworks-1.router.nl.coloclue.net chassisd[1432]: Cannot 
read hw.chassis.startup_time: No such file or directory
Feb 22 16:13:20  eunetworks-1.router.nl.coloclue.net /kernel: 
setsocketopts: setting SO_RTBL_INDEX to 1
Feb 22 16:13:20  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:20  eunetworks-1.router.nl.coloclue.net last message repeated 
18 times
Feb 22 16:13:24  eunetworks-1.router.nl.coloclue.net chassisd[1432]: Cannot 
read hw.chassis.startup_time: No such file or directory
Feb 22 16:13:24  eunetworks-1.router.nl.coloclue.net /kernel: 
setsocketopts: setting SO_RTBL_INDEX to 1
Feb 22 16:13:27  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:28  eunetworks-1.router.nl.coloclue.net last message repeated 
32 times
Feb 22 16:13:29  eunetworks-1.router.nl.coloclue.net chassisd[1432]: Cannot 
read hw.chassis.startup_time: No such file or directory
Feb 22 16:13:29  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:29  eunetworks-1.router.nl.coloclue.net last message repeated 
8 times
Feb 22 16:13:29  eunetworks-1.router.nl.coloclue.net /kernel: 
setsocketopts: setting SO_RTBL_INDEX to 1
Feb 22 16:13:30  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:31  eunetworks-1.router.nl.coloclue.net last message repeated 
26 times
Feb 22 16:13:34  eunetworks-1.router.nl.coloclue.net chassisd[1432]: Cannot 
read hw.chassis.startup_time: No such file or directory
Feb 22 16:13:34  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:34  eunetworks-1.router.nl.coloclue.net last message repeated 
11 times
Feb 22 16:13:34  eunetworks-1.router.nl.coloclue.net /kernel: 
setsocketopts: setting SO_RTBL_INDEX to 1
Feb 22 16:13:37  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb 22 16:13:39  eunetworks-1.router.nl.coloclue.net last message repeated 
3 times
Feb 22 16:13:39  eunetworks-1.router.nl.coloclue.net chassisd[1432]: Cannot 
read hw.chassis.startup_time: No such file or directory
Feb 22 16:13:39  eunetworks-1.router.nl.coloclue.net /kernel: 
setsocketopts: setting SO_RTBL_INDEX to 1
Feb 22 16:13:40  eunetworks-1.router.nl.coloclue.net /kernel: ifa for this 
rt ia is not present, consider ifa as ready
Feb