Hi All,

After rebooting a ubuntu 14.04 droplet earlier after an issue, the networking fails to come up.

I manually restored the network through the console:

ipconfig eth0 up
ifconfig eth0 x.x.x.x/x
ip ro add default via x.x.x.x

Zentyal fails to come up, and after a reboot the network stays down.

cat /var/log/boot.log

Cloud-init v. 0.7.5 running ‘init’ at Fri, 21 Jun 2019 12:56:26 +0000. Up 3.92 seconds.
ci-info: +++++++++++++++++++++++Net device info++++++++++++++++++++++++
ci-info: +——–+——-+———–+———–+——————-+
ci-info: | Device | Up | Address | Mask | Hw-Address |
ci-info: +——–+——-+———–+———–+——————-+
ci-info: | lo | True | | | . |
ci-info: | eth0 | False | . | . | 04:01:4b:34:6d:01 |
ci-info: +——–+——-+———–+———–+——————-+
ci-info: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Route info failed!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2019-06-21 14:56:31,697 - util.py[WARNING]: Getting data from <class 'cloudinit.sources.DataSourceDigitalOcean.DataSourceDigitalOcean’> failed
No 'init’ modules to run under section 'cloudinitmodules’

Anybody experienced this problem ? Have not been able to bring the machine back online properly.

1 comment
  • Managed to get zentyal up manually starting modules. If machine reboots I am sure it will loose its network settings until the above cloud init error is resolved.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

I believe this is directly an issue with Zentyal which hasn’t been fixed yet. I’ve seen a lot of reports about it.

Can you let me know how did you went about starting modules and which version of Zentyal are you using?