Installing w/ docker-compose results in an infinitely forking process starting on boot #513

Closed
opened 2026-04-05 16:20:12 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @TheMin3s on 4/8/2025

Describe the bug
When using the docker-compose install method, processes under the names/commands node --require ts-node/register Index.ts and another (i'll add it later) begin to infinitely fork and also start on boot

To Reproduce
Steps to reproduce the behavior:

  1. Use Git to clone oneuptime to a non-root directory
  2. run git checkout release
  3. cp config.example.env config.env
  4. Run npm start
  5. Regular installation proceeds and completes, but later begins to summon the endlessly forking processes

Expected behavior
Nothing out of the ordinary with install as dictated in the guide

Screenshots
SSH was not working (no memory) so i had to physically take a photo of the screen, photo of htop open
at times it would get to 100% usage on all cpu cores

Desktop (please complete the following information):

  • Debian Linux 12.10.0
  • n/a
  • n/a

Smartphone (please complete the following information):

  • n/a
  • n/a
  • n/a
  • Latest as of posting (idk)

Deployment Type
Self-hosted

Additional context
I'm not sure if this is a problem on my end or your end, but i thought it was a good idea to post it anyways. Wanted to see if maybe I could get help on this too as it has left my entire server completely unusable

*Originally created by @TheMin3s on 4/8/2025* **Describe the bug** When using the docker-compose install method, processes under the names/commands `node --require ts-node/register Index.ts` and another (i'll add it later) begin to infinitely fork and also start on boot **To Reproduce** Steps to reproduce the behavior: 1. Use Git to clone oneuptime to a non-root directory 2. run `git checkout release` 3. `cp config.example.env config.env` 4. `Run npm start` 5. Regular installation proceeds and completes, but later begins to summon the endlessly forking processes **Expected behavior** Nothing out of the ordinary with install as dictated in the guide **Screenshots** SSH was not working (no memory) so i had to physically take a photo of the screen, photo of htop open at times it would get to 100% usage on all cpu cores **Desktop (please complete the following information):** - Debian Linux 12.10.0 - n/a - n/a **Smartphone (please complete the following information):** - n/a - n/a - n/a - Latest as of posting (idk) **Deployment Type** Self-hosted **Additional context** I'm not sure if this is a problem on my end or your end, but i thought it was a good idea to post it anyways. Wanted to see if maybe I could get help on this too as it has left my entire server completely unusable
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#513