From: Andrew Griffin via rsyslog <[email protected]>
This is probably an easy one but I can’t quite figure it out. I’m trying to
run rsyslog as a service - meaning I’m running an instance of rsyslogd
separate from the local system’s rsyslogd, running on a separate port (10514),
running from a custom location under an application (non-root) account. I
need a way to collect logs - namely syslog facility messages - from this
separate instance and log to a specified location. I setup a rule as follows:
if $programname contains "rsyslog" or prifilt("syslog.*") then {
action(
name = "rsyslogd_internal_to_file"
type = "omfile"
dynaFile = "RsyslogdFileTemplate"
sync = "on"
template = "RsyslogdFileTemplate"
)
stop
}
Which sends off to a file. And added this to the top-level rsyslog.conf:
syslog.* @localhost:10514
I’ve restarted rsyslogd a few times just to generate some generic
shutdown/startup messages, but I’m still not seeing anything being logged. Is
my thinking correct here? Is it still logging to the system’s rsyslogd? I do
not have (and do not want) root access on this host so I can’t check
/var/log/messages to see if they’re going there
If you don't have root access, how are you modifying the rsyslog.conf and
restarting rsyslog on the parent system?
do your firewall rules allow connections on port 10514? does tcpdump show the
traffic being sent?
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
