[syslog-ng] Re: file issues

[Brian Loe]

Okay, running it with debug and verbose (-d -v) this is all I get in
the log (allmessages as defined by syslog-ng configuration):
Sep 26 12:57:08 machine syslog-ng[151718]: syslog-ng starting up;
version='2.0rc1'
Sep 26 12:57:08 machine syslog-ng[151718]: Initializing destination file
writer; template='/data/logs/$YEAR$MONTH$DAY.allmessages.log',
filename='/data/logs/20060926.allmessages.log'
Sep 26 12:57:08 machine syslog-ng[151718]: Initializing destination file
writer; template='/data/logs/$YEAR$MONTH$DAY.netmessages.log',
filename='/data/logs/20060926.netmessages.log'
Sep 26 12:57:38 machine syslog-ng[151718]: Reaping unused destination
files; template='/data/logs/router/$YEAR$MONTH$DAY.router.log'
Sep 26 12:57:38 machine syslog-ng[151718]: Reaping unused destination
files; template='/data/logs/switch/$YEAR$MONTH$DAY.switch.log'
Sep 26 12:57:38 machine syslog-ng[151718]: Reaping unused destination
files; template='/data/logs/pixen/$YEAR$MONTH$DAY.pixen.log'
Sep 26 12:57:38 machine syslog-ng[151718]: Reaping unused destination
files; template='/data/logs/$YEAR$MONTH$DAY.netmessages.log'
Sep 26 12:57:38 machine syslog-ng[151718]: Reaping unused destination
files; template='/data/logs/ids/$YEAR$MONTH$DAY.ids.log'
Sep 26 12:57:38 machine syslog-ng[151718]: Reaping unused destination
files; template='/data/logs/$YEAR$MONTH$DAY.allmessages.log'
Sep 26 12:57:38 machine syslog-ng[151718]: Reaping unused destination
files; template='/data/logs/vpn/$YEAR$MONTH$DAY.vpn.log'


Remember, I'm running this on AIX. I don't understand why its calling
those destinations "unused", to of them are. Also, no mention of the
pipes. Maybe its feeding the pipes though - I simply have no real way
of knowing...

On 9/26/06, Sandor Geller <wildy at balabit.hu> wrote:
> Brian Loe wrote:
> > No one with an idea of what might be going on here? I've reread most
> > of the documentation for syslog-ng and can't figure it out...perhaps
> > its an AIX/fs permissions issue?
>
> Currently we are trying to track down a similar issue, but it might be
> unrelated. You aren't running syslog-ng as a superuser. Have you checked
>  whether your syslog user has the needed permissions to create the files
> and open the pipes for writing?
>
> Some kind of trace output (like strace on linux) would be appreciated.
>
> --
> Sandor Geller
> wildy at balabit.hu
> _______________________________________________
> syslog-ng maillist  -  syslog-ng at lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
>
>