0

My setup is: Raspberry Pi 2 w/ Arch Linux ARM.

It’s been running headless from the get-go since 2019, used as a home server for Pi-hole and self-hosting my webpages. Pi is connected via Ethernet, and I ssh into it from my MacBook via Wi-Fi.

All good until yesterday when I lost my internet and realised it was because of my Pi struggling with something as I couldn’t SSH into it anymore:

  • ssh carapuce@10.0.1.6 gave a host is down
  • ssh carapuce@applepie which usually is my go-to just waited indefinitely with no answer whatsoever

All I have is my MacBook so without a keyboard and feeling a bit desperate, I unplugged my Pi from the power socket and replugged it after fifteen minutes.

Nothing changed, same thing.

Managed to find an HDMI cable and connected my Pi to the TV. It does seem to boot normally and showed the tty to login. Not long after, it went away and this showed up:

Arch Linux 5.10.92-2-rpi-legacy-ARCH (tty1)

applepie login: [   39.518154] cam1-reg: disabling
[       39.521392] cam-dummy-reg: disabling

A moment passed and then this came up:

[      136.641066] kauditd_printk_skb: 19 callbacks suppressed
[      136.641078] audit: type=1130 audit(1655905641.343:31): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=systemd-networkd-wait-online comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’

And a moment later:

[      136.666714] audit: type=1130 audit(1655905641.353:32): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=bitbot comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=failed’
[      144.783596] audit: type=1130 audit(1655905649.483:33): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=‘unit=bitbot comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’

And it goes on and on with many other identical ones that randomly fail or succeed.

(Bitbot is an IRC bot by the way, I guess it just likes to complain even more than I do when internet is down. :P)

More seriously my understanding is that something seems wrong with systemd-networkd but I have no idea what it could be or what to do about it?

It’s not my SD card dying, is it? That was my concern at first. It’s a SanDisk Ultra 128GB but I turn most logs off to preserve it and it has like over 80% free space.

SSH seems out of the question right now but if I buy a keyboard, do you think I can fix this? Do you have any idea how?

Your help would be appreciated greatly.

Thanks so much for your time.

Have a beautiful day :)

New contributor
Carapuce is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
2
  • Could you just borrow a keyboard from a friend?
    – NomadMaker
    Jun 23 at 12:54
  • "If I buy a keyboard, do you think I can fix this?" -> I think you cannot fix it without one, unless you just want to overwrite the card with a new image.
    – goldilocks
    2 days ago

0

Your Answer

Carapuce is a new contributor. Be nice, and check out our Code of Conduct.

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.