[Bug 1231430] New: Missing jinterface maven metadata
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1231430
Bug ID: 1231430
Summary: Missing jinterface maven metadata
Product: Fedora
Version: rawhide
Component: erlang
Assignee: lemenkov(a)gmail.com
Reporter: puntogil(a)libero.it
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, lemenkov(a)gmail.com,
rhbugs(a)n-dimensional.de, s(a)shk.io
Description of problem:
erlang-jinterface do not provides maven metadata, which used by some projects
e.g. https://github.com/spring-projects/spring-amqp/ (spring-erlang sub module)
The pom file is available but is not installed
https://github.com/erlang/otp/blob/maint/lib/jinterface/java_src/pom.xml.src
https://fedoraproject.org/wiki/Packaging:Java#Maven_pom.xml_files
and the JAR file should be placed in %_javadir
https://fedoraproject.org/wiki/Packaging:Java#JAR_file_installation
The spec file "should be" modified in this way:
%if %{?fedora} >= 21
BuildRequires: javapackages-local
%else
BuildRequires: maven-local
%endif
jinterface_lib_dir="$(ls -d1 $RPM_BUILD_ROOT%{_libdir}/erlang/lib/jinterface-*/
| sed "s,^$RPM_BUILD_ROOT,,")" test -d "$RPM_BUILD_ROOT$jinterface_lib_dir"
rm -rf "${jinterface_lib_dir}priv/OtpErlang.jar"
if the pom file is not processed
sed 's/%VSN%/%{version}/' <otp/lib/jinterface/java_src/pom.xml.src >pom.xml
generates maven metadata
%mvn_artifact [path of the processed pom file]/pom.xml [path of the built java
library]/[name of the java library].jar
install JAR file in %_javadir and generate a its symlink
%mvn_file org.erlang.otp:jinterface erlang/OtpErlang
${jinterface_lib_dir}priv/OtpErlang
%mvn_install
Version-Release number of selected component (if applicable):
All
How reproducible:
Always
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 5 months
[Bug 1295663] New: dialyzer --build_plt crashes
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1295663
Bug ID: 1295663
Summary: dialyzer --build_plt crashes
Product: Fedora
Version: rawhide
Component: erlang
Severity: high
Assignee: lemenkov(a)gmail.com
Reporter: rbarlow(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jeckersb(a)redhat.com,
lemenkov(a)gmail.com, rhbugs(a)n-dimensional.de, s(a)shk.io
Created attachment 1111752
--> https://bugzilla.redhat.com/attachment.cgi?id=1111752&action=edit
erl_crash.dump
Description of problem:
When I try to build a PLT, dialyzer crashes.
Version-Release number of selected component (if applicable):
$ rpm -q erlang-dialyzer
erlang-dialyzer-17.4-5.fc24.x86_64
How reproducible:
Every time
Steps to Reproduce:
1. $ dialyzer --build_plt --apps erts kernel stdlib
Actual results:
$ dialyzer --build_plt --apps erts kernel stdlib
Compiling some key modules to native code...{"init terminating in
do_boot",{{badmatch,{error,{'EXIT',{badarg,[{hipe_bifs,patch_call,[1095479243,94032498909904,[]],[]},{hipe_unified_loader,patch_call_insn,3,[{file,"hipe_unified_loader.erl"},{line,507}]},{hipe_unified_loader,patch_bif_call_list,4,[{file,"hipe_unified_loader.erl"},{line,492}]},{hipe_unified_loader,patch_call,5,[{file,"hipe_unified_loader.erl"},{line,483}]},{hipe_unified_loader,patch,5,[{file,"hipe_unified_loader.erl"},{line,458}]},{hipe_unified_loader,load_common,4,[{file,"hipe_unified_loader.erl"},{line,235}]},{hipe_unified_loader,load_module,3,[{file,"hipe_unified_loader.erl"},{line,156}]},{code_server,handle_call,3,[{file,"code_server.erl"},{line,332}]}]}}}},[{hipe,finalize,5,[{file,"hipe.erl"},{line,751}]},{hipe,compile_finish,3,[{file,"hipe.erl"},{line,708}]},{hipe,'-run_compiler_1/3-fun-0-',4,[{file,"hipe.erl"},{line,669}]}]}}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
Expected results:
Successful build.
Additional info:
I've attached the erl_crash.dump file.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 7 months
[Bug 1324922] New: Log handler repeatedly crashes
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1324922
Bug ID: 1324922
Summary: Log handler repeatedly crashes
Product: Fedora EPEL
Version: epel7
Component: erlang
Keywords: Regression, ZStream
Severity: urgent
Priority: urgent
Assignee: jeckersb(a)redhat.com
Reporter: jeckersb(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: apevec(a)redhat.com, binarin(a)binarin.ru,
erlang(a)lists.fedoraproject.org, fdinitto(a)redhat.com,
jeckersb(a)redhat.com, jschluet(a)redhat.com,
lhh(a)redhat.com, oblaut(a)redhat.com, rjones(a)redhat.com,
s(a)shk.io, ushkalim(a)redhat.com
Depends On: 1322609
Blocks: 1324185
+++ This bug was initially created as a clone of Bug #1322609 +++
Starting with erlang-erts-R16B-03.10min.6.el7ost.x86_64, the log handler
repeatedly crashes and fills up the rabbitmq startup_log with entries like:
Event crashed log handler:
{info_msg,<0.1719.0>,
{<0.1832.0>,"Mirrored ~s: Adding mirror on node ~p: ~p~n",
["queue 'l3_agent_fanout_0f6bc20f4c54484f9de482cd6d83a15a' in vhost
'/'",
'rabbit@overcloud-controller-1',<6192.10668.1>]}}
function_clause
Meanwhile the rabbitmq log is empty.
Looks like a regression introduced in the "Enable error_logger depth fine
tuning" patch.
--- Additional comment from Alexey Lebedeff on 2016-04-07 09:17:10 EDT ---
R16B-03.16.el7 is also affected.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1322609
[Bug 1322609] Log handler repeatedly crashes
https://bugzilla.redhat.com/show_bug.cgi?id=1324185
[Bug 1324185] Log handler repeatedly crashes
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 7 months
[Bug 1163812] New: Cannot control ejabberd with ejabberdctl
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1163812
Bug ID: 1163812
Summary: Cannot control ejabberd with ejabberdctl
Product: Fedora
Version: 21
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: juan.orti(a)miceliux.com
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jkaluza(a)redhat.com,
lemenkov(a)gmail.com, martin(a)laptop.org
Description of problem:
After a clean install of ejabberd in Fedora 21, I cannot use the ejabberdctl
utility to register users, etc.
I run:
# ejabberdctl register admin localhost password
Failed RPC connection to the node ejabberd@localhost: nodedown
Commands to start an ejabberd node:
start Start an ejabberd node in server mode
debug Attach an interactive Erlang shell to a running ejabberd node
live Start an ejabberd node in live (interactive) mode
Optional parameters when starting an ejabberd node:
--config-dir dir Config ejabberd: /etc/ejabberd
--config file Config ejabberd: /etc/ejabberd/ejabberd.yml
--ctl-config file Config ejabberdctl: /etc/ejabberd/ejabberdctl.cfg
--logs dir Directory for logs: /var/log/ejabberd
--spool dir Database spool dir: /var/lib/ejabberd
--node nodename ejabberd node name: ejabberd@localhost
And I see this in the log /var/log/ejabberd/ejabberd.log:
2014-11-13 14:57:30.188 [info] <0.7.0> Application lager started on node
ejabberd@localhost
2014-11-13 14:57:30.257 [info] <0.7.0> Application sasl started on node
ejabberd@localhost
2014-11-13 14:57:30.286 [info] <0.7.0> Application crypto started on node
ejabberd@localhost
2014-11-13 14:57:30.354 [info] <0.7.0> Application asn1 started on node
ejabberd@localhost
2014-11-13 14:57:30.354 [info] <0.7.0> Application public_key started on node
ejabberd@localhost
2014-11-13 14:57:30.421 [info] <0.7.0> Application ssl started on node
ejabberd@localhost
2014-11-13 14:57:30.450 [info] <0.7.0> Application p1_yaml started on node
ejabberd@localhost
2014-11-13 14:57:30.482 [info] <0.7.0> Application p1_tls started on node
ejabberd@localhost
2014-11-13 14:57:30.492 [info] <0.7.0> Application p1_xml started on node
ejabberd@localhost
2014-11-13 14:57:30.498 [info] <0.7.0> Application p1_stringprep started on
node ejabberd@localhost
2014-11-13 14:57:30.508 [info] <0.7.0> Application p1_zlib started on node
ejabberd@localhost
2014-11-13 14:57:30.515 [info] <0.7.0> Application p1_cache_tab started on node
ejabberd@localhost
2014-11-13 14:57:31.015 [info] <0.7.0> Application mnesia started on node
ejabberd@localhost
2014-11-13 14:57:33.259 [info] <0.37.0>@cyrsasl_digest:start:57 FQDN used to
check DIGEST-MD5 SASL authentication: charm.miceliux.com
2014-11-13 14:57:33.423 [info] <0.7.0> Application p1_iconv started on node
ejabberd@localhost
2014-11-13 14:57:42.556 [info] <0.564.0>@ejabberd_listener:listen_tcp:194
Reusing listening port for 5222
2014-11-13 14:57:42.556 [info] <0.565.0>@ejabberd_listener:listen_tcp:194
Reusing listening port for 5269
2014-11-13 14:57:42.557 [info] <0.566.0>@ejabberd_listener:listen_tcp:194
Reusing listening port for 5280
2014-11-13 14:57:42.557 [info] <0.37.0>@ejabberd_app:start:69 ejabberd
community is started in the node ejabberd@localhost
2014-11-13 14:57:42.557 [info] <0.7.0> Application ejabberd started on node
ejabberd@localhost
2014-11-13 14:59:18.926 [error] <0.567.0> ** Connection attempt from disallowed
node 'ejabberdctl-1@charm' **
Version-Release number of selected component (if applicable):
ejabberd-14.07-3.fc21.x86_64
How reproducible:
Always
Steps to Reproduce:
1. yum install ejabberd
2. systemctl start ejabberd
3. ejabberdctl register admin localhost password
Actual results:
Cannot register a user.
Expected results:
Register a user.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 9 months
[Bug 1341252] New: ejabberd does not log to journald
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1341252
Bug ID: 1341252
Summary: ejabberd does not log to journald
Product: Fedora
Version: rawhide
Component: ejabberd
Assignee: lemenkov(a)gmail.com
Reporter: jeremy(a)jcline.org
QA Contact: extras-qa(a)fedoraproject.org
CC: erlang(a)lists.fedoraproject.org, jeremy(a)jcline.org,
lemenkov(a)gmail.com, martin(a)laptop.org,
rbarlow(a)redhat.com
Created attachment 1163265
--> https://bugzilla.redhat.com/attachment.cgi?id=1163265&action=edit
Patch to ejabberd.service
Description of problem:
It'd be great if ejabberd logged to journald rather than /var/log/ejabberd/.
This can be achieved with a few small changes to the systemd unit file. I've
attached my proposed systemd unit file.
Version-Release number of selected component (if applicable):
All currently released versions.
Steps to Reproduce:
1. systemctl start ejabberd.service
2. journalctl -u ejabberd
3. :(
Actual results:
Logs are placed in /var/log/ejabberd
Expected results:
Logging is handled by journald
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 4 months