We need to extend configurable options for remote logging
like now we missing settings for port, protocol and more things
before implementing this, better first to move from Perl to python
Description
Description
Details
Details
- Version
- -
Related Objects
Related Objects
- Mentioned In
- rVYOSONEX4daf6494b10e: Merge pull request #23 from hagbard-01/current
rVYOSONEX0fdfe533cd2b: T736: hostname check for the occurence of white spaces
rVYOSONEXf1222dadfd0b: T736: bugfix, if facility is not set by the user, it defaults to *.err,in hosts…
rVYOSONEX8c44fa7fb35f: T736: import order changed, invoke-rc.d replaced by systemctl command
rVYOSONEXfc4d5bc4a4ab: T736: Rewrite remote logging (syslog) to XML/Python
rVYOSONEX51afeb661b82: T736: Rewrite remote logging (syslog) to XML/Python - Mentioned Here
- T741: move user home to persistent storage
Event Timeline
Comment Actions
@syncer, @c-po /opt/vyatta/etc/logrotate/global is generated as well (logrotate for syslog files), where should I place the new one just under /etc/logrotate.d? It's going to be generated via the cli config, so an image update wouldn't do anything bad.
Also, I'm going to created different config files, rather than 1 global one. That way, we could later drop in database logging support and the such. As far as I have seen, you can currently only log to a remote host.
Comment Actions
Yup, that's what I think too.
vyatta did place there 2 files for logrotation already:
/etc/logrotate.d/vyatta-config-logs
/etc/logrotate.d/vyatta-ipsec-logs
but:
/opt/vyatta/etc/logrotate/global
I was thinking to rename global to vyos-logrotate or vyos-syslogrotate or something like that, to make sure I don't interfere with any debian based packages aka:
(debian squueze, my desktop):
dpkg -S /etc/logrotate.d/rsyslog
rsyslog: /etc/logrotate.d/rsyslog
That should avoid then headaches when 1.3 is being done.
Do you guys have a mailing list or anyhing where dev stuff is being discussed?
Comment Actions
If anyone wants to view the progress, here is the link to the devel version.
https://github.com/hagbard-01/vyos-1x/blob/devel/src/conf_mode/syslog.py
Comment Actions
Now I found out the mystery from logrotate, vyatta put the logrotate files into persistent storage since they are triggered by rsyslog itself. I have them currently moved to /etc/logroate.d since they are configured with a size. But this might be prone to a race condition. @c-po I think we need some kind of persistent storage for vyos as well if we want to decom /opt/vyatta at one point. Would be also good for T741.
I'm going to be busy with testing and work this week and I know you are busy as well, so no rush on an answer.
Comment Actions
Syslog rewrite is now almost done, I currently testing everything, so I think if all goes well, I open a pull request next week for it. I'm still not sure how I should handle 'set system syslog user...', the help text states that it logs to the logged in user, but I didn't find anything implemented in the old perl script.
Comment Actions
Hi Guys, @dmbaturin
during my test I found the follwing:
- vyatta-cfg-system creates /etc/rsyslog.d/vyatta-log.conf
- I removed the syslog stuff from vyatta-cfg-system, rebuild the package and updated, /etc/rsyslog.d/vyatta-log.conf was generated so it's not being removed.
Shall I take care of the removal in my vyos-1x script or in vyatta-cfg-system?
Comment Actions
merged by Daniil. Please assign bugs to me, if any come up. I tested everything multiple times carefully, but you never know, so I take full responsibility :0.