[03:26] <g4mbit> hey all
[03:26] <g4mbit> running a DHCP server with a config that looks like this: https://privatebin.net/?d994efb6551f2bf6#6rEUxQnmtXiK6myCrwvuTmYzzXBSLWHMv8AYcBMGQKNe
[03:27] <g4mbit> does anyone know why I need to specify a range for the network if I'm using a fixed address?
[03:27] <g4mbit> is providing a range required even if I want a static fixed address to be assigned?
[04:58] <yurtesen> good morning
[06:13] <cpaelzer> hi yurtesen
[06:14] <cpaelzer> and good morning everyone else as well
[07:06] <ivoks> g4mbit: yes, you need the range
[12:21] <YeOldHinnerk> Hi. I have 5 packages which are being held back when I do apt-get upgrade or distr-upgrade. The log isn't really that helpfull other than naming the packages. What should I do about it?
[12:23] <YeOldHinnerk> Also, I'm about to upgrade form ubuntu 20 LTS to ubuntu 22 lts, so I would like the system be 'clean' from a package point of view.
[12:23] <YeOldHinnerk> Having packages, which are being held back before an upgrade to 22 sounds unhealthy.
[12:23] <YeOldHinnerk> Maybe it isn't.
[12:24] <murmel> YeOldHinnerk: did you look if you have pinned packages?
[12:24] <YeOldHinnerk> what are pinned packages?
[12:27] <YeOldHinnerk> Huh, seems like the issue resolved itself.
[12:28] <YeOldHinnerk> Not the message does not appear anymore.
[13:18] <oerheks> some packages can be installed after reboot, or try sudo apt dist-upgrade
[13:18] <YeOldHinnerk> Did both. On first try, that didn't help. Eventually, it apparently did.
[13:30] <Maik> try full-upgrade
[13:31] <Maik> YeOldHinnerk: also, is that on the server?
[13:31] <YeOldHinnerk> As I said, the issue seems to have resolved itself. The message does not appear anymore.
[13:31] <YeOldHinnerk> Yes, on a server.
[13:55] <paride> ahasenack, hi! https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1787409 popped up in my triage. Do you confirm it should be marked Invalid?
[13:56] <ahasenack> I've seen there was an update, but didn't read it yet
[13:56] <ahasenack> let me take a look
[13:58] <tomreyn> YeOldHinnerk: you may want to list packages installed from a (now) unknown (to apt) repository:     apt list --installed | grep ',local]$'     # since those can cause complications. as well as security vulnerabilities.
[14:01] <ahasenack> paride: I think this fixed it: https://git.launchpad.net/ubuntu/+source/squid/commit/?id=665afbf87f5d32d587445ff54de41ad79de2efde
[14:02] <paride> ahasenack, looking, thanks
[14:08] <paride> ahasenack, bug updated
[14:21] <YeOldHinnerk> Ok, back with another question. I just performed an upgrade of ubuntu 20 lts to ubuntu 22 lts. Everything went fine.
[14:21] <YeOldHinnerk> System rebooted without issues.
[14:21] <YeOldHinnerk> But there seems to be an issue with apache2 configuration concernin php versions.
[14:22] <YeOldHinnerk> I'm running nextcloud, which support php 7.4
[14:22] <YeOldHinnerk> the new distr has 8.1 as standard
[14:22] <YeOldHinnerk> so i did a2dis php8.1 and a2enmod php7.4
[14:22] <YeOldHinnerk> now apache fails to start
[14:23] <YeOldHinnerk> My best guess is, that somewhere, there's a hardcoded version of a php module somewhere in the config and now it can't find that.
[14:23] <YeOldHinnerk> Shot in the blue, really.
[14:25] <YeOldHinnerk> if I use php8.1 Apache starts, but nextcloud comes up with error message about only supporting 7.4...
[14:27] <YeOldHinnerk> Hmmm, on nextcloud's HP they say that recommend 8.0 and works fine with 8.1
[14:30] <tomreyn> YeOldHinnerk: you probably have an old version of nextcloud installed then.
[14:30] <YeOldHinnerk> Well, I just very very recently did all updates on nextcloud
[14:31] <YeOldHinnerk> I was lastest, as per its admin pade.
[14:31] <YeOldHinnerk> page
[14:31] <YeOldHinnerk> and stable
[14:31] <YeOldHinnerk> I'm talking about like last weekend, when I did all updates.
[14:32] <tomreyn> were you latest on the major version you're following, or latest on the latest major version? (i don't know whether that's how nextcloud upgrades work, just guessing)
[14:32] <YeOldHinnerk> Upgrade of ubuntu today, nextcloud last weekend, to be clear.
[14:32] <YeOldHinnerk> Looked like major version to me, given then way the version number looked.
[14:33] <tomreyn> you should inspect apache httpd error logs to get an idea of why it would not start without php enabled
[14:33] <tomreyn> https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html does not list Ubuntu 22.04 LTS
[14:36] <tomreyn> are you using ppa:ondrej/php ? if so, it's always good to point this out.
[14:38] <YeOldHinnerk> php
[14:38] <YeOldHinnerk> when I try to run php occ -v I also get the error message about php 8.1 not being supported
[14:38] <YeOldHinnerk> php -v gives 8.1.2
[14:39] <tomreyn> you may want to seek support with this from nextcloud support
[14:40] <YeOldHinnerk> I just found a thread on this. I'll just unistall php8.1 for now and downgrade to 7.4
[14:40] <YeOldHinnerk> just get a running system back
[14:41] <YeOldHinnerk> then check on upgrades
[14:43] <YeOldHinnerk> Hmm, not sure I will carry through with that plan.
[14:43] <YeOldHinnerk> I'm a bit concerned, it may have sideeffects to downgrade.
[14:45] <YeOldHinnerk> seems to me, the a2dis... and a2enmod should have worked, right?
[14:46] <YeOldHinnerk> why is apache2 not doing that?
[14:46] <YeOldHinnerk> Is it still trying to load something from 8.1?
 you should inspect apache httpd error logs to get an idea of why it would not start without php enabled
[14:47] <tomreyn> this also goes for other error situations regarding apache httpd
[14:48] <tomreyn> generally speaking, ubuntu supports the php versions available in it's releases. downgrading or running other releases packages is not supported.
[14:48] <tomreyn> ppa's are not supported.
[14:49] <YeOldHinnerk> yes, I'd rather not mess with that
[14:49] <tomreyn> for the PPA I suspect you are using, ppa:ondrej/php, there is support available fro its maintainer https://deb.sury.org/#support
[14:49] <YeOldHinnerk> but apache should be able to use the version I enabled.
[14:51] <tomreyn> apache httpd should be able to use apache httpd modules which were built against its version.
[14:53] <tomreyn> when you plan ubuntu release upgrades, first make sure that the software you are running will be supported on the target release, and there is an upgrade path.
[14:55] <patdk-lap> it's so much easier to just run the nextcloud docker image
[14:56] <patdk-lap> suprised they don't support php 8.1 yet though, they required an upgrade to mysql 8 awhile back, but no mysql 8 support in aws yet, so that screwed me over
[14:56] <YeOldHinnerk> Uh.
[14:57] <YeOldHinnerk> That doesn't sound good.
[14:57] <YeOldHinnerk> Well, I did apt install php7.4 again, to be safe.
[14:57] <YeOldHinnerk> Then a2enmod php7.4 and aedismod php8.1
[14:57] <YeOldHinnerk> now when I start apache2 I get an error message that may be more helpful:
[14:58] <patdk-lap> would highly recommend using php-fpm vs mod-php
[14:59] <YeOldHinnerk> It points to apache2.config line 146 which has a syntax error? In that line mods-enables/*.load is added.
[14:59] <tomreyn> 8.1 is listed as supported on the server requirements link i posted above. but it could be wrong, of course, i don't have first hand experience with nextcloud
[14:59] <YeOldHinnerk> I never touched that and it looks fine to me.
[14:59] <YeOldHinnerk> Yes, I'm surpised there's an issue.
[14:59] <tomreyn> s/ server / system /
[15:00] <YeOldHinnerk> I'll ask in nextcloud.
[21:09] <athos> bryceh: thanks for the symfony review! \o/
[21:10] <bryceh> yep
[21:20] <giu--> hi
[22:00] <giu---> hi gschanuel