Skip to main content
Participant
August 11, 2006
Answered

Not initializing core server

  • August 11, 2006
  • 6 replies
  • 601 views
Hello,

I installed FMS 2.0 develper version on a RedHat 3.0 and cannot initialize the server corerctly, when starting it using 'fmsmgr server fms start' or '/etc/init.d/fms start' the only process created is 'fmsadmin -console -conf ./conf/Server.xml' there is no sign of fmsedge, fmscore or fmsadmin therefore there is no listener on port 1935. The result is I can connect to the console but cannot initialize any applications for streaming or logging through the console.

I've tried different user ownerships and port numbers and nothing has worked. I'm pretty certain there is no firewall active in the server and no other process is listening on 1935.

I can't think of anything else to try, any pointers?

Thanks!
    This topic is closed to new replies. Start a new post to keep the conversation going.
    Correct answer yeraydiaz
    quote:

    Originally posted by: yeraydiaz
    thanks for the tip! seems my problem is a little different than yours, the output is:

    ./fmsmaster: error while loading shared libraries: libnspr4.so: cannot open shar
    ed object file: No such file or directory


    that was the error I got before I started to get 'Assert failed in /server/admin/FCSAdminServer.cpp line 358' :)

    installing the libnspr4 library fixed it for me, I'm sure it'll fix it for you too.



    It worked! I installed the library and now everything works great! I had to install a mozilla RPM though, couldn't find just the library RPM for RHEL 3.0 but everything is ok now.

    Thanks!

    6 replies

    Inspiring
    August 11, 2006
    Hi there,

    Check nohup.txt in your fms directory. I've found errors there before that weren't appearing anywhere else

    what version of the kernel are you running?
    yeraydiazAuthor
    Participant
    August 11, 2006
    It seems there is no nohup.txt anywhere, is it generated at startup?

    I'm using a 2.4.21 kernel, could that be a problem?
    Inspiring
    August 11, 2006
    Sorry, I edited my Server script so that the output stopped going to /dev/null.
    that created the nohup.txt on the next error

    I can't remember the line number, but it was somewhere around the 'please check /var/log/messages' message...

    Anyway, I was getting an 'assert failed' error that was preventing FMS from starting up and the only way to fix it was to upgrade the kernel to 2.6.8.