sytemd-hostnamed service is failing in coreos-1520.6.0

56 views
Skip to first unread message

je...@srcclr.com

unread,
Oct 13, 2017, 2:28:43 AM10/13/17
to CoreOS Dev
I was trying set the hostname using hostnamectl but it threw following error.

"ip-10-1-1-154 jeeva # hostnamectl set-hostname k8s-worker-1507708889.ops1.srcclr.com
Could not set property: Failed to activate service 'org.freedesktop.hostname1': timed out"

systemd-hostname.service also failed.

logs --
"ct 13 04:24:14 ip-10-1-1-154.us-west-2.compute.internal systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=226/NAMESPACE
Oct 13 04:24:14 ip-10-1-1-154.us-west-2.compute.internal systemd[1]: Failed to start Hostname Service.
Oct 13 04:24:14 ip-10-1-1-154.us-west-2.compute.internal systemd[1]: systemd-hostnamed.service: Unit entered failed state."


All the systemd files are updated on Oct12th.  Our application depends on the hostname and at the moment I could revert the AWS issued hostname with ours

OS - coreos-1520.6.0
systemd - 234

je...@srcclr.com

unread,
Oct 13, 2017, 2:43:12 AM10/13/17
to CoreOS Dev
Reply all
Reply to author
Forward
0 new messages