Hello; That did the trick. I can't thank you enough. Regards; John From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Scheidler, Balázs Sent: Friday, June 26, 2015 2:40 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] Migrating from syslog-ng v 3.2.5 to 3.6.4 Hi, Using the system() source instead of using unix-dgram() directly should solve this issue. The problem is that under systemd /dev/log is taken over by systemd, and it forwards messages to a different socket. The error is about this conflict as you use low-level primitives instead of the higher level system() source. I know that wasn't available in old times, but its preferred now. On Jun 25, 2015 3:11 PM, "Tech Support" <support@voipbusiness.us> wrote: All; I am currently migrating a CentOS 6.6 server running syslog-ng 3.2.5 to a CentOS 7.1 system running syslog-ng 3.6.4. I’m trying to use the same configuration file, but I’m getting the following message: /usr/sbin/syslog-ng -v -s -f /etc/syslog-ng/syslog-ng.conf [2015-06-25T09:05:16.796854] Using /dev/log Unix socket with systemd is not possible. Changing to systemd-syslog source, which supports socket activation.; I know one problem is that I’m just not up to speed yet with systemd, but I was hoping that someone could shed some light on this error. Any help at all would be greatly appreciated. Thanks; John V. Tech Support Tech Support VoIP Business Solutions 240-215-3479 x325 support@voipbusiness.us <mailto:fsd@voipbusiness.us> ______________________________________________________________________________ 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