Fix ifup-allow-boot.service failing to start #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Without this fix, the interface name seems to be empty:
ifup-allow-boot[786]: Interface floating is down, bringing it up
sh[787]: Failed to start [email protected]: Unit name [email protected] is missing the instance name.
sh[787]: See system logs and 'systemctl status [email protected]' for details.
systemd[1]: ifup-allow-boot.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: ifup-allow-boot.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Bring up non-hotpluggable interfaces on boot.
|
Thanks, that does the trick! 🙏 |
urscale
approved these changes
Jun 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without this fix, the interface name seems to be empty: