Fix for kernel bug in Ubuntu 20.04 causing various issues

[girish]

@odie on our servers, I get the new kernel like this when I do unattended-upgrade -d:

pkgs that look like they should be upgraded: linux-generic
linux-headers-generic
linux-image-generic
Get:1 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-5.4.0-135-generic amd64 5.4.0-135.152 [15.0 MB]                                                                                  
Get:2 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-5.4.0-135-generic amd64 5.4.0-135.152 [10.5 MB]                                                                                    
Get:3 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-modules-extra-5.4.0-135-generic amd64 5.4.0-135.152 [39.2 MB]                                                                            
Get:4 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-generic amd64 5.4.0.135.133 [1896 B]                                                                                                     
Get:5 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-image-generic amd64 5.4.0.135.133 [2520 B]                                                                                               
Get:6 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.4.0-135 all 5.4.0-135.152 [11.0 MB]                                                                                            
Get:7 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.4.0-135-generic amd64 5.4.0-135.152 [1403 kB]                                                                                  
Get:8 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-generic amd64 5.4.0.135.133 [2388 B]                                                                                             
Fetched 77.1 MB in 0s (0 B/s)                                                                                                                                                                                     
fetch.run() result: 0
...
Found linux image: /boot/vmlinuz-5.4.0-135-generic
Found initrd image: /boot/initrd.img-5.4.0-135-generic
Found linux image: /boot/vmlinuz-5.4.0-132-generic
Found initrd image: /boot/initrd.img-5.4.0-132-generic
Found linux image: /boot/vmlinuz-5.4.0-131-generic
Found initrd image: /boot/initrd.img-5.4.0-131-generic
done

When I run it again, it doesn't show anything interesting. It is like your output. So, maybe it has the kernel installed already. Can you see apt list -a linux-image-5.4.0-135-generic ?

[girish]

@odie BTW, I had edited my original post on how to reverse the changes. Did you see that? You have to make the grub changes if you haven't done so already.

[odie]

@girish said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

@odie BTW, I had edited my original post on how to reverse the changes. Did you see that? You have to make the grub changes if you haven't done so already.

Thanks for the quick response.

When I do the apt-list -a, I get the following output:

linux-image-5.4.0-135-generic/focal-updates,focal-security,now 5.4.0-135.152 amd64 [installed,automatic]

When I do the sudo update-grub, I get:

Sourcing file `/etc/default/grub'
/usr/sbin/grub-mkconfig: 6: /etc/default/grub: options: not found

Meanwhile, while I went home from work an hour+ ago, my Cloudron updated to 7.3.4, and it's been stuck on "starting services, this might take a while" for more than an hour now, according to logs. (logs stopped updating 1 hour 10 minutes ago)

[odie]

@odie said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

@girish said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

@odie BTW, I had edited my original post on how to reverse the changes. Did you see that? You have to make the grub changes if you haven't done so already.

Thanks for the quick response.

When I do the apt-list -a, I get the following output:

linux-image-5.4.0-135-generic/focal-updates,focal-security,now 5.4.0-135.152 amd64 [installed,automatic]

When I do the sudo update-grub, I get:

Sourcing file `/etc/default/grub'
/usr/sbin/grub-mkconfig: 6: /etc/default/grub: options: not found

Meanwhile, while I went home from work an hour+ ago, my Cloudron updated to 7.3.4, and it's been stuck on "starting services, this might take a while" for more than an hour now, according to logs. (logs stopped updating 1 hour 10 minutes ago)

I get logs like this on my Cloudron. All services fail to start, except "Cloudron", "docker", "nginx" and "unbound". Only the logs on "Cloudron" update. Logs like this:

GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 10.956 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 9.478 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 9.101 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 10.384 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 10.285 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 575.305 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 10.920 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 8.970 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 13.121 ms - 89
GET /api/v1/appstore/apps?repository=core 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 10.917 ms - 89
Dec 07 17:13:56 box:locker Lock unreleased platform_start
Dec 07 17:18:56 box:locker Lock unreleased platform_start
GET /api/v1/appstore/subscription 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 1038.846 ms - 89
Dec 07 17:23:22 box:shell statusUnbound exec: systemctl is-active unbound
Dec 07 17:23:22 box:shell statusNginx exec: systemctl is-active nginx
Dec 07 17:23:22 box:shell statusUnbound (stdout): active
Dec 07 17:23:22 box:shell statusUnbound (stderr): null
Dec 07 17:23:22 box:shell statusNginx (stdout): active
Dec 07 17:23:22 box:shell statusNginx (stderr): null
Dec 07 17:23:56 box:locker Lock unreleased platform_start
GET /api/v1/appstore/subscription 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 2381.412 ms - 89
Dec 07 17:27:38 box:shell statusUnbound exec: systemctl is-active unbound
Dec 07 17:27:38 box:shell statusUnbound (stdout): active
Dec 07 17:27:38 box:shell statusUnbound (stderr): null
Dec 07 17:27:38 box:shell statusNginx exec: systemctl is-active nginx
Dec 07 17:27:38 box:shell statusNginx (stdout): active
Dec 07 17:27:38 box:shell statusNginx (stderr): null
GET /api/v1/appstore/subscription 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 989.596 ms - 89
Dec 07 17:28:56 box:locker Lock unreleased platform_start
Dec 07 17:28:57 box:shell statusUnbound exec: systemctl is-active unbound
Dec 07 17:28:57 box:shell statusUnbound (stdout): active
Dec 07 17:28:57 box:shell statusUnbound (stderr): null
Dec 07 17:28:57 box:shell statusNginx exec: systemctl is-active nginx
Dec 07 17:28:57 box:shell statusNginx (stdout): active
Dec 07 17:28:57 box:shell statusNginx (stderr): null
Dec 07 17:29:00 box:cloudron Getting logs for box as json

[girish]

@odie said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

GET /api/v1/appstore/subscription 424 Failed Dependency getaddrinfo EAI_AGAIN api.cloudron.io 2381.412 ms - 89

The issue seems to be that unbound is down/not working. Does host cloudron.io 127.0.0.1 work on the server?

[odie]

@girish said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

host cloudron.io 127.0.0.1

No, I get the following output:

Using domain server:
Name: 127.0.0.1
Address: 127.0.0.1#53
Aliases:

Host cloudron.io not found: 2(SERVFAIL)

Would this be a workaround? https://forum.cloudron.io/post/57804

If so, and if it works, should I leave the forward-everything.conf file, or delete it aftwerwards?

Thanks!

[girish]

@odie You should leave the conf file. Are you also on a home server?

Initially, I thought that support request was an exception. Maybe there is some genuine unbound configuration issue. hmmm

[odie]

@girish said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

@odie You should leave the conf file. Are you also on a home server?

Initially, I thought that support request was an exception. Maybe there is some genuine unbound configuration issue. hmmm

Yes, I am on a home server. Services seem to start

[odie]

@odie said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

@girish said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

@odie You should leave the conf file. Are you also on a home server?

Initially, I thought that support request was an exception. Maybe there is some genuine unbound configuration issue. hmmm

Yes, I am on a home server. Services seem to start

Yup, all services have started, apps are running and everything seems to work. Thank you.

I guess that just leaves the original issue. I suddenly have a house full of family members, so I’ll have to check back later. Sorry about that, and thanks for helping me out!

[odie]

@girish said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

Edit /etc/default/grub . Change the line to GRUB_DEFAULT=Advanced options for Ubuntu>Ubuntu, with Linux 5.4.0-135-generic.

Hello again,
Thanks for the help earlier. And apologies for having to run, suddenly 8 family members on my door expecting dinner....

I think I figured out why I didn't manage to make the guide work for me when I tried to update grub. In the quoted line, there should be quotes around the "Advanced options..." line.

When doing that, the guide to revers the changes worked.

[jdaviescoates]

@odie said in Fix for kernel bug in Ubuntu 20.04 causing various issues:

n the quoted line, there should be quotes around the "Advanced options..." line.

@girish sounds like that needs to go in your reverse instructions in the post at the top - your commands there don't have the quotes.