<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks Jesper, for the quick and helpful answer. Playing around
with those flags did indeed help.<br>
</p>
<div class="moz-cite-prefix">Am 07.03.20 um 11:08 schrieb Jesper
Louis Andersen:<br>
</div>
<blockquote type="cite"
cite="mid:CAGrdgiWrizQ-x4djHSgxQe5tBN8SsvKU8VCNk=UFvTrjKjU-GA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">Try just
running `erl` in the shell. If that fails, you can try toying
with the flags +S +SDcpu and +SDio to control the amount of
schedulers you have. As a conservative start you want these to
be the number of available cores in the virtual machine. Check
the limits in the virtual machine w.r.t. number of threads.
You also have the +A parameter, which creates threads. So
while the error occurs at the dirty scheduler thread spawn, it
might be another thread pool using up your resources and
imposing limits.</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif">(Aside: your
virtual machine would have far more trouble with a Go program
if it limits threads)</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Mar 6, 2020 at 4:52 PM
Alemuell <<a href="mailto:alemuell@uos.de"
moz-do-not-send="true">alemuell@uos.de</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
there!<br>
<br>
My issue: the requirement for installing some software I need
is to have<br>
rabbitmq running which depends on erlang. So my first step is
to install<br>
erlang. I'm working on a virtual server (!) which has Ubuntu
18.04 LTS<br>
64bit running. I added the file<br>
/etc/apt/sources.list.d/bintray.erlang.list with the following
line:<br>
"deb <a href="http://dl.bintray.com/rabbitmq-erlang/debian"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://dl.bintray.com/rabbitmq-erlang/debian</a>
bionic erlang". Then I<br>
use apt to install erlang, which runs smoothly.<br>
<br>
When I now try to start erlang on the command line I directly
get:<br>
"Failed to create dirty cpu scheduler thread 9, error = 11" (I
can<br>
provide erlang crash report if needed)<br>
<br>
Searching for solutions for this issue already brought me to a<br>
rabbitmq-discussion:<br>
<a
href="https://groups.google.com/forum/#!msg/rabbitmq-users/fQzBHvgL5rg/iW1S6ln6BwAJ"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://groups.google.com/forum/#!msg/rabbitmq-users/fQzBHvgL5rg/iW1S6ln6BwAJ</a><br>
It seems to me, that I'm having exactly the same issue, but
the solution<br>
presented there is not working for me. Also I believe, that
the issue is<br>
related to erlang (since I don't even get to the point of
installing<br>
rabbitmq), thats why I wanted to post it on this erlang-list.
The main<br>
idea that the discussion in that rabbitmq-thread brings up,
is, that the<br>
issue is related to working on a virtual server: it seems that
erlang is<br>
not aware of the fact, that it can only use a limited amount
of<br>
cpu-ressources.<br>
<br>
Does any one have an idea of how to fix that? I really don't
understand<br>
a thing about erlang nor rabbitmq. I just need them to work
for another<br>
software I want to use. Digging into docs of erlang is a bit<br>
overwhelming to me and I don't really have an idea, where
exactly I<br>
would need to start looking. I have the feeling, that I would
just need<br>
to add some configuration file or something similar, so that
erlang is<br>
told, how many threads it should open (not calculating it by
itself).<br>
<br>
I would really much appreciate any help!<br>
<br>
Best,<br>
<br>
alemuell<br>
<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">J.</div>
</blockquote>
</body>
</html>