{ "id": "170472", "key": "DAEMON-193", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "12519", "key": "DAEMON", "name": "Appcelerator Daemon" }, "fixVersions": [ { "id": "18407", "description": "", "name": "Appc Daemon 1.0.0", "archived": false, "released": true, "releaseDate": "2017-12-05" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2017-11-29T21:30:41.000+0000", "created": "2017-11-28T04:45:04.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [], "versions": [], "issuelinks": [], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2017-11-29T21:30:41.000+0000", "status": { "description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.", "name": "Resolved", "id": "5", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "15049", "name": "appcd", "description": "Bootstrap, appcd CLI commands (start, stop, restart, exec, logcat, config, status)" } ], "description": "\"Failed to start the Appc Daemon\" message shown when I start a daemon. \r\n\r\n{code:java}\r\nITEM-AX40113:titanium_studio kkolipaka$ appc appcd start\r\nAppcelerator Command-Line Interface, version 7.0.0-master.48\r\nCopyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved.\r\n\r\n\r\nFailed to start the Appc Daemon\r\n{code}\r\n\r\nLooks like it's showing a wrong message when the daemon is already running.\r\n\r\n{code:java}\r\nITEM-AX40113:titanium_studio kkolipaka$ appc appcd start --debug\r\nAppcelerator Command-Line Interface, version 7.0.0-master.48\r\nCopyright (c) 2014-2017, Appcelerator, Inc. All Rights Reserved.\r\n\r\n\r\nStarting inspector on 127.0.0.1:9229 failed: address already in use\r\nFailed to start the Appc Daemon\r\n{code}\r\n", "attachment": [], "flagged": false, "summary": "Failed to start the Appc Daemon", "creator": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "kkolipaka", "key": "kkolipaka", "displayName": "Kondal Kolipaka", "active": false, "timeZone": "America/Los_Angeles" }, "environment": "7.0.0-master.48", "closedSprints": [ { "id": 976, "state": "closed", "name": "2017 Sprint 24 Tooling", "startDate": "2017-11-19T19:00:51.738Z", "endDate": "2017-12-03T19:00:00.000Z", "completeDate": "2017-12-04T23:20:34.438Z", "originBoardId": 219 } ], "comment": { "comments": [ { "id": "431337", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "You have another instance running in the background.\r\n\r\nIf 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.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2017-11-28T06:27:53.000+0000", "updated": "2017-11-28T06:27:53.000+0000" }, { "id": "431376", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "Implemented DAEMON-196 which ensure the pid file always exists while the daemon is running.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2017-11-28T10:46:31.000+0000", "updated": "2017-11-28T10:46:31.000+0000" }, { "id": "431484", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "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.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2017-11-29T21:30:41.000+0000", "updated": "2017-11-29T21:30:41.000+0000" } ], "maxResults": 3, "total": 3, "startAt": 0 } } }