# VNC connection hangs
**URL:** https://discourse.openondemand.org/t/vnc-connection-hangs/1986
**Category:** Get Help
**Tags:** question
**Created:** [March 30, 2022, 3:48am UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986 "2022-03-30T03:48:59Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@Cherry](https://discourse.openondemand.org/u/Cherry)
#### Post date: [March 30, 2022, 3:48am UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/1 "2022-03-30T03:48:59Z")
In order to make OOD server auto deployed. We have configured two servers for ondemand. (A)One is manually configured, (B)another one is configured with salt autoconfiguration tool.
Server B works on other applications but bc\_matlab and bc\_desktop. Since both servers are pointing to the same scheduler, and can see the submitted jobs from both servers. The same bc\_desktop job works on server A but not on server B. The VNC session is running on the compute node, but on server B, it just hangs with a connecting message.
Can anyone show a good way to debug this issue?
---
### Author:  [@gbyrket](https://discourse.openondemand.org/u/gbyrket)
#### Post date: [March 30, 2022, 1:41pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/2 "2022-03-30T13:41:30Z")
> [@Cherry](#):
>
> e
Hi Cherry. Thanks for your post and your question. This is definitely a tough one. With that being the case, I’m going to ask what may be perceived as some basic questions, so please bare with me.
1. Have you compared the 2 installs to ensure server B is setup properly?
2. Have you checked the logs for errors on server B.
If you can please send us the logs for server B for when you are trying to launch the failing apps, that would be great.
We’ll work through this.
Thanks again,
-gerald
---
### Author:  [@Cherry](https://discourse.openondemand.org/u/Cherry)
#### Post date: [March 30, 2022, 5:50pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/3 "2022-03-30T17:50:47Z")
Thanks Gerald,
1. Server B is built with the exact steps from manual built, only difference is the OOD version is 2.0.18 (Server A is 2.0.23).
2. The error shows when I click the Launch interactive desktop button:
App 17497 output: [2022-03-30 13:34:24 -0400] INFO “method=GET path=/pun/sys/dashboard/batch\_connect/sessions.js format=js controller=BatchConnect::SessionsController action=index status=200 duration=150.93 view=26.47”
App 17497 output: [2022-03-30 13:34:26 -0400] FATAL “”
App 17497 output: [2022-03-30 13:34:26 -0400] FATAL “ActionController::RoutingError (No route matches [GET] “/noVNC-1.1.0/vendor/pako/lib/utils/common.js”):”
App 17497 output: [2022-03-30 13:34:26 -0400] FATAL “”
App 17497 output: [2022-03-30 13:34:26 -0400] FATAL “actionpack (5.2.6) lib/action\_dispatch/middleware/debug\_exceptions.rb:65:in `call'\nactionpack (5.2.6) lib/action_dispatch/middleware/show_exceptions.rb:33:in `call’\nlograge (0.11.2) lib/lograge/rails\_ext/rack/logger.rb:15:in `call_app'\nrailties (5.2.6) lib/rails/rack/logger.rb:26:in `block in call’\nactivesupport (5.2.6) lib/active\_support/tagged\_logging.rb:71:in `block in tagged'\nactivesupport (5.2.6) lib/active_support/tagged_logging.rb:28:in `tagged’\nactivesupport (5.2.6) lib/active\_support/tagged\_logging.rb:71:in `tagged'\nrailties (5.2.6) lib/rails/rack/logger.rb:26:in `call’\nactionpack (5.2.6) lib/action\_dispatch/middleware/remote\_ip.rb:81:in `call'\nrequest_store (1.5.0) lib/request_store/middleware.rb:19:in `call’\nactionpack (5.2.6) lib/action\_dispatch/middleware/request\_id.rb:27:in `call'\nrack (2.2.3) lib/rack/method_override.rb:24:in `call’\nrack (2.2.3) lib/rack/runtime.rb:22:in `call'\nactivesupport (5.2.6) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call’\nactionpack (5.2.6) lib/action\_dispatch/middleware/executor.rb:14:in `call'\nrack (2.2.3) lib/rack/sendfile.rb:110:in `call’\nrailties (5.2.6) lib/rails/engine.rb:524:in `call'\n/opt/rh/ondemand/root/usr/share/ruby/vendor_ruby/phusion_passenger/rack/thread_handler_extension.rb:107:in `process\_request’\n/opt/rh/ondemand/root/usr/share/ruby/vendor\_ruby/phusion\_passenger/request\_handler/thread\_handler.rb:149:in `accept_and_process_next_request'\n/opt/rh/ondemand/root/usr/share/ruby/vendor_ruby/phusion_passenger/request_handler/thread_handler.rb:110:in `main\_loop’\n/opt/rh/ondemand/root/usr/share/ruby/vendor\_ruby/phusion\_passenger/request\_handler.rb:416:in `block (3 levels) in start_threads'\n/opt/rh/ondemand/root/usr/share/ruby/vendor_ruby/phusion_passenger/utils.rb:113:in `block in create\_thread\_and\_abort\_on\_exception’”
App 17497 output: [2022-03-30 13:34:27 -0400] INFO “method=GET path=/pun/sys/dashboard/404 format=_/_ controller=ErrorsController action=not\_found status=404 duration=117.16 view=8.91”
Let me know if you need other information.
Cherry
---
### Author:  [@gbyrket](https://discourse.openondemand.org/u/gbyrket)
#### Post date: [March 30, 2022, 6:26pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/4 "2022-03-30T18:26:06Z")
> [@Cherry](#):
>
> 2.0.23
Hi Cherry.
Thanks for the response. To get to a point where it’s apples to apples, please upgrade Server B to 2.0.23
Thanks,
-gerald
---
### Author:  [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [March 30, 2022, 6:52pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/5 "2022-03-30T18:52:58Z")
It seems like you’re upgrading so you probably want to fix the one first.
If I look at my `ondemand-nginx/$USER/access.log` I have the prefix `/pun/sys/dashboard` to these calls.
```nohighlight
unix: - - [30/Mar/2022:14:10:41 -0400] "GET /pun/sys/dashboard/noVNC-1.1.0/vendor/pako/lib/utils/common.js HTTP/1.1" 200 1062 "https://ondemand-test.osc.edu/pun/sys/dashboard/noVNC-1.1.0/vendor/pako/lib/zlib/inflate.js" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0" "131.187.45.7"
```
Are you sure they both have the same settings? Specifically around any `public` or `uri` related configurations.
---
### Author:  [@Cherry](https://discourse.openondemand.org/u/Cherry)
#### Post date: [March 30, 2022, 6:54pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/6 "2022-03-30T18:54:57Z")
After upgrading server B to 2.0.23, dashboard failed to start with error:
Could not spawn process for application /var/www/ood/apps/sys/dashboard: The application encountered the following error: undefined method `kubernetes?’ for #OodCore::Cluster:0x000000000323ebc0 (NoMethodError)
Error ID: 41a390e2
Error details saved to: /tmp/passenger-error-iOuqMi.html
---
### Author:  [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [March 30, 2022, 6:57pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/7 "2022-03-30T18:57:00Z")
Are you installing through the rpm? Can you remove the old `ondemand-gem` if so.
---
### Author:  [@Cherry](https://discourse.openondemand.org/u/Cherry)
#### Post date: [March 30, 2022, 8:12pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/8 "2022-03-30T20:12:26Z")
I think that I found the root cause, which is I have done some customization in /var/www/ood/apps/sys/dashboard/config/initializer by adding few files, looks like that dashborad doesn’t like it.
Putting it under /etc/ood/config/apps/dashboard/initializers seems working.
And the upgrades automatically resolves bc\_desktop issue.
Could you let me know what is best practice on putting things under /var/www/ood/apps vs /etc/ood/config/apps?
Thanks for your time.
---
### Author:  [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [March 30, 2022, 9:03pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/9 "2022-03-30T21:03:09Z")
Always put configurations in `/etc/ood/config` because they will keep through RPM updates. Anything in `/var/www/ood/apps` will be overwritten during updates.
---
### Author:  [@system](https://discourse.openondemand.org/u/system)
#### Post date: [September 26, 2022, 9:04pm UTC](https://discourse.openondemand.org/t/vnc-connection-hangs/1986/10 "2022-09-26T21:04:04Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.