Open ZmG opened 6 years ago
Try adding the line preserve_logs true;
to your /etc/shiny-server-client/shiny-server-client.conf and reloading the server. Then get the app to load again, and look in the /var/log/shiny-server/ (not the shiny-server-client.log file) directory for clues. It's likely that the app is hitting an unhandled exception and intentionally ending the session in response.
Thanks for the quick response.
Added the preserve_logs true;
to /etc/shiny-server/shiny-server.conf.
The output from /var/log/shiny-server/myshinyApp-xx-20181017-055013-37535.log
is not very helpful:
su: ignoring --preserve-environment, it's mutually exclusive with --login
Listening on http://127.0.0.1:37535
Execution halted
Is there an additional configuration that could enable more verbose output in the app log?
Hmmm, that indicates that everything terminated normally. There's nothing in the browser's JavaScript console when it disconnects?
Did you ever figure out what was going on here? I'm in a similar situation. In my case, the app runs fine in general, but I'm getting this error when restoring a bookmarked session. It doesn't happen with every bookmarked session, only ones after I've clicked a certain action button. I've dug in as best I can, and can't find any leads in the logs. Any ideas?
There's nothing noteworthy in the browser console:
Here's the relevant part of the server log:
[cnewton1@NCIENDEVAPP03 ~]$ tail -100 /var/log/shiny-server.log
[2019-04-12T14:18:24.781] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:24.783] [TRACE] shiny-server - Proxying request: /shared/strftime/strftime-min.js
[2019-04-12T14:18:24.783] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:24.784] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:24.791] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:24.791] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:24.792] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 0 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:24.944] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:24.944] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:24.944] [TRACE] shiny-server - Proxying request: /shared/bootstrap/js/bootstrap.min.js
[2019-04-12T14:18:24.945] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:24.945] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:24.953] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:24.954] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:24.955] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 0 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.057] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:25.057] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.058] [TRACE] shiny-server - Proxying request: /shared/bootstrap/shim/html5shiv.min.js
[2019-04-12T14:18:25.058] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:25.058] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:25.065] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:25.066] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 2 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.066] [TRACE] shiny-server - Proxying request: /shared/bootstrap/shim/respond.min.js
[2019-04-12T14:18:25.066] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:25.067] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:25.067] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:25.068] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:25.072] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.074] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:25.074] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 2 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.074] [TRACE] shiny-server - Proxying request: /Navigant.png
[2019-04-12T14:18:25.074] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:25.075] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:25.078] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:25.079] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:25.079] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.087] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:25.088] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:25.088] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 0 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.101] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:25.102] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.102] [TRACE] shiny-server - Proxying request: /shared/shiny.min.js.map
[2019-04-12T14:18:25.102] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:25.102] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:25.109] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:25.338] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:25.338] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 2 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.338] [TRACE] shiny-server - Proxying request: /crosstalk-1.0.0/js/crosstalk.min.js.map
[2019-04-12T14:18:25.338] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:25.338] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:25.345] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:25.346] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:25.346] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:25.548] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:25.549] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 0 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:26.080] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:26.080] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:26.080] [TRACE] shiny-server - Proxying request: /shinythemes/fonts/Roboto_400.ttf
[2019-04-12T14:18:26.080] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:26.081] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:26.081] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:26.082] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 2 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:26.082] [TRACE] shiny-server - Proxying request: /shinythemes/fonts/Roboto_500.ttf
[2019-04-12T14:18:26.082] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:26.082] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:26.088] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:26.088] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 3 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:26.088] [TRACE] shiny-server - Proxying request: /shinythemes/fonts/Roboto_700.ttf
[2019-04-12T14:18:26.088] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:26.088] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:26.093] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:26.094] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:26.094] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 2 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:26.100] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:26.100] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:26.100] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:26.105] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:26.105] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:26.105] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 0 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:26.185] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:26.185] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring http port. 1 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:26.185] [TRACE] shiny-server - Proxying request: /shared/bootstrap/css/bootstrap.min.css.map
[2019-04-12T14:18:26.186] [TRACE] shiny-server - http_proxy event: start
[2019-04-12T14:18:26.186] [TRACE] shiny-server - http_proxy event: proxyReq
[2019-04-12T14:18:26.193] [TRACE] shiny-server - http_proxy event: proxyRes
[2019-04-12T14:18:26.853] [TRACE] shiny-server - http_proxy event: end
[2019-04-12T14:18:26.853] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing http port. 0 HTTP, 0 WebSocket, 1 pending.
[2019-04-12T14:18:27.325] [DEBUG] shiny-server - Creating a new robust connection: pGZFGJtWkYBUpqJ0Ti
[2019-04-12T14:18:27.784] [TRACE] shiny-server - Accepted SockJS connection for /ShinyApps/NAVsamplr_Test/__sockjs__/n=pGZFGJtWkYBUpqJ0Ti/979/1h1jxta0/xhr_streaming
[2019-04-12T14:18:27.805] [TRACE] shiny-server - Reusing existing instance
[2019-04-12T14:18:27.805] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing pending port. 0 HTTP, 0 WebSocket, 0 pending.
[2019-04-12T14:18:27.805] [TRACE] shiny-server - No clients connected to worker #f7a1da87230d90dc. Starting timer
[2019-04-12T14:18:27.805] [TRACE] shiny-server - Worker #f7a1da87230d90dc acquiring sock port. 0 HTTP, 1 WebSocket, 0 pending.
[2019-04-12T14:18:28.525] [TRACE] shiny-server - Worker #f7a1da87230d90dc releasing sock port. 0 HTTP, 0 WebSocket, 0 pending.
[2019-04-12T14:18:28.526] [TRACE] shiny-server - No clients connected to worker #f7a1da87230d90dc. Starting timer
[2019-04-12T14:18:28.769] [TRACE] shiny-server - Withholding event 'end' from robust connection pGZFGJtWkYBUpqJ0Ti
[2019-04-12T14:18:28.770] [TRACE] shiny-server - Withholding event 'close' from robust connection pGZFGJtWkYBUpqJ0Ti
[2019-04-12T14:18:43.771] [DEBUG] shiny-server - Closing robust connection pGZFGJtWkYBUpqJ0Ti
[2019-04-12T14:19:20.842] [WARN] shiny-server - No host header sent by user-agent check_http/v2.2.1 (nagios-plugins 2.2.1)
[2019-04-12T14:19:20.843] [WARN] shiny-server - No host header sent by user-agent check_http/v2.2.1 (nagios-plugins 2.2.1)
And here's the session log (the errors listed are resolved after loading the input data set, and do not prevent the session from continuing to run):
Attaching package: ‘shinydashboard’
The following object is masked from ‘package:graphics’:
box
Attaching package: ‘DT’
The following objects are masked from ‘package:shiny’:
dataTableOutput, renderDataTable
Attaching package: ‘dplyr’
The following objects are masked from ‘package:stats’:
filter, lag
The following objects are masked from ‘package:base’:
intersect, setdiff, setequal, union
Attaching package: ‘gridExtra’
The following object is masked from ‘package:dplyr’:
combine
Listening on http://127.0.0.1:41933
Warning: Error in : slice condition does not evaluate to an integer or numeric vector.
192: <Anonymous>
Warning: Error in : slice condition does not evaluate to an integer or numeric vector.
192: <Anonymous>
I am also facing the similar issue on s390x build. Any resolution to this..?
Background: Built shiny servers versions: v1.5.7.907, v1.5.8.921
Build shiny server from source code for s390x architecture including installing node using install-node.sh for s390x architecture. NGINX sitting in front of Shiny Server.
Problem: When launching app, app loads but it greys out. SockJS conn is acquired but immediately released.
Debugging
Built both v1.5.7.907 and v1.5.8.921 - same issue
Tried different configuration options in NGINX including directives to upgrade to websocket protocols.
Surpassed Nginx, so traffic flows directly to shiny server. Browser -> Shiny-server.
Errors:
disable_protocols