Bug#989781: docker.io: Docker fails to run containers because it unsuccessfully tries to load an AppArmor profile
Package: docker.io Version: 20.10.5+dfsg1-1+b3 Severity: important Dear Maintainer, After installing docker.io on a Debian machine with a 'default' AppArmor installation, I am unable to run containers. The error message I get is as follows: Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: error: exec: "apparmor_parser": executable file not found in $PATH It appears that Docker tries to load an AppArmor profile, but fails to do so because I do not have the AppArmor userspace utilities installed, because I am not actually using AppArmor (nor do I intend to). However, because AppArmor is included/enabled in the kernel shipped by Debian by default, Docker thinks it needs to load a profile. I am not sure of the proper way to deal with this issue. Should I install the AppArmor userspace utilities, even though I do not need them myself? Or should I disable AppArmor completely by explicity setting a kernel parameter (which the Debian wiki does not recommend)? In the former case, docker.io should probably depend on the apparmor package (it is currently a recommendation), since Docker is not usable (as far as I understand) without it. Thanks in advance, Lars -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-2-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.118 ii containerd 1.4.5~ds1-1+b2 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc62.31-12 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libsystemd0 247.3-5 ii lsb-base 11.1.0 ii runc 1.0.0~rc93+ds1-5+b1 ii tini 0.19.0-1 Versions of packages docker.io recommends: pn apparmor ii ca-certificates 20210119 pn cgroupfs-mount ii git 1:2.30.2-1 ii needrestart 3.5-4 ii xz-utils 5.2.5-2 Versions of packages docker.io suggests: pn aufs-tools ii btrfs-progs5.10.1-2 pn debootstrap pn docker-doc ii e2fsprogs 1.46.2-1 pn rinse pn rootlesskit ii xfsprogs 5.10.0-4 pn zfs-fuse | zfsutils-linux -- no debconf information
Bug#954272: Missing mpi_pmix.so
Hi,
After updating, the interface between SLURM and MPI broke again...
This time, it looks like pmix support is completely missing.
# strace srun ./a.out 2>&1 | grep pmix
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/mpi_pmix.so", 0x7ffe65c74160) = -1
ENOENT (No such file or directory)
write(2, "srun: error: Couldn't find the s"..., 87srun: error: Couldn't find
the specified plugin name for mpi/pmix looking at all files
write(2, "srun: error: cannot find mpi plu"..., 49srun: error: cannot find mpi
plugin for mpi/pmix
write(2, "srun: error: cannot create mpi c"..., 52srun: error: cannot create
mpi context for mpi/pmix
write(2, "srun: error: invalid MPI type 'p"..., 70srun: error: invalid MPI type
'pmix', --mpi=list for acceptable types
It appears that SLURM is looking for `mpi_pmix.so`, which does not
exist. Has this been moved to a different package maybe?
Regards,
Lars
Bug#954272: Broken again
It's broken once again. While previously this was fixed by installing `libpmix-dev` which symlinked `/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so` to `libpmix.so.2`, the directory `/usr/lib/x86_64-linux-gnu/pmix/` does not exist anymore on my machine. Only `/usr/lib/x86_64-linux-gnu/pmix2/` exists, yet srun is still looking at `/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so`. I fixed it manually for now by creating the `/usr/lib/x86_64-linux-gnu/pmix/` directory again and symlinking `/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so` to `/usr/lib/x86_64-linux-gnu/pmix2/lib/libpmix.so`. Regards, Lars signature.asc Description: OpenPGP digital signature
Bug#954272: slurmd: SLURM not working with OpenMPI
On 20-07-2020 16:27, Alastair McKinstry wrote:
On 20/07/2020 14:52, Lars Veldscholte wrote:
Hi,
I believe I have found a solution.
I must confess that I still don't fully understand the difference
between the various PMI APIs, and which ones are supported by OpenMPI,
but I found that the recommended way is to use PMIx.
However, PMIx was not working on my system even though libpmix2 is
installed:
# srun --mpi pmix ./a.out
srun: error: (null) [0] /mpi_pmix.c:133 [init] mpi/pmix: ERROR:
pmi/pmix: can not load PMIx library
srun: error: Couldn't load specified plugin name for mpi/pmix: Plugin
init() callback failed
srun: error: cannot create mpi context for mpi/pmix
srun: error: invalid MPI type 'pmix', --mpi=list for acceptable types
Running `strace srun --mpi=pmix ./a.out` revealed that SLURM is
looking for the pmix library at
`/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so`, which does not exist,
only `libpmix.so.2` exists.
Which code is trying to load libpmix.so ? The compiled code should be
loading libpmix.so.2 directly; the libpmix.so should only be needed
at build-time.
srun is, I suppose. I've attached the entire strace output in case it's
of any help.
Perhaps the problem is that libpmix-dev is not installed at compile
time. I can add it as a Dependency of libopenmpi-dev.
Installing the package `libpmix-dev` installs this library (it
symlinks it to the same file `libpmix.so.2` is symlinked to).
Now, `srun --mpi=pmix ./a.out` is working!
I'm not 100% sure, but I think that the package `libpmix2` should also
install the file `libpmix.so`. The dev package shouldn't be required
for that, right?
Lars
Regards
Alastair
Regards,
Lars
# strace srun --mpi=pmix_v3 ./a.out
execve("/usr/bin/srun", ["srun", "--mpi=pmix_v3", "./a.out"], 0x7ffd4f380370 /*
17 vars */) = 0
brk(NULL) = 0x563aea4e4000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD,
"/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64/x86_64/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64/x86_64", 0x7ffe2154f320) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64", 0x7ffe2154f320) = -1
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/x86_64", 0x7ffe2154f320) = -1
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/tls/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/tls", 0x7ffe2154f320) = -1 ENOENT (No
such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64/x86_64/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64/x86_64", 0x7ffe2154f320) = -1
ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64", 0x7ffe2154f320) = -1 ENOENT
(No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm/x86_64", 0x7ffe2154f320) = -1 ENOENT
(No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/slurm-wlm/libz.so.1",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/x86_64-linux-gnu/slurm-wlm", {st_mode=S_IFDIR|0755,
st_size=20480, ...}) = 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=34055, ...}) = 0
mmap(NULL, 34055, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2eddeec000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libz.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0203\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=113088, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2eddeea000
mmap(NULL, 115088, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f2eddecd000
mprotect(0x7f2edded, 98304, PROT_NONE) = 0
mmap(0x7f2edded, 69632, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000)
Bug#954272: slurmd: SLURM not working with OpenMPI
Hi, I believe I have found a solution. I must confess that I still don't fully understand the difference between the various PMI APIs, and which ones are supported by OpenMPI, but I found that the recommended way is to use PMIx. However, PMIx was not working on my system even though libpmix2 is installed: # srun --mpi pmix ./a.out srun: error: (null) [0] /mpi_pmix.c:133 [init] mpi/pmix: ERROR: pmi/pmix: can not load PMIx library srun: error: Couldn't load specified plugin name for mpi/pmix: Plugin init() callback failed srun: error: cannot create mpi context for mpi/pmix srun: error: invalid MPI type 'pmix', --mpi=list for acceptable types Running `strace srun --mpi=pmix ./a.out` revealed that SLURM is looking for the pmix library at `/usr/lib/x86_64-linux-gnu/pmix/lib/libpmix.so`, which does not exist, only `libpmix.so.2` exists. Installing the package `libpmix-dev` installs this library (it symlinks it to the same file `libpmix.so.2` is symlinked to). Now, `srun --mpi=pmix ./a.out` is working! I'm not 100% sure, but I think that the package `libpmix2` should also install the file `libpmix.so`. The dev package shouldn't be required for that, right? Lars signature.asc Description: OpenPGP digital signature
Bug#954272: slurmd: SLURM not working with OpenMPI
Hello Gennaro, On 2020-03-24 00:54, Gennaro Oliva wrote: Hi Lars, On Thu, Mar 19, 2020 at 03:16:15PM +0100, Lars Veldscholte wrote: A simple test like `srun hostname` works, even on multiple cores. However, when trying to use MPI, it crashes with the following error message: *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, ***and potentially your MPI job) This happens even in the most simple "Hello World" case, as long as the program is MPI-enabled. I am trying to use OpenMPI (4.0.2) from the Debian repositories. `srun --mpi list` returns: srun: MPI types are... srun: openmpi srun: pmi2 srun: none I have tried all options, but the result is the same in all cases. Maybe this is user error, as this is my first time setting up SLURM, but I have not been able to find any possible causes/solutions and I am kind of stuck at this point. I don't know why srun doesn't execute openmpi directly, and I'll try to investigate this issue but as a workaround you can use both sbatch and salloc as in [1]: salloc -n 4 mpirun mympiprogram ... or sbatch -n 4 mympiprogram.sh where mympiprogram.sh is something like: #!/bin/sh mpirun mympiprogram ... Notice you don't need to specify the number of processes to mpirun, as it takes it from SLURM. [1] https://www.open-mpi.org/faq/?category=slurm Best regards, Thanks a lot, this seems to be working! I hadn't realised that you could simply use mpirun instead of srun inside salloc/sbatch. Regards, Lars signature.asc Description: OpenPGP digital signature
Bug#954272: slurmd: SLURM not working with OpenMPI
Package: slurmd Version: 19.05.3.2-2+b1 Severity: important Dear Maintainer, I am trying to get SLURM working on a single node. I have installed and configured slurmd and slurmctld. A simple test like `srun hostname` works, even on multiple cores. However, when trying to use MPI, it crashes with the following error message: *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, ***and potentially your MPI job) This happens even in the most simple "Hello World" case, as long as the program is MPI-enabled. I am trying to use OpenMPI (4.0.2) from the Debian repositories. `srun --mpi list` returns: srun: MPI types are... srun: openmpi srun: pmi2 srun: none I have tried all options, but the result is the same in all cases. Maybe this is user error, as this is my first time setting up SLURM, but I have not been able to find any possible causes/solutions and I am kind of stuck at this point. Regards, Lars -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-3-amd64 (SMP w/64 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages slurmd depends on: ii libc62.30-2 ii libhwloc15 2.1.0+dfsg-4 ii liblz4-1 1.9.2-2 ii libnuma1 2.0.12-1+b1 ii libpam0g 1.3.1-5 ii lsb-base 11.1.0 ii munge0.5.13-2+b1 ii openssl 1.1.1d-2 ii slurm-wlm-basic-plugins 19.05.3.2-2+b1 ii ucf 3.0038+nmu1 ii zlib1g 1:1.2.11.dfsg-2 slurmd recommends no packages. slurmd suggests no packages. -- no debconf information
Bug#834551: redis-server: Redis fails to start directly after install
Hi Chris, Did you spot this? Isn't "Stale file handle" something to do with NFS...? I've not seen it in many years.. Does that ring any bells for your configuration? That was it... I had a stale NFS mount somewhere in /mnt/. After unmounting the NFS mount, Redis starts up without any problems. I don't get why this (seemingly unrelated) issue caused Redis to fail to start though. If I manually run /usr/bin/redis-server /etc/redis/redis.conf, Redis starts up fine, which made me believe this is a problem with the init script. Well, you are running systemd and we ship a .service file so you are not even touching the legacy initscript.. *g* By "init script" I meant the systemd service file of course, not a legacy sysvinit init script. Sorry if I was unclear. Anyway, thanks a lot for your help. And sorry for wasting your time on something that was not a bug after all... Regards, Lars signature.asc Description: OpenPGP digital signature
Bug#834551: redis-server: Redis fails to start directly after install
Thanks for the quick response. That's weird. I got this error right after (during, in fact) the install, before I could have made any configuration errors, so I didn't expect this to be unreproducible. This is the full output from journalctl -xe: -- Unit redis-server.service has begun starting up. Aug 17 01:52:52 illium systemd[14621]: redis-server.service: Failed at step NAMESPACE spawning /bin/run-parts: Stale file handle -- Subject: Process /bin/run-parts could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /bin/run-parts could not be executed and failed. -- -- The error number returned by this process is 116. Aug 17 01:52:52 illium systemd[14686]: redis-server.service: Failed at step NAMESPACE spawning /usr/bin/redis-server: Stale file handle -- Subject: Process /usr/bin/redis-server could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /usr/bin/redis-server could not be executed and failed. -- -- The error number returned by this process is 116. Aug 17 01:52:52 illium systemd[1]: redis-server.service: Control process exited, code=exited status=226 Aug 17 01:52:52 illium systemd[1]: Failed to start Advanced key-value store. -- Subject: Unit redis-server.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit redis-server.service has failed. -- -- The result is failed. Aug 17 01:52:52 illium systemd[1]: redis-server.service: Unit entered failed state. Aug 17 01:52:52 illium systemd[1]: redis-server.service: Failed with result 'exit-code'. Aug 17 01:52:52 illium systemd[1]: redis-server.service: Service hold-off time over, scheduling restart. Aug 17 01:52:52 illium systemd[1]: Stopped Advanced key-value store. -- Subject: Unit redis-server.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit redis-server.service has finished shutting down. Aug 17 01:52:52 illium systemd[1]: redis-server.service: Start request repeated too quickly. Aug 17 01:52:52 illium systemd[1]: Failed to start Advanced key-value store. -- Subject: Unit redis-server.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit redis-server.service has failed. -- -- The result is failed. If I manually run /usr/bin/redis-server /etc/redis/redis.conf, Redis starts up fine, which made me believe this is a problem with the init script. When I researched the error given (code=exited status=226) I found something about /var/tmp/ being symlinked to /tmp/ which can cause the problem. I thought maybe the same thing extended to /var/run/ (which is symlinked to /run/ on my machine) but changing the line ReadWriteDirectories=-/var/run/redis to ReadWriteDirectories=-/run/redis did not solve my problem. If you need more info let me know :) Regards, Lars signature.asc Description: OpenPGP digital signature
Bug#834551: redis-server: Redis fails to start directly after install
Package: redis-server Version: 2:3.2.3-1 Severity: important Dear Maintainer, On a system on which Redis hasn't been installed before, Redis fails to start directly after install: Created symlink /etc/systemd/system/redis.service â /lib/systemd/system/redis-server.service. Created symlink /etc/systemd/system/multi-user.target.wants/redis-server.service â /lib/systemd/system/redis-server.service. Job for redis-server.service failed because the control process exited with error code. See "systemctl status redis-server.service" and "journalctl -xe" for details. invoke-rc.d: initscript redis-server, action "start" failed. â redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2016-08-17 01:13:49 CEST; 13ms ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 14426 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=226/NAMESPACE) Process: 14389 ExecStartPre=/bin/run-parts --verbose /etc/redis/redis-server.pre-up.d (code=exited, status=226/NAMESPACE) Aug 17 01:13:49 illium systemd[1]: Failed to start Advanced key-value store. Aug 17 01:13:49 illium systemd[1]: redis-server.service: Unit entered faile...e. Aug 17 01:13:49 illium systemd[1]: redis-server.service: Failed with result...'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package redis-server (--configure): Trying to start redis manually after dpkg exited result in the same error. This is probably an error in the init script? -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages redis-server depends on: ii adduser 3.115 ii init-system-helpers 1.42 ii libc62.23-4 ii libjemalloc1 3.6.0-9 ii redis-tools 2:3.2.3-1 redis-server recommends no packages. redis-server suggests no packages. -- Configuration Files: /etc/redis/redis.conf [Errno 13] Permission denied: u'/etc/redis/redis.conf' -- no debconf information
Bug#740560: sslh fails to start with systemd as PID=1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I just encountered the same problem. After I manually run "mkdir /var/run/sslh" it starts up fine, but after a reboot the directory is gone again. Thanks, Lars Veldscholte -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJTzVR8AAoJEFI9vWcHW6q4iwYH/1x8mqa0r4FcdRSKt831Y2hP yRBcpeBiQuYuqWUCatYC+DT4T4le2IGu8XV8SvjUyzg8EVVyz8cR8MAoA6xeZzlU rfhzIOIUz4S4XVkCuoJze6SMrlpI/Ioor0SsbyWOPJSpXgZvk8LsLcuJRvv9uCjY MK/3lY3AifJrEGCdbBEJdDAQIRwj1fnAu0VUZ8FgjBerOtTbEioWdm+Ar6CeomA8 BbaOSqhdNIgdbfqMTGyKt0z1NqJ883oWTV01ljZeIxQ9Koh9E8xeCdvkLH9jspDI NYWpywDusooD4kkMfoxsCle58j5vo2W/LP5H3FusYvRt9V/ufCQP7bf96qxfpcw= =g1kz -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754384: php5-fpm: Apache2 + php5-fpm using fastcgi breaks after upgrading to 5.6.0~rc2+dfsg-1
Alright, I'm using mod_proxy_fcgi and mod_proxy_handler now and I ditched mod_fastcgi. Although I had to compile mod_proxy_handler myself because it is not in the Debian package repos and Apache is still on 2.4.9 (both in testing and sid), it is not difficult at all if you use apxs2. I use it with UDS and if you configure it like in David's example, it works great. Also, no problems with mod_rewrite and such (which you do have if you use mod_proxy_fcgi with ProxyPass). I also upgraded to PHP 5.6.0~rc2+dfsg-1 again, and I have no issues with it. I recommend anyone hit by this bug to switch from mod_fastcgi to mod_proxy_handler. signature.asc Description: OpenPGP digital signature
Bug#754384: php5-fpm: Apache2 + php5-fpm using fastcgi breaks after upgrading to 5.6.0~rc2+dfsg-1
OK, so mod_fastcgi is deprecated. If I switch to mod_proxy_fcgi with mod_proxy_handler like this: SetHandler "proxy:fcgi://127.0.0.1:9000/" I won't have the problems I encountered when I used mod_proxy_fcgi with mod_proxy, right? (Like this:) ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9000/path/to/your/documentroot/$1 If so, I guess I'm gonna try that. signature.asc Description: OpenPGP digital signature
Bug#754384: [php-maint] Bug#754384: php5-fpm: Apache2 + php5-fpm using fastcgi breaks after upgrading to 5.6.0~rc2+dfsg-1
I was actually a bit surprised my self because most information sources on the internet indeed say that mod_fastcgi isn't supported with Apache 2.4, but mod_fastcgi is in the Debian packages and it installs and works just fine. I didn't compile the module myself, I just installed it from the Debian package manager. I'm not sure what you mean with mod_fastcgi info being unsupported due to licensing issues. You mean that the package is removed and no longer available now? That's a shame. Thanks for your advice but unfortunately, mod_proxy_fcgid is not a viable option for me. I actually tried it before I went with mod_fastcgi, but it has a lot of issues. You need to configure it for every vhost separately, and it only works with URLs ending on *.php (so http://site.com/ will fail, only http://site.com/index.php works), among some other issues I can't exactly remember anymore. I checked the permissions on /var/run/php5-fpm.sock, and they are as they should be (www-data:www-data). I tried to use a TCP socket as well, but that didn't work either. More debugging info, well, I checked the logs but php5-fpm wasn't outputting any weird things, the only errors I found was the error in Apache's error log I put in the last mail. If I can help you with any other debugging info, let me know :) Again thanks for helping me. Ondřej Surý schreef op 10/07/2014 16:20: > Control: tags -1 + moreinfo > Control: severity -1 normal > > I am sorry, but you are using mod_fastcgi info that is unsupported on > Debian due non-DFSG-free licensing[0]. > > Moreover the mod_fastcgi doesn't support Apache 2.4 yet. And I have > tried to compile the module with some custom ap2.4 patches, but I have > failed to compile the module. > > On the other hand I can confirm that the php5-fpm works with nginx and > mod_proxy_fcgid[2] in a clean sid chroot. > > Do you have correct permissions on /var/run/php5-fpm.sock? Or perhaps > you can provide more debugging information? > > Personally I would suggest to switch to mod_proxy_fcgi in apache2.4 > since it's supported by Apache itself, but I will do my best to fix your > error if you can provide enough information to be able to debug it and > fix it. > > 0. https://lists.debian.org/debian-legal/2000/12/msg00109.html > 1. > http://www.howtoforge.com/installing-nginx-with-php5-and-php-fpm-and-mysql-support-lemp-on-debian-wheezy > 2. https://wiki.apache.org/httpd/PHP-FPM > > O. > > On Thu, Jul 10, 2014, at 15:13, Lars Veldscholte wrote: >> Package: php5-fpm >> Version: 5.6.0~beta4+dfsg-4 >> Severity: grave >> Justification: renders package unusable >> >> Dear Maintainer, >> >> After I upgraded php5 from 5.6.0~rc1+dfsg-1 to 5.6.0~rc2+dfsg-1, I >> noticed php didn't work anymore. I use Apache 2.4 with php5-fpm using >> fastcgi. This is my fastcgi config: >> >> AddHandler php5-fcgi .php >> Action php5-fcgi /php5-fcgi >> Alias /php5-fcgi /usr/lib/cgi-bin/php5-fcgi >> FastCgiExternalServer /usr/lib/cgi-bin/php5-fcgi -socket >> /var/run/php5-fpm.sock -pass-header Authorization >> >> After the upgrade, every PHP page displays "file not found" and I get >> this error in /var/log/apache2/error.log: >> >> FastCGI: server "/usr/lib/cgi-bin/php5-fcgi" stderr: Primary script >> unknown >> >> I downgraded to 5.6.0~beta4+dfsg-4 now and everything works as expected >> again. >> >> -- Package-specific info: >> Additional PHP 5 information >> >> PHP 5 SAPI (php5query -S): >> fpm >> cli >> >> PHP 5 Extensions (php5query -M -v): >> imap (Enabled for fpm by maintainer script) >> imap (Enabled for cli by maintainer script) >> curl (Enabled for fpm by maintainer script) >> curl (Enabled for cli by maintainer script) >> mysql (Enabled for fpm by maintainer script) >> mysql (Enabled for cli by maintainer script) >> pdo (Enabled for fpm by maintainer script) >> pdo (Enabled for cli by maintainer script) >> pdo_pgsql (Enabled for fpm by maintainer script) >> pdo_pgsql (Enabled for cli by maintainer script) >> snmp (Enabled for fpm by maintainer script) >> snmp (Enabled for cli by maintainer script) >> pdo_mysql (Enabled for fpm by maintainer script) >> pdo_mysql (Enabled for cli by maintainer script) >> mysqli (Enabled for fpm by maintainer script) >> mysqli (Enabled for cli by maintainer script) >> pdo_sqlite (Enabled for fpm by maintainer script) >> pdo_sqlite (Enabled for cli by maintainer script) >> sqlite3 (Enabled for fpm by maintainer script) >> sqlite3 (Enabled for cli by maintainer script) >>
Bug#754384: php5-fpm: Apache2 + php5-fpm using fastcgi breaks after upgrading to 5.6.0~rc2+dfsg-1
Package: php5-fpm Version: 5.6.0~beta4+dfsg-4 Severity: grave Justification: renders package unusable Dear Maintainer, After I upgraded php5 from 5.6.0~rc1+dfsg-1 to 5.6.0~rc2+dfsg-1, I noticed php didn't work anymore. I use Apache 2.4 with php5-fpm using fastcgi. This is my fastcgi config: AddHandler php5-fcgi .php Action php5-fcgi /php5-fcgi Alias /php5-fcgi /usr/lib/cgi-bin/php5-fcgi FastCgiExternalServer /usr/lib/cgi-bin/php5-fcgi -socket /var/run/php5-fpm.sock -pass-header Authorization After the upgrade, every PHP page displays "file not found" and I get this error in /var/log/apache2/error.log: FastCGI: server "/usr/lib/cgi-bin/php5-fcgi" stderr: Primary script unknown I downgraded to 5.6.0~beta4+dfsg-4 now and everything works as expected again. -- Package-specific info: Additional PHP 5 information PHP 5 SAPI (php5query -S): fpm cli PHP 5 Extensions (php5query -M -v): imap (Enabled for fpm by maintainer script) imap (Enabled for cli by maintainer script) curl (Enabled for fpm by maintainer script) curl (Enabled for cli by maintainer script) mysql (Enabled for fpm by maintainer script) mysql (Enabled for cli by maintainer script) pdo (Enabled for fpm by maintainer script) pdo (Enabled for cli by maintainer script) pdo_pgsql (Enabled for fpm by maintainer script) pdo_pgsql (Enabled for cli by maintainer script) snmp (Enabled for fpm by maintainer script) snmp (Enabled for cli by maintainer script) pdo_mysql (Enabled for fpm by maintainer script) pdo_mysql (Enabled for cli by maintainer script) mysqli (Enabled for fpm by maintainer script) mysqli (Enabled for cli by maintainer script) pdo_sqlite (Enabled for fpm by maintainer script) pdo_sqlite (Enabled for cli by maintainer script) sqlite3 (Enabled for fpm by maintainer script) sqlite3 (Enabled for cli by maintainer script) gd (Enabled for fpm by maintainer script) gd (Enabled for cli by maintainer script) pgsql (Enabled for fpm by maintainer script) pgsql (Enabled for cli by maintainer script) mysqlnd (Enabled for fpm by maintainer script) mysqlnd (Enabled for cli by maintainer script) pspell (Enabled for fpm by maintainer script) pspell (Enabled for cli by maintainer script) readline (Enabled for fpm by maintainer script) readline (Enabled for cli by maintainer script) json (Enabled for fpm by maintainer script) json (Enabled for cli by maintainer script) opcache (Enabled for fpm by maintainer script) opcache (Enabled for cli by maintainer script) mcrypt (Enabled for fpm by maintainer script) mcrypt (Enabled for cli by maintainer script) gmp (Enabled for fpm by maintainer script) gmp (Enabled for cli by maintainer script) intl (Enabled for fpm by maintainer script) intl (Enabled for cli by maintainer script) Configuration files: [PHP] engine = On short_open_tag = Off asp_tags = Off precision = 14 output_buffering = On zlib.output_compression = Off implicit_flush = Off unserialize_callback_func = serialize_precision = 17 disable_functions = pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, disable_classes = zend.enable_gc = On expose_php = On max_execution_time = 30 max_input_time = 60 memory_limit = 128M error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT display_errors = Off display_startup_errors = Off log_errors = On log_errors_max_len = 1024 ignore_repeated_errors = Off ignore_repeated_source = Off report_memleaks = On track_errors = Off html_errors = On variables_order = "GPCS" request_order = "GP" register_argc_argv = Off auto_globals_jit = On post_max_size = 8M auto_prepend_file = auto_append_file = default_mimetype = "text/html" default_charset = "UTF-8" doc_root = user_dir = enable_dl = Off file_uploads = On upload_max_filesize = 2M max_file_uploads = 20 allow_url_fopen = On allow_url_include = Off default_socket_timeout = 60 [CLI Server] cli_server.color = On [Date] [filter] [iconv] [intl] [sqlite] [sqlite3] [Pcre] [Pdo] [Pdo_mysql] pdo_mysql.cache_size = 2000 pdo_mysql.default_socket= [Phar] [mail function] SMTP = localhost smtp_port = 25 mail.add_x_header = On [SQL] sql.safe_mode = Off [ODBC] odbc.allow_persistent = On odbc.check_persistent = On odbc.max_persistent = -1 odbc.max_links = -1 odbc.defaultlrl = 4096 odbc.defaultbinmode = 1 [Interbase] ibase.allow_persistent = 1 ibase.max_persistent = -1 ibase.max_links = -1 ibase.timestampformat = "%Y-%m-%d %H:%M:%S" ibase.dateformat = "%Y-%m-%d" ibase.timeformat = "%H:%M:%S" [MySQL] mysql.allow_local_infile = On mysql.allow_persistent = On mysql.cache_size = 2000 mysql.max_persistent = -1 mysql.max_links = -1 mysql.default_port = mysql.default_socket = mysql.default_host = mysql.default_user = mysql.default_password = mysql.connect_timeout = 60 mysql.trace_mode = Off [
