Red Hat Bugzilla – Bug 735618
/dev/stderr: no such device
Last modified: 2014-03-16 23:28:43 EDT
Description of problem: After started network service appears error in /var/log/messages: network: /etc/init.d/functions: line 58: /dev/stderr: No such device Version-Release number of selected component (if applicable): initscripts-9.31-3.fc16.i686 How reproducible: Every time. Steps to Reproduce: 1. Configure network with system-config-network 2. Disable NetworkManager and enable network service 3. Restart system Actual results: Error messages in /var/log/messages Expected results: No error messages.
At least this errors appears for me on minimal system installation. But network works fine after network service started.
*** Bug 735831 has been marked as a duplicate of this bug. ***
*** Bug 735832 has been marked as a duplicate of this bug. ***
This error comes from the sshd-keygen service, which tries to generate host keys for sshd. So with it failing, you don't have any host keys for sshd on a fresh install. That service should be set to run after whatever brings up /dev/stderr . After=udev-settle.service ?
cc mathieu, who did the systemd migration.
I don't see any indication that this error has any real implications. The ssh keys are generated correctly here anyway. The sysv library just fails to set the CONSOLETYPE environment variable and emits a warning that gets syslogged - that's all. I doubt anything depends on this variable - especially in this case. Bash fails because systemd has connected stderr to a syslog socket which have permissions for being readable but isn't. Bash will thus fail when it try to execute the "consoletype < /dev/stderr". It is bash that is failing, so there is no simple "2> /dev/null" "solution". I suggest dropping the special handling for setting CONSOLETYPE based on stderr: --- /etc/rc.d/init.d/functions 2011-09-18 01:04:14.303397362 +0200 +++ /etc/rc.d/init.d/functions 2011-09-18 01:06:53.663975555 +0200 @@ -54,11 +54,7 @@ [ -z "${COLUMNS:-}" ] && COLUMNS=80 if [ -z "${CONSOLETYPE:-}" ]; then - if [ -r "/dev/stderr" ]; then - CONSOLETYPE="$(/sbin/consoletype < /dev/stderr 2>/dev/null)" - else CONSOLETYPE="$(/sbin/consoletype 2>/dev/null)" - fi fi Alternatively it could be considered a systemd bug that a syslog socket isn't readable. It would however be strange if it was.
okay, back to initscripts, then. (the error does have at least one implication: the sshd-keygen service shows up as failed).
*** Bug 739560 has been marked as a duplicate of this bug. ***
http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=09bfb5033230e6846414bc6002aa12ce09c23687
initscripts-9.32-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/initscripts-9.32-2.fc16
Package initscripts-9.32-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initscripts-9.32-2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/initscripts-9.32-2.fc16 then log in and leave karma (feedback).
initscripts-9.32-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 744461 has been marked as a duplicate of this bug. ***