| === mybalzit1h is now known as mybalzitch | ||
| === masACC is now known as maswan | ||
| lordievader | Good morning | 07:16 |
|---|---|---|
| sveinse | What should I put in /etc/fstab to prevent 20.04 from locking up the boot? I have "nfs defaults,bg 0 0" in it, and it locked the boot for over 10 hours as the remove was unavailable :( Had to forcibly reboot the machine and use recovery mode to remote the fstab entry. | 08:42 |
| sveinse | The ssh server prevented me from logging in, so I couldn't fix it remotely either | 08:46 |
| lordievader | sveinse: Is the mount necessary for boot or can it be an automount (mount on first access)? | 09:08 |
| frickler | sveinse: the other solution would be to setup a systemd service that fires only after the network setup is done, see e.g. https://cloudnull.io/2017/05/nfs-mount-via-systemd/ | 09:23 |
| sveinse | lordievader: its not directly necessary for boot. The boot must not halt if it cannot be accessed | 09:23 |
| lordievader | sveinse: I typically have `noauto,_netdev,x-systemd.automount` in my fstab for NFS entries. `_netdev` tells systemd it is a networked file system and therefore requires the network-online.target. `noauto,x-systemd.automount` make sure it is not mounted at boot, but rather the first time it is accessed. | 09:28 |
| sveinse | lordievader: yeah, I thought one didn't need the '_netdev' any more, but I might be mistaking | 09:29 |
| === axino` is now known as axino | ||
| === leftyfb_ is now known as leftyfb | ||
| === genii-core is now known as genii | ||
| faceface | hello | 17:50 |
| faceface | A colleague of mine disabled DNS on a server (I think). Now I don't know how to reconfigure it to defaults. | 17:50 |
| faceface | /etc/dnsmasq.d is in cruft output... I guess they removed dnsmasq | 17:52 |
| faceface | What is the ip address of the apt server? | 17:53 |
| faceface | or.. do I need dnsmasq? | 17:53 |
| bigpod | faceface: what version of ubuntu server do you hve | 18:08 |
| faceface | bigpod: DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" | 19:09 |
| bigpod | maybe systemd-resolved needs to be enabled | 19:11 |
| ouzel8_ | Hi! I performed a do-release-upgrade on 18.04.4 to upgrade to 18.04.5 in the last few days. I note to you that the server had a static ip set using netplan, and the configuration seen under section "Static IP Address Assignment" found on https://ubuntu.com/server/docs/network-configuration. After rebooting the server, there was no network connectivity. | 22:20 |
| ouzel8_ | I tried to systemctl restart networking.service | 22:21 |
| ouzel8_ | But the tool said the unit file did not exist | 22:21 |
| ouzel8_ | I have since found that the netplan configuration file (with details about the static ip was deleted through the transfer) /etc/netplan/99_config.yaml. I have recreated the file, and run netplan apply. | 22:23 |
| ouzel8_ | However, with no effect to the networking after rebooting the server. | 22:23 |
| ouzel8_ | As a temporary measure I have assigned a static ip to the server using the ip tool as per "Temporary IP Address Assignment" on the same webpage given above. | 22:25 |
| ouzel8_ | Does anybody have any suggestions on how to solve this problem. | 22:25 |
| patdk-lap | that is really od | 22:29 |
| patdk-lap | do-release-upgrade doesn't upgrade you from 18.04.4 to 18.04.5, it upgrades you to 20.04 | 22:29 |
| patdk-lap | doing a *normal update* upgrades you do 18.04.x | 22:29 |
| ouzel8_ | I see | 22:29 |
| ouzel8_ | Well, I started do-release-upgrade via ssh | 22:29 |
| ouzel8_ | Despite the warnings. | 22:30 |
| patdk-lap | ya, I don't have time to figure out the issue | 22:30 |
| patdk-lap | but the problem was you where running in 18.04 and upgraded to 20.04 and some config files that where modified by hand need to be adjusted | 22:31 |
| patdk-lap | and your going have to locate each one and update it to work with 20.04 | 22:31 |
| ouzel8_ | I encountered some issues, then do-release-upgrade said do an upgrade through apt-get upgrade | 22:31 |
| patdk-lap | I normally do this during the upgrade, since it tells you each time it hits one of those files | 22:31 |
| patdk-lap | apt-get upgrade will get you to 18.04.5 without installing new dependencies | 22:31 |
| ouzel8_ | Then after this upgrade finished, then I rebooted the system, I then encountered the error. | 22:31 |
| patdk-lap | apt-get dist-upgrade will fully update you including kernel updates | 22:32 |
| ouzel8_ | After apt-get upgrade the system was upgraded to this version "Welcome to Ubuntu 18.04.5 LTS (GNU/Linux 5.4.0-77-generic x86_64)" | 22:34 |
| ouzel8_ | As you have detailed, the configuration files were deleted through the upgrade | 22:34 |
| ouzel8_ | I have regenerated the configuration file, however, now the networking.service unit file does not exist. | 22:35 |
| ouzel8_ | So systemd networking services do not start when the system firsts boots. | 22:36 |
| patdk-lap | ya, I do not know that, files don't just get deleted during the update | 22:36 |
| ouzel8_ | I was not prompted at all. | 22:36 |
| patdk-lap | but then I had migrated all of my systems to netplan awhile ago | 22:36 |
| ouzel8_ | Well as I have regenerated the netplan configuration. I now need to get the networking system renderer to actually use the configuration file. | 22:48 |
| ouzel8_ | I will await anybody whom can help with this. | 22:48 |
| sdeziel | ouzel8_: on 18.04, were you using netplan? | 23:03 |
| ouzel8_ | @sdeziel yes I am | 23:10 |
| === genii is now known as genii-core | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!