Skip to content

Fix systemd service example #453

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mysubb01 wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −9
Open

Fix systemd service example #453

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 11 additions & 9 deletions documentation/deployment/systemd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
---
title: Launch QuestDB with systemd
sidebar_label: systemd
description: This document describes how to launch QuestBD using systemd.
description: This document describes how to launch QuestDB using systemd.
---

Use systemd to run QuestDB as a system or user service. This guide will
demonstrate an initial configuration which you can use as the basis for your
installation scripts. It will also demonstrate how to setup and start a QuestDB
installation scripts. It will also demonstrate how to set up and start a QuestDB
systemd service.

## Prerequisites
Expand Down Expand Up @@ -37,6 +37,7 @@ export PATH=$JAVA_HOME/bin:$PATH
# Download and set up QuestDB
curl -s https://dl.questdb.io/snapshots/questdb-latest-no-jre-bin.tar.gz -o questdb.tar.gz
mkdir -p ~/questdb/binary
mkdir -p ~/bin ~/var/lib/questdb
tar -xzf questdb.tar.gz -C ~/questdb/binary --strip-components 1
mv ~/questdb/binary/questdb.jar ~/bin/
```
Expand All @@ -45,7 +46,7 @@ mv ~/questdb/binary/questdb.jar ~/bin/

Your QuestDB configuration is done in a `server.conf` file. The `server.conf`
file is populated with safe defaults on first startup if it does not exist. It
is common for user's of QuestDB to stick with the default configuration.
is common for users of QuestDB to stick with the default configuration.
However, should you choose to update your own and serve it via a scripted method
or similar, you may do so.

Expand Down Expand Up @@ -76,14 +77,15 @@ Restart=always
RestartSec=2
# Adjust java path to match requirements of a given distro
ExecStart=/home/[USER_NAME]/jdk/bin/java \
-XX:+UnlockExperimentalVMOptions \
-XX:+AlwaysPreTouch \
-XX:+UseParallelGC \
-DQuestDB-Runtime-66535 \
-Dcontainerized=false \
-ea -Dnoebug \
--add-exports java.base/jdk.internal.math=io.questdb \
-p /home/[USER_NAME]/bin/questdb.jar \
-m io.questdb/io.questdb.ServerMain \
-DQuestDB-Runtime-66535 \
-ea -Dnoebug \
-XX:+UnlockExperimentalVMOptions \
-XX:+AlwaysPreTouch \
-XX:+UseParallelOldGC \
-d /home/[USER_NAME]/var/lib/questdb

ExecReload=/bin/kill -s HUP $MAINPID
Expand Down Expand Up @@ -166,4 +168,4 @@ You can check the status of the timers using:

```bash
systemctl list-timers --all | grep apt
```
```