Skip to main content
B
bobakb
Known Participant
September 27, 2013
Question

Getting error: Process 21724 failed to create IPC queue __FCS_REGISTRY__ : Failed to allocate shared

  • September 27, 2013
  • 1 reply
  • 5361 views

FMIS 4.5 is giving this error in core log file:

Process 21724 failed to create IPC queue __FCS_REGISTRY__ : Failed to allocate shared memory.

Restarting FMIS doesn't seem to help, I have to physically restart the server.

Server has 8 GB RAM. 'freemem' report:

             total       used       free     shared    buffers     cached

Mem:       8164972    4622744    3542228          0    1197448    1851580

-/+ buffers/cache:    1573716    6591256

Swap:     10217332          0   10217332

What is this error about and are there any settings I can change to allocate FMIS more memory?

Thanks.

    This topic has been closed for replies.

    1 reply

    R
    rjp421
    Known Participant
    October 3, 2013

    can you paste the output of:

    su -c "ulimit -a" ams

    replace ams with the username of the account youre using to run the media server as.

    it should look similar to:

    root@ns1 [~]# su -c "ulimit -a" ams

    core file size          (blocks, -c) 0

    data seg size           (kbytes, -d) unlimited

    scheduling priority             (-e) 0

    file size               (blocks, -f) unlimited

    pending signals                 (-i) 127225

    max locked memory       (kbytes, -l) 64

    max memory size         (kbytes, -m) unlimited

    open files                      (-n) 1024

    pipe size            (512 bytes, -p) 8

    POSIX message queues     (bytes, -q) 819200

    real-time priority              (-r) 0

    stack size              (kbytes, -s) unlimited

    cpu time               (seconds, -t) unlimited

    max user processes              (-u) 2047

    virtual memory          (kbytes, -v) unlimited

    file locks                      (-x) unlimited

    root@ns1 [~]#

    B
    bobakbAuthor
    Known Participant
    October 5, 2013

    We just inreased the RAM from 8GB to 16GB and I think it's helped get rid of this error. FMS was installed as root so: here is the output of your request:

    su -c "ulimit -a" root

    core file size          (blocks, -c) 0

    data seg size           (kbytes, -d) unlimited

    scheduling priority             (-e) 0

    file size               (blocks, -f) unlimited

    pending signals                 (-i) 128309

    max locked memory       (kbytes, -l) 32

    max memory size         (kbytes, -m) unlimited

    open files                      (-n) 1024

    pipe size            (512 bytes, -p) 8

    POSIX message queues     (bytes, -q) 819200

    real-time priority              (-r) 0

    stack size              (kbytes, -s) 10240

    cpu time               (seconds, -t) unlimited

    max user processes              (-u) 128309

    virtual memory          (kbytes, -v) unlimited

    file locks                      (-x) unlimited

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices