Bug: Infrastructure agent won't launch on linux [ERR_MODULE_NOT_FOUND] #1011

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

Originally created by @sysoppl on 5/8/2024

Describe the bug
I tried to run infrastructure agent on several linux machines, VMs, LXCs and bare metal, but every time there is same behavior - it won't even start.

To Reproduce
Steps to reproduce the behavior:

  1. Installed agent using curl -s https://xxx/docs/static/scripts/infrastructure-agent/install-linux.sh | bash command
  2. Started agent using oneuptime-infrastructure-agent start --secret-key=1234 --oneuptime-url=https://xxx command
  3. Check logs file (oneuptime-infrastructure-agent logs show nothing)
  4. See error

Expected behavior
Work as intended

Server 1 :

  • OS: ubuntu 22 LXC

Server 2 :

  • OS: ubuntu-server 22.04 LTS

Server 3 :

  • OS: debian 12

Deployment Type
self hosted

Additional context

ubuntu@hostname:~$ cat err.log

node:internal/modules/run_main:125
    triggerUncaughtException(
    ^
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/ubuntu/Start.ts' imported from /home/ubuntu/
    at finalizeResolution (node:internal/modules/esm/resolve:264:11)
    at moduleResolve (node:internal/modules/esm/resolve:924:10)
    at defaultResolve (node:internal/modules/esm/resolve:1148:11)
    at nextResolve (node:internal/modules/esm/hooks:750:28)
    at y (file:///home/ubuntu/.nvm/versions/node/v22.1.0/lib/node_modules/tsx/dist/esm/index.mjs?1715183762080:2:2065)
    at j (file:///home/ubuntu/.nvm/versions/node/v22.1.0/lib/node_modules/tsx/dist/esm/index.mjs?1715183762080:2:3353)
    at nextResolve (node:internal/modules/esm/hooks:750:28)
    at Hooks.resolve (node:internal/modules/esm/hooks:238:30)
    at handleMessage (node:internal/modules/esm/worker:199:24)
    at Immediate.checkForMessages (node:internal/modules/esm/worker:141:28) {
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///home/ubuntu/Start.ts'
}

Node.js v22.1.0

logs and daemon file are created in the root folder of the user, so in this example in /home/ubuntu/

*Originally created by @sysoppl on 5/8/2024* **Describe the bug** I tried to run infrastructure agent on several linux machines, VMs, LXCs and bare metal, but every time there is same behavior - it won't even start. **To Reproduce** Steps to reproduce the behavior: 1. Installed agent using ```curl -s https://xxx/docs/static/scripts/infrastructure-agent/install-linux.sh | bash``` command 2. Started agent using ```oneuptime-infrastructure-agent start --secret-key=1234 --oneuptime-url=https://xxx``` command 3. Check logs file (```oneuptime-infrastructure-agent logs``` show nothing) 4. See error **Expected behavior** Work as intended **Server 1 :** - OS: ubuntu 22 LXC **Server 2 :** - OS: ubuntu-server 22.04 LTS **Server 3 :** - OS: debian 12 **Deployment Type** self hosted **Additional context** ``` ubuntu@hostname:~$ cat err.log node:internal/modules/run_main:125 triggerUncaughtException( ^ Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/home/ubuntu/Start.ts' imported from /home/ubuntu/ at finalizeResolution (node:internal/modules/esm/resolve:264:11) at moduleResolve (node:internal/modules/esm/resolve:924:10) at defaultResolve (node:internal/modules/esm/resolve:1148:11) at nextResolve (node:internal/modules/esm/hooks:750:28) at y (file:///home/ubuntu/.nvm/versions/node/v22.1.0/lib/node_modules/tsx/dist/esm/index.mjs?1715183762080:2:2065) at j (file:///home/ubuntu/.nvm/versions/node/v22.1.0/lib/node_modules/tsx/dist/esm/index.mjs?1715183762080:2:3353) at nextResolve (node:internal/modules/esm/hooks:750:28) at Hooks.resolve (node:internal/modules/esm/hooks:238:30) at handleMessage (node:internal/modules/esm/worker:199:24) at Immediate.checkForMessages (node:internal/modules/esm/worker:141:28) { code: 'ERR_MODULE_NOT_FOUND', url: 'file:///home/ubuntu/Start.ts' } Node.js v22.1.0 ``` logs and daemon file are created in the root folder of the user, so in this example in /home/ubuntu/
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#1011