upgrade Debian 11 to 12
-
@Sebastian-Roth Done
I haven’t had chance to look into it any further but it’s the initial bind function that fails. -
@Lee-Rowlett
So, does this mean that I’d better wait before updating my production server? -
@plegrand yes i would wait, i wouldn’t recommend updating your production server.
if you don’t rely on the LDAP plugin then everything else is functioning as it should but i still wouldn’t recommend it in a production environment.
-
@Lee-Rowlett said in upgrade Debian 11 to 12:
@plegrand yes i would wait, i wouldn’t recommend updating your production server.
if you don’t rely on the LDAP plugin then everything else is functioning as it should but i still wouldn’t recommend it in a production environment.
Would it be possible to tell me when it is reasonable to update, in this thread?
-
Hello,
I’m coming back to you regarding my initial request.
Has anyone of you tried to upgrade from Debian 11 (bullseye) to Debian 12 (bookworm) with FOG 1.5.10? -
@plegrand I have not had the time to test this myself but I can do so in about three weeks. The PHP issues with the LDAP plugin should be fixed in the dev-branch version (1.5.10.11).
-
@Sebastian-Roth
Hello, I’ll get back to you to know if, today, it’s possible to consider migrating our fog server from debian 11 bullseye to debian 12 bookworm (FOG 1.5.10).
Thank you in advance for your help. -
Hi, you can see here for my attempt :
https://forums.fogproject.org/topic/17083/installing-package-php-mysqlnd-failed/6?_=1701334310863&lang=fr -
I have just upgraded from Debian 11 to Debian 12.
No problems except this error in the apache logs:
[proxy:error] [pid 2033] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (127.0.0.1:9000) failed
and unable to access Fog.
I re-run “installfog.sh” and everything seems to be working correctly.
I don’t use LDAp so I don’t have any problems there.
Thanks -
@plegrand said in upgrade Debian 11 to 12:
127.0.0.1:9000
This is the communication port that apache talks to php-fpm (PHP Execution Engine). For some reason during the update php-fpm was not updated or failed to restart correctly.
Well done getting this resolved on your end.
