typicode/hotel

Hotel daemon not starting (macOS)

Open

#344 opened on 2019年9月30日

GitHub で見る
 (1 comment) (1 reaction) (0 assignees)JavaScript (9,939 stars) (474 forks)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
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.