Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install fails on Ubuntu 20.04.1 LTS #65

Open
TibboddiT opened this issue Nov 10, 2020 · 1 comment
Open

Install fails on Ubuntu 20.04.1 LTS #65

TibboddiT opened this issue Nov 10, 2020 · 1 comment

Comments

@TibboddiT
Copy link

Hello,

Installation fails on Ubuntu 20.04.1 LTS, on a server with only one network interface :

### Checks & detection
Checking augeas is installed  SKIP will try to install
Checking curl is installed  SKIP will try to install
Checking bridge-utils are installed  SKIP will try to install
Checking apt-transport-https is installed  SKIP will try to install
Checking AppArmor  SKIP will try to modify
Checking for present ssh key  SKIP
Checking (iptables|netfilter)-persistent are installed  SKIP will try to install

### Main deployment steps:
Install OpenNebula frontend version 5.12
Configure bridge minionebr with IP 172.16.100.1/24
Enable NAT over eno1
Modify AppArmor
Install OpenNebula KVM node
Export appliance and update VM template
Install  augeas-tools curl bridge-utils apt-transport-https iptables-persistent netfilter-persistent

Do you agree? [yes/no]:
yes

### Installation
Updating APT cache  OK
Install  augeas-tools curl bridge-utils apt-transport-https iptables-persistent netfilter-persistent  OK
Creating bridge interface minionebr  OK
Bring bridge interfaces up  OK
Enabling IPv4 forward  OK
Persisting IPv4 forward  OK
Configuring NAT using iptables  OK
Saving iptables changes  OK
Installing DNSMasq  OK
Starting DNSMasq  FAILED

--- STDERR ---
Job for dnsmasq.service failed because the control process exited with error code.
See "systemctl status dnsmasq.service" and "journalctl -xe" for details.

Ouput of systemctl status dnsmasq.service:

Nov 10 18:52:07 my-host systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
Nov 10 18:52:07 my-host dnsmasq[2314]: dnsmasq: syntax check OK.
Nov 10 18:52:07 my-host dnsmasq[2315]: dnsmasq: failed to create listening socket for 127.0.0.1: Address already in use
Nov 10 18:52:07 my-host dnsmasq[2315]: failed to create listening socket for 127.0.0.1: Address already in use
Nov 10 18:52:07 my-host dnsmasq[2315]: FAILED to start up
Nov 10 18:52:07 my-host systemd[1]: dnsmasq.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Nov 10 18:52:07 my-host systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Nov 10 18:52:07 my-host systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

It seems that dnsmasq can't bind to port 53 because it is already in use by named/bind9.
Do you have a solution that does not require to uninstall bind9 ?

@TibboddiT
Copy link
Author

I managed to solve the issue:

  • remove installation / configuration / launch of dnsmasq from the minione script
  • add the gateway to named options file /etc/bind/named.conf.options (for in guest names resolution):
...
listen-on { 127.0.0.1; 172.16.100.1; };
...

I'm curious to know why this isn't the standard procedure on Ubuntu servers, instead of using dnsmasq ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant