Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 702032 - sys-admin/syslog-ng-3.22.1 - /etc/init.d/syslog-ng restart does not always restart cleanly
Summary: sys-admin/syslog-ng-3.22.1 - /etc/init.d/syslog-ng restart does not always re...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Stabilization (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Tomáš Mózes
URL:
Whiteboard:
Keywords: CC-ARCHES, STABLEREQ
Depends on: 716006
Blocks:
  Show dependency tree
 
Reported: 2019-12-05 11:45 UTC by David Flogeras
Modified: 2020-08-05 16:16 UTC (History)
2 users (show)

See Also:
Package list:
app-admin/syslog-ng-3.26.1-r1 amd64 arm arm64 hppa ppc ppc64 sparc x86 dev-libs/boxfort-0.0.1_pre20200110 amd64 dev-libs/criterion-2.4_pre20200110 amd64
Runtime testing required: ---
nattka: sanity-check+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Flogeras 2019-12-05 11:45:13 UTC
I've noticed during the last few update cycles, after upgrading dependent libraries like libpcre, or openssl etc.  that performing a /etc/init.d/syslog-ng restart leaves stagnant syslog-ng processes.  The only way I've found to do a full restart is to /etc/init.d/syslog-ng stop, followed by a killall syslog-ng, then /etc/init.d/syslog start.

Reproducible: Always
Comment 1 David Flogeras 2019-12-05 11:45:30 UTC
emerge --info
Portage 2.3.79 (python 3.6.9-final-0, default/linux/amd64/17.1/desktop/plasma, gcc-9.2.0, glibc-2.29-r2, 4.19.86-gentoo x86_64)
=================================================================
System uname: Linux-4.19.86-gentoo-x86_64-Intel-R-_Core-TM-_i7-4770_CPU_@_3.40GHz-with-gentoo-2.6
KiB Mem:    16334756 total,    419296 free
KiB Swap:          0 total,         0 free
Timestamp of repository gentoo: Tue, 03 Dec 2019 16:00:01 +0000
Head commit of repository gentoo: 45f8af881e01f34cd8cfb565f0dbc183603a7d8d
sh bash 4.4_p23-r1
ld GNU ld (Gentoo 2.32 p2) 2.32.0
ccache version 3.7.4 [disabled]
app-shells/bash:          4.4_p23-r1::gentoo
dev-java/java-config:     2.2.0-r4::gentoo
dev-lang/perl:            5.28.2-r1::gentoo
dev-lang/python:          2.7.16::gentoo, 3.6.9::gentoo
dev-util/ccache:          3.7.4::gentoo
dev-util/cmake:           3.14.6::gentoo
dev-util/pkgconfig:       0.29.2::gentoo
sys-apps/baselayout:      2.6-r1::gentoo
sys-apps/openrc:          0.41.2::gentoo
sys-apps/sandbox:         2.13::gentoo
sys-devel/autoconf:       2.13-r1::gentoo, 2.69-r4::gentoo
sys-devel/automake:       1.13.4-r2::gentoo, 1.15.1-r2::gentoo, 1.16.1-r1::gentoo
sys-devel/binutils:       2.32-r1::gentoo
sys-devel/gcc:            4.7.4-r3::gentoo, 4.8.5-r3::gentoo, 4.9.4-r1::gentoo, 5.5.0::gentoo, 6.5.0-r1::gentoo, 7.4.0-r2::gentoo, 8.3.0-r1::gentoo, 9.2.0-r2::gentoo
sys-devel/gcc-config:     2.1::gentoo
sys-devel/libtool:        2.4.6-r3::gentoo
sys-devel/make:           4.2.1-r4::gentoo
sys-kernel/linux-headers: 4.19::gentoo (virtual/os-headers)
sys-libs/glibc:           2.29-r2::gentoo
Repositories:

gentoo
    location: /usr/portage
    sync-type: rsync
    sync-uri: rsync://rsync.gentoo.org/gentoo-portage
    priority: -1000
    sync-rsync-verify-jobs: 1
    sync-rsync-extra-opts: 
    sync-rsync-verify-metamanifest: yes
    sync-rsync-verify-max-age: 24

crossdev
    location: /usr/local/portage
    masters: gentoo
    priority: 0

Installed sets: @steam
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="@FREE"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -pipe -O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php7.3/ext-active/ /etc/php/cgi-php7.3/ext-active/ /etc/php/cli-php7.3/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=native -pipe -O2"
DISTDIR="/usr/portage/distfiles"
ENV_UNSET="DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://mirror.its.dal.ca/gentoo"
LANG="en_US.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="en"
MAKEOPTS="-j8"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X a52 aac acl acpi activities alsa amd64 berkdb bluetooth branding bzip2 cairo cdda cdr cli consolekit crypt cxx dbus declarative dri dts dvd dvdr emboss encode exif fam flac fortran gdbm gif gpm gtk iconv icu jpeg kde kipi kwallet lcms libnotify libtirpc mad mng mozbranding mp3 mp4 mpeg multilib ncurses nls nptl ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds qml qt5 readline sdl seccomp spell split-usr ssl startup-notification svg tcpd threads tiff truetype udev udisks unicode upower usb vorbis widgets wxwidgets x264 xattr xcb xcomposite xinerama xml xv xvid zlib" ABI_X86="64" ADA_TARGET="gnat_2018" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="words" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 fma3 mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" L10N="en" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" NETBEANS_MODULES="apisupport cnd groovy gsf harness ide identity j2ee java mobility nb php profiler soa visualweb webcommon websvccommon xml" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php7-2" POSTGRES_TARGETS="postgres10 postgres11" PYTHON_SINGLE_TARGET="python3_6" PYTHON_TARGETS="python2_7 python3_6" RUBY_TARGETS="ruby24 ruby25" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2019-12-05 12:46:13 UTC
It's probably a good idea to attach your (reduced) /etc/syslog-ng/syslog-ng.conf configuration, i.e. the output of `syslog-ng --preprocess-into=~syslog-ng-full-configuration`, if it differs from the default.
Comment 3 c.cboldt 2019-12-05 13:24:25 UTC
From my point of view, v. 3.22.1 is broken, or at least changed significantly from previous.   I had the same issue - /init.d/syslog-ng stop, does not stop.  There is a way (switch in the start command in /init.d/syslog-ng) to cure this, so "broken" might be an arguable point.

I keyworded the "unstable" version and the issue went away.  3.23 and 3.24 both worked "the old way" without any other config or init file change.

Has nothing to do with syslog-ng.conf or any related config stuff.
Comment 4 Tomáš Mózes 2019-12-05 13:51:17 UTC
Cam you please try 3.24.1? If it fixes your issue I'll call stabilization.
Comment 5 David Flogeras 2019-12-05 22:37:35 UTC
@Jeroen: I've seen this on multiple machines, most of which are default configuration.  The most customization I do on one machine is redirect ssh to a separate logfile:

#sshd logging to separate file
destination ssh { file("/var/log/sshd.log"); };
filter f_ssh { program("sshd"); };
log { source(src); filter(f_ssh); destination( ssh ); flags(final); };




@Tomáš: I've verified there isn't a problem after upgrading to 3.24.1.  However, I'm not 100% how to reproduce it on 3.22.1.  Simply restarting 3.22.1 doesn't always leave crumbs behind.  Maybe it has to run for a longer period of time and/or have something to do with logrotate jobs running (just a wildassguess).  I've only seen it on machines that have been running a long while, but require a syslog restart after upgrading deps.

I can leave 3.24.1 on this machine for a few days and restart it to see if I can verify one way or another?  I'll do the same with a machine running the old version.
Comment 6 Tomáš Mózes 2019-12-06 04:30:39 UTC
Well that's strange because I've been using 3.22.1 on like 50 machines with the hardened configuration and haven't observed such behavior. Nevertheless currently I'm using 3.24.1 on most of the machines without issues too, so I don't see a reason to not stabilize it if it fixes your issues. Please report back.
Comment 7 David Flogeras 2019-12-06 09:40:42 UTC
Yes, I hate when I cannot reproduce.  I will let the two versions run the weekend and report back.

Out of curiousity, are your machines openrc as well?
Comment 8 Tomáš Mózes 2019-12-06 10:51:12 UTC
(In reply to David Flogeras from comment #7)
> Out of curiousity, are your machines openrc as well?

Yes, 100% openrc.
Comment 9 c.cboldt 2019-12-07 17:53:20 UTC
I'm 100% openrc as well.

To see the problem ...

see what syslog-ng is running, `ps aux | grep syslog-ng`

You should see two entries, one being a supervisor

STOP (not restart) syslog-ng `/etc/init.d/syslog-ng stop`

see what syslog-ng is running, `ps aux | grep syslog-ng`

The reason I found this at all is that my instances of syslog-ng spawns a log watching program.  Every time syslog-ng 3.22 was restarted, another instance of the log watching program would be spawned. The running of syslog-ng otherwise looked great, fine, no trouble.

If you test with `/etc/init.d/syslog-ng restart` you will find two entries after restarting, and syslog-ng itself will be running correctly.  If syslog-ng spawns a program, you will find multiple instances of the spawned program

On my machines, syslog-ng spawns a program by using a config of this form ...

destination watch-logs { program("/usr/local/sbin/watch-logs"); };
log { source(src); destination(watch-logs); };

For testing purposes, /usr/local/sbin/watch-logs is essentially a never-ending loop.  Here is a simple never-ending loop

#! /bin/bash
while :
do
if read log_action; then
  :
fi
done

My real syslog-ng config is considerably more complex with filtering and rewrites, and "watch-logs" obviously does more than sit and spin on receipt of input.  However, the above essentials are sufficient to test the "multiple spawns" behavior.
Comment 10 c.cboldt 2019-12-07 18:02:50 UTC
On the issue of syslog-ng not writing to logs after logrotate (unless syslog-ng is reloaded or restarted after logrotate), use of "copytruncate" within logrotate configuration accomplishes the same effect.

I apply this as needed, log-by-log basis, as not all logs rotated by logrotate are written via syslog-ng in the first place.
Comment 11 David Flogeras 2019-12-10 03:35:47 UTC
Well after the weekend, restarting both 3.22.1 and 3.24.1 worked as expected.  I tried 3.22.1 on multiple machines, both with 'restart' and with 'stop' then 'start'.

I can't seem to reproduce it, even though I guarantee I have seen it (on many machines especially after gcc-9 upgrade and rebuilding).  I even tried rebuilding glib, libpcre, and openssl (this was the primary reason I restarted syslog-ng lately after upgrades, and it was holding on to old references of libraries).  It still restarted fine.

I'll leave it up to Tomáš whether it's worth stabling or waiting.
Comment 12 David Flogeras 2019-12-13 00:22:44 UTC
OK, finally got extra some info.  I was upgrading an armv7a machine (using syslog-ng-3.22.1).  Mainly the perl update and a glibc rebuild and some others:

2019-12-12T11:58:03 >>> dev-libs/libbsd
2019-12-12T11:59:29 >>> sys-libs/glibc
2019-12-12T12:01:19 >>> dev-libs/libxml2
2019-12-12T12:02:24 >>> sys-libs/talloc
2019-12-12T12:03:26 >>> sys-libs/tdb
2019-12-12T12:04:25 >>> sys-libs/tevent
2019-12-12T12:05:24 >>> sys-libs/ldb
2019-12-12T12:06:27 >>> dev-lang/perl
2019-12-12T18:36:57 >>> perl-core/File-Temp
2019-12-12T18:38:14 >>> virtual/perl-File-Temp
2019-12-12T18:39:18 >>> virtual/perl-Carp
2019-12-12T18:40:23 >>> virtual/perl-Exporter
2019-12-12T18:41:28 >>> virtual/perl-Encode
2019-12-12T18:42:32 >>> virtual/perl-Scalar-List-Utils
2019-12-12T18:43:40 >>> virtual/perl-MIME-Base64
2019-12-12T18:44:35 >>> dev-perl/LWP-MediaTypes
2019-12-12T18:45:33 >>> virtual/perl-Compress-Raw-Zlib
2019-12-12T18:46:28 >>> virtual/perl-IO
2019-12-12T18:47:23 >>> virtual/perl-File-Spec
2019-12-12T18:48:21 >>> virtual/perl-libnet
2019-12-12T18:49:16 >>> dev-perl/XML-Parser
2019-12-12T18:50:14 >>> virtual/perl-XSLoader
2019-12-12T18:51:08 >>> virtual/perl-Time-Local
2019-12-12T18:52:03 >>> virtual/perl-Data-Dumper
2019-12-12T18:53:00 >>> sys-devel/clang
2019-12-12T18:54:52 >>> virtual/perl-Test-Harness
2019-12-12T18:55:46 >>> virtual/perl-IO-Socket-IP
2019-12-12T18:56:41 >>> dev-perl/Tie-IxHash
2019-12-12T18:57:38 >>> virtual/perl-Digest
2019-12-12T18:58:36 >>> dev-perl/NetAddr-IP
2019-12-12T18:59:32 >>> dev-perl/Text-Iconv
2019-12-12T19:00:28 >>> virtual/perl-Digest-MD5
2019-12-12T19:01:23 >>> dev-perl/HTML-Tagset
2019-12-12T19:02:21 >>> dev-perl/Mozilla-CA
2019-12-12T19:03:20 >>> dev-perl/Socket6
2019-12-12T19:04:16 >>> virtual/perl-Storable
2019-12-12T19:05:11 >>> virtual/perl-Compress-Raw-Bzip2
2019-12-12T19:06:06 >>> virtual/perl-Time-HiRes
2019-12-12T19:07:01 >>> virtual/perl-File-Path
2019-12-12T19:07:59 >>> virtual/perl-parent
2019-12-12T19:08:54 >>> dev-perl/X11-Protocol
2019-12-12T19:09:52 >>> virtual/perl-JSON-PP
2019-12-12T19:10:47 >>> virtual/perl-Digest-SHA
2019-12-12T19:11:42 >>> dev-perl/HTTP-Date
2019-12-12T19:12:42 >>> dev-perl/URI
2019-12-12T19:13:39 >>> dev-perl/HTML-Parser
2019-12-12T19:14:35 >>> dev-perl/Encode-Locale
2019-12-12T19:15:31 >>> virtual/perl-IO-Compress
2019-12-12T19:16:26 >>> dev-perl/XML-XPath
2019-12-12T19:17:24 >>> dev-perl/IO-Socket-INET6
2019-12-12T19:18:20 >>> dev-perl/Net-SSLeay
2019-12-12T19:19:18 >>> dev-perl/IPC-System-Simple
2019-12-12T19:20:17 >>> dev-perl/Sub-Name
2019-12-12T19:21:12 >>> dev-perl/IO-HTML
2019-12-12T19:22:13 >>> dev-perl/Digest-SHA1
2019-12-12T19:23:10 >>> dev-perl/Data-Validate-IP
2019-12-12T19:24:06 >>> dev-perl/HTTP-Message
2019-12-12T19:25:01 >>> dev-perl/File-BaseDir
2019-12-12T19:25:57 >>> dev-perl/IO-Socket-SSL
2019-12-12T19:26:55 >>> dev-perl/WWW-RobotRules
2019-12-12T19:27:50 >>> dev-perl/File-Listing
2019-12-12T19:28:48 >>> dev-perl/Try-Tiny
2019-12-12T19:29:43 >>> dev-perl/Net-HTTP
2019-12-12T19:30:39 >>> dev-perl/HTTP-Daemon
2019-12-12T19:31:38 >>> dev-perl/HTTP-Cookies
2019-12-12T19:32:34 >>> dev-perl/HTTP-Negotiate
2019-12-12T19:33:29 >>> dev-perl/File-DesktopEntry
2019-12-12T19:34:25 >>> dev-perl/libwww-perl
2019-12-12T19:35:22 >>> dev-perl/XML-Twig
2019-12-12T19:36:21 >>> dev-perl/LWP-Protocol-https
2019-12-12T19:37:16 >>> dev-python/subunit
2019-12-12T19:38:21 >>> net-fs/samba
2019-12-12T19:39:47 >>> x11-misc/shared-mime-info
2019-12-12T19:40:46 >>> dev-perl/File-MimeInfo
2019-12-12T19:41:45 >>> net-wireless/bluez
2019-12-12T19:42:49 >>> dev-perl/Net-DBus
2019-12-12T19:43:46 >>> dev-vcs/git
2019-12-12T19:45:08 >>> dev-vcs/tig


After, I noticed syslog-ng held some deleted files (seems mainly from glibc, which wasn't an upgrade, but just a rebuild because of split-use USE):

syslog-ng  2525                       root  DEL       REG        8,1              135842 /lib/libpthread-2.27.so
syslog-ng  2525                       root  DEL       REG        8,1              135898 /lib/libdl-2.27.so
syslog-ng  2525                       root  DEL       REG        8,1              135392 /lib/librt-2.27.so
syslog-ng  2525                       root  DEL       REG        8,1              135815 /lib/libc-2.27.so
syslog-ng  2525                       root  DEL       REG        8,1              135270 /lib/ld-2.27.so
syslog-ng  2525                       root  DEL       REG        8,1              134679 /usr/lib/gconv/gconv-modules.cache
syslog-ng 23119                       root  DEL       REG        8,1              131846 /var/lib/syslog-ng/syslog-ng.persist
syslog-ng 23148                       root  DEL       REG        8,1              135842 /lib/libpthread-2.27.so
syslog-ng 23148                       root  DEL       REG        8,1              135898 /lib/libdl-2.27.so
syslog-ng 23148                       root  DEL       REG        8,1              135392 /lib/librt-2.27.so
syslog-ng 23148                       root  DEL       REG        8,1              135815 /lib/libc-2.27.so
syslog-ng 23148                       root  DEL       REG        8,1              135270 /lib/ld-2.27.so
syslog-ng 23148                       root  DEL       REG        8,1              134679 /usr/lib/gconv/gconv-modules.cache


After restarting the service (with /etc/init.d/syslog-ng restart) 'ps aux | grep syslog ' returns:

root      2525  0.0  0.2   7796  2220 ?        S    Dec08   0:00 supervising syslog-ng
root     23118  0.0  0.1   7796  1804 ?        S    20:15   0:00 supervising syslog-ng
root     23119  0.6  0.5  28704  5612 ?        Ss   20:15   0:00 /usr/sbin/syslog-ng --cfgfile /etc/syslog-ng/syslog-ng.conf --control /run/syslog-ng.ctl --persist-file /var/lib/syslog-ng/syslog-ng.persist --pidfile /run/syslog-ng.pid
root     23148  0.7  0.5  28704  5668 ?        Ss   20:15   0:00 /usr/sbin/syslog-ng --cfgfile /etc/syslog-ng/syslog-ng.conf --control /run/syslog-ng.ctl --persist-file /var/lib/syslog-ng/syslog-ng.persist --pidfile /run/syslog-ng.pid
root     23160  5.4  1.0  36712 10640 ?        Sl   20:15   0:00 /usr/bin/python3.6 /usr/bin/fail2ban-server --async -b -s /run/fail2ban/fail2ban.sock -p /run/fail2ban/fail2ban.pid --loglevel INFO --logtarget /var/log/fail2ban.log --syslogsocket auto
root     23173  0.0  0.0   4680   576 pts/1    S+   20:15   0:00 grep --colour=auto syslog


So there's two of the supervising, and two of the syslog-ng process.
Comment 13 David Flogeras 2019-12-13 00:25:02 UTC
In case it matters, trying to stop/start gave me this on stop:

/etc/init.d/syslog-ng stop
 * Stopping fail2ban ...                                                  [ ok ]
 * Stopping syslog-ng ...                                                 [ ok ]


Then:
ps aux| grep syslo
root      2525  0.0  0.2   7796  2220 ?        S    Dec08   0:00 supervising syslog-ng
root     23118  0.0  0.1   7796  1804 ?        S    20:15   0:00 supervising syslog-ng
root     23119  0.0  0.5  28704  5612 ?        Ss   20:15   0:00 /usr/sbin/sysl g-ng --cfgfile /etc/syslog-ng/syslog-ng.conf --control /run/syslog-ng.ctl --persist-file /var/lib/syslog-ng/syslog-ng.persist --pidfile /run/syslog-ng.pid
root     23299  2.6  0.5  28704  5624 ?        Ssl  20:22   0:00 /usr/sbin/sysl g-ng --cfgfile /etc/syslog-ng/syslog-ng.conf --control /run/syslog-ng.ctl --persist-file /var/lib/syslog-ng/syslog-ng.persist --pidfile /run/syslog-ng.pid


And finally:

/etc/init.d/syslog-ng start
 * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ...           [ ok ]
 * Starting syslog-ng ...
 * start-stop-daemon: /usr/sbin/syslog-ng is already running
 * Failed to start syslog-ng                                              [ !! ]
 * ERROR: syslog-ng failed to start

With the same 2x processes running as above.
Comment 14 Tomáš Mózes 2019-12-13 03:54:26 UTC
Does it behave the same after a reboot? Is it fixed in 3.24.1?
Comment 15 David Flogeras 2019-12-13 11:05:23 UTC
I have not yet seen this behaviour on the one machine I have upgraded to 3.24.1.  This includes the similar perl + glibc upgrade path and about a week running it.

Not sure about a reboot.  When the problem occurs, killing the stray processes and starting syslog-ng again seems to make it go back to "working as expected" (even then restarting it works).  I can try upgrading the machine from comment #12 + #13 to 3.24.1, then reinstall glibc and see if it triggers it, if that helps?

I really wish I knew how to trigger it reliably; I feel like we're in a false-positive/false-negative region.
Comment 16 c.cboldt 2019-12-18 20:53:10 UTC
My machines are all x86, kernel but little if anything else is 64bit.

Have had reason to restart syslog-ng a few times (I restart everything that shows up in `lib_users` after system updates - syslog-ng been restarted a few times since I updated past 3.22)

I have not had a "weird syslog-ng" restart on either 3.23 (no longer in tree) or 3.24.  I would say this problem was limited to 3.22, for the three machines on my local network.

I don't believe I ever ran into multiple supervisor instances!  Really strange and unpredictable behavior on init.d/stop
Comment 17 Rolf Eike Beer archtester 2019-12-28 09:24:15 UTC
So, what's preventing 3.24.1 from being called for stabilization? I see this issue on multiple machines as well, even if it has nothing to do with old files or so.
Comment 18 Tomáš Mózes 2019-12-28 16:27:26 UTC
(In reply to Rolf Eike Beer from comment #17)
> So, what's preventing 3.24.1 from being called for stabilization? I see this
> issue on multiple machines as well, even if it has nothing to do with old
> files or so.

I'll call 3.25.1 stabilization instead which will have tests too (and python 3.8 support).
Comment 19 c.cboldt 2020-01-01 14:55:34 UTC
3.25.1 does not exhibit the "duplicate spawn" or failure to stop behavior that I had under 3.22.
Comment 20 Rolf Eike Beer archtester 2020-06-09 14:52:12 UTC
Ping? Nearly half a year later and nothing has changed so far.
Comment 21 NATTkA bot gentoo-dev 2020-06-09 16:40:59 UTC
Sanity check failed:

> app-admin/syslog-ng-3.26.1
>   depend amd64 stable profile default/linux/amd64/17.0 (28 total)
>     dev-libs/criterion
>   depend amd64 dev profile default/linux/amd64/17.0/no-multilib/prefix/kernel-3.2+ (2 total)
>     dev-libs/criterion
Comment 22 Larry the Git Cow gentoo-dev 2020-06-10 01:22:54 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=754c5886ebc04dc73f689c5e0071c5fc95b5d41a

commit 754c5886ebc04dc73f689c5e0071c5fc95b5d41a
Author:     Tomáš Mózes <hydrapolic@gmail.com>
AuthorDate: 2020-06-09 17:03:58 +0000
Commit:     Thomas Deutschmann <whissi@gentoo.org>
CommitDate: 2020-06-10 01:21:22 +0000

    app-admin/syslog-ng: add support for glib 2.64
    
    Closes: https://bugs.gentoo.org/716006
    Bug: https://bugs.gentoo.org/702032
    Signed-off-by: Tomáš Mózes <hydrapolic@gmail.com>
    Signed-off-by: Thomas Deutschmann <whissi@gentoo.org>

 .../patches/syslog-ng-glib-2.64-support.patch      |  63 ++++++++
 app-admin/syslog-ng/syslog-ng-3.26.1-r1.ebuild     | 171 +++++++++++++++++++++
 2 files changed, 234 insertions(+)
Comment 23 Agostino Sarubbo gentoo-dev 2020-06-26 17:43:29 UTC
amd64 stable
Comment 24 Thomas Deutschmann (RETIRED) gentoo-dev 2020-06-28 20:29:50 UTC
x86 stable
Comment 25 Agostino Sarubbo gentoo-dev 2020-06-28 20:42:08 UTC
sparc stable
Comment 26 Agostino Sarubbo gentoo-dev 2020-06-29 06:22:14 UTC
arm stable
Comment 27 Agostino Sarubbo gentoo-dev 2020-06-29 06:24:21 UTC
ppc stable
Comment 28 Agostino Sarubbo gentoo-dev 2020-06-29 06:25:44 UTC
ppc64 stable
Comment 29 Rolf Eike Beer archtester 2020-06-29 20:54:28 UTC
hppa stable
Comment 30 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2020-08-05 16:16:12 UTC
arm64 done

all arches done