Hi! I noticed that some permissions of /var/lib/torque/ subdirs are changed in the spec file : > # fix permissions for some directories in /var/lib/torque > chmod 755 `find %{buildroot}/var/lib/torque -type d` However, I think these subdirs should keep their initial permissions, because they're used in the context of the user running the job, not root: /var/lib/torque/spool /var/lib/torque/undelivered /var/lib/torque/checkpoint Without these modifications, we got errors like these on the exec node : Apr 28 13:26:31 linux29 pbs_mom: LOG_ERROR::Permission denied (13) in sys_copy, can't open /var/lib/torque/spool/rcperr.24708, error = 13 Permission denied Apr 28 13:26:31 linux29 pbs_mom: LOG_ERROR::Permission denied (13) in sys_copy, can't open /var/lib/torque/spool/rcperr.24708, error = 13 Permission denied Apr 28 13:26:35 linux29 pbs_mom: LOG_ERROR::Permission denied (13) in sys_copy, can't open /var/lib/torque/spool/rcperr.24708, error = 13 Permission denied Apr 28 13:26:35 linux29 pbs_mom: LOG_ERROR::sys_copy, command '/usr/bin/scp -rpB /var/lib/torque/spool/1189924.linux1.OU bellet@linux1:/misc/raid/bellet/tmp/test.o1189924' failed with status=12, giving up after 4 attempts Apr 28 13:26:35 linux29 pbs_mom: LOG_ERROR::req_cpyfile, Unable to copy file /var/lib/torque/spool/1189924.linux1.OU to bellet@linux1:/misc/raid/bellet/tmp/test.o1189924, error 12 Apr 28 13:26:35 linux29 pbs_mom: LOG_ERROR::No such file or directory (2) in req_cpyfile, Unable to rename /var/lib/torque/spool/1189924.linux1.OU to /var/lib/torque/undelivered/1189924.linux1.OU Apr 28 13:26:35 linux29 pbs_mom: LOG_ERROR::Permission denied (13) in sys_copy, can't open /var/lib/torque/spool/rcperr.24708, error = 13 Permission denied Apr 28 13:26:35 linux29 pbs_mom: LOG_ERROR::Permission denied (13) in sys_copy, can't open /var/lib/torque/spool/rcperr.24708, error = 13 Permission denied Apr 28 13:26:39 linux29 pbs_mom: LOG_ERROR::Permission denied (13) in sys_copy, can't open /var/lib/torque/spool/rcperr.24708, error = 13 Permission denied
torque-4.2.10-3.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/torque-4.2.10-3.el5
torque-4.2.10-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/torque-4.2.10-3.el6
torque-4.2.10-3.el7 has been submitted as an update for Fedora EPEL 7. https://admin.fedoraproject.org/updates/torque-4.2.10-3.el7
torque-4.2.10-3.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/torque-4.2.10-3.fc21
torque-4.2.10-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/torque-4.2.10-3.fc20
torque-4.2.10-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/torque-4.2.10-3.fc22
Package torque-4.2.10-3.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing torque-4.2.10-3.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-8544/torque-4.2.10-3.fc22 then log in and leave karma (feedback).
torque-4.2.10-3.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
torque-4.2.10-3.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
torque-4.2.10-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
torque-4.2.10-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
torque-4.2.10-3.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
torque-4.2.10-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.