# \<App\> failed to start waiting for port

**URL:** <https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491>\
**Category:** Get Help\
**Tags:** ondemand2, question\
**Created:** [February 20, 2023, 6:23pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491 "2023-02-20T18:23:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenny.hanson](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kenny.hanson](https://discourse.openondemand.org/u/kenny.hanson)\
**Post date:** [February 20, 2023, 6:23pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491/1 "2023-02-20T18:23:02Z")

</div>

Hey guys,  
I guess this is a continuing issue and I’m not entirely sure how to approach debugging. As you know I posted a question regarding Jupyter app failing to start waiting for a server port that we could resolve by clearing out the web browser cache.

My RStudio Server, which was working last week just fine, has stopped working and keeps timing out waiting for a port to open. Our main cluster is split into two main nodes: epyc, and gpu. This is only happening on my “epyc” nodes, it works fine in GPU nodes. It’s the exact same script being run so I’m confused.

Kenny

---

<div class="post-metadata">

**Author:** ![gbyrket](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/gbyrket/32/894_2.png) [@gbyrket](https://discourse.openondemand.org/u/gbyrket)\
**Post date:** [February 20, 2023, 6:37pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491/2 "2023-02-20T18:37:00Z")

</div>

Hey Kenny.

I’m going to start by trying the over-simplified. What happens if you restart the epyc node?

Thanks,  
-gerald

---

<div class="post-metadata">

**Author:** ![kenny.hanson](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kenny.hanson](https://discourse.openondemand.org/u/kenny.hanson)\
**Post date:** [February 20, 2023, 6:41pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491/3 "2023-02-20T18:41:34Z")

</div>

No possible, every node (we have 20 epyc nodes) is running jobs.

I’m not showing any stale or zombie processes holding ports open across the cluster.

Kenny

---

<div class="post-metadata">

**Author:** ![gbyrket](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/gbyrket/32/894_2.png) [@gbyrket](https://discourse.openondemand.org/u/gbyrket)\
**Post date:** [February 20, 2023, 7:18pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491/4 "2023-02-20T19:18:27Z")

</div>

Thanks Kenny.

I’ve done a search within Discourse. There are some articles that may help you.

Can you please take a look at the results of this search, and let us know if any of these solutions help?

[https://discourse.openondemand.org/search?q=waiting%20for%20port](https://discourse.openondemand.org/search?q=waiting%20for%20port)

Thanks,  
-gerald

---

<div class="post-metadata">

**Author:** ![kenny.hanson](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kenny.hanson](https://discourse.openondemand.org/u/kenny.hanson)\
**Post date:** [February 20, 2023, 7:51pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491/5 "2023-02-20T19:51:10Z")

</div>

Been reading those for days.

I actually managed to solve it. I took a look at all the output.log files and found it was trying to start up on one particular host, epyc012. That host is running a few dozen 2-cpu jobs. I added a --exclude= and jobs are running again.

Sorry for the false alarm guys. 🤨

K

---

<div class="post-metadata">

**Author:** ![gbyrket](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/gbyrket/32/894_2.png) [@gbyrket](https://discourse.openondemand.org/u/gbyrket)\
**Post date:** [February 20, 2023, 8:15pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491/6 "2023-02-20T20:15:10Z")

</div>

Very cool. Do you know why it kept hitting the one host?

---

<div class="post-metadata">

**Author:** ![kenny.hanson](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kenny.hanson](https://discourse.openondemand.org/u/kenny.hanson)\
**Post date:** [March 23, 2023, 4:02pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491/7 "2023-03-23T16:02:20Z")

</div>

Hi Gerald, Sorry I missed your follow up question.

In that instance, slurm just kept trying to schedule the app as it had space for it on the node in question. Most users were able to start up apps after waiting 30 minutes or so until slurm scheduled them on a different node.

It wasn’t limited to one node, that was just the first time I ran into the problem. I’m posting a General Discussion to expand on this a bit. We have some jobs being submitted that are I/O intensive for either memroy or storage, sometimes both. These cause enough of a delay that port assignments for an interactive app times out. I’ve played with the timeout wait value a bit, but it’s hit and miss.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/osc/original/2X/b/bae70bd0ed39a3ae769c2108155f4cb3e9da8385.png) [@system](https://discourse.openondemand.org/u/system)\
**Post date:** [September 19, 2023, 4:03pm UTC](https://discourse.openondemand.org/t/app-failed-to-start-waiting-for-port/2491/8 "2023-09-19T16:03:17Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.