Description of problem: Connecting to /dev/log, at least via Python/Python3 results in a ConnectionRefusedError This prevents Anaconda from running, and thus I'll be nominating this bug as a blocker bug. An easy way to reproduce is to run the following two lines in the python interpreter: import logging.handlers handler = logging.handlers.SysLogHandler(address = '/dev/log') The permissions on /run/systemd/journal/dev-log are srw-rw-rw-. Version-Release number of selected component (if applicable): systemd 231-1.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Boot system 2. Open terminal 3. Run python or python3 4. Type in the previously mentioned code Actual results: /dev/log is not writable Expected results: /dev/log is writable Additional info: Nominating as a blocker bug as this clearly prevents installation.
Proposed as a Blocker for 25-alpha by Fedora user jdulaney using the blocker tracking app because: The installer must run when launched normally from the release-blocking images.
Also attempted this with enforcing set to permissive, with the same result.
ConnectionRefused is thrown when the socket has been closed by the listener. For example, if systemd-journald was stopped, then this result would be expected. But normally journald is immediately restarted, even if it stops. So something special must be going on here... In what situation did you see the error? Running from the installation dvd, or from an installed system? Can you attach the logs?
LiveCD booted in a vm, will attach logs shortly.
Which CD image?
Okay, I see nothing interesting in the logs. This is with the XFCE image. I'm going to try to reproduce with a newer image.
I just tried this in both a BIOS KVM and a UEFI KVM with Fedora-Workstation-Live-x86_64-25-20160805.n.0.iso and could not reproduce it. anaconda launches fine and the given python code runs without error.
Discussed during the 2016-08-08 blocker review meeting: [1] The decision was made to delay the classification of this as a bug, as no one in the blocker-review meeting had experienced the bug and as such, more information and testing are required before this can be appropriately classified. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-08-08/f25-blocker-review.2016-08-08-16.01.txt
The reproducer from #c0 works fine with Fedora-Xfce-Live-i386-25-20160809.n.0.iso. I think it must have been just a bleep on the radar, please reopen if you can reproduce.
Yeah, I cannot reproduce with new images.