This info might help:
https://serverfault.com/questions/228140/lost-modified-etc-hosts-file-on-amazon-ec2-every-reboot-instance
--Jamie
-----Original Message-----
From: Christopher Schultz <ch...@christopherschultz.net>
Sent: Thursday, August 22, 2019 4:01 PM
To: solr-user@lucene.apache.org
Subject: Can't start Solr 7.7.1 due to name-resolution issue
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
All,
I'm getting a failure to start my Solr instance. Here's the error from the
console log:
Error: Exception thrown by the agent : java.net.MalformedURLException:
Local host name unknown: java.net.UnknownHostException: [hostname]:
[hostname]: Name or service not known
sun.management.AgentConfigurationError:
java.net.MalformedURLException: Local host name unknown:
java.net.UnknownHostException: [hostname]: [hostname]: Name or service not known
at
sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(C
onnectorBootstrap.java:480)
at sun.management.Agent.startAgent(Agent.java:262)
at sun.management.Agent.startAgent(Agent.java:452)
Caused by: java.net.MalformedURLException: Local host name unknown:
java.net.UnknownHostException: [hostname]: [hostname]: Name or service not known
at
javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:289)
at
javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:253)
at
sun.management.jmxremote.ConnectorBootstrap.exportMBeanServer(ConnectorB
ootstrap.java:739)
at
sun.management.jmxremote.ConnectorBootstrap.startRemoteConnectorServer(C
onnectorBootstrap.java:468)
... 2 more
Now, my hostname is just the first part of the hostname, so like "www"
instead of "www.example.com". Running "host [hostname]" on the CLI returns
"Host [hostname]" not found: 3(NXDOMAIN)" so it's not entirely surprising that
this name resolution is failing.
What's the best way for me to get around this?
I'm running on Debian Stretch in Amazon EC2. I've tried fixing the local name
resolution so that it actually works, but when I reboot, the EC2 instance
reverts my DNS settings so those changes won't survive a reboot.
Can I give the fully-qualified hostname to the JMX component in some way ?
I've this answer[1] on SO and everyone seems to say "edit /etc/hosts"
and, as I said, the EC2 startup scripts end up resetting those files during a
reboot.
Any ideas?
- -chris
[1]
https://stackoverflow.com/questions/20093854/jmx-agent-throws-java-net-m
alformedurlexception-when-host-name-is-set-to-all-num
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl1e9IQACgkQHPApP6U8
pFjG6g//XM6nPgioIuJs40gB9534GnsG9q8d42AUIoiDzJ+t8isFFxtphEChdcye
9/5ePo36fODIsNkzzXsAJh9L1iRgmnVy7QGQIDp07WEo9v2bVo2RkWl42zm+UQ5u
XIz//bpT+J9y3eBPdPCKaXou+UYeR9/2W/UYyN08/uayP2QVVd2ZavC6AbFW93i1
IF5vOmETOsxBgVlgngX4TQRNSKfe5gCqWT0l/diHpm7PjT2BDzNO7x3vRbfioOMS
ktXcRqdBJAzM9XLV1acI+0z7I1kzs/A+jCymT/4++VmI0Lf4AACIhoaqnmS9pxyY
nrXU8tttozbaHMiBS3dIIMZP1ZF4jzY0+/UPBfgXqM4OcErWTjrha4G/5oBlLqf8
msuVRTg6qbsQJP//UcDhN8kl593xCK/bcQMkzq1ABkwFUhb8PhXp/3IJCRjJm5q3
U3gTwMwA/k+R4aM8qGaLw+07aFCdVJKrIUW0NEEHEnwkjJxAeqIRdpV8acfrT6uy
3v78cVFvWaxcOtAyioUhek0jhKzCobcxsZEcxZqWWxY0DOFHWbip/agTJESC/sXV
wLY2P9lldo+S5dAoaGM7Ze1WJ5FOSLm6Juvl4CvyMeebyPFie4PrWX7b7ess8I+A
YwLyqfKQOV4qmWoiO7yNGcwfgIYNn3bJ/1b/vkmo+ua0KvjscYk=
=zeBa
-----END PGP SIGNATURE-----
