Bug #78963 [Opn->Csd]: php-fpm-7.4.0 can't access devices
| From: | jeanmarc dot louviaux at gmail dot com | Date: | Sat, 21 Dec 2019 05:46:36 +0000 |
| Subject: | Bug #78963 [Opn->Csd]: php-fpm-7.4.0 can't access devices | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-224456@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=78963&edit=1
ID: 78963
User updated by: jeanmarc dot louviaux at gmail dot com
Reported by: jeanmarc dot louviaux at gmail dot com
Summary: php-fpm-7.4.0 can't access devices
-Status: Open
+Status: Closed
Type: Bug
Package: FPM related
Operating System: Arch
PHP Version: 7.4.0
Block user comment: N
Private report: N
New Comment:
see comment
Previous Comments:
------------------------------------------------------------------------
[2019-12-20 06:49:15] jeanmarc dot louviaux at gmail dot com
Hello,
You may close this bug as it is not related to php. The issue is related to Arch which now set 755
on /var/lock, thus some apps that request port com via php-fpm can't write /var/lock/LCK..
files.
It may be usefull :
Set PrivateDevices=false in php-fpm.service (thanks happypuzzle9)
via systemctl edit --full php-fpm.service
systemctl daemon-reload & systemctl restart php-fpm
And if 'http' can't write in /var/lock/
set the permissions to 777 into
cp /usr/lib/tmpfiles.d/legacy.conf /etc/tmpfiles.d/
nano /etc/tmpfiles.d/legacy.conf
systemctl restart systemd-tmpfiles-setup
------------------------------------------------------------------------
[2019-12-18 11:43:42] jeanmarc dot louviaux at gmail dot com
Thanks for your kind comment.
I am not the author of communication application but it seem ok to me to have port lock files there
(/var/lock/LCK..)
I don't mind if those files survive a reboot or not
------------------------------------------------------------------------
[2019-12-18 11:09:23] bugreports at gmail dot com
> I have set PrivateDevices=false
> but i also have to chmod 777 /run/lock/ to allow lock files from devices
would you mind not f**p your whole setup?
* nobody and nothing has a business to write directly to /run root-dir
* whatever you do below /run won#t survive a reboot
* learn basics like https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html
------------------------------------------------------------------------
[2019-12-18 10:19:47] jeanmarc dot louviaux at gmail dot com
Ok i get it
I have set PrivateDevices=false
but i also have to chmod 777 /run/lock/ to allow lock files from devices
Thanks
------------------------------------------------------------------------
[2019-12-16 10:47:44] happypuzzle9 at gmail dot com
thinks your url
```
[Service]
ProtectHome=false
```
I perfectly solved the problem of
home inaccessibility caused by upgrading from 7.3 to
7.4
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=78963
--
Edit this bug report at https://bugs.php.net/bug.php?id=78963&edit=1