Bug 1280346
Summary: | "stack depth limit exceeded" when submitting 600ESXi hypervisors/6500VMs via virt-who | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Christian Horn <chorn> | ||||||||
Component: | Candlepin | Assignee: | satellite6-bugs <satellite6-bugs> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | jcallaha | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 6.1.1 | CC: | bbuckingham, bkearney, chorn, csnyder, cwelton, dmoessne, egolov, ehelms, hsun, jcallaha, jokot3, mmccune, sauchter, tspeetje, xdmoon | ||||||||
Target Milestone: | Unspecified | Keywords: | Triaged | ||||||||
Target Release: | Unused | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | candlepin-0.9.54-5 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | |||||||||||
: | 1321630 1327220 1327224 (view as bug list) | Environment: | |||||||||
Last Closed: | 2016-09-27 09:01:46 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | 1327224 | ||||||||||
Bug Blocks: | 1296845, 1321630, 1351644 | ||||||||||
Attachments: |
|
Description
Christian Horn
2015-11-11 14:24:47 UTC
Any comments? Will this be approached in 6.2 ? Increasing max_stack_depth to 3Mb might be a simple thing to do? Or are there other suggestions for workarounds? Alternatively the query could be structured differently, maybe? max_stack_depth (integer) Specifies the maximum safe depth of the server's execution stack. The ideal setting for this parameter is the actual stack size limit enforced by the kernel (as set by ulimit -s or local equivalent), less a safety margin of a megabyte or so. The safety margin is needed because the stack depth is not checked in every routine in the server, but only in key potentially-recursive routines such as expression evaluation. The default setting is two megabytes (2MB), which is conservatively small and unlikely to risk crashes. However, it might be too small to allow execution of complex functions. Only superusers can change this setting. Setting max_stack_depth higher than the actual kernel limit will mean that a runaway recursive function can crash an individual backend process. On platforms where PostgreSQL can determine the kernel limit, the server will not allow this variable to be set to an unsafe value. However, not all platforms provide the information, so caution is recommended in selecting a value. Hi, Can you provide the Candlepin logs from the time of this error? It would be helpful in tracking down the exact code path if we had the stack trace on the Candlepin side. Thanks! Created attachment 1164087 [details]
candlepin_stack
Verified in Satellite 6.1.10 Snap 3. 1. downloaded the file located here: http://file.rdu.redhat.com/csnyder/test_vodaphone.json 2. Registered the satellite to itself 3. Ran this command curl -k -X POST --cert /etc/pki/consumer/cert.pem --key /etc/pki/consumer/key.pem https://rhsm-qe-1.rhq.lab.eng.bos.redhat.com/rhsm/hypervisors -H "Content-Type: application/json" -d @"test_vodaphone.json" The command completed successfully and all content hosts were added correctly (see attached). The output was captured and will be attached as well. Created attachment 1204262 [details]
verification screenshot
Created attachment 1204263 [details]
output.txt
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1938 |