I am working on a robotic skeleton using the Radxa zero 3w with radxa-zero3_debian_bullseye_xfce_b6 as the OS. The first time I booted it (from SD card) I got an error saying the hostname (hank) could not be resolved. I checked the journalctl -xe command with the following output:
radxa@hank:/etc$ sudo journalctl -xe
sudo: unable to resolve host hank: Name or service not known
░░ The job identifier is 1248.
May 29 12:16:15 hank dnsmasq[2469]: dnsmasq: failed to create listening socket for port 53: Address already in use
May 29 12:16:15 hank dnsmasq[2469]: failed to create listening socket for port 53: Address already in use
May 29 12:16:15 hank dnsmasq[2469]: FAILED to start up
May 29 12:16:15 hank systemd[1]: dnsmasq.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit dnsmasq.service has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 2.
May 29 12:16:15 hank systemd[1]: dnsmasq.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit dnsmasq.service has entered the ‘failed’ state with result ‘exit-code’.
May 29 12:16:15 hank systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
░░ Subject: A start job for unit dnsmasq.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit dnsmasq.service has finished with a failure.
░░
░░ The job identifier is 1248 and the job result is failed.
May 29 12:16:15 hank sudo[2461]: pam_unix(sudo:session): session closed for user root
May 29 12:16:34 hank sudo[2475]: radxa : unable to resolve host hank: Name or service not known
May 29 12:16:34 hank sudo[2475]: radxa : problem with defaults entries ; TTY=pts/0 ; PWD=/etc ; USER=root ;
May 29 12:16:34 hank sudo[2475]: radxa : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/usr/bin/journalctl -xe
May 29 12:16:34 hank sudo[2475]: pam_unix(sudo:session): session opened for user root(uid=0) by radxa(uid=1000)
May 29 12:16:46 hank sudo[2475]: pam_unix(sudo:session): session closed for user root
May 29 12:20:40 hank xfce4-screensav[2485]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.Ser>
May 29 12:20:41 hank org.xfce.ScreenSaver[2485]: libGL error: failed to create dri screen
May 29 12:20:41 hank org.xfce.ScreenSaver[2485]: libGL error: failed to load driver: rockchip
May 29 12:20:42 hank org.xfce.ScreenSaver[2485]: libGL error: failed to create dri screen
May 29 12:20:42 hank org.xfce.ScreenSaver[2485]: libGL error: failed to load driver: rockchip
May 29 12:20:45 hank xfce4-screensaver-dialog[2592]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyri>
May 29 12:20:45 hank xfce4-screensaver-dialog[2592]: PAM adding faulty module: pam_gnome_keyring.so
May 29 12:25:52 hank xfce4-screensav[2687]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.Ser>
May 29 12:25:53 hank org.xfce.ScreenSaver[2687]: libGL error: failed to create dri screen
May 29 12:25:53 hank org.xfce.ScreenSaver[2687]: libGL error: failed to load driver: rockchip
May 29 12:25:54 hank org.xfce.ScreenSaver[2687]: libGL error: failed to create dri screen
May 29 12:25:54 hank org.xfce.ScreenSaver[2687]: libGL error: failed to load driver: rockchip
May 29 12:26:05 hank xfce4-screensaver-dialog[2796]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyri>
May 29 12:26:05 hank xfce4-screensaver-dialog[2796]: PAM adding faulty module: pam_gnome_keyring.so
May 29 12:26:13 hank unix_chkpwd[2853]: password check failed for user (radxa)
May 29 12:26:13 hank xfce4-screensaver-dialog[2796]: pam_unix(xfce4-screensaver:auth): authentication failure; logname= uid=10>
May 29 12:26:15 hank xfce4-screensaver-dialog[2796]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyri>
May 29 12:26:15 hank xfce4-screensaver-dialog[2796]: PAM adding faulty module: pam_gnome_keyring.so
May 29 12:36:56 hank xfce4-screensav[2947]: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.Ser>
May 29 12:36:57 hank org.xfce.ScreenSaver[2947]: libGL error: failed to create dri screen
May 29 12:36:57 hank org.xfce.ScreenSaver[2947]: libGL error: failed to load driver: rockchip
May 29 12:36:58 hank org.xfce.ScreenSaver[2947]: libGL error: failed to create dri screen
May 29 12:36:58 hank org.xfce.ScreenSaver[2947]: libGL error: failed to load driver: rockchip
May 29 12:41:20 hank xfce4-screensaver-dialog[3083]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyri>
May 29 12:41:20 hank xfce4-screensaver-dialog[3083]: PAM adding faulty module: pam_gnome_keyring.so
May 29 12:50:44 hank sudo[3178]: radxa : unable to resolve host hank: Name or service not known
May 29 12:50:44 hank sudo[3178]: radxa : problem with defaults entries ; TTY=pts/0 ; PWD=/etc ; USER=root ;
May 29 12:50:50 hank sudo[3178]: radxa : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/usr/bin/journalctl -xe
May 29 12:50:50 hank sudo[3178]: pam_unix(sudo:session): session opened for user root(uid=0) by radxa(uid=1000)
May 29 12:51:42 hank sudo[3178]: pam_unix(sudo:session): session closed for user root
May 29 12:51:53 hank sudo[3182]: radxa : unable to resolve host hank: Name or service not known
May 29 12:51:53 hank sudo[3182]: radxa : problem with defaults entries ; TTY=pts/0 ; PWD=/etc ; USER=root ;
May 29 12:51:53 hank sudo[3182]: radxa : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/usr/bin/journalctl -xe
May 29 12:51:53 hank sudo[3182]: pam_unix(sudo:session): session opened for user root(uid=0) by radxa(uid=1000)
This is the content of the resolve.conf file:
Generated by NetworkManager
nameserver 192.168.4.1 <<<<<< my routers DNS
nameserver 8.8.8.8 <<<<<<<<< google DNS
nameserver 2607:fdc8:c::2
NOTE: the libc resolver may not support more than 3 nameservers.
The nameservers listed below may not be recognized.
nameserver 2607:fdc8:c::3
I have googled the issue till I was blue in the face, but was unable to make any of the solutions work. I am hoping someone here has had a similar issue!
Thanks
Bill