Description of problem: This was after a vanilla install of motion (and zomeminder in order to compare the two. Not sure why motion is using zomeminder labels. The one camera in the system is /dev/video0 and is a USB camera (Logitech C920). Motion seems to run when started from the command line with "motion -s". It is only the systemd started instance that has the problem. SELinux is preventing /usr/bin/motion from 'listen' accesses on the tcp_socket . ***** Plugin catchall_boolean (89.3 confidence) suggests ******************* If you want to allow system to run with NIS Then you must tell SELinux about this by enabling the 'nis_enabled' boolean. You can read 'zoneminder_selinux' man page for more details. Do setsebool -P nis_enabled 1 ***** Plugin catchall (11.6 confidence) suggests *************************** If you believe that motion should be allowed listen access on the tcp_socket by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep motion /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:zoneminder_t:s0 Target Context system_u:system_r:zoneminder_t:s0 Target Objects [ tcp_socket ] Source motion Source Path /usr/bin/motion Port <Unknown> Host (removed) Source RPM Packages motion-3.3.0-trunkREV557.11.fc19.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-74.10.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.11.6-200.fc19.x86_64 #1 SMP Fri Oct 18 22:34:18 UTC 2013 x86_64 x86_64 Alert Count 1809 First Seen 2013-10-25 15:40:15 PDT Last Seen 2013-10-25 16:38:19 PDT Local ID 1fb29741-92a8-45db-80fe-7e3b52775d7b Raw Audit Messages type=AVC msg=audit(1382744299.213:1714): avc: denied { listen } for pid=13066 comm="motion" laddr=127.0.0.1 lport=8081 scontext=system_u:system_r:zoneminder_t:s0 tcontext=system_u:system_r:zoneminder_t:s0 tclass=tcp_socket type=SYSCALL msg=audit(1382744299.213:1714): arch=x86_64 syscall=listen success=no exit=EACCES a0=6 a1=a a2=7f0674000040 a3=74726f7020312e30 items=0 ppid=1 pid=13066 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=motion exe=/usr/bin/motion subj=system_u:system_r:zoneminder_t:s0 key=(null) Hash: motion,zoneminder_t,zoneminder_t,tcp_socket,listen Additional info: reporter: libreport-2.1.8 hashmarkername: setroubleshoot kernel: 3.11.6-200.fc19.x86_64 type: libreport
Hi, Yes, We know about problem with motion, and we fixed this for F20. Miroslav, Should we back port motion policy to F19?
Yes, I would back port it because the policy is wrong in F19 and it looks it works fine in F20.
good, I'm going to back port it.
commit aa4386dfe47b37642b7e5dc15f8c4d2086b80674 Author: Lukas Vrabec <lvrabec> Date: Tue Oct 29 13:16:29 2013 +0100 Update zoneminder policy commit 105a2940da5cbfb66482f6020d3f97da5836f6f4 Author: Lukas Vrabec <lvrabec> Date: Tue Oct 8 15:14:20 2013 +0200 Add policy for motion service
selinux-policy-3.12.1-74.12.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-74.12.fc19
Package selinux-policy-3.12.1-74.12.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-74.12.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20980/selinux-policy-3.12.1-74.12.fc19 then log in and leave karma (feedback).
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.