# How to get the error output of the desktop app

**URL:** https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946
**Category:** Get Help
**Tags:** question
**Created:** [June 2, 2020, 10:22am UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946 "2020-06-02T10:22:58Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![baverhey](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/baverhey/32/605_2.png) [@baverhey](https://discourse.openondemand.org/u/baverhey)
#### Post date: [June 2, 2020, 10:22am UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946/1 "2020-06-02T10:22:58Z")

</div>

Only output.log is available in subdirectories of $HOME/ondemand/data/sys/dashboard/batch\_connect/sys/bc\_desktop/login/output/

error output is nowhere to be found (and there definitely should be errors in a test case we made)

The goal is that the users can see there own error.log to lower the helpdesk tickets for the easy errors.

---

<div class="post-metadata">

### Author: ![mario](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/mario/32/662_2.png) [@mario](https://discourse.openondemand.org/u/mario)
#### Post date: [June 3, 2020, 3:51pm UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946/2 "2020-06-03T15:51:24Z")

</div>

@baverhey

Logs for a `bc_desktop` session will be available here:

`/users/$PROJECT/$USER/ondemand/data/sys/dashboard/batch_connect/sys/bc_desktop/vdi-owens/output/$UUID/output.log`

If you click on `Session ID` in your interactive sessions list you will be taken to the logs output for that session.

 ![image](https://us1.discourse-cdn.com/flex015/uploads/osc/original/1X/635642e266b7db65c58d40b894e9e786b9971bb0.png)

---

<div class="post-metadata">

### Author: ![baverhey](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/baverhey/32/605_2.png) [@baverhey](https://discourse.openondemand.org/u/baverhey)
#### Post date: [June 4, 2020, 6:23am UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946/3 "2020-06-04T06:23:21Z")

</div>

Those we have: its the location of error log when the desktop session does not start or break down.

The trigger for this request:  
A module was beeing loaded that was not available on that specefic cluster and no errors where to be found.

---

<div class="post-metadata">

### Author: ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [November 13, 2020, 5:59pm UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946/4 "2020-11-13T17:59:43Z")

</div>

Hi, sorry for the delay. What is your scheduler? For desktops, we set the output path to this log file you’ve identified.

For Torque OOD sets `headers.merge!(Join_Path: 'oe') if script.error_path.nil?` which joins stdout and stderr if error\_path isn’t set (which it isn’t).

Then for Slurm sbatch documentation says “By default both standard output and standard error are directed to the same file” so setting the output path is enough.

It seems like you’re scheduler is like Torque, where we need to pass another flag to get stderr output joined to stdout? Is that about right?

---

<div class="post-metadata">

### Author: ![baverhey](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/baverhey/32/605_2.png) [@baverhey](https://discourse.openondemand.org/u/baverhey)
#### Post date: [January 26, 2021, 1:36pm UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946/5 "2021-01-26T13:36:38Z")

</div>

I’m back 😉  
Our scheduler is slurm.

---

<div class="post-metadata">

### Author: ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [January 26, 2021, 9:09pm UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946/6 "2021-01-26T21:09:45Z")

</div>

Hi there! It looks like I half answered this.

While you’re able to set `script.error_path`, you can’t use the staged root where all the other files are.

```auto
script:
  error_path: "/some/known/path"

```

But I just opened this ticket to possibly enable using the same staged\_root directory that all the other files are in.

> <https://github.com/OSC/ondemand/issues/864>
>
> A discourse topic about error paths came in, and while folks are able to set script.error\_path in their submit yml, they...

---

<div class="post-metadata">

### Author: ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [May 27, 2021, 4:05pm UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946/7 "2021-05-27T16:05:37Z")

</div>

This is available in 2.0.9.

So you could do something like this in the `submit.yml.erb`.

```auto
script:
  error_path: "<%= staged_root %>/error.log"

```

---

<div class="post-metadata">

### Author: ![westburg.2](https://avatars.discourse-cdn.com/v4/letter/w/0ea827/32.png) [@westburg.2](https://discourse.openondemand.org/u/westburg.2)
#### Post date: [May 26, 2022, 3:42pm UTC](https://discourse.openondemand.org/t/how-to-get-the-error-output-of-the-desktop-app/946/8 "2022-05-26T15:42:52Z")

</div>


