Troubleshooting

This page records commonly-encountered issues one might face when attempting to implement UserALE into Superset, and offers possible solutions.

Superset

Error: When initializing Superset's container through Docker, the initialization logs will spit out a superset ERROR: relation "report_schedule" does not exist at character error, and opening superset will yield a 500 server error:

Solution: Take down the superset container by running docker-elk down -v inside of your local superset instance, and set up the container again.

---

Docker-ELK

Error: Logstash times out when running its container and produces the following error message:

 => ERROR [2/2] RUN logstash-plugin install logstash-input-http                                                 
------
 > [2/2] RUN logstash-plugin install logstash-input-http:
#5 0.358 Using bundled JDK: /usr/share/logstash/jdk
#5 0.659 OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
#5 9.423 Validating logstash-input-http
#5 70.31 Unable to download data from https://rubygems.org - timed out (https://rubygems.org/latest_specs.4.8.gz)
#5 70.32 ERROR: Installation aborted, verification failed for logstash-input-http
------
executor failed running [/bin/sh -c logstash-plugin install logstash-input-http]: exit code: 1
ERROR: Service 'logstash' failed to build : Build failed

Solution: Under Docker-Desktop's settings, navigate to the "Engine" tab and delete the following code block:

"features": {
    "buildkit": true
  },

Hit save and try setting up docker-ELK again.