Hi Tom, all, solution: use "monitor start /var/log/messages" (i.e. specify the complete path) instead of the command below, which does not work anymore with 12.1R3.5.
Regards, Vincent On 16 June 2013 01:11, Tom Storey <[email protected]> wrote: > Just a thought, but have you tried doing a "chmod 664 /var/log/messages"? > > That should make it world readable, so should not matter what your user > level/permissions are. > > I would also compare the user/group ownership against a working box to > make sure its all the same. > > > On 13 June 2013 16:06, Vincent De Keyzer <[email protected]> wrote: > >> Hello, >> >> I hope this is a simple one. >> >> I have trouble with "monitor start messages": >> >> dude@LON2-R96-01-re0> monitor start messages >> >> {master} >> dude@LON2-R96-01-re0> >> *** error - couldn't open 'messages' (Permission denied) - removed *** >> >> >> {master} >> dude@LON2-R96-01-re0> >> >> It is unclear to me whether this is a file permission issue, or a system >> login configuration issue. >> >> These are the rights I have: >> >> dude@LON2-R96-01-re0> show configuration system login class noc-team-user >> permissions >> permissions [ access access-control admin configure firewall flow-tap >> interface-control network routing security snmp-control system >> trace-control view view-configuration ]; >> >> {master} >> dude@LON2-R96-01-re0> >> >> Logging on with higher priviledges, I can start a shell and see that: >> >> % ls -al /var/log/messages >> -rw-rw---- 1 root wheel 316194 Jun 13 14:57 /var/log/messages >> % >> >> Strangely, a similar configuration works ok on an EX4200 (it is on a MX960 >> that it does not work). >> >> Any idea? >> >> Thanks, >> >> Vincent >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
