typicode/hotel

Hotel daemon not starting (macOS)

Open

#344 建立於 2019年9月30日

在 GitHub 查看
 (1 留言) (1 反應) (0 負責人)JavaScript (9,939 star) (474 fork)batch import
PR welcomehelp wanted

描述

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.

貢獻者指南

技術棧
nodejs
領域
tooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Node.jsmacOShotel
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
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.