Error on booting into 4.4 kernel with Ubuntu 20 - TMCC exited with status 256!

[Yueying Li]

Hello,

After successfully booting into 4.4 kernel with some network errors, I saw this error in the  PXE (Pre-Boot Execution Environment).

root@localhost:~# [  211.228822] testbed[1144]: gethostbyname(UNKNOWN) failed
[  211.228932] testbed[1144]: TMCC exited with status 256!
[  211.228977] testbed[1144]: *** WARNING: Could not get bossinfo from tmcc!

I was wondering if you could help shed some light? I also attached the logs before the PXE here. 

Thank you! 

Regards,

      Starting Self Monitoring a…g Technology (SMART) Daemon...
         Starting Login Service...
[  OK  ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
[  OK  ] Started System Logging Service.
[  OK  ] Started LSB: Record successful boot for GRUB.
[  OK  ] Started Self Monitoring an…ing Technology (SMART) Daemon.
         Starting GRUB failed boot detection...
[  OK  ] Started LSB: Execute the k…c -e command to reboot system.
[  OK  ] Started Login Service.
[  OK  ] Started Dispatcher daemon for systemd-networkd.
[  OK  ] Finished GRUB failed boot detection.
         Starting Authorization Manager...
[  OK  ] Started Authorization Manager.
[  OK  ] Started Accounts Service.
[FAILED] Failed to start Force udev…efore systemd-networkd starts.
See 'systemctl status emulab-udev-settle.service' for details.
[DEPEND] Dependency failed for Network Service.
[DEPEND] Dependency failed for Wait for Network to be Configured.
         Starting Network Name Resolution...
[  OK  ] Stopped Force udev to sett…efore systemd-networkd starts.
         Starting Force udev to set…ore systemd-networkd starts...
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
[  OK  ] Reached target Host and Network Name Lookups.
         Starting Network Time Service...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
         Starting Availability of block devices...
[  OK  ] Started Regular background program processing daemon.
         Starting LSB: Load kernel image with kexec...
         Starting The Emulab publish/subscribe daemon...
         Starting OpenBSD Secure Shell server...
         Starting Permit User Sessions...
         Starting Testbed Services...
[  OK  ] Started Network Time Service.
[  OK  ] Finished Availability of block devices.
[FAILED] Failed to start The Emulab publish/subscribe daemon.
See 'systemctl status pubsubd.service' for details.
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started OpenBSD Secure Shell server.
[  129.221573] testbed[1124]: testbed config:
[  129.221877] testbed[1144]: Checking manifest...

[David M Johnson]

On 6/11/22 14:53, Yueying Li wrote:
> Hello,
>
> After successfully booting into 4.4 kernel with some network errors, I
> saw this error in the  PXE (Pre-Boot Execution Environment).
>
> root@localhost:~# [  211.228822] testbed[1144]: gethostbyname(UNKNOWN)
> failed
> [  211.228932] testbed[1144]: TMCC exited with status 256!
> [  211.228977] testbed[1144]: *** WARNING: Could not get bossinfo from tmcc!
>
> I was wondering if you could help shed some light? I also attached the
> logs before the PXE here.

Most likely the necessary NIC driver is missing for the control net --
or the version of it in 4.4 is too old for whatever hardware you're
running this on. I don't have an exact list, but 4.4 will definitely be
missing updated drivers for a number of our more modern hardware types,
so this may be hard or impossible.

Our standard advice for building custom kernels that will run on any of
our nodes is to based your config on the distro's config (on Ubuntu,
/boot/config-`uname -r`); typically you would `cp /boot/config-`uname
-r` .config && make oldconfig`). However, there are far too many major
changes between the 5.4 kernel in Ubuntu 20 and the 4.4 kernel you're
trying to use. To get around that, you might try starting from our
UBUNTU18-64-STD image instead. The UBUNTU18-64-STD image has an
additional advantage -- it uses DKMS to upgrade many network drivers
that are too old in the stock LTS kernel (in Ubuntu 18, 4.15). With
DKMS, any kernel you install from apt or from source via `make install`
will have the DKMS hooks invoked to build the updated modules, and if
those are both newer than the in-tree version, and build successfully,
they will override the in-tree versions.

(Our DKMS tree is at https://gitlab.flux.utah.edu/emulab/linux-dkms, and
the drivers you see in
https://gitlab.flux.utah.edu/emulab/linux-dkms/-/tree/master/drivers are
present in our Ubuntu 18 image.)

> Regards,

David

>       Starting Self Monitoring a…g Technology (SMART) Daemon...
>          Starting Login Service...
> [  OK  ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
> [  OK  ] Started System Logging Service.
> [  OK  ] Started LSB: Record successful boot for GRUB.
> [  OK  ] Started Self Monitoring an…ing Technology (SMART) Daemon.
>          Starting GRUB failed boot detection...
> [  OK  ] Started LSB: Execute the k…c -e command to reboot system.
> [  OK  ] Started Login Service.
> [  OK  ] Started Dispatcher daemon for systemd-networkd.
> [  OK  ] Finished GRUB failed boot detection.
>          Starting Authorization Manager...
> [  OK  ] Started Authorization Manager.
> [  OK  ] Started Accounts Service.

> *[FAILED] Failed to start Force udev…efore systemd-networkd starts.
> **See 'systemctl status emulab-udev-settle.service' for details.
> *[DEPEND] Dependency failed for Network Service.

> [DEPEND] Dependency failed for Wait for Network to be Configured.
>          Starting Network Name Resolution...
> [  OK  ] Stopped Force udev to sett…efore systemd-networkd starts.
>          Starting Force udev to set…ore systemd-networkd starts...
> [  OK  ] Started Network Name Resolution.
> [  OK  ] Reached target Network.
> [  OK  ] Reached target Network is Online.
> [  OK  ] Reached target Host and Network Name Lookups.
>          Starting Network Time Service...
> [  OK  ] Reached target Remote File Systems (Pre).
> [  OK  ] Reached target Remote File Systems.
>          Starting Availability of block devices...
> [  OK  ] Started Regular background program processing daemon.
>          Starting LSB: Load kernel image with kexec...
>          Starting The Emulab publish/subscribe daemon...
>          Starting OpenBSD Secure Shell server...
>          Starting Permit User Sessions...
>          Starting Testbed Services...
> [  OK  ] Started Network Time Service.
> [  OK  ] Finished Availability of block devices.

> *[FAILED] Failed to start The Emulab publish/subscribe daemon.
> *See 'systemctl status pubsubd.service' for details.

> [  OK  ] Finished Permit User Sessions.
> [  OK  ] Started OpenBSD Secure Shell server.
> [  129.221573] testbed[1124]: testbed config:
> [  129.221877] testbed[1144]: Checking manifest...
>
>
>
>

> --
> You received this message because you are subscribed to the Google
> Groups "cloudlab-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to cloudlab-user...@googlegroups.com
> <mailto:cloudlab-user...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/cloudlab-users/3774c0aa-8c7f-4d15-851f-d08c41cfab2cn%40googlegroups.com
> <https://groups.google.com/d/msgid/cloudlab-users/3774c0aa-8c7f-4d15-851f-d08c41cfab2cn%40googlegroups.com?utm_medium=email&utm_source=footer>.