# Killing jobs adversely affects qstat

**URL:** <https://community.openpbs.org/t/killing-jobs-adversely-affects-qstat/3443>\
**Category:** Users/Site Administrators\
**Created:** [February 14, 2023, 10:21am UTC](https://community.openpbs.org/t/killing-jobs-adversely-affects-qstat/3443 "2023-02-14T10:21:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CGully](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@CGully](https://community.openpbs.org/u/CGully)\
**Post date:** [February 14, 2023, 10:21am UTC](https://community.openpbs.org/t/killing-jobs-adversely-affects-qstat/3443/1 "2023-02-14T10:21:42Z")

</div>

Killing jobs, appears to slow down qstat.  
Usually qstat takes fractions of a second, but after killing of jobs qstat can take a long time to execute more than 18s. We have also seen it take more than 1minute to execute and cause  
“pbs\_iff: cannot connect to host”  
“pbs\_iff: all reserved ports in use”  
Warnings, after killing jobs.  
Not really sure how to debug exactly what is happening, any help would be appreciated. Thanks

---

<div class="post-metadata">

**Author:** ![CGully](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@CGully](https://community.openpbs.org/u/CGully)\
**Post date:** [March 22, 2023, 6:59pm UTC](https://community.openpbs.org/t/killing-jobs-adversely-affects-qstat/3443/2 "2023-03-22T18:59:58Z")

</div>

This appear to be related to having large job history.  
Users then refreshing the GUI impatiently wanting to see the job finish, upset qstat.

Consider it closed. Thanks