Couldn't install isc-dhcp-server on Ubuntu Server 18.04
up vote
0
down vote
favorite
I tried to install DHCP server on my Ubuntu Server 18.04, but it failed.
sudo apt install isc-dhcp-server
The following messages were shown after the trial:
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
As you may assume, I've already set a static IP address on 50-cloud-init.yaml file.
My settings are as follows:
This file is generated from information provided by
the datasource. Changes to it will not persist across an instance.
To disable cloud-init's network configuration capabilities, write a file
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
network: {config: disabled}
network:
ethernets:
enp0s3:
addresses: [192.168.0.101/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
dhcp4: no
version: 2
And of course, I made the above changes take effect by running the following command:
sudo netplan apply
SI there any solution you can provide?
Please advise!
server 18.04
asked Nov 26 at 12:35
John2
11
add a comment |
up vote
0
down vote
favorite
I tried to install DHCP server on my Ubuntu Server 18.04, but it failed.
sudo apt install isc-dhcp-server
The following messages were shown after the trial:
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
As you may assume, I've already set a static IP address on 50-cloud-init.yaml file.
My settings are as follows:
This file is generated from information provided by
the datasource. Changes to it will not persist across an instance.
To disable cloud-init's network configuration capabilities, write a file
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
network: {config: disabled}
network:
ethernets:
enp0s3:
addresses: [192.168.0.101/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
dhcp4: no
version: 2
And of course, I made the above changes take effect by running the following command:
sudo netplan apply
SI there any solution you can provide?
Please advise!
server 18.04
asked Nov 26 at 12:35
John2
11
The warning you get has nothing to do with your network configuration. It just says that you are trying to install two packages at the same time, or you have one package manager open while doingaptin a terminal. If closing open package managers doesn't help, you can always remove the lock file the hard way withsudo rm /var/lib/dpkg/lock-frontend.
– Jos
Nov 26 at 12:44
@Jos Thank you for your comment. As you have suggested, I removed lock-frontend file, but now it showd another error message that goes as follows: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
– John2
Nov 26 at 12:50
That message is a summary of previous messages that tell you which archives couldn't be fetched, and why not. From this summary, I can't tell what went wrong.
– Jos
Nov 26 at 13:00
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I tried to install DHCP server on my Ubuntu Server 18.04, but it failed.
sudo apt install isc-dhcp-server
The following messages were shown after the trial:
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
As you may assume, I've already set a static IP address on 50-cloud-init.yaml file.
My settings are as follows:
This file is generated from information provided by
the datasource. Changes to it will not persist across an instance.
To disable cloud-init's network configuration capabilities, write a file
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
network: {config: disabled}
network:
ethernets:
enp0s3:
addresses: [192.168.0.101/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
dhcp4: no
version: 2
And of course, I made the above changes take effect by running the following command:
sudo netplan apply
SI there any solution you can provide?
Please advise!
server 18.04
asked Nov 26 at 12:35
John2
11
I tried to install DHCP server on my Ubuntu Server 18.04, but it failed.
sudo apt install isc-dhcp-server
The following messages were shown after the trial:
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
As you may assume, I've already set a static IP address on 50-cloud-init.yaml file.
My settings are as follows:
This file is generated from information provided by
the datasource. Changes to it will not persist across an instance.
To disable cloud-init's network configuration capabilities, write a file
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
network: {config: disabled}
network:
ethernets:
enp0s3:
addresses: [192.168.0.101/24]
gateway4: 192.168.1.1
nameservers:
addresses: [192.168.1.1,8.8.8.8]
dhcp4: no
version: 2
And of course, I made the above changes take effect by running the following command:
sudo netplan apply
SI there any solution you can provide?
Please advise!
server 18.04
server 18.04
asked Nov 26 at 12:35
John2
11
asked Nov 26 at 12:35
John2
11
edited Nov 26 at 12:40
asked Nov 26 at 12:35
John2
11
asked Nov 26 at 12:35
John2
11
asked Nov 26 at 12:35
John2
11
11
The warning you get has nothing to do with your network configuration. It just says that you are trying to install two packages at the same time, or you have one package manager open while doingaptin a terminal. If closing open package managers doesn't help, you can always remove the lock file the hard way withsudo rm /var/lib/dpkg/lock-frontend.
– Jos
Nov 26 at 12:44
@Jos Thank you for your comment. As you have suggested, I removed lock-frontend file, but now it showd another error message that goes as follows: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
– John2
Nov 26 at 12:50
That message is a summary of previous messages that tell you which archives couldn't be fetched, and why not. From this summary, I can't tell what went wrong.
– Jos
Nov 26 at 13:00
add a comment |
The warning you get has nothing to do with your network configuration. It just says that you are trying to install two packages at the same time, or you have one package manager open while doingaptin a terminal. If closing open package managers doesn't help, you can always remove the lock file the hard way withsudo rm /var/lib/dpkg/lock-frontend.
– Jos
Nov 26 at 12:44
@Jos Thank you for your comment. As you have suggested, I removed lock-frontend file, but now it showd another error message that goes as follows: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
– John2
Nov 26 at 12:50
That message is a summary of previous messages that tell you which archives couldn't be fetched, and why not. From this summary, I can't tell what went wrong.
– Jos
Nov 26 at 13:00
The warning you get has nothing to do with your network configuration. It just says that you are trying to install two packages at the same time, or you have one package manager open while doing
apt in a terminal. If closing open package managers doesn't help, you can always remove the lock file the hard way with sudo rm /var/lib/dpkg/lock-frontend.– Jos
Nov 26 at 12:44
The warning you get has nothing to do with your network configuration. It just says that you are trying to install two packages at the same time, or you have one package manager open while doing
apt in a terminal. If closing open package managers doesn't help, you can always remove the lock file the hard way with sudo rm /var/lib/dpkg/lock-frontend.– Jos
Nov 26 at 12:44
@Jos Thank you for your comment. As you have suggested, I removed lock-frontend file, but now it showd another error message that goes as follows: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
– John2
Nov 26 at 12:50
@Jos Thank you for your comment. As you have suggested, I removed lock-frontend file, but now it showd another error message that goes as follows: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
– John2
Nov 26 at 12:50
That message is a summary of previous messages that tell you which archives couldn't be fetched, and why not. From this summary, I can't tell what went wrong.
– Jos
Nov 26 at 13:00
That message is a summary of previous messages that tell you which archives couldn't be fetched, and why not. From this summary, I can't tell what went wrong.
– Jos
Nov 26 at 13:00
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096160%2fcouldnt-install-isc-dhcp-server-on-ubuntu-server-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The warning you get has nothing to do with your network configuration. It just says that you are trying to install two packages at the same time, or you have one package manager open while doing
aptin a terminal. If closing open package managers doesn't help, you can always remove the lock file the hard way withsudo rm /var/lib/dpkg/lock-frontend.– Jos
Nov 26 at 12:44
@Jos Thank you for your comment. As you have suggested, I removed lock-frontend file, but now it showd another error message that goes as follows: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
– John2
Nov 26 at 12:50
That message is a summary of previous messages that tell you which archives couldn't be fetched, and why not. From this summary, I can't tell what went wrong.
– Jos
Nov 26 at 13:00