Handling and passing down of privileges

[Alaricus]

Hello!

Mine may be an edge case, and if it cannot be made to work that's fine, but I just want to make sure I understand what's happening.

So, my setup is as follows: I am trying to run NextJS via Deno on an Ubuntu server. I am using a user with sudo privileges. Runing sudo deno task start works fine. The server launches and I am able to access it externally.

When I try deno task start without sudo, I get the following error, which makes sense:

PermissionDenied: Permission denied (os error 13): Permission denied (os error 13)
    at listen (ext:deno_net/01_net.js:504:35)
    at serve (ext:deno_http/00_serve.ts:555:16)
    at Array.processTicksAndRejections (ext:deno_node/_next_tick.ts:28:11)
    at eventLoopTick (ext:core/01_core.js:172:29) {
  name: "PermissionDenied",
  code: "EACCES"
}

Now, when I attempt to use pup, which I also run with sudo like this: sudo pup run myserver I get an infinite loop of crashes and restarts. The logs contain the same errors as above, which leads me to believe that when pup invokes deno, it does not run it with superuser privileges.

In case this matters, my pup.json looks like this:

  "processes": [
    {
      "id": "myserver",
      "cmd": "deno run start",
      "autostart": true
    }
  ]
}

Changing cmd to sudo deno run start doesn't seem to prevent the errors entirely. Instead, something strange happens. I see this being logged to the terminal:

2024-12-24T03:10:07.284Z [LOG] [core:processes] Process 'myserver' loaded
2024-12-24T03:10:07.285Z [LOG] [myserver:starting] Process starting, reason: autostart
2024-12-24T03:10:07.292Z [INFO] [core:api-rest] Starting the Rest API on 127.0.0.1:49152
2024-12-24T03:10:07.277Z [INFO] [core:rest] Initializing rest api
2024-12-24T03:10:07.401Z [ERROR] [myserver:stderr] Task start next start -H MY-IP-ADDRESS-HERE -p 80
2024-12-24T03:10:08.080Z [LOG] [myserver:stdout]    ▲ Next.js 15.0.3
2024-12-24T03:10:08.092Z [LOG] [myserver:stdout]    - Local:        http://MY-IP-ADDRESS-HERE:80
2024-12-24T03:10:08.099Z [LOG] [myserver:stdout]    - Network:      http://MY-IP-ADDRESS-HERE:80
2024-12-24T03:10:08.105Z [LOG] [myserver:stdout]
2024-12-24T03:10:08.112Z [LOG] [myserver:stdout]  ✓ Starting...
2024-12-24T03:10:08.520Z [LOG] [myserver:stdout]  ✓ Ready in 874ms

And then the terminal is never cleared despite the fact that I ran pup enable-service earlier.

What's even more strange is that the site is actually served, BUT, if I later terminate it and look at the logs, I see those endless restarts, even if I'd cleared the logs before! How can this be?

In light of all of the above I'd like to find out whether I'm doing something incorrectly or if this is what I should expect to be seeing.

Thank you! I appreciate any information on the matter.

[Hexagon]

Thanks for the detailed report, I'll look into this when i find some spare time.

Pup is currently designed to run as the current user with deno's privilege model, and when installed as a service, it's installed in user mode. It is also possible to install pup as a system service using flags, still with deno's privilege model.

Running Pup with escalated privileges will require more code, and need to be implemented carefully. Currently It's unclear when and why the privileges are downgraded.

[Alaricus]

Pup is currently designed to run as the current user with deno's privilege model

Oh, I see, that changes things a bit. I just tried running it without sudo, so only pup run myserver, and observed the same behavior: it starts, errors, continues, somehow serves the site, but refuses to run as a service. Maybe the problem is with Next, which refuses to run without sudo. (I'm assuming it's Next and not Deno because other than when running Next, Deno by itself does not require sudo.)

It seems I may have been barking up the wrong tree. Either way, thank you for your prompt response!

Edit: I think I know why it happens. Running on port 80 isn't possible without superuser privileges. So I do need for pup to pass that down to what it's attempting to run.

As an experiment I installed Nginx so that I could run Next on localhost. Still seeing the following:

2024-12-25T07:33:26.494Z [LOG] [core:processes] Process 'myserver' loaded
2024-12-25T07:33:26.495Z [LOG] [myserver:starting] Process starting, reason: autostart
2024-12-25T07:33:26.499Z [INFO] [core:api-rest] Starting the Rest API on 127.0.0.1:49152
2024-12-25T07:33:26.488Z [INFO] [core:rest] Initializing rest api
2024-12-25T07:33:26.583Z [ERROR] [myserver:stderr] Task start next start
2024-12-25T07:33:27.063Z [LOG] [myserver:stdout]    ▲ Next.js 15.0.3
2024-12-25T07:33:27.070Z [LOG] [myserver:stdout]    - Local:        http://localhost:3000
2024-12-25T07:33:27.076Z [LOG] [myserver:stdout]
2024-12-25T07:33:27.080Z [LOG] [myserver:stdout]  ✓ Starting...
2024-12-25T07:33:27.507Z [LOG] [myserver:stdout]  ✓ Ready in 766ms

If I Ctrl+C out of this I see:

^C2024-12-25T07:35:07.770Z [LOG] [core:terminate] Termination requested
2024-12-25T07:35:07.796Z [LOG] [myserver:stopping] Stopping process, reason: terminating
2024-12-25T07:35:07.796Z [LOG] [myserver:stop] Process stopped, reason: terminating
2024-12-25T07:35:07.782Z [LOG] [myserver:block] Process blocked, reason: terminating
2024-12-25T07:35:07.853Z [LOG] [myserver:errored] Process exited with error: Error: Aborted with exit code: 143
2024-12-25T07:35:08.356Z [INFO] [core:cleanup] /home/user1/git/deno-next-experiment/.pup/pup.json-tmp removed.

Funny enough, if following that I type in pup status I see this:

pup 1.0.4
https://github.com/hexagon/pup

Configuration:  /home/user1/git/deno-next-experiment/pup.json
Working dir:    /home/user1/git/deno-next-experiment
Instance name:  Not set
Rest API URL:   http://127.0.0.1:49152

Id              Type  Status     Blocked  Started    Exited     Restarts RSS    Code
pup             main  RUNNING    N/A      55 s ago   N/A        N/A      103 MB N/A
 myserver       proc  RUNNING    No       54 s ago   N/A        0        N/A    N/A