[gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Helmut Jarausch]

Hi,

after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system has 
stopped logging, i.e. I only get the messages
Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; 
version='3.6.1'
Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; 
version='3.6.1'

Has anybody observed the same problem, and how to fix it?

Many thanks for a hint,
Helmut

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Alan McKinnon]

On 13/11/2014 18:41, Helmut Jarausch wrote:
> Hi,
> 
> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system has 
> stopped logging, i.e. I only get the messages
> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; 
> version='3.6.1'
> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; 
> version='3.6.1'
> 
> Has anybody observed the same problem, and how to fix it?
> 
> Many thanks for a hint,
> Helmut
> 
> 


Run a syntax check on the config file, I don't have a man page to hand
but it's quite obvious what the option is.
syslog-ng has sometimes been picky about version numbers in the past and
it's tagged in the config file. Read the syntax check output carefully
to see if anything is amiss.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Tomas Mozes]

On 2014-11-13 17:41, Helmut Jarausch wrote:
> Hi,
> 
> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system has
> stopped logging, i.e. I only get the messages
> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down;
> version='3.6.1'
> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up;
> version='3.6.1'
> 
> Has anybody observed the same problem, and how to fix it?
> 
> Many thanks for a hint,
> Helmut

I'm running it with "hardened" configuration and it works fine 
(https://bugs.gentoo.org/show_bug.cgi?id=528788). Do you run syslog-ng 
on normal kernel or hardened?

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Tomas Mozes]

On 2014-11-13 17:41, Helmut Jarausch wrote:
> Hi,
> 
> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system has
> stopped logging, i.e. I only get the messages
> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down;
> version='3.6.1'
> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up;
> version='3.6.1'
> 
> Has anybody observed the same problem, and how to fix it?
> 
> Many thanks for a hint,
> Helmut

Just checked with the default configuration, it seems to log correctly 
to /var/log/messages (~amd64).

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[J. Roeleveld]

On Thursday, November 13, 2014 05:41:27 PM Helmut Jarausch wrote:
> Hi,
> 
> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system has
> stopped logging, i.e. I only get the messages
> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down;
> version='3.6.1'

Here it stops

> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up;
> version='3.6.1'

Here it starts

> Has anybody observed the same problem, and how to fix it?

See above.

--
Joost

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Helmut Jarausch]

On 11/13/2014 09:05:50 PM, Alan McKinnon wrote:
> On 13/11/2014 18:41, Helmut Jarausch wrote:
> > Hi,
> > 
> > after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system
> has 
> > stopped logging, i.e. I only get the messages
> > Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; 
> > version='3.6.1'
> > Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; 
> > version='3.6.1'
> > 
> > Has anybody observed the same problem, and how to fix it?
> > 
> > Many thanks for a hint,
> > Helmut
> > 
> > 
> 
> 
> Run a syntax check on the config file, I don't have a man page to 
> hand
> but it's quite obvious what the option is.
> syslog-ng has sometimes been picky about version numbers in the past
> and
> it's tagged in the config file. Read the syntax check output 
> carefully
> to see if anything is amiss.

Thanks, Alan.

The only unusual message is
Systemd is not detected as the running init system;

which is true since I still use openrc (but with systemd installed, as 
well)
Could this be the culprit?

Helmut

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Alan McKinnon]

On 14/11/2014 18:18, Helmut Jarausch wrote:
> On 11/13/2014 09:05:50 PM, Alan McKinnon wrote:
>> On 13/11/2014 18:41, Helmut Jarausch wrote:
>>> Hi,
>>>
>>> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system
>> has 
>>> stopped logging, i.e. I only get the messages
>>> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; 
>>> version='3.6.1'
>>> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; 
>>> version='3.6.1'
>>>
>>> Has anybody observed the same problem, and how to fix it?
>>>
>>> Many thanks for a hint,
>>> Helmut
>>>
>>>
>>
>>
>> Run a syntax check on the config file, I don't have a man page to 
>> hand
>> but it's quite obvious what the option is.
>> syslog-ng has sometimes been picky about version numbers in the past
>> and
>> it's tagged in the config file. Read the syntax check output 
>> carefully
>> to see if anything is amiss.
> 
> Thanks, Alan.
> 
> The only unusual message is
> Systemd is not detected as the running init system;
> 
> which is true since I still use openrc (but with systemd installed, as 
> well)
> Could this be the culprit?


I doubt it, I also use 3.6.1 without systemd.

Please post eix syslog-ng so we can see how your USE is set up, and your
syslog-ng.conf


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Helmut Jarausch]

On 11/14/2014 06:46:28 PM, Alan McKinnon wrote:
> On 14/11/2014 18:18, Helmut Jarausch wrote:
> > On 11/13/2014 09:05:50 PM, Alan McKinnon wrote:
> >> On 13/11/2014 18:41, Helmut Jarausch wrote:
> >>> Hi,
> >>>
> >>> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my 
> system
> >> has 
> >>> stopped logging, i.e. I only get the messages
> >>> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; 
> >>> version='3.6.1'
> >>> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; 
> >>> version='3.6.1'
> >>>
> >>> Has anybody observed the same problem, and how to fix it?
> >>>
> >>> Many thanks for a hint,
> >>> Helmut
> >>>
> >>>
> >>
> >>
> >> Run a syntax check on the config file, I don't have a man page to 
> >> hand
> >> but it's quite obvious what the option is.
> >> syslog-ng has sometimes been picky about version numbers in the
> past
> >> and
> >> it's tagged in the config file. Read the syntax check output 
> >> carefully
> >> to see if anything is amiss.
> > 
> > Thanks, Alan.
> > 
> > The only unusual message is
> > Systemd is not detected as the running init system;
> > 
> > which is true since I still use openrc (but with systemd installed,
> as 
> > well)
> > Could this be the culprit?
> 
> 
> I doubt it, I also use 3.6.1 without systemd.
> 
> Please post eix syslog-ng so we can see how your USE is set up, and
> your
> syslog-ng.conf
> 
Thanks, Alan.

[U] app-admin/syslog-ng
     Available versions:  3.4.7^t 3.4.8^t (~)3.5.6^t{tbz2}[1] 
(~)3.6.1^t{tbz2} {amqp caps dbi geoip ipv6 json mongodb pacct +pcre 
redis smtp spoof-source ssl systemd tcpd}
     Installed versions:  3.5.6^t{tbz2}[1](05:21:52 PM 11/14/2014)(ipv6 
json pcre ssl systemd tcpd -amqp -caps -dbi -geoip -mongodb -pacct -
smtp -spoof-source)
     Homepage:            http://www.balabit.com/network-security/
syslog-ng
     Description:         syslog replacement with advanced filtering 
features

And here are the config files (I've left out the commented lines)

================ /etc/syslog-ng/scl.conf =============================
@define scl-root "`syslog-ng-data`/include/scl"
@define include-path "`include-path`:`syslog-ng-data`/include"

@include 'scl/system/plugin.conf'
@include 'scl/pacct/plugin.conf'
@include 'scl/syslogconf/plugin.conf'

================ /etc/syslog-ng/syslog-ng.conf =================
options { 
	threaded(yes);
	chain_hostnames(no); 
	stats_freq(43200); 

	mark_freq(3600); 
};

source src { system(); internal(); };

destination messages { file("/var/log/messages"); };
destination console_all { file("/dev/tty12"); };
log { source(src); destination(messages); };
log { source(src); destination(console_all); };


================ /etc/conf.d/syslog-ng =================
SYSLOG_NG_OPTS=""

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Tanstaafl]

On 11/14/2014 12:46 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 14/11/2014 18:18, Helmut Jarausch wrote:
>> The only unusual message is
>> Systemd is not detected as the running init system;
>>
>> which is true since I still use openrc (but with systemd installed, as 
>> well)
>> Could this be the culprit?

> I doubt it, I also use 3.6.1 without systemd.

But did you miss that:

a) he has it installed, and

b) he gets a message about 'systemd is not detected as the running init
system'

?

Maybe it is trying to use systemd but since it isn't running?

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Stroller]

On Thu, 13 November 2014, at 4:41 pm, Helmut Jarausch <jarausch@igpm.rwth-aachen.de> wrote:
> 
> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system has 
> stopped logging, i.e. I only get the messages
> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; 
> version='3.6.1'
> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; 
> version='3.6.1'

There's been some activity on bugs.gentoo.org about this.

Stroller.

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Alan McKinnon]

On 14/11/2014 20:44, Helmut Jarausch wrote:
> On 11/14/2014 06:46:28 PM, Alan McKinnon wrote:
>> On 14/11/2014 18:18, Helmut Jarausch wrote:
>>> On 11/13/2014 09:05:50 PM, Alan McKinnon wrote:
>>>> On 13/11/2014 18:41, Helmut Jarausch wrote:
>>>>> Hi,
>>>>>
>>>>> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my 
>> system
>>>> has 
>>>>> stopped logging, i.e. I only get the messages
>>>>> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; 
>>>>> version='3.6.1'
>>>>> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; 
>>>>> version='3.6.1'
>>>>>
>>>>> Has anybody observed the same problem, and how to fix it?
>>>>>
>>>>> Many thanks for a hint,
>>>>> Helmut
>>>>>
>>>>>
>>>>
>>>>
>>>> Run a syntax check on the config file, I don't have a man page to 
>>>> hand
>>>> but it's quite obvious what the option is.
>>>> syslog-ng has sometimes been picky about version numbers in the
>> past
>>>> and
>>>> it's tagged in the config file. Read the syntax check output 
>>>> carefully
>>>> to see if anything is amiss.
>>>
>>> Thanks, Alan.
>>>
>>> The only unusual message is
>>> Systemd is not detected as the running init system;
>>>
>>> which is true since I still use openrc (but with systemd installed,
>> as 
>>> well)
>>> Could this be the culprit?
>>
>>
>> I doubt it, I also use 3.6.1 without systemd.
>>
>> Please post eix syslog-ng so we can see how your USE is set up, and
>> your
>> syslog-ng.conf
>>
> Thanks, Alan.
> 
> [U] app-admin/syslog-ng
>      Available versions:  3.4.7^t 3.4.8^t (~)3.5.6^t{tbz2}[1] 
> (~)3.6.1^t{tbz2} {amqp caps dbi geoip ipv6 json mongodb pacct +pcre 
> redis smtp spoof-source ssl systemd tcpd}
>      Installed versions:  3.5.6^t{tbz2}[1](05:21:52 PM 11/14/2014)(ipv6 
> json pcre ssl systemd tcpd -amqp -caps -dbi -geoip -mongodb -pacct -
> smtp -spoof-source)
>      Homepage:            http://www.balabit.com/network-security/
> syslog-ng
>      Description:         syslog replacement with advanced filtering 
> features


I don't find any info on what the syslog-ng ebuild does with
USE=systemd, I suspect it may want to use the fancy logging features
built into systemd.

Since you have it, but don't run it, does USE=-systemd fix the issue?


> 
> And here are the config files (I've left out the commented lines)
> 
> ================ /etc/syslog-ng/scl.conf =============================
> @define scl-root "`syslog-ng-data`/include/scl"
> @define include-path "`include-path`:`syslog-ng-data`/include"
> 
> @include 'scl/system/plugin.conf'
> @include 'scl/pacct/plugin.conf'
> @include 'scl/syslogconf/plugin.conf'
> 
> ================ /etc/syslog-ng/syslog-ng.conf =================
> options { 
> 	threaded(yes);
> 	chain_hostnames(no); 
> 	stats_freq(43200); 
> 
> 	mark_freq(3600); 
> };
> 
> source src { system(); internal(); };
> 
> destination messages { file("/var/log/messages"); };
> destination console_all { file("/dev/tty12"); };
> log { source(src); destination(messages); };
> log { source(src); destination(console_all); };
> 
> 
> ================ /etc/conf.d/syslog-ng =================
> SYSLOG_NG_OPTS=""


That all looks normal, I don't see anything problematic there


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

On Sat, 15 Nov 2014 07:04:03 +0200, Alan McKinnon wrote:

> > [U] app-admin/syslog-ng
> >      Available versions:  3.4.7^t 3.4.8^t (~)3.5.6t,^t{tbz2}[1] 
> > (~)3.6.1^t{tbz2} {amqp caps dbi geoip ipv6 json mongodb pacct +pcre 
> > redis smtp spoof-source ssl systemd tcpd}
> >      Installed versions:  3.5.6^t{tbz2}[1](05:21:52 PM
> > 11/14/2014)(ipv6 json pcre ssl systemd tcpd -amqp -caps -dbi -geoip
> > -mongodb -pacct - smtp -spoof-source)
> >      Homepage:            http://www.balabit.com/network-security/
> > syslog-ng
> >      Description:         syslog replacement with advanced filtering 
> > features  
> 
> I don't find any info on what the syslog-ng ebuild does with
> USE=systemd, I suspect it may want to use the fancy logging features
> built into systemd.

Looking at the ebuild and ./configure --help output, it seems to be used
to install service files and to change the restart command used by
logrotate, which would cause you a problem later if you did actually
get it working properly.

There's also a configure option to use the journal, which may be the
source of the problem.

> Since you have it, but don't run it, does USE=-systemd fix the issue?

Worth a try. If it does fix it I would consider it a bug since adding
systemd support should not implicitly disable it under openrc.


-- 
Neil Bothwick

Windows Error #02: Multitasking attempted. System confused.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Walter Dnes]

On Sat, Nov 15, 2014 at 09:34:18AM +0000, Neil Bothwick wrote
> On Sat, 15 Nov 2014 07:04:03 +0200, Alan McKinnon wrote:
>
> > Since you have it, but don't run it, does USE=-systemd fix the issue?
> 
> Worth a try. If it does fix it I would consider it a bug since adding
> systemd support should not implicitly disable it under openrc.

  I disagree.  He's telling the build that it's running under systemd,
but there is no systemd running.  That's a problem with them pesky
computers... they do what you tell them to do, not what you want them to
do.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Rich Freeman]

On Sat, Nov 15, 2014 at 3:08 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> On Sat, Nov 15, 2014 at 09:34:18AM +0000, Neil Bothwick wrote
>> On Sat, 15 Nov 2014 07:04:03 +0200, Alan McKinnon wrote:
>>
>> > Since you have it, but don't run it, does USE=-systemd fix the issue?
>>
>> Worth a try. If it does fix it I would consider it a bug since adding
>> systemd support should not implicitly disable it under openrc.
>
>   I disagree.  He's telling the build that it's running under systemd,
> but there is no systemd running.  That's a problem with them pesky
> computers... they do what you tell them to do, not what you want them to
> do.
>

USE=systemd simply means to enable support for systemd, not that it is
running.  Generally stuff like this should be a matter of
configuration, not build options.

Otherwise your life as a Gentoo user would be a living nightmare when
you look at how many profile use flags there are.

--
Rich

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

On Sat, 15 Nov 2014 15:08:02 -0500, Walter Dnes wrote:

> > Worth a try. If it does fix it I would consider it a bug since adding
> > systemd support should not implicitly disable it under openrc.  
> 
>   I disagree.  He's telling the build that it's running under systemd,
> but there is no systemd running.  That's a problem with them pesky
> computers... they do what you tell them to do, not what you want them to
> do.

The USE flag is there to enable, or otherwise, systemd support. USE flags
affect build tie behaviour, not run time behaviour. Building with systemd
support should not silently disable openrc support - that should be done
with a separate USE flag, if wanted.


-- 
Neil Bothwick

TROI : What am I sensing?? I'm sensing INCOMPETENCE, you pretentious
bald pseudo-French dickweed!

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Walter Dnes]

On Sat, Nov 15, 2014 at 04:11:56PM -0500, Rich Freeman wrote
> 
> USE=systemd simply means to enable support for systemd, not that it is
> running.  Generally stuff like this should be a matter of
> configuration, not build options.
> 
> Otherwise your life as a Gentoo user would be a living nightmare when
> you look at how many profile use flags there are.

  There are already some situations where 2 programs cannot co-exist,
e.g. 2 MTAs.  This may be a similar situation in principle.  A system
daemon may operate differently under openrc than systemd.  When I run

emerge -pv syslog-ng

  I see that a "systemd" USE flag exists, but not an "openrc" USE flag.
I think that's the root of the problem.  The default is to support
openrc.  When the ebuild sees sees the "systemd", it assumes you're not
running openrc.  Maybe the solution for syslog-ng is to add an "openrc"
USE flag.  Build in support for whichever flag is set.  When
experimenting, people might want to set both "openrc" and "systemd" USE
flags for syslog-ng.  If systemd users have to set the "systemd" flag
for some ebuilds, I have no objection to setting the "openrc" USE flag
in make.conf.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Tom H]

On Mon, Nov 17, 2014 at 12:54 AM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> On Sat, Nov 15, 2014 at 04:11:56PM -0500, Rich Freeman wrote
>>
>> USE=systemd simply means to enable support for systemd, not that it is
>> running. Generally stuff like this should be a matter of
>> configuration, not build options.
>>
>> Otherwise your life as a Gentoo user would be a living nightmare when
>> you look at how many profile use flags there are.
>
> There are already some situations where 2 programs cannot co-exist,
> e.g. 2 MTAs. This may be a similar situation in principle. A system
> daemon may operate differently under openrc than systemd. When I run
>
> emerge -pv syslog-ng
>
> I see that a "systemd" USE flag exists, but not an "openrc" USE flag.
> I think that's the root of the problem. The default is to support
> openrc. When the ebuild sees sees the "systemd", it assumes you're not
> running openrc. Maybe the solution for syslog-ng is to add an "openrc"
> USE flag. Build in support for whichever flag is set. When
> experimenting, people might want to set both "openrc" and "systemd" USE
> flags for syslog-ng. If systemd users have to set the "systemd" flag
> for some ebuilds, I have no objection to setting the "openrc" USE flag
> in make.conf.

Is the "systemd" USE flag an actual syslog-ng compilation option or it
is a flag to generate systemd units when syslog-ng is installed?

If it's the latter, an "openrc" flag would be a no-op, unless someone
wants the option to set "-openrc" and not have a runscript installed.

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 434 bytes --]

On Mon, 17 Nov 2014 05:32:14 -0500, Tom H wrote:

> Is the "systemd" USE flag an actual syslog-ng compilation option or it
> is a flag to generate systemd units when syslog-ng is installed?

Both.


-- 
Neil Bothwick

Quantum leap: (adj.) literally, to move by the smallest amount
theoretically possible. In advertising, to move by the largest leap
imaginable (in the mind of the advertiser). There is no contradiction.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Rich Freeman]

On Mon, Nov 17, 2014 at 5:44 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Mon, 17 Nov 2014 05:32:14 -0500, Tom H wrote:
>
>> Is the "systemd" USE flag an actual syslog-ng compilation option or it
>> is a flag to generate systemd units when syslog-ng is installed?
>
> Both.
>

Please read the ebuild before giving answers like this.  The unit file
is installed regardless of flag setting (which is the standard
policy).  There is a compile-time option which this also toggles, and
it also changes the logrotate script (which probably isn't ideal).

I don't know offhand what toggling the compile-time option does.  It
seems that it does more than simply enable systemd support, though
there might be run-time options to control that and if so those should
be added to the openrc init.d script.

Looking at the syslog-ng admin guide, consider changing your log
source from system() (which autodetects the source) to something like:

unix-dgram("/dev/log");

file("/proc/kmsg" program-override("kernel") flags(kernel));

That appears to be what system() does when not running systemd.  If
this works then I think upstream might accept a bug report on this -
the autodetection code isn't actually detecting whether systemd is
running, but whether it was enabled/installed/etc.

--
Rich

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

On Mon, 17 Nov 2014 07:59:57 -0500, Rich Freeman wrote:

> >> Is the "systemd" USE flag an actual syslog-ng compilation option or
> >> it is a flag to generate systemd units when syslog-ng is installed?  
> >
> > Both.
> >  
> 
> Please read the ebuild before giving answers like this.  The unit file
> is installed regardless of flag setting (which is the standard
> policy).  There is a compile-time option which this also toggles, and
> it also changes the logrotate script (which probably isn't ideal).

I did, it's just that my memory isn't what it used to be. I know about
the compile time option and the logrotate script, see my previous post on
it, but for some reason thought that the unit file was also optional.


-- 
Neil Bothwick

Head: (n.) the part of a disk drive which detects sectors and decides
which of the two possible values to return: 'lose a turn' or 'bankrupt.'

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Helmut Jarausch]

On 11/13/2014 05:41:27 PM, Helmut Jarausch wrote:
> Hi,
> 
> after upgrading from syslog-ng-3.5.6  to syslog-ng-3.6.1 my system 
> has
> 
> stopped logging, i.e. I only get the messages
> Nov 12 21:04:10 numa syslog-ng[1392]: syslog-ng shutting down; 
> version='3.6.1'
> Nov 13 14:52:20 numa syslog-ng[1392]: syslog-ng starting up; 
> version='3.6.1'
> 
> Has anybody observed the same problem, and how to fix it?
> 

As noted earlier, I'm still using openrc but I have systemd installed, 
as well.

Meanwhile, I have re-installed syslog-ng-3.6.1   WITHOUT the systemd 
use flag. Now, it works just fine.

Should I make a bug report on this?

Many thanks to all who have helped,
Helmut

Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore

[Rich Freeman]

On Mon, Nov 17, 2014 at 10:51 AM, Helmut Jarausch
<jarausch@igpm.rwth-aachen.de> wrote:
>
> Should I make a bug report on this?
>

See my post.  I suggest testing the different input source options to
understand what the actual problem is.

I suspect this is an upstream bug in the implementation of system(),
but I can't say for sure without testing.

--
Rich