Alpine/OpenRC networking fails to start (boot toofast?)
Clash Royale CLAN TAG#URR8PPP
I am using alpine, my primary distro for servers is Arch with NetworkManager or the built-in "netctl".
I installed Alpine onto a server. It boots up OK, but the networking never comes up on its own. It appears this is because the server boots so fast (login prompt in only 2s!). When the OpenRC init runs the networking script, the "eth0" device has not yet been initialized and thus is not yet available:
* Starting networking
* lo ...
* eth0 ...
Cannot find device "eth0"
If I login as root at the console and execute service networking start then networking comes up successfully. But obviously this is not suitable for a server which needs to be able to bring its networking back up on its own after a reboot.
I can further confirm because in dmesg output, the Ethernet driver's initialization messages are the last to appear, with timestamps of 8 seconds (remember, login prompt appears in only 2 seconds).
How can I get OpenRC to wait for the device to be available before trying to bring the networking up - or at least background the process and keep trying to bring the interface up in the background while bootup continues?
networking alpine-linux openrc
edited Dec 28 '18 at 23:24
Rui F Ribeiro
39.4k1479131
asked Dec 28 '18 at 22:40
fdmillionfdmillion
7601812
add a comment |
I am using alpine, my primary distro for servers is Arch with NetworkManager or the built-in "netctl".
I installed Alpine onto a server. It boots up OK, but the networking never comes up on its own. It appears this is because the server boots so fast (login prompt in only 2s!). When the OpenRC init runs the networking script, the "eth0" device has not yet been initialized and thus is not yet available:
* Starting networking
* lo ...
* eth0 ...
Cannot find device "eth0"
If I login as root at the console and execute service networking start then networking comes up successfully. But obviously this is not suitable for a server which needs to be able to bring its networking back up on its own after a reboot.
I can further confirm because in dmesg output, the Ethernet driver's initialization messages are the last to appear, with timestamps of 8 seconds (remember, login prompt appears in only 2 seconds).
How can I get OpenRC to wait for the device to be available before trying to bring the networking up - or at least background the process and keep trying to bring the interface up in the background while bootup continues?
networking alpine-linux openrc
edited Dec 28 '18 at 23:24
Rui F Ribeiro
39.4k1479131
asked Dec 28 '18 at 22:40
fdmillionfdmillion
7601812
can you identify which module your eth0 uses? n networking is supposed to wake up eth0 only after "modules" is called: n depend() { n need localmount n after bootmisc hwdrivers modules <-----
– FabioM
Dec 28 '18 at 23:10
add a comment |
I am using alpine, my primary distro for servers is Arch with NetworkManager or the built-in "netctl".
I installed Alpine onto a server. It boots up OK, but the networking never comes up on its own. It appears this is because the server boots so fast (login prompt in only 2s!). When the OpenRC init runs the networking script, the "eth0" device has not yet been initialized and thus is not yet available:
* Starting networking
* lo ...
* eth0 ...
Cannot find device "eth0"
If I login as root at the console and execute service networking start then networking comes up successfully. But obviously this is not suitable for a server which needs to be able to bring its networking back up on its own after a reboot.
I can further confirm because in dmesg output, the Ethernet driver's initialization messages are the last to appear, with timestamps of 8 seconds (remember, login prompt appears in only 2 seconds).
How can I get OpenRC to wait for the device to be available before trying to bring the networking up - or at least background the process and keep trying to bring the interface up in the background while bootup continues?
networking alpine-linux openrc
edited Dec 28 '18 at 23:24
Rui F Ribeiro
39.4k1479131
asked Dec 28 '18 at 22:40
fdmillionfdmillion
7601812
I am using alpine, my primary distro for servers is Arch with NetworkManager or the built-in "netctl".
I installed Alpine onto a server. It boots up OK, but the networking never comes up on its own. It appears this is because the server boots so fast (login prompt in only 2s!). When the OpenRC init runs the networking script, the "eth0" device has not yet been initialized and thus is not yet available:
* Starting networking
* lo ...
* eth0 ...
Cannot find device "eth0"
If I login as root at the console and execute service networking start then networking comes up successfully. But obviously this is not suitable for a server which needs to be able to bring its networking back up on its own after a reboot.
I can further confirm because in dmesg output, the Ethernet driver's initialization messages are the last to appear, with timestamps of 8 seconds (remember, login prompt appears in only 2 seconds).
How can I get OpenRC to wait for the device to be available before trying to bring the networking up - or at least background the process and keep trying to bring the interface up in the background while bootup continues?
networking alpine-linux openrc
networking alpine-linux openrc
edited Dec 28 '18 at 23:24
Rui F Ribeiro
39.4k1479131
asked Dec 28 '18 at 22:40
fdmillionfdmillion
7601812
edited Dec 28 '18 at 23:24
Rui F Ribeiro
39.4k1479131
asked Dec 28 '18 at 22:40
fdmillionfdmillion
7601812
edited Dec 28 '18 at 23:24
Rui F Ribeiro
39.4k1479131
edited Dec 28 '18 at 23:24
Rui F Ribeiro
39.4k1479131
edited Dec 28 '18 at 23:24
Rui F Ribeiro
39.4k1479131
39.4k1479131
asked Dec 28 '18 at 22:40
fdmillionfdmillion
7601812
asked Dec 28 '18 at 22:40
fdmillionfdmillion
7601812
asked Dec 28 '18 at 22:40
fdmillionfdmillion
7601812
7601812
can you identify which module your eth0 uses? n networking is supposed to wake up eth0 only after "modules" is called: n depend() { n need localmount n after bootmisc hwdrivers modules <-----
– FabioM
Dec 28 '18 at 23:10
add a comment |
can you identify which module your eth0 uses? n networking is supposed to wake up eth0 only after "modules" is called: n depend() { n need localmount n after bootmisc hwdrivers modules <-----
– FabioM
Dec 28 '18 at 23:10
can you identify which module your eth0 uses? n networking is supposed to wake up eth0 only after "modules" is called: n depend() { n need localmount n after bootmisc hwdrivers modules <-----
– FabioM
Dec 28 '18 at 23:10
can you identify which module your eth0 uses? n networking is supposed to wake up eth0 only after "modules" is called: n depend() { n need localmount n after bootmisc hwdrivers modules <-----
– FabioM
Dec 28 '18 at 23:10
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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%2funix.stackexchange.com%2fquestions%2f491389%2falpine-openrc-networking-fails-to-start-boot-toofast%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f491389%2falpine-openrc-networking-fails-to-start-boot-toofast%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
can you identify which module your eth0 uses? n networking is supposed to wake up eth0 only after "modules" is called: n depend() { n need localmount n after bootmisc hwdrivers modules <-----
– FabioM
Dec 28 '18 at 23:10