We are running MAAS here and that server is one that was deployed a
month ago approximately.

1a)
[    0.000000] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
[    0.000000] Command line: 
BOOT_IMAGE=ubuntu/amd64/generic/bionic/daily/boot-kernel nomodeset ro 
root=squash:http://10.223.0.5:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs
 ip=::::finer-panda:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc 
cloud-config-url=http://10.223.0.5:5240/MAAS/metadata/latest/by-id/yx6d6w/?op=get_preseed
 apparmor=0 log_host=10.223.0.5 log_port=514 --- elevator=noop console=tty1 
console=ttyS0,115200 initrd=ubuntu/amd64/generic/bionic/daily/boot-initrd 
BOOTIF=01-f4-e9-d4-b6-5d-70

1b) Last check for them was a couple of months ago
1c) iDRAC says no.
2a) Say what? I tried starting it up and I got the shell appearing in the 
console. Then it just shut itself down again before I had time to react to log 
in. Could be a MAAS thing shutting it down?
2b) And what's that?
2c) Don't see any failures. First it boots up:
Ubuntu 18.04.1 LTS finer-panda ttyS0

finer-panda login: [   50.049021] cloud-init[2188]: Cloud-init v. 
18.4-0ubuntu1~18.04.1 running 'modules:config' at Fri, 08 Feb 2019 07:21:19 
+0000. Up 48.36 seconds.
[   51.015952] cloud-init[2270]: Powering node off.
ci-info: no authorized ssh keys fingerprints found for user ubuntu.


Then promptly after that:
[   51.169438] cloud-init[2270]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 
'modules:final' at Fri, 08 Feb 2019 07:21:22 +0000. Up 50.67 seconds.
[   51.169580] cloud-init[2270]: ci-info: no authorized ssh keys fingerprints 
found for user ubuntu.
[   51.169694] cloud-init[2270]: Cloud-init v. 18.4-0ubuntu1~18.04.1 finished 
at Fri, 08 Feb 2019 07:21:23 +0000. Datasource DataSourceMAAS 
[http://10.223.0.5:5240/MAs
         Stopping Authorization Manager...
[  OK  ] Stopped target Timers.
[  OK  ] Stopped Daily apt upgrade and clean activ         Stopping Accounts 
Service...
[  OK  ] Stopped target Host and Network Name Lookups.
         Stopping Read required files in advance...
         Stopping OpenBSD Secure Shell server...
         Stopping LVM2 PV scan on device 8:2...
[  OK  ] Unmounted /var/lib/lxcfs.
etc..

2d) This is the host running the dozens of virtual machines popping up
and shut down daily. Until this day and all the 32 exactly identical
hosts are still up and running...and have been for a month.

I'll try to dig out the info what causes it to shut down instead of
staying up.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814628

Title:
  divide error: 0000 with Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814628/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to