Lost log file

Results archived in the past are not a guarantee for the future. Merge issues can happen, you just need to deal with them. And these issues probably happened earlier, you just didn't notice them.
 
kerogaz said:
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?
Click to expand...
I think it happened earlier and you just didn't notice, patch levels are very unlikely to change any configuration files.

But in general, because this specific update when it happened finally changed some lines in config files you also changed previously.
 
I manually created the daemon.log file. Rebooted the system. The previous error has disappeared. Now a new one has appeared
Code: 
Creating and/or trimming log filesnewsyslog:error in config file; bad permissons:
<<<<<<<current version
newsyslog: missing field in config file:
=======
 
Those are the conflict markers <<<<<<<, ======= and >>>>>>>). They are not supposed to be in the config files at all. They separate the parts that YOU changed versus the parts that were changed by the update and it's your job to find a sane way of merging these changes (and then remove all the conflict markers).
 
kerogaz said:
So what exactly should I fix then?
Click to expand...
I have had the same behaviour as you, but during a former update. Please check the difference between the old entries and the new ones. Normally it is sane to delete the old sections including the markers. And just in case - you can keep the current situation until everything works fine by tar the /etc/ directory.
 
That's why i always do a fresh new install. Even when updating to a new minor version.

But seriously, an update to just another patch level should not have such issues.
 
chrbr said:
I have had the same behaviour as you, but during a former update. Please check the difference between the old entries and the new ones. Normally it is sane to delete the old sections including the markers. And just in case - you can keep the current situation until everything works fine by tar the /etc/ directory.
Click to expand...
Maybe this error appeared for me as well as for you in an earlier update, I just paid attention to it only in p5
 
I'd rather wait for the next update, maybe this bug will disappear, although the developer claims that this is not a bug, but this is already an area of casuistry. "A software bug is an error, flaw or fault in the design, development, or operation of computer software that causes it to produce an incorrect or unexpected result, or to behave in unintended ways."
 
richardtoohey2 said:
The point is that the next update will not magically unmangle your files.

So there will be no change until you manually fix them.

Waiting will not change that.
Click to expand...
And I have not changed anything in my config files since 2015, this update changed them, letting the developers correct if something means to them the prestige of the system.I noticed that with each new release the system becomes more complicated and somewhat worse. I don't know what the reason for such an incident.
Therefore, you probably do not need to remove the support of old but reliable releases. The system should be for the user and not for himself. It turns out as soon as you removed all the bugs from the system the following release with new bugs appears. Is it possible to preserve one systems for 10 years as it was on CentOS?I worked with Centos 6 without problems for 10 years until Red Hat took her to his hands finally and the terms of support were cut. Freebsd turned out to have become like Linux Rolling Release as ArchLinux
 
You must log in or register to reply here.
Back
Top