I've just installed ejabberd 16.01 on my CentOS 7.1.1503, I have used the rpm installer downloaded from ProcessOne's web site using:
sudo rpm -Uvh ejabberd-16.01-0.x86_64.rpm
The installation went well up until the end, but finally I got an error message (without any description). I took a look into /opt/ejabberd-16.01 and saw everything was in it's place so I've tried running /bin/postinstall.sh manually to see what might go wrong.
When I run the script I get the following output:
-=- ejabberd post installation script -=-
(c) 2005-2015 ProcessOne
* Checking ejabberd installation
usermod: no changes
* Starting ejabberd instance
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
Failed to create main carrier for ll_alloc
Aborted (core dumped)
I get a familiar experience when I start the ejabbered server using:
ejabberdctl start
and then when I try to use ejabberdctl again (to stop/register a user) I get the same result:
1
From searching around I've found some connection to memory issues (erl with centos Failed to create main carrier for ll_alloc)
but this doesn't seem to be the case since I have 1GB of RAM and this is the output of top command: 3
so as you can see I have 573MB of free RAM (shouldn't it be enough??)
any help would be very much appreciated,
Thank you.
Related
2022-11-13 03:03:35 [info] logging to syslog
bgpdump: bgpdump_lib.c:676: process_mrtd_table_dump_v2_ipv6_unicast: Assertion `e->peer_index <= entry->dump->table_dump_v2_peer_index_table->peer_count' failed.
Aborted (core dumped)
I check my disk space is enough,and I thought the file was too large, split into several small files and the resulting file was empty
Hey I am trying to run a svelte app using vite but when I run npm run dev it gives error in terminal :
QSocketNotifier: Can only be used with threads started with QThread
(./src/core/Core.cpp l.710): Opening the file: dev
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Cannot open file dev
Aborted (core dumped)
Is it something to do with my pc ?
node: v16.15.0
platform: ubuntu 22
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:mergeDebugResources'.
Multiple task action failures occurred:
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> AAPT2 aapt2-4.0.0-6051327-windows Daemon #4: Daemon startup failed
Please check if you installed the Windows Universal C Runtime.
This should not happen under normal circumstances, please file an issue if it does.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> AAPT2 aapt2-4.0.0-6051327-windows Daemon #3: Daemon startup failed
Please check if you installed the Windows Universal C Runtime.
This should not happen under normal circumstances, please file an issue if it does.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> AAPT2 aapt2-4.0.0-6051327-windows Daemon #5: Daemon startup failed
Please check if you installed the Windows Universal C Runtime.
This should not happen under normal circumstances, please file an issue if it does.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> AAPT2 aapt2-4.0.0-6051327-windows Daemon #6: Daemon startup failed
Please check if you installed the Windows Universal C Runtime.
This should not happen under normal circumstances, please file an issue if it does.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> AAPT2 aapt2-4.0.0-6051327-windows Daemon #7: Daemon startup failed
Please check if you installed the Windows Universal C Runtime.
This should not happen under normal circumstances, please file an issue if it does.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> AAPT2 aapt2-4.0.0-6051327-windows Daemon #8: Daemon startup failed
Please check if you installed the Windows Universal C Runtime.
This should not happen under normal circumstances, please file an issue if it does.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> AAPT2 aapt2-4.0.0-6051327-windows Daemon #9: Daemon startup failed
Please check if you installed the Windows Universal C Runtime.
This should not happen under normal circumstances, please file an issue if it does.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> AAPT2 aapt2-4.0.0-6051327-windows Daemon #10: Daemon startup failed
Please check if you installed the Windows Universal C Runtime.
This should not happen under normal circumstances, please file an issue if it does.
Daemon startup failed Please check if you installed the Windows
Universal C Runtime.
Have you updated your Runtime ?
Download: https://support.microsoft.com/en-ca/help/2999226/update-for-universal-c-runtime-in-windows
I'm getting the following error while trying to connect
Failed to connect to domain: REDHAWK_DEV
org.eclipse.core.runtime.CoreException: Error while executing callable. Caused by
org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
I tried
$ nodeBooter -D
Segmentation fault (core dumped)
and also
$ cleanomni
sh: 1: /etc/init.d/omniNames: not found
I'm on Ubuntu 14.04.5 64bit with redhawk-src-2.0.3
Is there any solution?
Based on the dialog, this was a network issue, not a REDHAWK configuration issue. We will consider adding the text mentioned in the manual for clarification.
I have been getting 'FATAL ERROR: JS Allocation failed - process out of memory
Aborted (core dumped)' error while running a nodejs process although I am using the command :
node --max-old-space-size=8192 run.js
I am using v10.25.
The code simply downloads data(size=2gb) from aws s3 and there are some data manipulation associated.
Why would nodejs run out of memory?
How to run this nodejs process without the fatal error?
Any help is appreciated.
Edit 1:-
inspecting with
console.log(util.inspect(process.memoryUsage()));
Just before crashing gives this:-
{ rss: 1351979008, heapTotal: 1089684736, heapUsed: 1069900560 }
For anyone who is facing this issue.
I installed nodejs v12.02 to use --max-old-space-size=8192.
It was not working in v10.25.