Skip to content

Common Networking Troubleshooting

@AlanOrlikoski edited this page Apr 16, 2018 · 10 revisions

Common Issues and Fixes

No IP Address Assigned (Networking Failed to Start)

Symptoms

Cannot access the web sites
ElasticSearch failed to start due to network issue  

Possible Problem and Solution

Interface name was changed by virtualization technology on import of the OVF. This is very common when using VirtualBox

To fix perform the following commands replace $new_interface:
Verify the network interface to NAT or Bridged

ifconfig -a # capture the name of the network interface to use  

Here is an example with the new interface name circled in red (in this case it's enp0s17)

new_int="`insert the correct interface here`" # must keep the double quotes
org_int=$(tail -3 /etc/network/interfaces /etc/network/interfaces |grep -v The |awk '{print $2}|sort|uniq)
sudo sed -i "s/$org_int/$new_int/g" /etc/network/interfaces
sudo service networking restart
ifconfig -a # confirm there is now an IP address on the new interface (in this case it's `enp0s17`)

You should now be able to open a local browser and connect to SSH, Kibana, and Cerebro via that address. If anything is not responding try rebooting the primary services: sudo systemctl restart elasticsearch timesketch kibana cerebro