rabbitmq is not starting on webfaction shared server.

[TM Waseer]

I've followed this post(http://raichev.net/adding-celery-with-rabbitmq-to-a-django-project-on-webfaction.html) to setup rabbitmq on server. I've successfully installed erlang and it is running on my server.
But following the steps for rabbitmq-server does not work. Post seems to be old, is there anything else I need to do with the latest version of erlang and rabbitmq-server.

[Luke Bakken]

Hello,

It is impossible for us to help you out without more information. What steps aren't working? What output are you seeing? What versions of Erlang and RabbitMQ are you using?

There appear to be a number of other articles with regard to setting up RabbitMQ on Webfaction:

https://community.webfaction.com/questions/2366/can-i-use-rabbit-mq-on-the-shared-servers

http://aameer.github.io/installing-rabbitmq-on-webfaction/

I suggest following up here with more information, or asking on community.webfaction.com

Thanks,

Luke

Staff Software Engineer

Pivotal / RabbitMQ

[TM Waseer]

I've installed erlang(v20) on server. And next followed the steps to install rabbitmq-server;

1. I've downloaded the unix generic release of rabbit-mq server and extracted it under my custom app directory.
2. Created a simlink to erlang using cd ~/lib/erlang/lib/; ln -s mycustom_app/rabbitmq_server-3.6.14
3. then changed the defaults to as suggested in tutorial;

     

...
# comment these lines:
#CONFIG_FILE=${SYS_PREFIX}/etc/rabbitmq/rabbitmq
#LOG_BASE=${SYS_PREFIX}/var/log/rabbitmq
#MNESIA_BASE=${SYS_PREFIX}/var/lib/rabbitmq/mnesia
# add these lines:
CONFIG_FILE=/home/<username>/rabbitmq_server-3.6.14/sbin/
LOG_BASE=/home/<username>/logs/user/rabbitmq # create this directory!
MNESIA_BASE=/home/<username>/rabbitmq_server-3.6.14/sbin/

4. Create the RabbitMQ log directory: mkdir /home/<username>/logs/user/rabbitmq

5. updated rabbitmq-env:

export ERL_EPMD_PORT=<your Erlang port>
export RABBITMQ_NODE_PORT=<your RabbitMQ port>
export ERL_INETRC=$HOME/.erl_inetrc

6.  $HOME/hosts, replacing dweb125 with your Webfaction hostname prefix:

127.0.0.1 developmenthost.developmentdomain developmenthost

::1 developmenthost6.developmentdomain6 developmenthost6

127.0.0.1 dweb125 dweb125.webfaction.com 

7. Create $HOME/.erl_inetrc:

{hosts_file, "/home/<username>/hosts"}.

{lookup, [file,native]}

Test RabbitMQ

Make sure you have Erlang running. Start RabbitMQ via ./rabbitmq_server-3.6.14/sbin/rabbitmq-server -detached, then check on its status via ./rabbitmq_server-3.6.14/sbin/rabbitmqctl status, and look for a line with {amqp,<your RabbitMQ port>,":

at this level I am always getting this error output when I run rabbitmq-server:

Failed to create dirty cpu scheduler thread 3

Crash dump is being written to: erl_crash.dump...done

[Luke Bakken]

Hello,

The "Failed to create dirty cpu scheduler thread" error is not easy to diagnose. It has never appeared on this mailing list, nor can I find any information about it online, other than the code that generates the error:

https://github.com/erlang/otp/blob/master/erts/emulator/beam/erl_process.c#L8470-L8477

At this point I suspect that the error is due to something specific about the Linux build environment on your webfaction server. I don't know if we can help any further. If you do resolve this issue, please let us know how since this is such an obscure error.

Good luck -

Luke

[Michael Klishin]

Note that the message says “thread 3”, which to me means that we are not dealing with dozens or 100s of cores/schedulers here, and therefore it’s unlikely to be due to a kernel limit on the max number of threads a process is allowed to create.

Just thinking out loud.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[TM Waseer]

Thanks Luke for putting in the effort, I appreciate it. I do have a notion that this is happening due to restriction on thread creation by kernal. As this is shared hosting and they put many limitations on resources, so I would agree a bit with @Michael here but I am not sure that this is the reason. I'll be upgrading my plan or move to some other cloud hosting provider like Linode or Digital Ocean. I hope, I could get it working on a virtual machine with root access :).

[Luke Bakken]

Hello,

Thanks for reporting back. For what it's worth I have had good experiences with virtual machines hosted by DigitalOcean.

Thanks for trying RabbitMQ out and continue to use this mailing list if you have issues in the future.

Luke

[Javier Vega Segura]

Hello, have you solved the issue about "Failed to create dirty cpu scheduler thread". 

I have same issue. Some clue?

Regards,

[Michael Klishin]

The runtime cannot create threads when the kernel prevents it from doing so due to explicit or implicit limits.
A RabbitMQ node will use close to 160 threads by default (128 of them for I/O, controlled via RABBITMQ_IO_THREAD_POOL_SIZE).

Many shared hosting offerings enforce limits much lower than that. Curiously several members of our team didn't have any issues with RabbitMQ

on Digital Ocean (I personally have been a customer of them for ~ 8 years). It may be a restriction present only in certain regions, older or newer versions

of droplets and so on.