Description of problem: When jobs are running under pbs_server, an attempt to change server loglevel through qmgr causes qmgr to silently abort. When no jobs are running, qmgr changes the loglevel as expected. Version-Release number of selected component (if applicable): pbs_server 3.0.4 How reproducible: Always Steps to Reproduce: 1. Run some jobs using pbs_server 2. Issue the 'set server log_level' command to qmgr: [root@sc1 torque]# qmgr Max open servers: 10239 Qmgr: set server log_level=0 [root@sc1 torque] Actual results: qmgr aborts with no messages (note: log level was at 7; nothing appeared even in the server logs). When the running jobs complete, qmgr behaves normally: [root@sc1 torque]# qmgr Max open servers: 10239 Qmgr: set server log_level=0 Qmgr: set server log_level=1 Qmgr: set server log_level=0 Qmgr: list server @localhost Server localhost server_state = Active scheduling = True total_jobs = 1 state_count = Transit:0 Queued:0 Held:0 Waiting:0 Running:1 Exiting:0 acl_hosts = sc1.snu.ac.kr,kaya,localhost log_events = 511 mail_from = adm resources_assigned.nodect = 1 scheduler_iteration = 600 node_check_rate = 150 tcp_timeout = 6 log_level = 0 pbs_version = 3.0.4 next_job_number = 541 net_counter = 2 1 0 Expected results: I don't understand the server architecture well enough to know exactly what is feasible - there may be some deep reason why the log level can't be changed while jobs are running. So I can only suggest a range of behaviours: Ideal: qmgr changes the log level under all conditions. Good: qmgr gives an error message about the command, and continues Acceptable: qmgr gives an error message that the command can't be executed, then aborts Marginal: qmgr gives a warning before attempting to execute the command, and aborts when it fails Unacceptable: qmgr simply aborts
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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.
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.