Spontaneous locale change on Bookworm

Sep 21, 2024 Last reply: 1 year ago 54 Replies

systemd myth number 20: “systemd makes it impossible to run syslog”.

formatting link

No, you can run rsyslog, what you can't do is only run rsyslog and get rid of journald.

You are stuck with it either spaffing 2GB of unfiltered binary logs over your disc, or configuring it to RAM only and having it ignore the vacuum settings, so things stop working when /run gets full.

In all a total shitshow that just isn't needed on Linux.

---druck

I was amazed sitting in an airport to notice 'amandasIPhone'...

That's just someone with network sharing on their phone.

---druck

Yes, but she wasnt. She was just doing something I-phoneish oblivious to the fact that her phone was severely compromised by leaving it in access point mode

Just configure it not to save anything in the journal, if you really want. You know it’s configurable, right?

formatting link

During my attempt to run bookworm over the last 3 months I had the problem of the wifi dropping as well. Couldn't be arsed to find out why. Real life gets in the way. My Hammer / nut solution is run a cron job every 5 min. If I can't ping the router then sleep 10 If I still can't ping the router sleep 20 If I still can't ping the router sleep 30 If I still can't ping the router reboot.

I suspect this won't help you but all my pi zeroes are headless and this does (did) work. See my bookworm resolution in the other thread.

This is a very poor solution. If you must do an automatic reboot when network connectivity fails, install and configure the watchdog package.

Getting to the bottom of the problem is the best thing to do.

---druk

“Have you tried turning it off and on again?” is something they do in the Windows world, we try to avoid that in the Linux world.

Apropos that, since the more powerful power supply, my Bookworm on the PXZW has been rock solid on Wifi.

...make that PZ2W..I plead BC - Before Caffeine

Oddly the name I gave to the script was lan_watchdog :-) Don't need it now. I'm back on buster and the wifi is solid.

I'm happy to just accept that someone somewhere sometime fscked up and broke it. I wouldn't be at all surprised if they now stand in a dole queue next to someone from Crowdstrike. :-!

OMG. I was going to say I haven't touched a windows machine this century. Then I realised we're only 3 months from being 1/4 the way through it. 2025 already! Where did the time go and why didn't I enjoy it more?

Yeah. The 21st century began in 2000. Don’t listen to those who try to say it didn’t start until 2001.

For me, this century has been my journey away from being an Apple Mac enthusiast/expert/fanatic to being a Linux enthusiast/somewhat-expert/ slightly-fanatic.

There's no year zero. So the first century didn't start until the year

  1. :-p

do you have NTP configured and do you have networkmanager in use?

If not get them running and see if it solved the issues.

(been there seen it all)

BR

Hard to get NTP to run without a network connection

My PICO pi Ws dont even have calendar clocks, and they connect OK. Let me list all the things that people have said f***ed up their wifi on PI Zeros Ws...and other Pis...

- power saving mode (one existing Pi Zero W had it, the other did not. No difference connecting to same wifi access point)

- different wifi chipset (eventually I discovered all my pis were running the same chipset)

- interference from HDMI (Headless. HDMI disabled)

- random allocation of MAC addresses. (disabled - no difference)

- No NTP configured (you) [always configured by me anyway]

- network manager not running (you) [it's part of the default bookworm installation]

- various odd 802.11 modes on their router.. (my other two Pis connected to my main wifi point just fine. I changed the Pi to run on a different one and the problem persisted)

- crappy power supply (me, and others) [ changing the power supply has resulted in no drops since connected to any WiFi access point]

(pifi2:~ $ uptime 11:52:12 up 1 day, 22:49, 2 users, load average: 0.00, 0.00, 0.00

That now running against the access point that it had when dropping out at least once every 24 hours

I will leave it a few more days to make sure...)

As you can see I went through *every single one*.

And fixed it one way or another, (I didn't worry about ntp: If I am running linux on a network there is no way that wont be enabled by me, and Bookworm defaults to network manager anyway, so that is also default)

The *only* one that actually fixed the problem and made Bookworm Pi Z 2W as rock stable as all my other Pi's was putting a larger PSU on it.

I am not saying that other people's problems are the same cause, but I am saying that hairy ass guesses are simply no substitute for trying

*all* of the above systematically.

Because the log files - systemd or otherwise -, are simply full of useless detail. There to help the programmer debug his code, not to help Joe Ordinary find out why his wifi is f***ed.

For us, its a matter of trial and error until a stable system is arrived at.

Now my *conjecture* is that both a Zero 2W, a Pi 5 and indeed Bookworm on it, use more power. And a marginal PSU will fail more readily, and the wifi is the first point of failure

Because this problem is not in general related to Bookworm on any other platform. And the wifi chips themselves are pretty much the same

But in the end, my original thread was not 'give me your hairy assed guesses' but 'how do I solve this issue algorithmically'

And the answer was that the log files were useless, and trial and error and eliminating one issue at a time was the only pragmatic approach.

And everyone had a 'this worked for me' fix and none of them were the same.

Now I too have a 'this worked for me' fix, but I *also* have a pragmatic approach to bug hunting this one.

So how many years are there in a century? Does it depend on which century it is?

It goes from 1 to 100 for the first century. Then 101 to 200.

1 2 3 4 5 6 7 8 9 10 .. .. .. 91 92 93 94 95 96 97 98 99 100

No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or

100(n+1) BCE to 100n+1 BCE inclusive).

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required