Call to i:im() in application debugger failed in ejabberd - erlang

I'm trying to debug ejabberd. I have compiled the files with debug_info. I start ejabberd, then use ejabberd debug to get into the shell. Once in there, running im() produces "Call to i:im() in application debugger failed". I can't figure out what's causing this. Any ideas on how to debug?
Edit
I've tried running this in just the erl shell independent of ejabberd and it still fails. So it looks like it's related to my erlang setup as opposed to a problem with my ejabberd setup.

Foolish me: apt-get install erlang-debugger solved the problem.

Related

How to configure Intellij for the erlang build tool rebar3?

I have started developing for Erlang using Rebar3 in the IntelliJ IDE and have run into the following problem - when trying to use the ide to clean or run i get the following error:
Testing started at 8:33 AM ...
D:\DevelopmentTools\erl10.0.1\bin\escript.exe D:\DevelopmentTools\erl10.0.1\rebar\rebar3.cmd skip_deps=true clean -C C:\Users\coreRNM\AppData\Local\Temp\eunit_teamcity1\rebar.config
D:\DevelopmentTools\erl10.0.1\rebar\rebar3.cmd:2: syntax error before: set
escript: There were compilation errors.
It should be a fairly easy configuration but the code breaks in the following location.
#echo off
setlocal
set rebarscript=%~f0
escript.exe "%rebarscript:.cmd=%" %*
My question is: has anyone experienced this before or am I missing something?
Honestly, I have no idea what's happened here and it doesn't look like an integration issue. Better ask guys about running rebar3 on Windows.

iisnode 7.x (64x) full Setup install fails with a message saying a script could not be run

As a result of a question I wrote a little earlier I person was kind enough to write an answer. He suggested installing iisnode to fix a problem where node.js was in the path but docker couldnt find it.. However, on his suggestion I downloaded iisnode for iis 7.x(x64) and proceeded to run it... and with the luck I am having I got the following error..
There was a problem with this Windows Install package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.
I have no idea how to solve this.. any ideas.. I have entered docker for this as I suspect this problem has occured for others when they tried to run a dotnet core SPA project...
Sorry my bad English!
I had this issue while i was working with "Plesk" but maybe my solution works for you or others.
First you should go to "C:\Windows\System32\inetsrv\config".
Make a backup of "applicationHost.config" somewhere.
Then remove every line that contains "iisnode" in that file.
Then try to install "iisnode" again. if it does not work, restart your OS and try again.
If it does not work again, restore your backup and restart your OS and i don't know how you can fix it, Sorry :((

ejabberd and Erlang installation with lager_transform undefined

I am new to Erlang, I have been trying to install Erlang and ejabberd on EC2 ubuntu machine, everything went well till I started compiling some external modules in ejabberd. It started throwing error undefined parse transform 'lager_transform'.
I tried everything which is as below:
Did rebar get-deps, make clean, make deps, make install. After this I am able to see that lager_transform.beam is made and present in /lib/ folder.
Checked rebar.config file, it had lager deps on top, which is widely suggested, no help even after that.
Added -compile[{parse_tranform},{lager_transform}] on top of module, even then their is no luck.
I am really blocked on this, and not able to complete the installation. I have done this before on fedora with ejabberd 15.11 and otp 18.2, at that time it was using p1_logger instead of lager. But now when I am installing fresh with otp 18.2 and ejabberd 16.0 or 15.11, I am getting lager_transform undefined error.
Please make sure you compile ejabberd as described in documentation: http://docs.ejabberd.im/admin/guide/installation/#installing-ejabberd-from-source-code
For example, you can compile it with:
./configure --enable-lager --enable-mysql
make
You need to run configure and make to set properly the build chain.

Regarding Neoload 5.0.2

I'm getting an error msg "Load Generator Unavailable" pop up evry 2 iterations when I run the script via check virtual user.Closing and reopeing Neoload solves the issue.Could any of you please help me in resolving this issue?
This looks like it is a common issue with Neoload across versions, we have seen this across all of our windows installations where we run with localhost as a load generator or when we run with stand-alone generators. Most of the time a stop and restart of the load generators and load controllers will solve this issue. On more rare occasions a complete restart of the controller server needs to happen. This is issue is appearing in the latest version as of the date of my response.
I use to have this problem. I just needed to restart my load generator. All I did was ssh into my load generator that was acting up. Then ran sudo –u neoload /opt/neoload/bin/LoadGeneratorAgent stop then after that I would run sudo –u neoload /opt/neoload/bin/LoadGeneratorAgent start & Exit and restart neoload and I stopped having the problem. You will just replace the path with your own. This is for external load generators not local host generators.

Eclipse freezes when erlide tries to run

I'm just getting started with erlide, using a fresh install of Eclipse Juno and erlide. I've used erlang on my system (64-bit Fedora) from the command-line, so I'm just trying to make the switch. I started with R15B, and have upgraded to R15B02 (built from source) as suggested by another SO post. If I right-click on a .erl file and pick Run As..Erlang Application, the IDE freezes and I have to kill it. If I try to run from Run Configurations and specify the module and function, it will start to execute, but never progresses beyond 27%. This is on a simple function that runs instantaneously on the command line.
Please try with the latest nightly from http://erlide.org/update_nightly, we did some work about similar issues, I hope they will solve yours too.
It would help to see the log from /erlide.log.
You can also open the launch configuration from run->configurations and see if there is some weird value in any of the fields in the "runtime" tab, most probably the node host name.
[I will be away for a week or so, so I can't answer very soon. Sorry about that.]
/Vlad

Resources