# Dedicated\_time bug in 22.05.11?

**URL:** https://community.openpbs.org/t/dedicated-time-bug-in-22-05-11/3215
**Category:** Users/Site Administrators
**Created:** [July 19, 2022, 8:52pm UTC](https://community.openpbs.org/t/dedicated-time-bug-in-22-05-11/3215 "2022-07-19T20:52:36Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![coreyferrier](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@coreyferrier](https://community.openpbs.org/u/coreyferrier)
#### Post date: [July 19, 2022, 8:52pm UTC](https://community.openpbs.org/t/dedicated-time-bug-in-22-05-11/3215/1 "2022-07-19T20:52:36Z")

</div>

I’ve got an empty /var/spool/pbs/sched\_priv/dedicated\_time file, yet when I submit a test job, it will not run due to “Dedicated Time”.

07/19/2022 16:48:36;0100;pbs\_sched;Svr;;It is primetime. It will never end  
07/19/2022 16:48:36;0040;pbs\_sched;Job;10.pbs02;Dedicated Time  
07/19/2022 16:48:36;0080;pbs\_sched;Req;;Leaving Scheduling Cycle

[root@pbs02 sched\_priv]# pwd  
/var/spool/pbs/sched\_priv  
[root@pbs02 sched\_priv]# cat dedicated\_time  
[root@pbs02 sched\_priv]#

I’ve also tried setting dedicated\_time to some time in the past and some time in the future but get same result. I’ve HUP’d the sched daemon and also restarted PBS. No change.

Any ideas?

Thanks,  
Corey

---

<div class="post-metadata">

### Author: ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)
#### Post date: [July 20, 2022, 8:58am UTC](https://community.openpbs.org/t/dedicated-time-bug-in-22-05-11/3215/2 "2022-07-20T08:58:48Z")

</div>

Please share the contents of your dedicated time file .

---

<div class="post-metadata">

### Author: ![coreyferrier](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@coreyferrier](https://community.openpbs.org/u/coreyferrier)
#### Post date: [July 20, 2022, 10:20am UTC](https://community.openpbs.org/t/dedicated-time-bug-in-22-05-11/3215/3 "2022-07-20T10:20:39Z")

</div>

The dedicated\_time file is empty.

[root@pbs02 sched\_priv]# cat dedicated\_time  
[root@pbs02 sched\_priv]#

---

<div class="post-metadata">

### Author: ![coreyferrier](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@coreyferrier](https://community.openpbs.org/u/coreyferrier)
#### Post date: [July 20, 2022, 10:27am UTC](https://community.openpbs.org/t/dedicated-time-bug-in-22-05-11/3215/4 "2022-07-20T10:27:12Z")

</div>

I submit a job that never starts:

[coreyf@master ~]$ qsub -I -l select=1:ncpus=20:mem=250gb  
qsub (Warning): Interactive jobs will be treated as not rerunnable  
qsub: waiting for job 23.pbs02 to start

From the sched\_log:

07/20/2022 06:25:52;0080;pbs\_sched;Req;;Starting Scheduling Cycle

07/20/2022 06:25:52;0100;pbs\_sched;Svr;;It is primetime. It will never end

07/20/2022 06:25:52;0040;pbs\_sched;Job;23.pbs02;Dedicated Time

07/20/2022 06:25:52;0080;pbs\_sched;Req;;Leaving Scheduling Cycle

---

<div class="post-metadata">

### Author: ![coreyferrier](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@coreyferrier](https://community.openpbs.org/u/coreyferrier)
#### Post date: [July 20, 2022, 3:11pm UTC](https://community.openpbs.org/t/dedicated-time-bug-in-22-05-11/3215/5 "2022-07-20T15:11:25Z")

</div>

I was able to narrow the bug down to 3 lines in the sched\_config file. Six tests are shown here with the result. After each sched\_config file change pbs was restarted. The dedicated\_time file is empty.

You should be able to reproduce this too. I was using a fresh installation of OpenPBS with default configuration.

The test job is a simple “qsub -I”, default queue is “workq” as defined by the fresh install.

TEST 1. sched\_config:

#dedicated\_prefix: ded  
#primetime\_prefix: p\_  
#nonprimetime\_prefix: np\_

Result: Job does not run  
07/20/2022 10:40:39;0080;pbs\_sched;Req;;Starting Scheduling Cycle  
07/20/2022 10:40:39;0040;pbs\_sched;Job;7.pbs03;Dedicated Time  
07/20/2022 10:40:39;0080;pbs\_sched;Req;;Leaving Scheduling Cycle

TEST 2. sched\_config:

dedicated\_prefix: ded  
#primetime\_prefix: p\_  
#nonprimetime\_prefix: np\_

Result: Job does not run  
07/20/2022 10:20:42;0080;pbs\_sched;Req;;Starting Scheduling Cycle  
07/20/2022 10:20:42;0040;pbs\_sched;Job;4.pbs03;Job only runs in nonprimetime  
07/20/2022 10:20:42;0080;pbs\_sched;Req;;Leaving Scheduling Cycle

TEST 3. sched\_config:

dedicated\_prefix: ded  
primetime\_prefix: p\_  
#nonprimetime\_prefix: np\_

Result: Job does not run  
07/20/2022 10:35:55;0080;pbs\_sched;Req;;Starting Scheduling Cycle  
07/20/2022 10:35:55;0040;pbs\_sched;Job;5.pbs03;Job only runs in nonprimetime  
07/20/2022 10:35:55;0080;pbs\_sched;Req;;Leaving Scheduling Cycle

TEST 4. sched\_config:

dedicated\_prefix: ded  
#primetime\_prefix: p\_  
nonprimetime\_prefix: np\_

Result: Job runs  
07/20/2022 10:37:15;0080;pbs\_sched;Req;;Starting Scheduling Cycle  
07/20/2022 10:37:15;0080;pbs\_sched;Job;6.pbs03;Considering job to run  
07/20/2022 10:37:15;0040;pbs\_sched;Job;6.pbs03;Job run  
07/20/2022 10:37:15;0080;pbs\_sched;Req;;Leaving Scheduling Cycle

TEST 5. sched\_config:

dedicated\_prefix: ded  
primetime\_prefix: p\_  
nonprimetime\_prefix: np\_

Result: Job runs  
07/20/2022 10:47:23;0080;pbs\_sched;Req;;Starting Scheduling Cycle  
07/20/2022 10:47:23;0080;pbs\_sched;Job;8.pbs03;Considering job to run  
07/20/2022 10:47:23;0040;pbs\_sched;Job;8.pbs03;Job run  
07/20/2022 10:47:23;0080;pbs\_sched;Req;;Leaving Scheduling Cycle

TEST 6. sched\_config:

#dedicated\_prefix: ded  
primetime\_prefix: p\_  
nonprimetime\_prefix: np\_

Result: Job does not run  
07/20/2022 13:23:07;0080;pbs\_sched;Req;;Starting Scheduling Cycle  
07/20/2022 13:23:07;0040;pbs\_sched;Job;11.pbs03;Dedicated Time  
07/20/2022 13:23:07;0080;pbs\_sched;Req;;Leaving Scheduling Cycle
