Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 616981 - Failure to boot if HOSTNAME not set
Failure to boot if HOSTNAME not set
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-21 17:01 EDT by Eric Paris
Modified: 2010-07-21 20:28 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-21 20:28:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Eric Paris 2010-07-21 17:01:55 EDT
I do not set HOSTNAME= in /etc/sysconfig/network and the system picks up my hostname from a reverse dns entry eventually.  With systemd however it just refuses to boot:

systemd[1]: Set hostname to <�V�.
type=1701 audit(1279744659.081:5): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:init_t:s0 pid=1388 comm="systemd" sig=6
systemd[1]: Caught <ABRT>, core dump failed.
systemd[1]: Freezing execution.

I added HOSTNAME=localhost.localdomain and it now boots.
Comment 1 Lennart Poettering 2010-07-21 20:28:50 EDT
Thanks, fixed upstream. Will be fixed in the next I upload which I am currently preparing.

Note You need to log in before you can comment on or make changes to this bug.