github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-11 11:59:55 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #2086] [Bug]: Container Fails to Start With Node Error #7754

New Issue
Closed
opened 2026-04-10 17:45:31 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-10 17:45:31 -05:00
Owner
Copy Link

Originally created by @b-dont on GitHub (Dec 14, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2086

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I'm attempting to run an Actual server on my Raspberry Pi 4, however the container is failing to start with a Node.js error. Here's my machine specs:

OS: Raspbian GNU/Linux 10 (buster) armv7l
Host: Raspberry Pi 4 Model B Rev 1.2
Kernel: 5.10.103-v7l+
CPU: BCM2711 (4) @ 1.500GHz
Memory: 573MiB / 3838MiB

Docker version 24.0.7, build afdd53b
docker-compose.yml:

version: '3'
services:
  actual_server:
    image: docker.io/actualbudget/actual-server:latest
    ports:
      # This line makes Actual available at port 5006 of the device you run the server on,
      # i.e. http://localhost:5006. You can change the first number to change the port, if you want.
      - '5006:5006'
    environment:
      # Uncomment any of the lines below to set configuration options.
      - ACTUAL_HTTPS_KEY=/data/selfhost.key
      - ACTUAL_HTTPS_CERT=/data/selfhost.crt
      # - ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB=20
      # - ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB=50
      # - ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB=20
      # See all options and more details at https://actualbudget.github.io/docs/Installing/Configuration
      # !! If you are not using any of these options, remove the 'environment:' tag entirely.
    volumes:
      # Change './actual-data' below to the path to the folder you want Actual to store its data in on your server.
      # '/data' is the path Actual will look for its files in by default, so leave that as-is.
      - ./actual-data:/data
    restart: unless-stopped

What error did you receive?

btp@pihole:~/apps/actual-server $ docker-compose up
Creating network "actual-server_default" with the default driver
Creating actual-server_actual_server_1 ... done
Attaching to actual-server_actual_server_1
actual_server_1  | Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
actual-server_actual_server_1 exited with code 134
actual_server_1  | Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
actual_server_1  | Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
actual_server_1  | Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
actual-server_actual_server_1 exited with code 134

btp@pihole:~/apps/actual-server $ docker logs -f actual-server_actual_server_1
Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Other

Operating System

Linux

Originally created by @b-dont on GitHub (Dec 14, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/2086 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? I'm attempting to run an Actual server on my Raspberry Pi 4, however the container is failing to start with a Node.js error. Here's my machine specs: ``` OS: Raspbian GNU/Linux 10 (buster) armv7l Host: Raspberry Pi 4 Model B Rev 1.2 Kernel: 5.10.103-v7l+ CPU: BCM2711 (4) @ 1.500GHz Memory: 573MiB / 3838MiB ``` `Docker version 24.0.7, build afdd53b` `docker-compose.yml`: ``` version: '3' services: actual_server: image: docker.io/actualbudget/actual-server:latest ports: # This line makes Actual available at port 5006 of the device you run the server on, # i.e. http://localhost:5006. You can change the first number to change the port, if you want. - '5006:5006' environment: # Uncomment any of the lines below to set configuration options. - ACTUAL_HTTPS_KEY=/data/selfhost.key - ACTUAL_HTTPS_CERT=/data/selfhost.crt # - ACTUAL_UPLOAD_FILE_SYNC_SIZE_LIMIT_MB=20 # - ACTUAL_UPLOAD_SYNC_ENCRYPTED_FILE_SYNC_SIZE_LIMIT_MB=50 # - ACTUAL_UPLOAD_FILE_SIZE_LIMIT_MB=20 # See all options and more details at https://actualbudget.github.io/docs/Installing/Configuration # !! If you are not using any of these options, remove the 'environment:' tag entirely. volumes: # Change './actual-data' below to the path to the folder you want Actual to store its data in on your server. # '/data' is the path Actual will look for its files in by default, so leave that as-is. - ./actual-data:/data restart: unless-stopped ``` ### What error did you receive? ``` btp@pihole:~/apps/actual-server $ docker-compose up Creating network "actual-server_default" with the default driver Creating actual-server_actual_server_1 ... done Attaching to actual-server_actual_server_1 actual_server_1 | Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. actual-server_actual_server_1 exited with code 134 actual_server_1 | Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. actual_server_1 | Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. actual_server_1 | Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. actual-server_actual_server_1 exited with code 134 ``` ``` btp@pihole:~/apps/actual-server $ docker logs -f actual-server_actual_server_1 Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. Node.js[7]: ../src/util.cc:193:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed. ``` ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Other ### Operating System Linux
GiteaMirror added the bug label 2026-04-10 17:45:31 -05:00
GiteaMirror commented 2026-04-10 17:45:34 -05:00
Author
Owner
Copy Link

@HansiWursti commented on GitHub (Dec 15, 2023):

Hi,

for me it seems to be a problem with raspberry, docker and node, and not specifically with actual:

example:
https://github.com/nodejs/docker-node/issues/1746

<!-- gh-comment-id:1858090305 --> @HansiWursti commented on GitHub (Dec 15, 2023): Hi, for me it seems to be a problem with raspberry, docker and node, and not specifically with actual: example: https://github.com/nodejs/docker-node/issues/1746
GiteaMirror commented 2026-04-10 17:45:34 -05:00
Author
Owner
Copy Link

@b-dont commented on GitHub (Dec 15, 2023):

Oh, thanks for finding that. I probably should have checked that.

<!-- gh-comment-id:1858092864 --> @b-dont commented on GitHub (Dec 15, 2023): Oh, thanks for finding that. I probably should have checked that.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#7754
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?