-
Notifications
You must be signed in to change notification settings - Fork 27
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
StackOverflowError on highstate #106
Comments
So far, I'm not able to directly replicate. In my setup where all minions return, things run as expected. In the situation where some minions are offline, a runtime exception is raised to fail the build.
In your case, did the FATAL: null error occur about 120 seconds after some minions returned?
|
Hey @rbjorklin Are you still able to replicate this problem? As discussed in #107, it may be related to the Jenkins version. What version were you on when you encountered the exception? |
We have had this running as a nightly job which magically started working last night. We are on 2.83 right now and have been for about 2 days. The job has now failed once and worked once with 2.83 so not sure it's related to the Jenkins version. |
Is the saltapi response very large? Based on comments in #101, I think we may have found a cause for this issue. The http call to get the response from the salt-api only waits 5 seconds, and if it is a large response, this might not be enough. I've just upped it to 30 in this release. Could test and see if this helps? |
Just published the release with the increased timeout. It should hit the mirrors within the next 24 hours. Since everything is currently working, I'll close this out for now, but please let me know if you have any further problems. |
Sorry about the delay, I'll upgrade the plugin today and get back to you if the problem reoccurs but I think it's safe to leave this issue as closed. |
Actually, the issue reoccurred over the weekend but the stacktrace is slightly different so it might be a new issue?
|
Hmmm. These errors sure look like the jsonSearializer isn't able to parse json, meaning the response back from the salt-api isn't proper json. I'm currently unable to replicate, but perhaps we can get he bad return. If you were able to increase logging and able to view the response, that would be really helpful. Alternatively, perhaps manually querying the salt-api will show a bad response. Here's some curl to submit and query the salt-api. If you run the last curl on your JID, do you get a consistant reply, and is it valid json?
|
I had a look at the response, the JSON is in deed valid but it's 3 Mb in size so that may have something to do with it ;) My suspicion is that the JSON structure is too deep so I'll try increasing Java's stack memory and check if that helps. For context, what we're doing is running the highstate on all machines as part of a nightly build to make sure that they're all in sync. |
Can you send me the json return? I'd like to see if I can replicate with your results. |
Ping @rbjorklin, he should be able to fetch it |
Can you try this release? https://github.com/jenkinsci/saltstack-plugin/releases/tag/3.1.4-beta1 |
I've tried 3.1.4-beta1 without success :/ I emailed you the json response. Sorry about the delay @mchugh19. |
Tried running this:
And the output is as follows:
The text was updated successfully, but these errors were encountered: