Solved How to get rid of this error?

Code:
 Creating and/or trimming log filesnewsyslog:error in config file;bad permissions

<<<<<< current version

.
Starting syslog
 
Code:
syslog:error in config file;bad permissions

<<<<<< current version

.
This seems like a merge leftover.

Do a test run of newsyslog(8): newsyslog -nv and search for errors.

Also check permissions of /etc/newsyslog.conf, files in /etc/newsyslog.conf.d/ and files in /usr/local/etc/newsyslog.conf.d/.
 
Code:
newsyslog -nv
Processing /etc/newsyslog.conf
newsyslog: error in config file; bad permissions:
<<<<<<< current version
this error began to appear after the upgrade 11.2 to 12.0
Code:
ls -la newsyslog.conf
-rw-r--r--  1 root  wheel  1886 Dec 29 10:09 newsyslog.conf

ls -la /etc/newsyslog.conf.d/
total 72
drwxr-xr-x   2 root  wheel   512 Dec 29 10:09 .
drwxr-xr-x  25 root  wheel  2560 Jan  2 12:21 ..
-rw-r--r--   1 root  wheel   146 Dec 29 10:09 amd.conf
-rw-r--r--   1 root  wheel   147 Dec 29 10:09 ftp.conf
-rw-r--r--   1 root  wheel   148 Dec 29 10:09 lpr.conf
-rw-r--r--   1 root  wheel   166 Dec 29 10:09 opensm.conf
-rw-r--r--   1 root  wheel   168 Dec 29 10:09 pf.conf
-rw-r--r--   1 root  wheel   158 Dec 29 10:09 ppp.conf
-rw-r--r--   1 root  wheel   154 Dec 29 10:09 sendmail.conf
 
Code:
ls -l /etc/newsyslog.conf
-rw-r--r--  1 root  wheel  1886 Dec 29 10:09 /etc/newsyslog.conf


cat /etc/newsyslog.conf
# configuration file for newsyslog
# $FreeBSD: releng/12.0/usr.sbin/newsyslog/newsyslog.conf 337686 2018-08-12 13:24:53Z brd $
#
# Entries which do not specify the '/pid_file' field will cause the
# syslogd process to be signalled when that log file is rotated.  This
# action is only appropriate for log files which are written to by the
# syslogd process (ie, files listed in /etc/syslog.conf).  If there
# is no process which needs to be signalled when a given log file is
# rotated, then the entry for that file should include the 'N' flag.
#
# Note: some sites will want to select more restrictive protections than the
# defaults.  In particular, it may be desirable to switch many of the 644
# entries to 640 or 600.  For example, some sites will consider the
# contents of maillog, messages, and lpd-errs to be confidential.  In the
# future, these defaults may change to more conservative ones.
#
# logfilename          [owner:group]    mode count size when  flags [/pid_file] [sig_num]
/var/log/all.log            600  7       *    @T00  J
/var/log/auth.log            600  7     1000 @0101T JC
/var/log/console.log            600  5       1000    *     J
/var/log/cron                600  3       1000    *     JC
/var/log/daily.log            640  7       *    @T00  JN
/var/log/debug.log            600  7     1000 *     JC
/var/log/init.log            644  3       1000    *     J
/var/log/kerberos.log            600  7       1000    *     J
/var/log/maillog            640  7       *    @T00  JC
/var/log/messages            644  5       1000    @0101T JC
/var/log/monthly.log            640  12       *    $M1D0 JN
/var/log/devd.log            644  3       1000    *     JC
/var/log/security            600  10       1000    *     JC
/var/log/utx.log            644  3       *    @01T05 B
/var/log/weekly.log            640  5       *    $W6D0 JN
<<<<<<< current version
/var/log/xferlog            600  7       100    *     JC
/var/log/mysql.log                      600  2     500  *     ZC
=======

>>>>>>> 12.0-RELEASE
<include> /etc/newsyslog.conf.d/*
<include> /usr/local/etc/newsyslog.conf.d/*
 
cat /etc/newsyslog.conf:
Code:
<<<<<<< current version
/var/log/xferlog            600  7       100    *     JC
/var/log/mysql.log                      600  2     500  *     ZC
=======

>>>>>>> 12.0-RELEASE
Seems like you were too quick to dismiss configuration file merge. I believe the right way to fix your problem is to
  1. make a backup of /etc/newsyslog.conf: cp /etc/newsyslog.conf /etc/newsyslog.conf.orig;
  2. edit /etc/newsyslog.conf to delete lines starting with <<<<<<<, ======= and >>>>>>>;
  3. move line /var/log/xferlog... to file /etc/newsyslog.conf.d/ftp;
  4. move line /var/log/mysql.log... to file /usr/local/etc/newsyslog.conf.d/mysql;
  5. retest your configuration with newsyslog -nv.
Omit steps 3 and 4 if you're in a hurry.
 
Code:
newsyslog -nv
Processing /etc/newsyslog.conf
Found: <include> /etc/newsyslog.conf.d/*
Found: <include> /usr/local/etc/newsyslog.conf.d/*
Processing /etc/newsyslog.conf.d/amd.conf
Processing /etc/newsyslog.conf.d/ftp.conf
Processing /etc/newsyslog.conf.d/lpr.conf
Processing /etc/newsyslog.conf.d/opensm.conf
Processing /etc/newsyslog.conf.d/pf.conf
Processing /etc/newsyslog.conf.d/ppp.conf
Processing /etc/newsyslog.conf.d/sendmail.conf
/var/log/all.log <7J>: does not exist, skipped.
/var/log/auth.log <7J>: --> will trim at Wed Jan  1 00:00:00 2020
/var/log/console.log <5J>: does not exist, skipped.
/var/log/cron <3J>: size (Kb): 31 [1000] --> skipping
/var/log/daily.log <7J>: does not exist, skipped.
/var/log/debug.log <7J>: size (Kb): 0 [1000] --> skipping
/var/log/init.log <3J>: does not exist, skipped.
/var/log/kerberos.log <7J>: does not exist, skipped.
/var/log/maillog <7J>: --> will trim at Fri Jan  4 00:00:00 2019
/var/log/messages <5J>: --> will trim at Wed Jan  1 00:00:00 2020
/var/log/monthly.log <12J>: does not exist, skipped.
/var/log/devd.log <3J>: size (Kb): 0 [1000] --> skipping
/var/log/security <10J>: size (Kb): 0 [1000] --> skipping
/var/log/utx.log <3>: --> will trim at Fri Feb  1 05:00:00 2019
/var/log/weekly.log <5J>: does not exist, skipped.
/var/log/xferlog <7J>: size (Kb): 0 [100] --> skipping
/var/log/mysql.log <2Z>: size (Kb): 0 [500] --> skipping
/var/log/amd.log <7J>: does not exist, skipped.
/var/log/xferlog <7J>: size (Kb): 0 [1000] --> skipping
/var/log/lpd-errs <7J>: size (Kb): 0 [1000] --> skipping
/var/log/opensm.log <7Z>: does not exist, skipped.
/var/log/pflog <3J>: does not exist, skipped.
/var/log/ppp.log <3J>: size (Kb): 0 [1000] --> skipping
/var/log/sendmail.st <10>: does not exist, skipped.

(steps 3 and 4 omits)
 
Back
Top