Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not enough information for investigation agent failure from error output at AbstractAgentLauncher #4777

Closed
skryzhny opened this issue Apr 11, 2017 · 1 comment
Closed

Not enough information for investigation agent failure from error output at AbstractAgentLauncher #4777

skryzhny opened this issue Apr 11, 2017 · 1 comment
Assignees
@mmorhun
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@skryzhny
Copy link

Got several such errors:

2017-04-10 13:36:38,568[aceSharedPool-6]  [ERROR] [.a.a.s.l.AbstractAgentLauncher 149]  - An error occurs while starting 'SSH' agent. The agent didn't produce any logs.

This all I got in logs.
It's not possible start investigation, please fix it by including at least workspaceId.
Also container ID needed, if possible
It would be great also to have NodeID in case of swarm.

Reproduction Steps:
None

OS and version: Centos 7.3
@vkuznyetsov vkuznyetsov added kind/bug Outline of a bug - must adhere to the bug report template. sprint/next status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/enterprise labels Apr 11, 2017
@skryzhny skryzhny changed the title Impossible to investigate agent failure from error output at AbstractAgentLauncher Not enough information for investigation agent failure from error output at AbstractAgentLauncher Apr 13, 2017
@vkuznyetsov vkuznyetsov added the severity/P2 Has a minor but important impact to the usage or development of the system. label Apr 18, 2017
@mmorhun mmorhun mentioned this issue Apr 18, 2017
Merged
@mmorhun
Copy link
Contributor

mmorhun commented Apr 19, 2017

done

@mmorhun mmorhun closed this as completed Apr 19, 2017
@mmorhun mmorhun removed sprint/next status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Apr 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmorhun mmorhun

Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@skryzhny @vkuznyetsov @mmorhun