• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

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

New Here ,
Sep 27, 2013 Sep 27, 2013

Copy link to clipboard

Copied

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.

Views

5.2K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 02, 2013 Oct 02, 2013

Copy link to clipboard

Copied

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 [~]#

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 04, 2013 Oct 04, 2013

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Dec 08, 2013 Dec 08, 2013

Copy link to clipboard

Copied

LATEST

I've meet the same error.

How to resolve it ?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines