Cannot start ejabberd server 14.05 - erlang

i have installed ejabberd 14.05 and while installing i had no issues but while starting the server i got the following message:
2016-05-24 15:50:37.636 [critical] <0.37.0>#gen_mod:start_module:77 Problem starting the module mod_client_state for host <<"localhost">>
options: []
error: undef
[{mod_client_state,start,[<<"localhost">>,[]],[]},
{gen_mod,start_module,3,[{file,"src/gen_mod.erl"},{line,69}]},
{lists,foreach,2,[{file,"lists.erl"},{line,1336}]},
{ejabberd_app,start,2,[{file,"src/ejabberd_app.erl"},{line,66}]},
{application_master,start_it_old,4,
[{file,"application_master.erl"},{line,272}]}]
2016-05-24 15:50:37.636 [critical] <0.37.0>#gen_mod:start_module:82 ejabberd initialization was aborted because a module start failed.
I cannot find mod_client_state.erl in src folder.
Sorry I am new to ejabberd and erlang

You are likely a version of ejabberd that does not have mod_client_state. mod_client_state feature was added in newer version.
Please upgrade to newer version if you want to use mod_client_state.
You need at least version 14.12: https://www.ejabberd.im/ejabberd-14.12

Related

Elixir error with genserver.call timeout db connection

after i installed wxWidgets libs and reinstall my version of erlang otp to can i run ":observer.start", my application come fails with this error:
i'm use evm to manage my erlang otp versions.
[info] GET /dashboard/admin
[error] #PID<0.1290.0> running DashboardWeb.Endpoint (cowboy_protocol) terminated
Server: test.lvh.me:5000 (http)
Request: GET /dashboard/admin
** (exit) exited in: :gen_server.call(#PID<0.797.0>, {:checkout, #Reference<0.3971714438.3053715457.259419>, true, 15000}, 5000)
** (EXIT) time out
i researched to try solve error and i finded this link "https://github.com/elixir-ecto/db_connection/issues/127", but i can't solve error, i use elixir 1.6.6 and erlang otp 20.3, i install erlang otp 21.0 like link mention but not work, anyone solved this issue?

OpsCenter 6.1.2 keeps crashing after update from 6.0.X "No agents available to query for getDsePerformanceStatusFromOneAgent"

After updating OpsCenter 6.0.X to 6.1.2 using yum, OpsCenter frequently crashes with the following error in opsenterd.log:
2017-08-25 10:03:34,066 [opscenterd] ERROR: Unhandled error in Deferred: No agents available to query for getDsePerformanceStatusFromOneAgent.
File "/usr/share/opscenter/lib/py/twisted/internet/defer.py", line 1124, in _inlineCallbacks
result = g.send(result)
File "/usr/share/opscenter/jython/Lib/site-packages/opscenterd/Cluster.py", line 1301, in callOnAgent
(MainThread)
Any idea how to fix this?
I was able to resolve this by updating the run directory file /etc/opscenter/clusters/< clustername >.conf
with
[agent_config]
tmp_dir = /path/to/agent/tmp
But this is a temporary solution.

grails -version FATAL ERROR in native method

I'm trying to get grails version, but getting error all the time. OS: windows server 2012 and windows 8. I suspect that the port is busy, and I can't release it - need another exit from situation
So, I'm doing something like this in command line:
{PATH_TO_/bin/grails.bat} -version
The result is:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
So.. what can I do with it?
Thanks.
To resolve problem I've just set JAVA_OPTS
with
-Xrunjdwp:transport=dt_shmem,server=y,suspend=n
Documentation link

How to make mod_archive_odbc works on ejabberd 2.1.13?

I'm install ejabberd 2.1.13 from binary installer.
After module compilation and copying *.beam files to /opt/ejabberd_2.1.13/lib/ejabberd_2.1.13/ebin directory ejabberd crushes with this error (also with undef error):
=ERROR REPORT==== 2014-08-25 16:45:07 ===
beam/beam_load.c(1365): Error loading module mod_archive_odbc:
use of opcode 153; this emulator supports only up to 152
Erlang OTP version is R17.
I've also tried to install R15B1 on VM and compile module on it. After copying beam files i still see the same error.
What should i do to make it work?
UPD: I've tried to build mod on R14B04 and get this error from compiler:
=ERROR REPORT==== 26-Aug-2014::15:30:32 ===
beam/beam_load.c(1365): Error loading module gen_mod:
use of opcode 153; this emulator supports only up to 152
I decided to checkout the repository from SVN (instead of GIT). Module compiles without errors (on R14B04). Server starts without error logs and warnings. Yep, it Works!

RabbitMQ will not start after upgrade 3.3.3-1

After updating RabbitMQ to version 3.3.3-1 using their APT repository, it will no longer start:
Setting up rabbitmq-server (3.3.3-1) ...
* Starting message broker rabbitmq-server * FAILED - check /var/log/rabbitmq/startup_{log, _err}
[fail]
invoke-rc.d: initscript rabbitmq-server, action "start" failed.
dpkg: error processing package rabbitmq-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
rabbitmq-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
startup_log:
{"init terminating in do_boot",{{case_clause,{ok,[]}},[{rabbit_prelaunch,dist_port_set_check,0,[]},{rabbit_prelaunch,start,0,[]},{init,start_it,1,[]},{init,start_em,1,[]}]}}
startup_err:
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
erl_crash.dump
I'm running Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64)
Erlang version: 1:17.0
I can't seem to find any information on why it is failing to start. Any help would be much appreciated.
Looking at rabbit_prelaunch I think this could happen if you have a config file but it is completely empty. That's not allowed (not a legal Erlang term), but this exception certainly sucks. I'll file a bug to fix that.
EDIT: fixed in 3.3.4.

Resources