[DAEMON-193] Failed to start the Appc Daemon
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2017-11-29T21:30:41.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Appc Daemon 1.0.0 |
| Components | appcd |
| Labels | n/a |
| Reporter | Kondal Kolipaka |
| Assignee | Chris Barber |
| Created | 2017-11-28T04:45:04.000+0000 |
| Updated | 2017-11-29T21:30:41.000+0000 |
Description
"Failed to start the Appc Daemon" message shown when I start a daemon.
ITEM-AX40113:titanium_studio kkolipaka$ appc appcd start
Appcelerator Command-Line Interface, version 7.0.0-master.48
Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved.
Failed to start the Appc Daemon
ITEM-AX40113:titanium_studio kkolipaka$ appc appcd start --debug
Appcelerator Command-Line Interface, version 7.0.0-master.48
Copyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved.
Starting inspector on 127.0.0.1:9229 failed: address already in use
Failed to start the Appc Daemon
You have another instance running in the background. If the pid file is removed, the running server will not know and continue to run. The new instance can either A) have the running instance regenerate the pid file or B) stop the running instance. Option A is probably better.
Implemented DAEMON-196 which ensure the pid file always exists while the daemon is running.
In addition to the pid file always being made available, error handling during the start of the daemon has been improved and tested thoroughly on macOS and Windows. I believe this issue has been fixed.