Home » Forums » ejabberd & XMPP » ejabberd Development

[error] <0.37.0> CRASH REPORT Process <0.37.0> with 0 neighbours exited with reason: {undefined_macro,''} in application_master:

Submitted by John Carpin on Wed, 2017-05-03 15:39

Hello,

I am trying to start ejabberd on my linux Debian but it's crashing all the time with the same error.

I'm using the ejabberd wheezy backport 14.07-4+deb8u3~bpo7+1 version and erlang:

# erl
Erlang/OTP 17 [erts-6.2] [source] [64-bit] [async-threads:10] [kernel-poll:false]

and the error is:

2017-05-03 16:18:27.596 [info] <0.7.0> Application lager started on node e jabberd@voip80
2017-05-03 16:18:27.607 [info] <0.7.0> Application sasl started on node ejabberd@voip80
2017-05-03 16:18:27.612 [info] <0.7.0> Application crypto started on node ejabberd@voip80
2017-05-03 16:18:27.619 [info] <0.7.0> Application asn1 started on node ejabberd@voip80
2017-05-03 16:18:27.619 [info] <0.7.0> Application public_key started on node ejabberd@voip80
2017-05-03 16:18:27.629 [info] <0.7.0> Application ssl started on node ejabberd@voip80
2017-05-03 16:18:27.637 [info] <0.7.0> Application p1_yaml started on node ejabberd@voip80
2017-05-03 16:18:27.655 [info] <0.7.0> Application p1_tls started on node ejabberd@voip80
2017-05-03 16:18:27.671 [info] <0.7.0> Application p1_xml started on node ejabberd@voip80
2017-05-03 16:18:27.679 [info] <0.7.0> Application p1_stringprep started on node ejabberd@voip80
2017-05-03 16:18:27.687 [info] <0.7.0> Application p1_zlib started on node ejabberd@voip80
2017-05-03 16:18:27.695 [info] <0.7.0> Application p1_cache_tab started on node ejabberd@voip80
2017-05-03 16:18:27.896 [info] <0.7.0> Application mnesia started on node ejabberd@voip80
2017-05-03 16:18:28.605 [error] <0.37.0> CRASH REPORT Process <0.37.0> with 0 neighbours exited with reason: {undefined_macro,''} in application_master:init/4 line 133
2017-05-03 16:18:28.606 [info] <0.7.0> Application ejabberd exited with reason: {undefined_macro,''}

I think it might get something to do with erlang version but I really don't know.

Thanks in advance :!

‹ If the stanza-id can be used as message time? Message-level read receipts on user action ›

I can reproduce that error

Submitted by badlop on Wed, 2017-05-03 19:04.

I can reproduce that error message by setting this in the ejabberd configuration file:

loglevel: ''

Notice the value is two commands: ' and ', which in the configuration file are used to call a macro, for example:

define_macro:
  'LOG_LEVEL_NUMBER': 5
loglevel: 'LOG_LEVEL_NUMBER'

See https://docs.ejabberd.im/admin/configuration/#option-macros-in-configura...

»

But if in the code of my

Submitted by John Carpin on Thu, 2017-05-04 10:17.

But if in the code of my configuration file I am not using any macro ( eg. ' and ' ), it is not supposed to show this type of error right?

»

You can investigate the

Submitted by badlop on Fri, 2017-05-05 10:42.

You can investigate the problem yourself: remove some lines of the config file, try to start again, and repeat until you find which lines produce the problem.

Or show here your configuration file, so I can try that myself.

»
Syndicate content

User login