Bug 967940 - Fails with --- spRcvMsg max message length exceeded, 12249384 bytes from 140
Summary: Fails with --- spRcvMsg max message length exceeded, 12249384 bytes from 140
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sblim-sfcb
Version: 19
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-28 15:35 UTC by Tomáš Bžatek
Modified: 2015-03-03 23:06 UTC (History)
5 users (show)

Fixed In Version: sblim-sfcb-1.3.16-5.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-16 01:37:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomáš Bžatek 2013-05-28 15:35:50 UTC
Description of problem:
sfcbd fails with the following message when trying to enumerate class names in the /root/cimv2 namespace:

--- spRcvMsg max message length exceeded, 12249384 bytes from 140


Version-Release number of selected component (if applicable):
sblim-sfcb-1.3.16-3.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. start sfcbd, register sufficient amount of providers
2. try to enumerate class names, e.g. using YAWN

Additional info:
Looking at the source code, it seems this is caused by large CIM XML reply, exceeding the limit set in sfcb.cfg. Simply raising the value of the maxMsgLen argument makes it work again.

## Max message length, in bytes. This is a limit on the size of messages
## written across sockets, for instance, between providers and SFCB.
## Default is 10000000
maxMsgLen:      10000000

Since this is limiting when having sblim and openlmi providers registered, suggesting to raise this value in Fedora packages to get reasonable experience when using OpenLMI.

Comment 1 Peter Schiffer 2013-06-24 12:40:05 UTC
I've also just encountered this problem. Thanks for workaround.

peter

Comment 2 Fedora Update System 2013-06-24 14:28:21 UTC
sblim-sfcb-1.3.16-5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/sblim-sfcb-1.3.16-5.fc19

Comment 3 Fedora Update System 2013-06-24 18:51:26 UTC
Package sblim-sfcb-1.3.16-5.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sblim-sfcb-1.3.16-5.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-11616/sblim-sfcb-1.3.16-5.fc19
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-07-16 01:37:41 UTC
sblim-sfcb-1.3.16-5.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.