Description of problem: I have installed Fedora 26 Beta using kickstart. After installation, I found many error messages like this 02:08:44,946 INFO rsyslogd: [origin software="rsyslogd" swVersion="8.26.0" x-pid="1507" x-info="http://www.rsyslog.com"] start 02:08:44,946 ERR rsyslogd:file '/tmp/X.log': open error: No such file or directory [v8.26.0 try http://www.rsyslog.com/e/2040 ] 02:08:44,949 ERR rsyslogd:file '/tmp/anaconda-tb-all.log': open error: No such file or directory [v8.26.0 try http://www.rsyslog.com/e/2040 ] This two messages are repeated very often 02:08:54,954 ERR rsyslogd:file '/tmp/X.log': open error: No such file or directory [v8.26.0 try http://www.rsyslog.com/e/2040 ] 02:08:54,954 ERR rsyslogd:file '/tmp/anaconda-tb-all.log': open error: No such file or directory [v8.26.0 try http://www.rsyslog.com/e/2040 ] # grep /tmp/anaconda-tb-all.log /var/log/anaconda/syslog|wc 361 5415 51262 Version-Release number of selected component (if applicable): Fedora 26 Beta x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 26 Beta x86_64 (using kickstart)
Fedora 26 is already released. So is it still a problem?
(In reply to Marek Tamaskovic from comment #1) > Fedora 26 is already released. So is it still a problem? Kickstart installation seems to work on Fedora 26, but there are still some errors logged. I don't know if they are a problem, or can be ignored? I have done an installation yesterday. /tmp/anaconda-tb-all.log is only found once: # grep /tmp/anaconda-tb-all.log /var/log/anaconda/syslog 09:58:25,848 ERR rsyslogd:file '/tmp/anaconda-tb-all.log': open error: No such file or directory [v8.27.0 try http://www.rsyslog.com/e/2040 ] I attach the output of two other greps.
Created attachment 1328997 [details] Output of "grep 'No such file or directory' /var/log/anaconda/syslog"
Created attachment 1328998 [details] Output of: "grep -i error /var/log/anaconda/syslog"
Please send a config
Insufficient data
removing stale needinfo
Created attachment 1412103 [details] Kickstart file used for Fedora 27 at 2018-03-19 Oh, sorry! I see this error still on a Fedora 27 installation done 2018-03-19: # grep anaconda-tb-all.log /var/log/anaconda/* /var/log/anaconda/journal.log:Mar 19 18:39:31 localhost rsyslogd[1642]: file '/tmp/anaconda-tb-all.log': open error: No such file or directory [v8.29.0 try http://www.rsyslog.com/e/2040 ] /var/log/anaconda/syslog:18:39:31,272 ERR rsyslogd:file '/tmp/anaconda-tb-all.log': open error: No such file or directory [v8.29.0 try http://www.rsyslog.com/e/2040 ]
Can you please share your rsyslog config file?
Created attachment 1412105 [details] /etc/rsyslog.conf It is the original file, I didn't change it.
Do you have any additional files present in /etc/rsyslog.d/*.conf ? Can you share few messages before and after the error you referenced?
Created attachment 1412109 [details] /var/log/anaconda/syslog Attached /var/log/anaconda/syslog, with domain names and ip addresses replaced. Do you need /var/log/anaconda/journal.log too?
There should be some additional config files, by default rsyslog pulls in everything matching /etc/rsyslog.d/*.conf In log you shared there is warning about "~" action which is not present in default fedora config same as rsyslog trying to read "/tmp/X.log" and "/tmp/anaconda-tb-all.log" files.
(In reply to Jiří Vymazal from comment #13) > There should be some additional config files, by default rsyslog pulls in > everything matching /etc/rsyslog.d/*.conf /etc/rsyslog.d/ on the installed host is empty. # ll -r /etc/rsyslog.* -rw-r--r--. 1 root root 3168 12. Jan 15:02 /etc/rsyslog.conf /etc/rsyslog.d: insgesamt 0 But I think that during the anaconda installation there will be used the config files on the initial ram disk from the installation image? I use vmlinuz and initrd.img from Fedora 27 netinst image Fedora-Everything-netinst-x86_64-27-1.6.iso for pxeboot, and Fedora 27 server dvd image Fedora-Server-dvd-x86_64-27-1.6.iso extracted to a file system as nfs repo for installation (see kickstart file). > In log you shared there is warning about "~" action which is not present in > default fedora config same as rsyslog trying to read "/tmp/X.log" and > "/tmp/anaconda-tb-all.log" files. I have booted the Fedora 27 server dvd to rescue mode and copied file /etc/rsyslog.conf . I will attach it. This file differs from the file on the installed host. It contains a line $ grep \~ f27-server-dvd-rsyslog.conf :programname,isequal,"dracut" ~
Created attachment 1412166 [details] /etc/rsyslog.conf from Fedora 27 Server DVD in rescue mode
Ok, the config you posted contains also the lines causing the original error, I am re-targeting this against distribution as we do not own the config on dvd image. Solution for whoever will be fixing this is to remove lines 27-33 or just use the config we provide in rsyslog package.
Moving to anaconda as they configure things in the install env.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
On a new installed Fedora 29 system I still get errors from syslog. Fedora 29 installation images still contains the old (wrong) file rsyslog.conf. # grep rsyslog /var/log/anaconda/syslog|grep ERR 14:30:49,437 ERR rsyslogd:imfile: on startup file '/tmp/X.log' does not exist but is configured in static file monitor - this may indicate a misconfiguration. If the file appears at a later time, it will automatically be processed. Reason: No such file or directory [v8.37.0] 14:30:49,437 ERR rsyslogd:imfile: on startup file '/tmp/anaconda-tb-all.log' does not exist but is configured in static file monitor - this may indicate a misconfiguration. If the file appears at a later time, it will automatically be processed. Reason: No such file or directory [v8.37.0] 14:30:23,016 ERR rsyslogd:imjournal: sd_journal_get_cursor() failed: Cannot assign requested address [v8.37.0] 14:30:42,004 ERR rsyslogd:imjournal: sd_journal_get_cursor() failed: Cannot assign requested address [v8.37.0]
The file rsyslog.conf is provided by lorax. Reassigning.
(In reply to Edgar Hoch from comment #19) > On a new installed Fedora 29 system I still get errors from syslog. Fedora > 29 installation images still contains the old (wrong) file rsyslog.conf. > > # grep rsyslog /var/log/anaconda/syslog|grep ERR > 14:30:49,437 ERR rsyslogd:imfile: on startup file '/tmp/X.log' does not > exist but is configured in static file monitor - this may indicate a > misconfiguration. If the file appears at a later time, it will automatically > be processed. Reason: No such file or directory [v8.37.0] > 14:30:49,437 ERR rsyslogd:imfile: on startup file '/tmp/anaconda-tb-all.log' > does not exist but is configured in static file monitor - this may indicate > a misconfiguration. If the file appears at a later time, it will > automatically be processed. Reason: No such file or directory [v8.37.0] > 14:30:23,016 ERR rsyslogd:imjournal: sd_journal_get_cursor() failed: Cannot > assign requested address [v8.37.0] > 14:30:42,004 ERR rsyslogd:imjournal: sd_journal_get_cursor() failed: Cannot > assign requested address [v8.37.0] Those are from the installation, not from the running system. /var/log/anaconda is a copy of the logs created during the install. The reason these errors show up (really they should be warnings) is that when the image boots most of those logs haven't been created because anaconda isn't running yet. Note that it says "If the file appears at a later time, it will automatically be processed." Anaconda uses rsyslog to combine logs and output them on tty4, as well as log them to a remote system if configured to do so. So you can safely ignore these.