Bug #2007
Handle xml-rpc message size limit
| Status: | Closed | Start date: | 05/09/2013 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.0 |
Description
Bug reported in the mailing list by Thomas Higdon:
The daemon was passing back 500 because xmlrpc-c thought the monitoring data
I was asking for was too big. Changing VM_MONITORING_EXPIRATION_TIME to 300
solved my problem.
History
#1
Updated by Ruben S. Montero about 8 years ago
- Category set to Core & System
#2
Updated by Ruben S. Montero about 8 years ago
- Priority changed from Normal to Low
#3
Updated by Carlos Martín almost 7 years ago
- Status changed from New to Closed
- Resolution set to fixed
Should have been closed before, oned.conf now has MESSAGE_SIZE.