After upgrade to 23.05 RELEASE, Syslog-NG won't start
-
@provels Good finding. I will create a redmine on the issue to see if there is a developer that can upstream a fix. I have no idea who maintains this package.
-
@keyser Cool. But even after the edit, it will quit after a while. Dunno, I'm just a shoemaker.
-
I was just looking for showstoppers on 23.05 for me. Looks like you found the only one for most of our boxes. Thanks for the post.
-
Thanks for posting here. I simply removed the package because I could not figure out "expecting LL_EOL". I plan to reinstall hoping that since the .conf is auto generated that it might work correctly. Maybe I'll wait awhile longer to see what other posts are made.
-
Getting a little annoyed this isn't getting more high priority love from Netgate. We get told pfsense has limitations on log viewing because it's a firewall and to send logs elsewhere. The native syslog only supports UDP and remote logging basically requires TCP/SSL. So syslog-ng is a must. We upgraded a dozen boxes, but anything of any importance is stuck on 23.01 because of this. We need @jimp or someone from Netgate in this thread.
-
@Cylosoft I know Jim is going to ask for a Redmine to be open if it hasnt been already so get that ready.
-
-
@Cylosoft Yeah would be good to have it fixed soon. I too have a lot of boxes i cannot upgrade because I need secure TCP syslog collection from those boxes (and the other networking devices on the same site that forwards to SYSLOG-NG)
-
-
@keyser said in After upgrade to 23.05 RELEASE, Syslog-NG won't start:
Yeah would be good to have it fixed soon.
Both of the Redmine links are showing this fixed. Looks to me like it's avail in packages.
-
Thanks @jimp !!! I upgraded a couple of boxes and the syslog-ng 1.16 you just released is working great. Much appreciated.
-
-
@jimp Yes, great work as always. All it takes is another one of us mooks to run your code and it's, "Oh, yeah, that..."!
