syslog-ng 3.0.1-4 upgrade

kanon · 2009-03-10 21:38:54

I recently upgraded to syslog-ng 3.0.1-4 and now receive the following error:

[root@nsslog log]# /etc/rc.d/syslog-ng restart
:: Stopping Syslog-NG [FAIL]
:: Starting Syslog-NG [BUSY] Configuration file has no version number, assuming syslog-ng 2.1 format. Please add @version: maj.min to the beginning of the file;
WARNING: global: the default value of chain_hostnames is changing to 'no' in version 3.0, please update your configuration accordingly;
WARNING: input: sources do not remove new-line characters from messages by default in version 3.0, please add 'no-multi-line' flag to your configuration if you want to retain this functionality;
WARNING: template: the default value for template-escape is changing to 'no' in version 3.0, please update your configuration file accordingly;

Your configuration file uses an obsoleted keyword, please update your configuration; keyword='sync', change='flush_lines'
WARNING: file source: default value of follow_freq in file sources is changing in 3.0 to '1' for all files except /proc/kmsg;
syntax error in /etc/syslog-ng.conf at line 39.

Any ideas?

bender02 · 2009-03-10 21:41:46

Forgot to merge changes /etc/syslog-ng.conf.pacnew?

Allan · 2009-03-10 21:46:19

If you are using [testing] then you must subscript to the arch-dev-public mailing list. Otherwise, you will miss important discussion that occurs regarding packages in [testing].

Non-testing users will see

Attention syslog-ng update:
Configuration file syntax has changed. Make sure to update /etc/syslog-ng.conf

when they update.

brisbin33 · 2009-03-10 21:53:39

i use syslog-ng from testing, didn't touch syslog-ng.conf and can restart fine. am i just lucky?

i do get the dmesg warning about 32 bit capabilities that's been mentioned on the ML though.

here's my "stock" syslog-ng.conf if you want to copy it and see if you can restart then.

@version: 3.0
#
# /etc/syslog-ng.conf
#

options {
  stats_freq (0);
  flush_lines (0);
  time_reopen (10);
  log_fifo_size (1000);
  long_hostnames(off);
  use_dns (no);
  use_fqdn (no);
  create_dirs (no);
  keep_hostname (yes);
  perm(0640);
  group("log");
};

source src {
  unix-stream("/dev/log");
  internal();
  file("/proc/kmsg");
};

destination d_authlog { file("/var/log/auth.log"); };
destination d_syslog { file("/var/log/syslog.log"); };
destination d_cron { file("/var/log/crond.log"); };
destination d_daemon { file("/var/log/daemon.log"); };
destination d_kernel { file("/var/log/kernel.log"); };
destination d_lpr { file("/var/log/lpr.log"); };
destination d_user { file("/var/log/user.log"); };
destination d_uucp { file("/var/log/uucp.log"); };
destination d_mail { file("/var/log/mail.log"); };
destination d_news { file("/var/log/news.log"); };
destination d_ppp { file("/var/log/ppp.log"); };
destination d_debug { file("/var/log/debug.log"); };
destination d_messages { file("/var/log/messages.log"); };
destination d_errors { file("/var/log/errors.log"); };
destination d_everything { file("/var/log/everything.log"); };
destination d_iptables { file("/var/log/iptables.log"); };
destination d_acpid { file("/var/log/acpid.log"); };
destination d_console { usertty("root"); };

# Log everything to vc12
destination console_all { file("/dev/vc/12"); };

filter f_auth { facility(auth); };
filter f_authpriv { facility(auth, authpriv); };
filter f_syslog { program(syslog-ng); };
filter f_cron { facility(cron); };
filter f_daemon { facility(daemon); };
filter f_kernel { facility(kern) and not filter(f_iptables); };
filter f_lpr { facility(lpr); };
filter f_mail { facility(mail); };
filter f_news { facility(news); };
filter f_user { facility(user); };
filter f_uucp { facility(cron); };
filter f_news { facility(news); };
filter f_ppp { facility(local2); };
filter f_debug { not facility(auth, authpriv, news, mail); };
filter f_messages { level(info..warn) and not facility(auth, authpriv, mail, news, cron) and not program(syslog-ng) and not filter(f_iptables); };
filter f_everything { level(debug..emerg) and not facility(auth, authpriv); };
filter f_emergency { level(emerg); };
filter f_info { level(info); };
filter f_notice { level(notice); };
filter f_warn { level(warn); };
filter f_crit { level(crit); };
filter f_err { level(err); };
filter f_iptables { match("IN=" value("MESSAGE")) and match("OUT=" value("MESSAGE")); };
filter f_acpid { program("acpid"); };

log { source(src); filter(f_acpid); destination(d_acpid); };
log { source(src); filter(f_authpriv); destination(d_authlog); };
log { source(src); filter(f_syslog); destination(d_syslog); };
log { source(src); filter(f_cron); destination(d_cron); };
log { source(src); filter(f_daemon); destination(d_daemon); };
log { source(src); filter(f_kernel); destination(d_kernel); };
log { source(src); filter(f_lpr); destination(d_lpr); };
log { source(src); filter(f_mail); destination(d_mail); };
log { source(src); filter(f_news); destination(d_news); };
log { source(src); filter(f_ppp); destination(d_ppp); };
log { source(src); filter(f_user); destination(d_user); };
log { source(src); filter(f_uucp); destination(d_uucp); };
#log { source(src); filter(f_debug); destination(d_debug); };
log { source(src); filter(f_messages); destination(d_messages); };
log { source(src); filter(f_err); destination(d_errors); };
log { source(src); filter(f_emergency); destination(d_console); };
log { source(src); filter(f_everything); destination(d_everything); };
log { source(src); filter(f_iptables); destination(d_iptables); };

# Log everything to vc12
#log { source(src); destination(console_all); };

Last edited by brisbin33 (2009-03-10 21:54:17)

bender02 · 2009-03-10 22:41:08

brisbin33 wrote:

i use syslog-ng from testing, didn't touch syslog-ng.conf and can restart fine. am i just lucky?

Well that happens when you don't touch the original config file - pacman then just overwrites it with the new one, instead of creating ..conf.pacnew. (Happened to me as well.)

Last edited by bender02 (2009-03-10 22:41:42)

kanon · 2009-03-10 22:42:48

Thank you for the quick replies, i didn't even check the .pacnew file *blush* I did a quick merge and all is running correctly.

brisbin33 · 2009-03-11 13:34:12

bender02 wrote:

brisbin33 wrote:
i use syslog-ng from testing, didn't touch syslog-ng.conf and can restart fine. am i just lucky?
Well that happens when you don't touch the original config file - pacman then just overwrites it with the new one, instead of creating ..conf.pacnew. (Happened to me as well.)

ah yes, now i remember that section of man pacman. thanks for the clarification.

toxygen · 2009-03-11 13:45:52

speaking of syslog-ng 3.0.1-4 (now in base) -
- there was a warning after upgrade about checking /etc/syslog.conf.pacnew for changes
- man syslog, man syslog.conf no longer working (have to use man syslog-ng, man syslog-ng.conf)
- the one thing i had changed on my original /etc/syslog.conf was adding "stats (0);" to options, the new file had "stats_freq (0);". I ended up just overwriting the original with the pacnew, and added "stats (0);" which syslog-ng complained about. "man syslog-ng.conf" told me "stats (0);" was still a valid option though... i ended just removing "stats (0);" and leaving "stats_freq (0);" but the man page seems outdated or incorrect.

otherwise, it seems to be working well

Arch Linux

#1 2009-03-10 21:38:54

syslog-ng 3.0.1-4 upgrade

#2 2009-03-10 21:41:46

Re: syslog-ng 3.0.1-4 upgrade

#3 2009-03-10 21:46:19

Re: syslog-ng 3.0.1-4 upgrade

#4 2009-03-10 21:53:39

Re: syslog-ng 3.0.1-4 upgrade

#5 2009-03-10 22:41:08

Re: syslog-ng 3.0.1-4 upgrade

#6 2009-03-10 22:42:48

Re: syslog-ng 3.0.1-4 upgrade

#7 2009-03-11 13:34:12

Re: syslog-ng 3.0.1-4 upgrade

#8 2009-03-11 13:45:52

Re: syslog-ng 3.0.1-4 upgrade

Board footer