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.

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

Find a way to display full output/error when forked process fails #293

Open
ypujante opened this issue Apr 29, 2015 · 1 comment
Open

Find a way to display full output/error when forked process fails #293

ypujante opened this issue Apr 29, 2015 · 1 comment
Labels

Comments

@ypujante
Copy link
Member

As reported in this forum thread: http://glu.977617.n3.nabble.com/Glu-truncates-script-output-td4026892.html what happens is that ShellExec catches any error and throws an exception with an excerpt of the output and error (while preserving full output and error). There is currently no way to get a hold of the full output or error.

@sodul
Copy link
Contributor

sodul commented Apr 29, 2015

We have a similar issue. I think the current approach we (at Skyhigh Networks) should take is to catch the shell exec exception in the groovy script and have this print the tail of the python or whatever script (being called). I'm not sure it is desirable to modify the agent code to do that automatically modifying the default behavior of ShellExec. One option on the Glu Agent side could be to extend the ShellExec with a new option to throw the output of the called process with the current line number in the groovy script and the command line that was called. In that case capturing the output and present it to the stack trace is not necessarily trivial or desirable to implement directly in the agents either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants