Skip to content

Troubleshooting

Ilya Tsarev edited this page May 27, 2021 · 7 revisions

What's my DGLux Server build (version)?

  1. Open Data tab.
  2. Left-click sys -> Metrics panel -> Server Build
Server Build

How can I access the server's log file?

Using DGLux designer

  1. Open Data tab.
  2. Right-click sys -> Server Log -> Get
  3. Enter 500 and then Invoke.
  4. Expand the text window.
  5. Copy log records and save them as a text file.
Server Log

Using file system

  1. Open the DGLux server directory.
  2. Go to logs
  3. Download dglux_server.log.

What's my DSLink version?

  1. Open Data tab.
  2. Expand sys -> links
  3. Left-click on dslink name.
  4. In the Metrics panel search for version.
Server Build

How can I access dslink's log file?

Using DGLux designer

  1. Open Data tab.
  2. Expand sys -> links.
  3. Right-click on the dslink name -> Log -> Get
  4. Enter 500 and then Invoke.
  5. Expand the text window.
  6. Copy log records and save them as a text file.
DSLink Log

Using file system

  1. Open the DGLux server directory.
  2. Go to logs
  3. Download <dslink name>.log.

How do I restart a dslink?

  1. Open DGLux UI and switch to Data tab.
  2. Expand sys -> links.
  3. Right-click on the dslink name -> Stop Link
    1. Stop DSLink
  4. Make sure the dslink state says stopped.
    1. DSLink Stopped
  5. Then start dslink with right-click on the dslink name -> Start Link
  6. DSLink should change state to connected. If the state says started, dslink is not able to connect to the broker and won't be available under the /downstream.

How do I clear dslink duplicates running in the background?

  1. Stop dslink with right-click on the dslink name -> Stop Link.
  2. Connect to the server using ssh client (Putty, iTerm, ssh).
  3. In the command line interface type ps aux | grep dart. This should display a list of all the Dart dslinks and their corresponding process IDs. If you're looking for a Java dslink use ps aux | grep java.
    1. PS AUX
  4. If you see a process with the same name as the dslink you just stopped, then it's a copy of dslink running in the background. There shouldn't be any duplicates by default, but this could happen after the broker restarted incorrectly.
  5. Kill the duplicate process using its process ID kill 1754. There might be more than one duplicate, feel free to add multiple IDs separated with space.
  6. Start dslink with right-click on the dslink name -> Start Link in the DGLux UI.

Protocol
 ◌ Design
 ◌ Initializing Connection
 ◌ Node API
  ◌ Methods
  ◌ Broker
   ◌ Broker Discovery
  ◌ Configs
  ◌ Value Types
 ◌ Tokens
 ◌ Quality of Service
DSLink Manager
 ◌ dslink.json
 ◌ Startup Command
SDK Development
 ◌ Implementation Guide
DSA Server
 ◌ Installation
 ◌ Update Server
 ◌ Server Configuration
 ◌ CLI Tools
 ◌ DSA Permission Basics
 ◌ DSA Permission Model
  ◌ Permission List for the Root
 ◌ Authentication
  ◌ OpenID Connect
  ◌ Password Hasher
 ◌ DGLux Server SSL (HTTPS)
 ◌ Docker
 ◌ Audit
 ◌ Data Node
 ◌ Install NGINX with DSA Server
 ◌ Configure Ubuntu Linux to auto start DSA server
 ◌ Troubleshooting

Clone this wiki locally