Re: a couple rpi problems
On Mon, Mar 04, 2024 at 11:41:07PM +, ghe2001 wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > rpi5 and 4, standard Debian clone OS > > 1) The 5, pi5.slsware.lan, keeps sending me email saying, > "*** SECURITY information for pi5 ***" > and > "pi5 : Mar 4 15:40:14 : root : unable to resolve host pi5: Name or service > not known" > I have no idea why it's complaining or what's bent. mike@DevuanPI4b:~> cat /etc/hostname MikesDevuanPI mike@DevuanPI4b:~> cat /etc/hosts 127.0.0.1 MikesDevuanPI > 2) On both the 4 and 5, 'needrestart' says I'm running on an old kernel and > tells me that a reboot will start the newer version. But it's just kidding > -- I reboot and I get the same message again. The 4's been doing that for a > long time, and I've just let it keep running the old kernel because I'm > afraid I might break something if I try to delete the old kernel. But I just > got the 5 a few days ago, it's doing the same thing, and I'd like to get this > dealt with. I've never seen that either and have 2 RPI4bs running Devuan daedalus on this one, Rasbian bookworm on the other. I assume you ran apt update & apt upgrade before reboot. One thing I have noticed is that reboot and 'shutdown -h now' then toggling the power, don't always give the same results. > -- > Glenn English Be well, Mike -- For more information, please reread.
Re: a couple rpi problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, March 4th, 2024 at 9:26 PM, Jeffrey Walton wrote: > Here's what one looks like for a host named 'raptor' after the Intel ISA: Yeah, I put it in there when I understood what it was looking for. When I went to computer school, there was no Internet or IP anything, so I didn't know that "resolve" meant "what's your IP address" (I hit vi real quick to add an IP to hosts -- everybody seems to be happy with their resolution now). Any thoughts on my kernel replacement notice problem? -- Glenn English -BEGIN PGP SIGNATURE- Version: ProtonMail wsBzBAEBCAAnBYJl5qQICZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC rIwyAAAKfQgAygPy80F4EiZzWgfFviPK7woPLTJt0a/cfWKy9hWb7HAJJal5 iJCu5ptloZ0mbwKQehmfMlJK/Qfp4wIwhCm0X/Z5Ye4OqlJ972YQn/RyJZjO QdrO4UjJ2biTqcc84iHjfeR9qBB/VTXZosLVM9Nd6Sl23fYckp7GQpAtYkNT WVjz16rUT0t3xeXr7QXaSo2x/MMY2qcldRROxDZVAa8oH74HC5P4+mAC3EB7 Srk0ZKfu2IBFVurp8LbyzuEQVL3c5CdkYXNS3P/nc3Tl27S+yDN98Q5zrREL iV7eMHdbw/QXzSVvbNxt0fZM5Bg3KLYmcgYp8LhiEwjBezRakt/UYw== =OGEg -END PGP SIGNATURE-
Re: a couple rpi problems
On Mon, Mar 4, 2024 at 11:07 PM ghe2001 wrote: > > On Monday, March 4th, 2024 at 5:01 PM, Greg Wooledge > wrote: > [...] > > So, "pi5" appears to be your hostname. > > Yup. > > > It can't resolve its own hostname. You're probably missing a line in > > your /etc/hosts file. > > Oh! It wants the IP! You're right -- pi5 isn't in there. Thanks. Here's what one looks like for a host named 'raptor' after the Intel ISA: $ cat /etc/hosts # Loopback entries; do not change. # For historical reasons, localhost precedes localhost.localdomain: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 # 127.0.1.1 is often used for the FQDN of the machine 127.0.1.1 raptor.home.arpa raptor # The following lines are desirable for IPv6 capable hosts ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
Re: a couple rpi problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, March 4th, 2024 at 5:01 PM, Greg Wooledge wrote: > On Mon, Mar 04, 2024 at 11:41:07PM +, ghe2001 wrote: > > > 1) The 5, pi5.slsware.lan, keeps sending me email saying, > > > > "*** SECURITY information for pi5 ***" > > > So, "pi5" appears to be your hostname. Yup. > It can't resolve its own hostname. You're probably missing a line in > your /etc/hosts file. Oh! It wants the IP! You're right -- pi5 isn't in there. Thanks. -- Glenn English -BEGIN PGP SIGNATURE- Version: ProtonMail wsBzBAEBCAAnBYJl5mNYCZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC rIwyAAANBwgAq7nMSAqNTRA7YRx9vW/7JkI/ely4QL6xYUrQ9g7+JWLvi5Do Qu2vfEKrPuidVahKp3YRcXMNXIryAKS9mO5ghUieiEUMTSH3M+aXiSC7m3CO Xu7qR5YPdKRM58iMkxHLN2IW2ioDGWAkQo9IdKxFNQvKP7KDhGleWmscFtjC nbD7kfkKZNShC3s/woEdctrqx2HlJQrbcU4pm6VUNsX0xAL71xPV/jro1Tr3 zPEnAy1Gq5VbcspMShUngaKEFn686GLlyaTaVR5ZWZJZOpEeRf2K/Qf8fZSt sR/orl0tSGZO2BJdGrZUu9vjkdNwHiSMLC7wkiKU9HdtM58f7PtYRw== =u7/T -END PGP SIGNATURE-
Re: a couple rpi problems
On Mon, Mar 04, 2024 at 11:41:07PM +, ghe2001 wrote: > 1) The 5, pi5.slsware.lan, keeps sending me email saying, > > "*** SECURITY information for pi5 ***" So, "pi5" appears to be your hostname. > "pi5 : Mar 4 15:40:14 : root : unable to resolve host pi5: Name or service > not known" > > I have no idea why it's complaining or what's bent. It can't resolve its own hostname. You're probably missing a line in your /etc/hosts file.
a couple rpi problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 rpi5 and 4, standard Debian clone OS 1) The 5, pi5.slsware.lan, keeps sending me email saying, "*** SECURITY information for pi5 ***" and "pi5 : Mar 4 15:40:14 : root : unable to resolve host pi5: Name or service not known" I have no idea why it's complaining or what's bent. 2) On both the 4 and 5, 'needrestart' says I'm running on an old kernel and tells me that a reboot will start the newer version. But it's just kidding -- I reboot and I get the same message again. The 4's been doing that for a long time, and I've just let it keep running the old kernel because I'm afraid I might break something if I try to delete the old kernel. But I just got the 5 a few days ago, it's doing the same thing, and I'd like to get this dealt with. IIRC (I'm 81, and that's no longer a given), I never saw this with the rpi2s or 3s or the real Debian boxen. Any thoughts/suggestions would be appreciated... -- Glenn English -BEGIN PGP SIGNATURE- Version: ProtonMail wsBzBAEBCAAnBYJl5lv0CZDmyitW0WqrdxYhBMRG7aHlwXhPX67r9+bKK1bR aqt3AAAKKwf/QpSQ5LbO3FflxshXl0s+7TZWnW1dWw3XmWHuhuLM904ie6vL DdaZWr2C/7ZuVN0iKvwpX5Z+8AwtyUTNfrxV7yMKvZw+Gzuc8ZZ2NN/7oGI4 7o8Ua/OXYlwIeKVL8agb3frMvz7Flsh3C9eOqvv7WJTmhkLE23ZKN84VHPcz GpaSi/K7l6bpHDrC50F1HvgtYzGZIp7bJVY930+IRv1BYLJI7EwLDiC5JjeN 37T1s/Ul7460FFM0J49LMZYUEQKkWqBPw8wqf6zK0WNJ8DYJ6dHA+6Hqf6Xz CZyPRL2E1Zd0wAtrHPrl+JMHxfMblwyZMu0vkI+h6HHzfbcaEkwMBg== =BPuV -END PGP SIGNATURE-
