Lost log file

sudo newsyslog -CC
Password:
newsyslog: error in config file; bad permissions:
<<<<<<< current version

newsyslog: missing field in config file:
=======
 
you have a botched update merge
find /etc -type f |xargs grep -l =====
then inspect the listed files for sequences
like
>>>>>> freebsd old version
foo
bar baz
=========
bar baz
foo3
<<<<<<< current version
and fix them by keeping just one of the fragment between ===== and >>>> or <<<<
also delete the <<<< >>>> ===== containing lines
 
sudo find /etc -type f |xargs grep -l =====
Password:
grep: /etc/ppp/ppp.conf: Permission denied
grep: /etc/opieaccess: Permission denied
grep: /etc/ssh/ssh_host_key: Permission denied
grep: /etc/ssh/ssh_host_rsa_key: Permission denied
grep: /etc/ssh/ssh_host_dsa_key: Permission denied
grep: /etc/ssh/ssh_host_ecdsa_key: Permission denied
grep: /etc/ssh/ssh_host_ed25519_key: Permission denied
grep: /etc/ssl/private/dovecot.pem: Permission denied
grep: /etc/defaults/devfs.rules: Permission denied
grep: /etc/spwd.db: Permission denied
grep: /etc/snmpd.config: Permission denied
/etc/mail/mailer.conf
grep: /etc/mail/aliases.db: Permission denied
grep: /etc/mail/certs/host.key: Permission denied
/etc/newsyslog.conf
/etc/newsyslog.conf.orig
/etc/services
grep: /etc/security/audit_user: Permission denied
grep: /etc/security/audit_control: Permission denied
grep: /etc/security/audit_warn: Permission denied
grep: /etc/nsmb.conf: Permission denied
grep: /etc/ntp/leap-seconds: Permission denied
grep: /etc/bluetooth/hcsecd.conf: Permission denied
grep: /etc/master.passwd: Permission denied
grep: /etc/opiekeys: Permission denied
grep: /etc/pw.WqSqQs: Permission denied
There are a lot of them. And why should I do this and not the developer, It's kind of a bug
 
do it as root or
sudo find /etc -type f |sudo xargs grep -l =====
/etc/mail/mailer.conf
/etc/newsyslog.conf
/etc/newsyslog.conf.orig
seem to be problematic
 
kerogaz said:
And why should I do this and not the developer, It's kind of a bug
Click to expand...
when you update configuration files are merged
when the automatic process can't decide what to keep and what to change it creates a file with >>>===<<< sequence in it which you are supposed to fix manually
 
I noticed that these listed files are neither root nor sudo accessible. Maybe this is the problem.To be honest, I have never seen anything like this in any Unix-like system, neither in Arch, nor in Red Hat, nor in Debian.
 
id && head /etc/ppp/ppp.conf
uid=0(root) gid=0(wheel) groups=0(wheel),5(operator)
#################################################################
# PPP Sample Configuration File
# Originally written by Toshiharu OHNO
# Simplified 5/14/1999 by wself@cdrom.com
#
# See /usr/share/examples/ppp/ for some examples
#
# $FreeBSD$
#################################################################
 
so it reads it, you should be able to run the initial find | xargs command as root and get the list of problematic merged files
 
Thank you. I'd rather wait for the next update. And if I manually create the missing log file, will it work?Because on the example of a red hat, files created in this way do not always work
 
you have to fix the config files
otherwise different services like newsyslog wont run
this is not complicated at all
 
kerogaz said:
There are a lot of them. And why should I do this and not the developer, It's kind of a bug
Click to expand...
You had merge conflicts in config files on upgrade. This is definitely not a bug. There will be messages about it, telling you to resolve them. Seems you missed this.
kerogaz said:
I'd rather wait for the next update.
Click to expand...
This certainly won't help. Merge conflicts happen when a change in the default config (from FreeBSD) conflicts with a change you did locally. You have to solve these conflicts.
 
As mentioned, you need to do something about it. There are probably more problems than you've noticed so far. It may be helpful that you can find default versions of these files under /usr/src.
An example:
find / -name opieaccess
/etc/opieaccess
/var/db/etcupdate/current/etc/opieaccess
/usr/src/lib/libopie/opieaccess
 
Can this link help?
serverfault.com

syslogd no such file or directory - OpenBSD 3.9

OK - long story short: I have OpenBSD box that was setup as a network appliance (long time ago) I have returned to life. Several errors I am working on and could use any help I can get. Errors on s...
serverfault.com serverfault.com

""have you tried by reinstalling the package, like i have faced same issue in ubuntu 12.04, in which suddenly default logs are unavailable and i solved by installing syslog again.""
 
No, fix those merge errors in the configuration files, as has been suggested multiple times already. You could have solved the entire issue by now.
 
zirias@ said:
You had merge conflicts in config files on upgrade. This is definitely not a bug. There will be messages about it, telling you to resolve them. Seems you missed this.

This certainly won't help. Merge conflicts happen when a change in the default config (from FreeBSD) conflicts with a change you did locally. You have to solve these conflicts.
Click to expand...
I consistently upgrade from 10.0 to 13.1 on this computer and never had conflicts with the local config. Then why only now did it arise, when updating 13.1 from p4 to p5?
 
You must log in or register to reply here.
Back
Top