I ran these commands: sudo netstat -lpn | grep 443 and sudo /usr/sbin/lsof | grep LISTEN | grep -w https and here are the results. [jmcdonald@servername ~]$ sudo netstat -lpn | grep 443 tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3511/syslog-ng [jmcdonald@servername ~]$ sudo /usr/sbin/lsof | grep LISTEN | grep -w https syslog-ng 3511 root 11u IPv4 12997 0t0 TCP *:https (LISTEN) If syslog-ng is the one listening/accessing the port, then why am I unable to start/restart the service? -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Lay, James Sent: Monday, August 06, 2012 11:43 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] syslog-ng service not starting -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of James McDonald Sent: Monday, August 06, 2012 9:33 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] syslog-ng service not starting There are other syslog-ng servers configured this way in our environments but I am only having problems with this particular one. Does anyone have any other suggestions? I tried rebooting to clear any connections and re-establish a new one, but I still get the error after a reboot. I tested restarting the service on another syslog-ng server and it worked fine. James, Assuming you're running a linux distro of some sort: sudo netstat -lpn | grep 443 will get you to see what's listening to that port. I would suggest that this is more of an operating system issue then syslog-ng. James ____________________________________________________________________________ __ 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