[JIRA] Commented: (SSPCPP-423) After upgrading SP to Alpha SP 2.5 RPM from previous version of SP, shibd does not start.

Scott Cantor (JIRA) noreply at shibboleth.net
Fri Feb 17 18:43:37 GMT 2012


    [ https://issues.shibboleth.net/jira/browse/SSPCPP-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846#comment-13846 ] 

Scott Cantor commented on SSPCPP-423:
-------------------------------------

Ah, this is the Xerces issue, I think I have some platforms stuck with different versions of Xerces in the two repos. I'll see if I can get that sync'd up.

> After upgrading SP to Alpha SP 2.5 RPM from previous version of SP, shibd does not start.
> -----------------------------------------------------------------------------------------
>
>                 Key: SSPCPP-423
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-423
>             Project: Shibboleth SP - C++
>          Issue Type: Bug
>          Components: Installation / Packaging
>         Environment: CentOS 5.7 / i386
>            Reporter: Takeshi Nishimura
>            Assignee: Scott Cantor
>
> After upgrading SP to Alpha SP 2.5 RPM from previous version of SP, shibd does not start.
> Error messages:
> {noformat}
> $ sudo /sbin/service shibd start
> Starting shibd: bash: line 1: 12826 Segmentation fault      /usr/sbin/shibd -p /var/run/shibboleth/shibd.pid -f -w 30
>                                                            [FAILED]
> {noformat}
> libxml-security-c16-1.6.1-3.1 (or any version in security_shibboleth repository) does not work with new shibboleth package. Version 1.6.1-4.1 (or any version in home_Scott_Cantor repository) does work.
> Packages:
> {noformat}
> $ rpm -qa | egrep log4shib\|opensaml\|shib\|xerces\|xml-security-c\|xmltooling | sort
> liblog4shib1-1.0.4-5.3
> liblog4shib-devel-1.0.4-5.3
> libxerces-c-3_0-3.0.1-3.2
> libxerces-c-3_1-3.1.1-2.1
> libxerces-c-devel-3.1.1-2.1
> libxml-security-c16-1.6.1-3.1
> libxml-security-c-devel-1.6.1-3.1
> libxmltooling5-1.4.2-3.1
> libxmltooling6-1.5-33.1
> log4shib-debuginfo-1.0.4-5.3
> opensaml-debuginfo-2.5-16.1
> opensaml-schemas-2.5-16.1
> shibboleth-2.5-43.1
> shibboleth-debuginfo-2.5-43.1
> xerces-c-debuginfo-3.1.1-2.1
> xml-security-c-debuginfo-1.6.1-3.1
> xmltooling-debuginfo-1.5-33.1
> xmltooling-schemas-1.5-33.1
> {noformat}
> Backtraces:
> {noformat}
> $ sudo gdb /usr/sbin/shibd
> GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-37.el5_7.1)
> ... snip ...
> Reading symbols from /usr/sbin/shibd...Reading symbols from /usr/lib/debug/usr/sbin/shibd.debug...done.
> done.
> (gdb) run -p /var/run/shibboleth/shibd.pid -f -w 30
> Starting program: /usr/sbin/shibd -p /var/run/shibboleth/shibd.pid -f -w 30
> warning: .dynamic section for "/lib/libnsl.so.1" is not at the expected address
> warning: difference appears to be caused by prelink, adjusting expectations
> ... snip ...
> [Thread debugging using libthread_db enabled]
> Program received signal SIGSEGV, Segmentation fault.
> 0x01d0f2cb in xercesc_3_1::XMLString::transcode (toTranscode=0x4422d9 "", manager=0x0) at xercesc/util/XMLString.cpp:615
> 615         return gTranscoder->transcode(toTranscode, manager);
> (gdb) bt
> #0  0x01d0f2cb in xercesc_3_1::XMLString::transcode (toTranscode=0x4422d9 "", manager=0x0) at xercesc/util/XMLString.cpp:615
> #1  0x003d0674 in DSIGConstants::create () at dsig/DSIGConstants.cpp:237
> #2  0x003fa1d5 in XSECPlatformUtils::Initialise (p=0x0) at utils/XSECPlatformUtils.cpp:111
> #3  0x00e7d02f in ing::XMLToolingInternalConfig::init (this=0xffa600) at XMLToolingConfig.cpp:412
> #4  0x0087081b in opensaml::SAMLInternalConfig::init (this=0xc122a0, initXMLTooling=true) at SAMLConfig.cpp:167
> #5  0x001a083c in shibsp::SPConfig::init(char const*, char const*) () from /usr/lib/libshibsp.so.6
> #6  0x001a2e9e in shibsp::SPInternalConfig::init(char const*, char const*) () from /usr/lib/libshibsp.so.6
> #7  0x08049843 in main (argc=Cannot access memory at address 0x12c
> ) at shibd.cpp:370
> {noformat}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the commits mailing list