[Ambari] 'service ambari-server start' never finishes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Sahara |
Fix Released
|
High
|
Vitalii Gridnev | ||
Mitaka |
Fix Released
|
High
|
Vitalii Gridnev |
Bug Description
In my Sahara deployment (Mitaka), it seems like my Ambari server takes just long enough to start that it hits a deadlock. I've updated the ssh_timeout_common from 300 to 900 and it never finishes. The odd part is that when the ssh session times out the server finishes starting properly. My current running theory is that since they flush to stdout and it doesn't look like the output is being captured this is causing the script to wait for the ability to write to the OS stdout buffer but since it's not being read the OS blocks when trying to flush. I've changed the line here [0] to 'service ambari-server start >/dev/null' and it seemed to fix my installation. This change feels like a hack though so maybe the system should be piping the output somehow? The related change in Ambari is here [1] and [2]. I'm not sure a change in Ambari caused this to happen though as I was having intermittent issues with this before the Mitaka upgrade.
[0]: https:/
[1]: https:/
[2]: https:/
Changed in sahara: | |
importance: | Medium → High |
Changed in sahara: | |
assignee: | nobody → Vitaly Gridnev (vgridnev) |
Changed in sahara: | |
milestone: | newton-1 → newton-2 |
no longer affects: | sahara/mitaka |
Can you explain what image was used?