[syslog-ng] SSL Problem after update

[Scheidler, Balázs]

the error message clearly says that the port 6514 is already occupied.
maybe an old instance of syslog-ng is still running.

try investigating with netstat -antp to see which process keeps that opened.

-- 
Bazsi

On Thu, Apr 21, 2016 at 11:51 AM, Ivan Adji - Krstev <akivanradix at gmail.com>
wrote:

> Hi all,
> I have update the syslog-ng to 3.8 ( yum remove syslog-ng && yum install
> syslog-ng ) and change from MySQL to Mongo DB and now when i restart i have
> the following errors:
>
> Error binding socket; addr='AF_INET(0.0.0.0:6514)', error='Address
> already in use (98)'
> I'm using mutual self certification and the certificates are there in the
> directories "ca.d"  "cert.d". Do i have to re-create all the certificates
> now or can i fix this somehow.
>
> P.S. This problem i have on the Syslog-NG Server, they all send messages
> to this server. So if i have to change the certificate here i will have to
> change on the clients too. :(
>
> Any hints on this ?
>
>
> ______________________________________________________________________________
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20160421/23e5d670/attachment.htm