(04-21-2024, 11:53 AM)Tim Curtis Wrote: You will need to create a list of steps that I can follow in order to try repro the issue.

A 500 error means a line of code "blew up" and crashed the script. This is usually caused by mistakes in refactoring where variable or function names/parameters are changed.

(04-21-2024, 12:46 PM)popej Wrote: Looking at nginx log, maybe you could find something:

Code:

2024/04/21 14:19:22 [crit] 602#602: *1 connect() to unix:/run/php/php8.2-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.185, server: , request: "GET /engine-cmd.php?_=1713701981522 HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "192.168.1.8", referrer: "http://192.168.1.8/sys-config.php"
2024/04/21 14:19:24 [crit] 602#602: *1 connect() to unix:/run/php/php8.2-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.185, server: , request: "GET /engine-mpd.php?state=reconnect&_=1713701992056 HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "192.168.1.8", referrer: "http://192.168.1.8/sys-config.php"
2024/04/21 14:20:34 [error] 602#602: *1 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught TypeError: explode(): Argument #2 ($string) must be of type string, array given in /var/www/sys-config.php:462
Stack trace:
#0 /var/www/sys-config.php(462): explode()
#1 {main}
  thrown in /var/www/sys-config.php on line 462" while reading response header from upstream, client: 192.168.1.185, server: , request: "GET /sys-config.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "192.168.1.8", referrer: "http://192.168.1.8/index.php"
2024/04/21 14:24:23 [error] 602#602: *39 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught TypeError: explode(): Argument #2 ($string) must be of type string, array given in /var/www/sys-config.php:462
Stack trace:
#0 /var/www/sys-config.php(462): explode()
#1 {main}
  thrown in /var/www/sys-config.php on line 462" while reading response header from upstream, client: 192.168.1.185, server: , request: "GET /sys-config.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "192.168.1.8", referrer: "http://192.168.1.8/"

(04-20-2024, 08:26 PM)nosferatu_cat Wrote:

(04-20-2024, 07:18 PM)Tim Curtis Wrote:

(04-20-2024, 07:09 PM)nosferatu_cat Wrote: Just loaded the latest image on a Pi4 with an Allo Boss 2.  I'm assuming that the Boss 2 fix hasn't been implemented yet.  aplay-l shows the Allo HAT as the default audio device and trying to play a file results in an MPD error:

    "Failed to open "ALSA Default" (alsa); Failed to open ALSA device "_audioout": No such device."    

I also loaded it on a Pi 5 with USB audio out and it has worked well.  Looking forward to the production release.

The "Boss 2 fix" was done way back in kernel 6.1.35. If it's not working in Bookworm (kernel 6.6.20) then something else is wrong with the driver. Given that Allo is no longer maintaining their products its up to someone else to debug and possibly fix the driver.

Thanks.

(04-21-2024, 05:44 PM)fdealexa Wrote: Hi all,
I encountered a difficulty configuring the network (static addresses). After entering the parameters for both the etho and wlan0 interfaces, I, as usual, rebooted the system: the addresses do not change but the new parameters remain set; I also tried turning the system off and on again but the result doesn't change. It appears that the files "/etc/network/interfaces.d/eth0" and "/etc/network/interfaces.d/wlan0" are not created.
Do you think it could be a bug or did I do something wrong?
Thank you and best regards,
Francesco