Not able to execute plugin enable command RabbitMQ - rabbitmq

I installed Erlang and RabbitMQ on windows 7. RabbitMQ Service is running. But when I am trying to execute plugin enable command, I am getting below error
=SUPERVISOR REPORT==== 9-Jul-2018::14:14:46.134000 ===
supervisor: {local,'Elixir.Logger.Supervisor'}
errorContext: start_error
=INFO REPORT==== 9-Jul-2018::14:14:46.149000 ===
application: logger
exited: {{shutdown,
{failed_to_start_child,'Elixir.Logger.ErrorHandler',noproc}},
{'Elixir.Logger.App',start,[normal,[]]}}
type: temporary
Could not start application logger: Logger.App.start(:normal, []) returned an er
ror: shutdown: failed to start child: Logger.ErrorHandler
** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started

You are using a version of RabbitMQ prior to 3.7.7 with Erlang 21. This is not supported and is clearly documented here: https://www.rabbitmq.com/which-erlang.html
Solution: upgrade to RabbitMQ 3.7.7 or downgrade Erlang to version 20.3.
Also, you could have found the answer to this yourself by searching Google with the following text:
rabbitmq "Elixir.Logger.ErrorHandler"
NOTE: the RabbitMQ team monitors the rabbitmq-users mailing list and only sometimes answers questions on StackOverflow.

Related

Installation issue in ActiveMQ 5.8

I today tried to install Apache Active MQ 5.8 on Win XP. When I used the command activemq_install_dir\bin\activemq to start it, I got the following output:
H:\apache-activemq-5.8.0\bin>activemq
Java Runtime: Oracle Corporation 1.7.0_80 H:\Java\jdk1.7.0_80\jre
Heap sizes: current=1013632k free=991262k max=1013632k
JVM args: -Dcom.sun.management.jmxremote -Xms1G -Xmx1G -Djava.util.logging.c
onfig.file=logging.properties -Dactivemq.classpath=H:\apache-activemq-5.8.0\bin\
..\conf;H:\apache-activemq-5.8.0\bin\../conf;H:\apache-activemq-5.8.0\bin\../con
f; -Dactivemq.home=H:\apache-activemq-5.8.0\bin\.. -Dactivemq.base=H:\apache-act
ivemq-5.8.0\bin\.. -Dactivemq.conf=H:\apache-activemq-5.8.0\bin\..\conf -Dactive
mq.data=H:\apache-activemq-5.8.0\bin\..\data -Djava.io.tmpdir=H:\apache-activemq
-5.8.0\bin\..\data\tmp
Extensions classpath:
[H:\apache-activemq-5.8.0\bin\..\lib,H:\apache-activemq-5.8.0\bin\..\lib\camel
,H:\apache-activemq-5.8.0\bin\..\lib\optional,H:\apache-activemq-5.8.0\bin\..\li
b\web,H:\apache-activemq-5.8.0\bin\..\lib\extra]
ACTIVEMQ_HOME: H:\apache-activemq-5.8.0\bin\..
ACTIVEMQ_BASE: H:\apache-activemq-5.8.0\bin\..
ACTIVEMQ_CONF: H:\apache-activemq-5.8.0\bin\..\conf
ACTIVEMQ_DATA: H:\apache-activemq-5.8.0\bin\..\data
Loading message broker from: xbean:activemq.xml
The output doesn't proceed past "Loading message broker from: xbean:activemq.xml" .. what should I do? Why did it hang at Loading message broker from: xbean:activemq.xml ? Any solution for it?

Red5 Service Fails to Start on Win 10 - Incorrect Function

I installed Red5. Service installed ok, but when I manually try to start it, I get the following error in my Windows Event Log:
"The Red5 Media Server service terminated with the following service-specific error:
Incorrect function"
In the commons-daemon.log, I see the following:
[2017-05-17 20:36:54] [info] [11044] Starting service...
[2017-05-17 20:36:54] [error] [11044] Failed creating java
[2017-05-17 20:36:54] [error] [11044] ServiceStart returned 1
[2017-05-17 20:36:54] [info] [13816] Run service finished.
[2017-05-17 20:36:54] [info] [13816] Commons Daemon procrun finished
Event ID was 7024. Any help would be appreciated. Thanks!
Had the same issue on Windows Server 2012 R2. Solution was to install the latest release of the Java SE Development Kit. In my case I just installed Java SE DK 8U144: http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-windows-x64.exe
I resolved it by setting up the rtmp:// url correctly. I did not enter in a stream name, as I thought the name parameter above the rtmp text box would do it for me.
It works, but it seems that the chip in my Note 5 just doesn't have the cpu power to stream smoothly, although I will admit I have only spent about 20 minutes trying to tune settings for best performance on my Sprint cell service.
Thank you for your quick reply.

Live Migration Failure: unable to execute QEMU command 'migrate': Migration disabled: failed to allocate shared memory

I have a 2 node OpenStack Mitaka environment consisting of a controller/compute node and a compute node.
I've followed the setup guide to enable instance live migration using LVM block storage. I.e.: There's no shared storage backend, just local LVM block storage.
Using OpenStack Horizon to perform the live migration a success message is displayed, however, the migration is far from successful. This worked pretty much out-of-the-box with our Juno installation. I've exhausted Google and cannot find any other instances of people facing the same problem. I thought it might have been a time synchronisation problem so have set both nodes to UTC. Still the problems persists.
Source machine /var/log/nova/nova-compute.log
2016-08-12 15:56:42.120 2230 ERROR nova.virt.libvirt.driver [req-b71ea7b0-5fa8-4b57-92d2-4edec62135c2 b017d86d1143461a92a267d4b912c104 88c686f09e1b427fb750f5c00716f84e - - -] [instance: 5763b6b6-370c-448c-8e8f-8b71eafaa8f1] Migration operation has aborted
2016-08-12 15:56:42.470 2230 ERROR nova.virt.libvirt.driver [req-b71ea7b0-5fa8-4b57-92d2-4edec62135c2 b017d86d1143461a92a267d4b912c104 88c686f09e1b427fb750f5c00716f84e - - -] [instance: 5763b6b6-370c-448c-8e8f-8b71eafaa8f1] Live Migration failure: internal error: unable to execute QEMU command 'migrate': Migration disabled: failed to allocate shared memory
Target node /var/log/libvirt/libvirtd.log
2016-08-12 15:56:41.864+0000: 2170: error : qemuMonitorJSONGetMigrationStatsReply:2443 : internal error: info migration reply was missing return status
2016-08-12 15:56:41.864+0000: 2170: error : virNetClientProgramDispatchError:177 : Cannot open log file: '/var/log/libvirt/qemu/instance-0000006a.log': Device or resource busy
There are no other events captured in the source or target nova or libvirt logs.
I should also note that I am trying to use qemu+tcp (libvirt listening enabled, default tcp port, no auth) rather than qemu+ssh in order to keep things simple while testing. In fact, I intend to only use qemu+tcp anyway.
Which version of ubuntu did you deploy?
I had the same error with ubuntu 14.04 and mitaka version.
And I figured out that default kernel (3.13) makes this problem.
I upgraded the kernel from 3.13 to 4.40 and this problem is gone now.
I hope my experience help you solve this problem out.
Thanks

HttpHostConnectException let Apache Stanbol Integration Tests fail

I tried to install the Stanbol version from branch "release-0.12" from github.
On my system I have:
Apache Maven 3.0.5
Maven home: /usr/share/maven
Java version: 1.7.0_55, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-i386/jre
When I start the command:
mvn install
I get the following error for the Apache Stanbol Integration Tests => error-log
The first lines of the error are:
06.08.2014 15:47:02.025 *INFO * [main] Setting org.osgi.service.http.port=8765
06.08.2014 15:47:02.026 *INFO * [main] Starting launcher ...
06.08.2014 15:47:02.030 *INFO * [main] HTTP server port: 8765
15:47:03,614 INFO StanbolTestBase:163 - Got HttpHostConnectException at
http://localhost:8765/ - will retry
When I skiped the test I also got no response from the server...
I already tried it with java-version 1.6, but there I got the error:
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion failed
with message:
Java 7 or higher is required to compile this module
Has someone an idea what I made wrong (does it need some further software requirements)? Or how can I get the server running correctly?
The integration test starts a Stanbol Server (actually the full launcher) in its own JVM. The tests waits for up to 180 seconds for this server to start. During that time the test resends some test requests to check if the server is up and running.
Based on the provided log this period starts at about "15:47" so the test should wait until about "15:50" before it gives up.
Because of the line
^C15:48:42,236 INFO StanbolTestBase:146 - Got 404 at http://localhost:8765/entityhub - will retry
in the log my guess is that the build process was manually canceled with ^C before the server was fully started.
The server side logs of the test run are available at target/launchdir/stanbol/logs/error.log. If the integration tests do fail one will usually find the reason in this log file.

Erlang crashes (must be ejabberd): Why and how to debug the logfile?

Everyday I have a new Erlang crash report on my server. As ejabberd is the only Erlang-thing I use, this must be the cause of the crash.
The logfile (erl_crash.dump) has almost 9,000 lines so I have no idea how to debug that. But when I searched for "ejabberd" in that logfile, there were 5 occurrences - and every single occurrence was something related to "ejabberdctl".
I'm addressing ejabberdctl via PHP script (exec()) to programatially create users. Could that be the cause for the crash (somehow)?
In /var/log/ejabberd directory, I've found some errors in erlang.log and ejabberd.log. But I don't really know how to resolve them:
=ERROR REPORT====
Mnesia('ejabberd#MYHOST'): ** ERROR ** (core dumped to file: "/var/lib/ejabberd/MnesiaCore.ejabberd#MYHOST_...")
** FATAL ** mnesia_monitor crashed: {badarg,
[{ets,lookup,
[mnesia_decision,
'ejabberdctl#MYHOST']},
{mnesia_recover,has_mnesia_down,1},
{mnesia_monitor,handle_info,2},
{gen_server,handle_msg,5},
{proc_lib,init_p_do_apply,3}]} state: {state,
<0.65.0>,
[],
[],
true,
[],
undefined,
[]}
=ERROR REPORT====
Mnesia('ejabberd#MYHOST'): ** WARNING ** Mnesia is overloaded: {dump_log,
time_threshold}
=CRASH REPORT====
crasher:
initial call: ejabberd_listener:init/3
pid: <0.366.0>
registered_name: []
exception exit: {timeout,
{gen_server,call,
[<0.682.0>,{become_controller,<0.685.0>}]}}
in function gen_server:call/2
in call from ejabberd_listener:accept/3
ancestors: [ejabberd_listeners,ejabberd_sup,<0.39.0>]
messages: [{#Ref<0.0.0.11304>,ok}]
links: [#Port<0.2761>,<0.274.0>]
dictionary: []
trap_exit: false
status: running
heap_size: 2584
stack_size: 24
reductions: 20938
neighbours:
The erl_crash.dump file contains the states of almost everything in the moment when the Erlang VM crashed. There's a tool for analyzing it, just:
Start an Erlang shell and start the webtool:
somebody#somehost> erl
Erlang R15B02 (erts-5.9.2) [source] [smp:2:2] [async-threads:0] [kernel-poll:false]
Eshell V5.9.2 (abort with ^G)
1> webtool:start().
WebTool is available at http://localhost:8888/
Or http://127.0.0.1:8888/
{ok,<0.35.0>}
2>
Navigate to the address given above with your browser, and click WebTool -> Start Tools -> CrashDumpViewer -> Start, then CrashDumpViewer -> Load Crashdump.
Look for the Slogan in General Information. It's the summarized reason of crashing.
Look for processes with a state other than Waiting. Those processes are doing something while the Erlang VM crashed, they are probably the sources.
You can only execute ejabberdctl once. Executing it twice from your PHP will generate conflict in node naming and the crash you see.
Do not use ejabberdctl from code, but rely on API.
Are they any chances that you are string ejabberd twice?
Do you have an erlang.log log file? If so, you should find good info in there about a crash.
You could use ssh port forwarding to export webtool to your local machine, where you can point a browser at it. Exposing it to the whole internet would probably be a bad security error.