Read this before submitting a ticket!

Created by Steve Place, Modified on Thu, 31 Aug 2023 at 11:41 AM by Steve Place

What to include in your ticket

Everyone:

  • A complete description of the problem you're having, including steps to reproduce the issue
  • Your stardog.log file

If you have query issues:

  • The query you're having trouble with
  • The output of the query profiler (stardog query explain --profile myDb myQuery)

If you're running a cluster:

  • The diagnostics report (stardog-admin cluster diagnostics report)
  • ZooKeeper logs from all the ZooKeeper nodes
  • Description of how Stardog was installed: zip, packages, Docker, helm charts in Kubernetes

  • Output of stardog-admin zk info (please remove any sensitive data like passwords)


If your issue involves permissions:


If your issue is with Studio:

  • The output of the browser console



My problem is about X, what do I do?

The first place to check is the Stardog documentation, as it has information on all parts of Stardog.


If you don't find the solution there, check the Support Portal's knowledge base. The knowledge base is constantly growing, so someone may have asked your question already.  


FAQ's:


Stardog also has an active forum, Stardog Community. There, users can discuss issues and share tips and tricks about Stardog.


My ticket was closed automatically, what happened?

The Support Portal closes all inactive tickets after 3 weeks. We'll send you an automatic reminder after 1 and 2 weeks of inactivity, as well as a notice we're closing the ticket at 3 weeks. To reopen a closed ticket, simply open the ticket, find the gray box that says "This ticket has been Closed | about X ago Reply" and hit "Reply".


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article