Archived

This forum has been archived. Please start a new discussion on GitHub.

Segmentation fault in Icestorm

Hello!!

I have updated to Ice 3.1.0 and I can't start IceStorm by using IceBox. I use Debian Sid. Here is my config file:

IceBox.Service.IceStorm=IceStormService,30:create
Freeze.DbEnv.IceStorm.DbHome=db
IceStorm.TopicManager.Endpoints=default -h localhost -p 9999
IceStorm.Publish.Endpoints=tcp

#TopicManager Tracing
IceStorm.Trace.TopicManager=2
#Topic Tracing
IceStorm.Trace.Topic=1

IceStorm.InstanceName=DirectoryFacilitator

And here is my order:

$ icebox --Ice.Config=config/icestorm.cfg

with the error:

icebox: error: ServiceManager: unable to load entry point `IceStormService,30:create': libIceStormService.so.30: cannot open shared object file: No such file or directory

If I change IceStormService,30 to IceStormService,31, I obtain the following error:

icebox: error: ServiceManager: unable to load entry point `IceStormService,31:create': /usr/lib/libIceStormService.so.31: undefined symbol: create

Thank you very much!!

Comments

  • bernard
    bernard Jupiter, FL
    Hi David,

    The name of the function changed in 3.1: it's now createIceStorm. You just need to update your configuration to:
    IceBox.Service.IceStorm=IceStormService,31:createIceStorm
    

    Cheers,
    Bernard
  • Problems activating server with icegridadmin

    Thank you very much! I have solved my current problems.
  • matthew
    matthew NL, Canada
    Did IceStorm actually segfault under these circumstances? If so, that's a bug with Ice 3.1.
  • It is not a bug

    Hello again!

    It is not a bug, it was an error of mine.