Step 3. Check Service Status

Launcher configuration issues

You’re unable to access the Workbench home page unable to start new remote sessions in Kubernetes.

Workbench

Return to Troubleshooting index

Symptoms

  • Unable to access the Posit Workbench home page
  • Unable to start new remote sessions in Kubernetes

Error messages

When inspecting the log files for Workbench, Launcher, and Kubernetes, you might see errors similar to the following:

Workbench Home Page
Job information unavailable. Sessions are read-only.
Contact your administrator for help.

Error occurred while executing method (100)
Connection refused

void rstudio::core::http::TcpIpAsyncConnector::handleConnect(const rstudio_boost::system::error_code&, rstudio_boost::asio::ip::basic_resolver<rstudio_boost::asio::ip::tcp>::iterator) /var/lib/jenkins/workspace/IDE/pro-pipeline/v1.2-patch/src/cpp/core/include/core/http/TcpIpAsyncConnector.hpp:197
/var/lib/rstudio-server/monitor/log/rstudio-server.log
04 May 2020 03:36:03 [rserver] ERROR system error 111 (Connection refused); OCCURRED AT: void rstudio::core::http::TcpIpAsyncConnector::handleConnect(const rstudio_boost::system::error_code&, rstudio_boost::asio::ip::basic_resolver<rstudio_boost::asio::ip::tcp>::iterator) /var/lib/jenkins/workspace/IDE/pro-pipeline/v1.2-patch/src/cpp/core/include/core/http/TcpIpAsyncConnector.hpp:197; LOGGED FROM: rstudio::server::job_launcher::{anonymous}::ensureServerUserIsLauncherAdmin()::__lambda7::__lambda10 /var/lib/jenkins/workspace/IDE/pro-pipeline/v1.2-patch/src/cpp/server/ServerJobLauncher.cpp:678

Possible cause

For Workbench, Launcher, and Kubernetes to function properly, both the rstudio-server and rstudio-launcher services should be running and healthy.

The following troubleshooting steps help you check the status of both services and attempt to restart them in case they are not yet running.

Troubleshooting steps

Run the following commands in a terminal to check the status of the services:

$ sudo rstudio-server status
$ sudo rstudio-launcher status

which should return output similar to the following:

● rstudio-server.service - RStudio Server
   Loaded: loaded (/etc/systemd/system/rstudio-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2020-05-01 18:16:53 UTC; 1min 38s ago
  Process: 13126 ExecStop=/usr/bin/killall -TERM rserver (code=exited, status=0/SUCCESS)
  Process: 13128 ExecStart=/usr/lib/rstudio-server/bin/rserver (code=exited, status=0/SUCCESS)
 Main PID: 13129 (rserver)
   CGroup: /system.slice/rstudio-server.service
           ├─13129 /usr/lib/rstudio-server/bin/rserver
           ├─13286 /usr/lib/rstudio-server/bin/rserver-monitor --monitor-domain-socket /tmp/rstudio-rserver/rserver-monitor.socket --monitor-data-path /var/l...
           ├─13287 nginx: master process /usr/lib/rstudio-server/bin/rserver-http
           ├─13288 /usr/lib/rstudio-server/bin/rserver-launcher --server-user rstudio-server --server-project-sharing 1 --server-shared-storage-path /var/lib...
           ├─13291 /usr/bin/rrdtool -
           └─13292 nginx: worker process

May 01 18:16:53 rstudio-server-pro systemd[1]: Starting RStudio Server...
May 01 18:16:53 rstudio-server-pro systemd[1]: Started RStudio Server.
● rstudio-launcher.service - RStudio Launcher
   Loaded: loaded (/etc/systemd/system/rstudio-launcher.service; disabled; vendor preset: disabled)
   Active: active (running) since Fri 2020-05-01 18:16:53 UTC; 2min 7s ago
 Main PID: 13148 (rstudio-launche)
   CGroup: /system.slice/rstudio-launcher.service
           ├─13148 /usr/lib/rstudio-server/bin/rstudio-launcher
           ├─13161 /usr/lib/rstudio-server/bin/rstudio-kubernetes-launcher --server-user rstudio-server --enable-debug-logging 1 --scratch-path /var/lib/rstu...
           └─13173 /usr/lib/rstudio-server/bin/rstudio-local-launcher --server-user rstudio-server --enable-debug-logging 1 --scratch-path /var/lib/rstudio-l...

May 01 18:16:53 rstudio-server-pro systemd[1]: Started RStudio Launcher.
May 01 18:16:53 rstudio-server-pro rstudio-launcher[13148]: Bootstrapping plugin Kubernetes
May 01 18:16:53 rstudio-server-pro rstudio-kubernetes-launcher[13161]: Pruning 0 jobs
May 01 18:16:53 rstudio-server-pro rstudio-launcher[13148]: Bootstrapping plugin Local
May 01 18:16:53 rstudio-server-pro rstudio-local-launcher[13173]: Loading jobs from file...
May 01 18:16:53 rstudio-server-pro rstudio-local-launcher[13173]: Loaded 0 jobs from file
May 01 18:16:53 rstudio-server-pro rstudio-local-launcher[13173]: Pruning 0 jobs
May 01 18:16:53 rstudio-server-pro rstudio-launcher[13148]: Initializing TcpIpAsyncServer with address 127.0.0.1 and port 5559
May 01 18:16:53 rstudio-server-pro rstudio-launcher[13148]: Running server

Restart services and test

After you’ve verified the status of the services, restart both of them if needed:

$ sudo rstudio-server restart
$ sudo rstudio-launcher restart

and check their statuses again:

$ sudo rstudio-server status
$ sudo rstudio-launcher status

Verify that the services are running and try to start a new session from the Workbench home page.

If the services are still not starting or you are still experiencing errors when starting a new session, then proceed to
Step 4 - Verify License Status.

Back to top