Finally started doing some bullseye to bookworm upgrades, first glitch is php-geoip's having disappeared (removed because of missing support for PHP 8). Will need to investigate what to do for #matomo…
Another problem is losing XMPP-based notifications because the (old, written in Perl) scripts suddenly error out, while the relevant libraries seem to have only received minimal packaging changes (mostly metadata).
Alright, for some reason, session information is missing on bookworm, meaning no session ID, and of course the “what does this thing support” question doesn't get a “yes I support SASL” hence the fallback to AuthIQAuth…
Alright, that's FUBAR. The connection is established, session information as well. Then xmpp-tls says we need to StartTLS, and there's absolutely no error handling, so we lose session information entirely, for unknown reasons, and with no warnings. No wonder the rest explodes.
To be honest, debugging, hopefully fixing, and extending life support for a Perl module last released in 2014 does sound very much less appealing than just reimplementing a few scripts in Python, which features several XMPP modules, released… this decade (this year even).
And restart takes ages, probably because that's now a Java-based thing. Maybe one day I'll get tired of those various #puppet annoyances, and move everything to #ansible…
Gotta enjoy the schizophrenia, with #puppet's erroring out because it doesn't find lookup_options in hiera.yaml, and https://www.puppet.com/docs/puppet/7/hiera_merging insisting on hiera.yaml's not being the place to set this key!!!
Error while evaluating a Function Call, Function Load Error for function 'eyaml_lookup_key': Lookup using eyaml lookup_key function is only supported when the hiera_eyaml library is present
The 300 lines of puppetserver log generated by a single puppet agent -t call (mostly call trace) makes me wonder whether hiera-eyaml and puppetserver are actually compatible in #bookworm…
@CyrilBrulebois I guess jruby doesn't like the packaged one for some reason, but I've not used Debians puppetserver yet at all. For mailalias there is at least puppet-module-puppetlabs-mailalias-core.
@zhenech I think I'll stay away from the “trying to understand the current state of puppet architecture and packaging” rabbit hole, but nice try interesting me into jumping!
Things could be said about the compared memory footprint between the deprecated default non-production server that worked so well for this < 20 hosts setup, and the new Java-based monster.
@zhenech I must confess I stopped when things looked like they worked again, and only noticed that while checking unrelated graphs… Thanks again for the excellent feedback, I'll try and work my way through your suggestions in the next few days.
Another weird issue: I'm no longer seeing regular IRC messages in #irssi, possibly some format thing changed and broke the theme I've been using for ~ 15 years or so. Back to the default one for the time being (and oh wow it's bad).
This is definitely weird as the irssi theme repository seems to have received almost no changes in many years (and I don't think my irssi config is very heavy). Time to debug then!
A trivial loop across all themes, minimizing the diff against my broken config says oscar.theme was the source for my custom theme; and there are many changes in placeholders/format strings! Switching back to the original, and if that works, problem solved!
Another problem is all the /load something.pl lines in ~/.irssi/startup are now failing, with each http://something.pl triggering an attempt to load a plugin (ELF shared object, .so).
Time to switch to /script load something.pl instead.
Add comment