Griefed/ServerPackCreator

Watch

Fork 0

[Bug]: Systemd seems to have issues launching the start script #527

New issue

Closed

opened 2026-06-26 21:12:39 +02:00 by Griefed · 3 comments

Griefed commented

2026-06-26 21:12:39 +02:00

Owner

@DisruptionSystemsINC on GitHub · https://github.com/Griefed/ServerPackCreator/issues/478

What happened?

It seems like, starting servers via the start.sh script via a systemd service, just throws an error in systemd

Mind you, this only happens specifically when started via a systemd Service, not when manually cd-ing into a directory and running ./start.sh
My service setup is as follows:

`[Unit]
Description=Create Stellar Server
After=network.target

[Service]
User=disruption
ExecStart=/home/disruption/Create_Stellar/start.sh
Restart=on-failure
[Install]
WantedBy=multi-user.target`

The user is the main user of the system, therefore also has the neccessary permissions to access the files inside the directory. The st art.sh has been giving the executeable attribute via chmod +x

What did you expect to happen?

Server should start as usual

Version

4.3.0

Relevant log output

Oct 29 18:18:02 node01 java[39918]: Error: Unable to access jarfile server.jar
Oct 29 18:18:02 node01 systemd[1]: CreateServerStarter.service: Main process exited, code=exited, status=1/FAILURE
Oct 29 18:18:02 node01 systemd[1]: CreateServerStarter.service: Failed with result 'exit-code'.
Oct 29 18:18:03 node01 systemd[1]: CreateServerStarter.service: Scheduled restart job, restart counter is at 1.
Oct 29 18:18:03 node01 systemd[1]: Stopped Create Stellar Server.
Oct 29 18:18:03 node01 systemd[1]: Started Create Stellar Server.
Oct 29 18:18:03 node01 java[39920]: Error: Unable to access jarfile server.jar
Oct 29 18:18:03 node01 systemd[1]: CreateServerStarter.service: Main process exited, code=exited, status=1/FAILURE

Anything else you would like to add?

No response

If you are using the webservice, in which browers did you encounter this bug?

No response

Code of Conduct

I agree to follow this project's Code of Conduct

> **@DisruptionSystemsINC** on **GitHub** · https://github.com/Griefed/ServerPackCreator/issues/478 ### What happened? It seems like, starting servers via the start.sh script via a systemd service, just throws an error in systemd Mind you, this only happens specifically when started via a systemd Service, not when manually cd-ing into a directory and running ./start.sh My service setup is as follows: `[Unit] Description=Create Stellar Server After=network.target [Service] User=disruption ExecStart=/home/disruption/Create_Stellar/start.sh Restart=on-failure [Install] WantedBy=multi-user.target` The user is the main user of the system, therefore also has the neccessary permissions to access the files inside the directory. The st art.sh has been giving the executeable attribute via chmod +x ### What did you expect to happen? Server should start as usual ### Version 4.3.0 ### Relevant log output ```shell Oct 29 18:18:02 node01 java[39918]: Error: Unable to access jarfile server.jar Oct 29 18:18:02 node01 systemd[1]: CreateServerStarter.service: Main process exited, code=exited, status=1/FAILURE Oct 29 18:18:02 node01 systemd[1]: CreateServerStarter.service: Failed with result 'exit-code'. Oct 29 18:18:03 node01 systemd[1]: CreateServerStarter.service: Scheduled restart job, restart counter is at 1. Oct 29 18:18:03 node01 systemd[1]: Stopped Create Stellar Server. Oct 29 18:18:03 node01 systemd[1]: Started Create Stellar Server. Oct 29 18:18:03 node01 java[39920]: Error: Unable to access jarfile server.jar Oct 29 18:18:03 node01 systemd[1]: CreateServerStarter.service: Main process exited, code=exited, status=1/FAILURE ``` ### Anything else you would like to add? _No response_ ### If you are using the webservice, in which browers did you encounter this bug? _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct

Griefed closed this issue

2026-06-26 21:12:39 +02:00

Griefed commented

2026-06-26 21:12:39 +02:00

Author

Owner

@Griefed on GitHub

Heyoo,

does this still happen when you set the working directory to the same directory containing the script and server pack, i.e.:

[Unit]
Description=Create Stellar Server
After=network.target

[Service]
User=disruption
WorkingDirectory=/home/disruption/Create_Stellar
ExecStart=/home/disruption/Create_Stellar/start.sh
Restart=on-failure
[Install]
WantedBy=multi-user.target

> **@Griefed** on **GitHub** Heyoo, does this still happen when you set the working directory to the same directory containing the script and server pack, i.e.: ```bash [Unit] Description=Create Stellar Server After=network.target [Service] User=disruption WorkingDirectory=/home/disruption/Create_Stellar ExecStart=/home/disruption/Create_Stellar/start.sh Restart=on-failure [Install] WantedBy=multi-user.target ```

Griefed commented

2026-06-26 21:12:39 +02:00

Author

Owner

@DisruptionSystemsINC on GitHub

Oh yeah, Sorry my fault^^"

> **@DisruptionSystemsINC** on **GitHub** Oh yeah, Sorry my fault^^"

Griefed commented

2026-06-26 21:12:40 +02:00

Author

Owner

@Griefed on GitHub

No worries! I take it this resolved the issue for you?
That's good to know. Happy server packing, and please do not hesitate to open another issue if you encounter anything else.

Until then.
Cheers,
Griefed

> **@Griefed** on **GitHub** No worries! I take it this resolved the issue for you? That's good to know. Happy server packing, and please do not hesitate to open another issue if you encounter anything else. Until then. Cheers, Griefed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Griefed/ServerPackCreator#527

No description provided.

Rows
Columns