If you get the mentioned errors right after the upgrade, maybe the install scripts are not able to stop syslog-ng -> the upgraded syslog-ng isn't able to start. Could you check the install scripts, please?
2016-05-06 14:28 GMT+02:00 Ivan Adji - Krstev <akivanradix@gmail.com>:
Here it is
[root@syslogserver syslog-ng]# lsof | grep LISTEN
sshd 854 root 3u IPv4 15103 0t0 TCP *:ssh (LISTEN)
sshd 854 root 4u IPv6 15105 0t0 TCP *:ssh (LISTEN)
mongod 1325 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 1346 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 1922 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 1923 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 1924 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2010 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2011 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2012 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2013 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2165 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2167 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2168 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2169 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2170 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2171 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 2172 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 27857 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 27874 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 27876 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
mongod 1325 28175 mongod 6u IPv4 15950 0t0 TCP localhost:27017 (LISTEN)
master 1577 root 13u IPv4 16582 0t0 TCP localhost:smtp (LISTEN)
master 1577 root 14u IPv6 16583 0t0 TCP localhost:smtp (LISTEN)
syslog-ng 28172 root 21u IPv4 3116883 0t0 TCP *:syslog-tls (LISTEN)
syslog-ng 28172 28173 root 21u IPv4 3116883 0t0 TCP *:syslog-tls (LISTEN)
[root@syslogserver syslog-ng]# netstat -antp | grep 6514
tcp 0 0 0.0.0.0:6514 0.0.0.0:* LISTEN 28172/syslog-ng
[root@syslogserver syslog-ng]#
Kind regards
Ivan
On 05/06/2016 02:25 PM, Tibor Benke wrote:
Hi Ivan,
Could you check what program listens on 0.0.0.0:6514? Thanks! (I suppose it's a syslog-ng which failed to stop from some unknown reason.)
Tibor
2016-05-06 14:18 GMT+02:00 Ivan Adji - Krstev <akivanradix@gmail.com>:
I have to say ... defenetly we have a problem with this version. I have install minimal CentOS 7 (CentOS Linux release 7.2.1511 (Core) ) and Syslog-NG 3.8 and again i have the problem when i update from 3.7 to 3.8.
[2016-05-06T08:14:35.480042] Error binding socket; addr='AF_INET(0.0.0.0:6514)', error='Address already in use (98)'
[2016-05-06T08:14:35.480091] Error initializing message pipeline;
If you have any suggestions about this problem pleas do it as im on the way to go back on 3.7
Kind regards
Ivan
On 04/26/2016 02:40 AM, Scot Needy wrote:
No issues on CentOS 7.1
On Apr 25, 2016, at 1:11 PM, Scheidler, Balázs <balazs.scheidler@balabit.com> wrote:
Anyway, I don't think your "address is already in use" is a 3.8 related issue, it is most probably systemd/initscript related.Hi,3.8 is not yet considered stable, although we do everything to keep it that way. It is where we integrate new stuff, both features and bugfixes. I would stick to 3.7 in a production environment, even though your feedback of 3.8 is very valuable and appreciated, so it becomes really stable when we get to the release button.
______________________________________________________________________________
--
Bazsi
On Mon, Apr 25, 2016 at 2:18 PM, Ivan Adji - Krstev <akivanradix@gmail.com> wrote:
Hi all,
I have open a issue about the error i got when i update the Syslog-NG to
3.8 for "syslog-ng Address already in use (98)". I'm still working on
the issue, but i would like to know if this newest version 3.8 is
stabled as im building new environment and im asking myself do i use
this 3.8 version or 3.7 ?
Thanks
Ivan
______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq