syslog-ng 3.5.4.1 failure on boot

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

syslog-ng 3.5.4.1 failure on boot

L0 Member

Hi, We have integrated syslog-ng 3.5.4.1 on a client machine which sends logs to server which is running syslog-ng 3.16.1, some times, I see below error at the boot up of our target

syslog-ng[1762]: Error opening control socket, bind() failed; socket='/var/lib/syslog-ng/syslog-ng.ctl', error='Permission denied (13)'

and logs will not be sent to the server.

Is the version difference at the client and server is cause of this? but it works most of the times..

 

I have recently started working on syslog-ng and don't have much internal knowledge how it works and don't have a clue where to start.

 

Any help in resolving the issue is much appreciated, please let me  know if any other details are needed.

2 REPLIES 2

Cyber Elite
Cyber Elite

you're going to want to ask that over at https://www.syslog-ng.com/ , they'll know what to do

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

L0 Member

I have the same issue

 

  • 2328 Views
  • 2 replies
  • 1 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!