Unable to determine node name

Chef Infra (archive)
1

Hi,

We’re running chef version 12.11.18 on our amazon opsworks instances and getting the following error when converging recipes,

[2016-09-09T01:18:48+00:00] INFO: Forking chef instance to converge…
[2016-09-09T01:18:48+00:00] INFO: *** Chef 12.11.18 ***
[2016-09-09T01:18:48+00:00] INFO: Platform: x86_64-linux
[2016-09-09T01:18:48+00:00] INFO: Chef-client pid: 12235
[2016-09-09T01:18:49+00:00] WARN: unable to detect ipaddress
[2016-09-09T01:18:49+00:00] ERROR: Running exception handlers
[2016-09-09T01:18:49+00:00] ERROR: Exception handlers complete
[2016-09-09T01:18:49+00:00] FATAL: Stacktrace dumped to /var/chef/runs/7c706854-be17-4d21-9c78-e9fc910e96ee/local-mode-cache/cache/chef-stacktrace.out
[2016-09-09T01:18:49+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2016-09-09T01:18:49+00:00] ERROR: Unable to determine node name: configure node_name or configure the system’s hostname and fqdn
[2016-09-09T01:18:50+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

Wondering if anyone has seen this and what we might look for. Some relevant info -

hostnamectl
Static hostname: ******-dev-combined3
Icon name: computer-vm
Chassis: vm
Boot ID: eecc81d816e047fdb55130ec72b73049
Virtualization: xen
Operating System: Ubuntu 14.04.5 LTS
Kernel: Linux 3.13.0-95-generic
Architecture: x86_64

dpkg -l | grep -ie

ii chef 12.11.18-1 amd64 The full stack of chef

2

The contents of the stack track might help as well.

Nathan Clemons
DevOps Engineer
Moxie Cloud Services (MCS)

O +1.425.467.5075
M +1.360.861.6291
E nclemons@gomoxie.com
W www.gomoxie.comhttp://www.gomoxie.com/

3

I suspect the key is in the “unable to detect ipaddress”. It looks like your instance for some reason doesn’t have networking configured, or the configuration readable. Are you running chef as user root? What do you get when you run “ip address show” or ifconfig manually?

Kevin Keane
Whom the IT Pros Call
The NetTech
http://www.4nettech.com
Our values: Privacy, Liberty, Justice
See https://www.4nettech.com/corp/the-nettech-values.html

4

this can get weird on AWS. But if this is on a VPC check your VPC “DNS resolution” options… again this gets funky behavior node.name fails without this for example

Maybe shot in dark but I know i had issues when coding stuff with chef-provisioning when i realized the default was to not use dns resolution … check it out?
-Geo

5

I recently started using the built-in Mail app for Windows 10 - a surprisingly good mail client.

But whenever I try to respond to this mailing list (and only here), the mailing list responds with an error. The exact text of the message is:

We're sorry, but your email message to ["chef@discoursemail.com"] (titled RE: [chef] Unable to determine node name) didn't work.

None of the destination email addresses are recognized. Please make sure that you are sending to the correct email address provided by staff.

Is there something non-standard about either Discourse emails, Windows 10 Mail, or both?

Kevin Keane
Whom the IT Pros Call
The NetTech
http://www.4nettech.com
Our values: Privacy, Liberty, Justice
See https://www.4nettech.com/corp/the-nettech-values.html

6

Thanks all for the replies, one issue I found was high memory usage, which we believe is caused by something unrelated. restarted the node and the node name / fqdn issues have disappeared for now.