typicode/hotel

Hotel daemon not starting (macOS)

Open

#344 opened on Sep 30, 2019

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (9,939 stars) (474 forks)batch import
PR welcomehelp wanted

Description

Using macOS 10.14.5 (18F132) (Mojave) and node @ 10.41.1 and latest hotel.

I found that hotel start reported it had started, but the daemon wasn't running (as confirmed by curl http://localhost:2000 - gives no connection).

I was able to work around by running launchctl start hotel and then the daemon starts up. I'm not sure why user-startup doesn't make it run, but figured it was worth filing an issue (even if closed) so that others can find the work around.

Contributor guide

Tech stack
nodejs
Domain
tooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Node.jsmacOShotel
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue reports that `hotel start` claims to start the daemon but the daemon is not actually running on macOS Mojave. The workaround is to run `launchctl start hotel`. The root cause likely lies in the `user startup` script or the launchd plist configuration that fails to start the daemon automatically. To fix, investigate the file `user startup` in the repository and examine how the launchd plist is generated and loaded. Compare with the working case of manual `launchctl start`. The solution may involve updating the plist or the startup script to ensure the daemon is correctly registered and started.