[DCOS_OSS-957] navstar component is unable to start Created: 17/Apr/17  Updated: 09/Nov/18  Resolved: 26/Jul/18

Status: Resolved
Project: DC/OS
Component/s: navstar
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: High
Reporter: Maksym Naboka (Inactive) Assignee: Deepak Goel
Resolution: Cannot Reproduce  
Labels: networking
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: DELETE Networking Team
Watchers:
Deepak Goel, Maksym Naboka (Inactive), Marco Monaco

 Description   

A number of failing jobs have been noticed with unhappy navstar lately.

It seems that sometimes the service is failing to start.

Logs from journald:

2017-04-17 16:47:50: Starting Navstar: A distributed systems & network overlay orchestration engine...
2017-04-17 16:47:50: dcos-navstar.service: Control process exited, code=exited status=1
2017-04-17 16:47:50: Failed to start Navstar: A distributed systems & network overlay orchestration engine.
2017-04-17 16:47:50: dcos-navstar.service: Unit entered failed state.
2017-04-17 16:47:50: dcos-navstar.service: Failed with result 'exit-code'.
2017-04-17 16:47:55: dcos-navstar.service: Service hold-off time over, scheduling restart.
2017-04-17 16:47:55: Stopped Navstar: A distributed systems & network overlay orchestration engine.
2017-04-17 16:47:55: Starting Navstar: A distributed systems & network overlay orchestration engine...
2017-04-17 16:47:55: dcos-navstar.service: Control process exited, code=exited status=1
2017-04-17 16:47:55: Failed to start Navstar: A distributed systems & network overlay orchestration engine.
2017-04-17 16:47:55: dcos-navstar.service: Unit entered failed state.
2017-04-17 16:47:55: dcos-navstar.service: Failed with result 'exit-code'.
2017-04-17 16:48:00: dcos-navstar.service: Service hold-off time over, scheduling restart.
2017-04-17 16:48:00: Stopped Navstar: A distributed systems & network overlay orchestration engine.
2017-04-17 16:48:00: Starting Navstar: A distributed systems & network overlay orchestration engine...
2017-04-17 16:48:00: dcos-navstar.service: Control process exited, code=exited status=1
2017-04-17 16:48:00: Failed to start Navstar: A distributed systems & network overlay orchestration engine.
2017-04-17 16:48:00: dcos-navstar.service: Unit entered failed state.
2017-04-17 16:48:00: dcos-navstar.service: Failed with result 'exit-code'.

https://teamcity.mesosphere.io/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=620350#_focus=3907

https://teamcity.mesosphere.io/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=620513#_focus=3890

https://teamcity.mesosphere.io/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=620242#_focus=3898

 



 Comments   
Comment by Maksym Naboka (Inactive) [ 17/Apr/17 ]

it seems that navstar has been failing for a long time, here is the history of failed jobs

https://teamcity.mesosphere.io/project.html?projectId=ClosedSource_Dcos_IntegrationTests_CloudIntegrationTests&buildTypeId=&tab=testDetails&testNameId=-8649139282545815058&order=TEST_STATUS_DESC&branch_ClosedSource_Dcos_IntegrationTests_CloudIntegrationTests=__all_branches__&itemsCount=50

Comment by Maksym Naboka (Inactive) [ 17/Apr/17 ]

cc Sebastien Pahl

Comment by Marco Monaco [ 26/Jul/18 ]

This is a old ticket, but nothing happened so far. I am trying to address it now. Can you please make sure this is still valid and appears on the right team's radar? Thanks

Generated at Thu Dec 02 12:49:53 CST 2021 using JIRA 7.8.4#78004-sha1:5704c55c9196a87d91490cbb295eb482fa3e65cf.