Erlang Rabbitmq未在solaris 10上退出启动_Erlang_Rabbitmq

Erlang Rabbitmq未在solaris 10上退出启动

erlang rabbitmq

Erlang Rabbitmq未在solaris 10上退出启动,erlang,rabbitmq,Erlang,Rabbitmq,我正在尝试让Rabbitmq在solaris 10（sparc）上工作。当我运行Rabbitmq时，我会进入启动屏幕 RabbitMQ 3.6.1. Copyright (C) 2007-2016 Pivotal Software, Inc. ## ## Licensed under the MPL. See http://www.rabbitmq.com/ ## ## ########## Logs: /opt/rabbitmq/log/rabbit@19

我正在尝试让Rabbitmq在solaris 10（sparc）上工作。当我运行Rabbitmq时，我会进入启动屏幕

          RabbitMQ 3.6.1. Copyright (C) 2007-2016 Pivotal Software, Inc.
##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
##  ##
##########  Logs: /opt/rabbitmq/log/rabbit@192.168.0.1.log
######  ##        /opt/rabbitmq/log/rabbit@192.168.0.1-sasl.log
##########
          Starting broker... completed with 8 plugins.

然后，如果我执行rabbitmqctl status，它就会挂起

Status of node 'rabbit@192.168.0.1' ...
Error: unable to connect to node 'rabbit@192.168.0.1': nodedown

DIAGNOSTICS
===========

attempted to contact: ['rabbit@192.168.0.1']

rabbit@192.168.0.1:
   * connected to epmd (port 4369) on 192.168.0.1
   * epmd reports node 'rabbit' running on port 25672
   * TCP connection succeeded but Erlang distribution failed
   * suggestion: hostname mismatch?
   * suggestion: is the cookie set correctly?
   * suggestion: is the Erlang distribution using TLS?

我检查了所有的东西，没有发现任何建议有任何错误

这是我的配置文件

[
    {rabbit, [
                {tcp_listeners, [4003]},
                {loopback_users, []},
                {cluster_nodes, {['rabbit@192.168.0.1'], disc}}
    ]},
    {rabbitmq_management, [{listener, [{port, 15672}]}]}
].

我尝试过在有ssl配置和没有ssl配置的情况下执行此操作，但都遇到了相同的问题。我的Erlang版本是18.3，rabbitmq是3.6.1 我在这里遗漏了什么导致它在显示完成后挂断

编辑这里是我的ps aux输出和rabbitmq日志

    =INFO REPORT==== 4-May-2016::10:15:49 ===
Starting RabbitMQ 3.6.1 on Erlang 18.3
Copyright (C) 2007-2016 Pivotal Software, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

=INFO REPORT==== 4-May-2016::10:15:50 ===
node           : rabbit@192.168.0.1
home dir       : /export/home/jckunz
config file(s) : /opt/rabbitmq/config/rabbitmq.config
cookie hash    : eF4lT09DIn3wKUXARVnbrw==
log            : /opt/rabbitmq/log/rabbit@192.168.0.1.log
sasl log       : /opt/rabbitmq/log/rabbit@192.168.0.1-sasl.log
database dir   : /opt/rabbitmq/db/rabbit@192.168.0.1

=WARNING REPORT==== 4-May-2016::10:16:04 ===
You are using a 32-bit version of Erlang: you may run into memory address
space exhaustion or statistic counters overflow.

=WARNING REPORT==== 4-May-2016::10:16:04 ===
Only 2048MB of 32640MB memory usable due to limited address space.
Crashes due to memory exhaustion are possible - see
http://www.rabbitmq.com/memory.html#address-space

=INFO REPORT==== 4-May-2016::10:16:04 ===
Memory limit set to 819MB of 32640MB total.

=INFO REPORT==== 4-May-2016::10:16:04 ===
Disk free limit set to 50MB

=INFO REPORT==== 4-May-2016::10:16:04 ===
Limiting to approx 156 file handles (138 sockets)

=INFO REPORT==== 4-May-2016::10:16:04 ===
FHC read buffering:  OFF
FHC write buffering: ON

=INFO REPORT==== 4-May-2016::10:16:04 ===
Database directory at /opt/rabbitmq/db/rabbit@192.168.0.1 is empty. Initialising from scratch...

=WARNING REPORT==== 4-May-2016::10:16:04 ===
Could not find any node for auto-clustering from: ['rabbit@192.168.0.1']
Starting blank node...

=INFO REPORT==== 4-May-2016::10:16:05 ===
Priority queues enabled, real BQ is rabbit_variable_queue

=INFO REPORT==== 4-May-2016::10:16:05 ===
Management plugin: using rates mode 'basic'

=INFO REPORT==== 4-May-2016::10:16:05 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 4-May-2016::10:16:05 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide index

=WARNING REPORT==== 4-May-2016::10:16:05 ===
msg_store_persistent: rebuilding indices from scratch

=INFO REPORT==== 4-May-2016::10:16:05 ===
Adding vhost '/'

=INFO REPORT==== 4-May-2016::10:16:05 ===
Creating user 'guest'

=INFO REPORT==== 4-May-2016::10:16:05 ===
Setting user tags for user 'guest' to [administrator]

=INFO REPORT==== 4-May-2016::10:16:05 ===
Setting permissions for 'guest' in '/' to '.*', '.*', '.*'

=INFO REPORT==== 4-May-2016::10:16:05 ===
started TCP Listener on [::]:4003

=INFO REPORT==== 4-May-2016::10:16:05 ===
started TCP Listener on 0.0.0.0:4003

=INFO REPORT==== 4-May-2016::10:16:05 ===
Management plugin started. Port: 15672

=INFO REPORT==== 4-May-2016::10:16:05 ===
Statistics database started.

=INFO REPORT==== 4-May-2016::10:16:05 ===
Server startup complete; 8 plugins started.
 * rabbitmq_federation_management
 * rabbitmq_management
 * rabbitmq_management_agent
 * rabbitmq_federation
 * amqp_client
 * rabbitmq_web_dispatch
 * webmachine
 * mochiweb


USER       PID %CPU %MEM   SZ  RSS TT       S    START  TIME COMMAND
jckunz  19849  1.1  0.4327960118576 pts/1    S 10:15:44 10:32 /opt/rabbitmq/solaris/erlang/erts-7.3/bin/beam.smp -W w -A 64 -P 1048576 
-B i -- -root /opt/rabbitmq/solaris/erlang -progname erl -- -home /export/home/jckunz -epmd_port 4369 -- -pa /opt/rabbitmq/solaris/rabbitmq/ebin 
-noshell -noinput -s rabbit boot -name rabbit@192.168.0.1 -boot start_sasl -config /opt/rabbitmq/config/rabbitmq 
-kernel inet_default_connect_options [{nodelay,true}] -sasl errlog_type error -sasl sasl_error_logger false 
-rabbit error_logger {file,"/opt/rabbitmq/log/rabbit@192.168.0.1.log"} -rabbit sasl_error_logger {file,"/opt/rabbitmq/log/rabbit@192.168.0.1-sasl.log"} 
-rabbit enabled_plugins_file "/opt/rabbitmq/config/enabled_plugins" -rabbit plugins_dir "/opt/rabbitmq/solaris/rabbitmq/plugins" 
-rabbit plugins_expand_dir "/opt/rabbitmq/db/rabbit@192.168.0.1-plugins-expand" -os_mon start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup false 
-mnesia dir "/opt/rabbitmq/db/rabbit@192.168.0.1" -setcookie jckunz -kernel inet_dist_listen_min 25672 
-kernel inet_dist_listen_max 25672 inet_dist_listen_max 25672

jckunz  19711  0.1  0.329051277936 pts/1    S 10:15:42  0:50 /opt/rabbitmq/solaris/erlang/erts-7.3/bin/beam.smp -- -root /opt/rabbitmq/solaris/erlang 
-progname erl -- -home /export/home/jckunz -epmd_port 4369 -- -pa /opt/rabbitmq/solaris/rabbitmq/ebin -noshell -noinput -hidden -setcookie jckunz 
-boot start_clean -sasl errlog_type error -mnesia dir "/opt/rabbitmq/db/rabbit@192.168.0.1" -s rabbit_control_main -nodename rabbit@192.168.0.1 
-extra wait /opt/rabbitmq/solaris/rabbitmq/sbin/lock

您需要访问已启动节点上的shell或查看其日志来调试问题。此时，您的节点正在启动（epmd显示它正在运行），但应用程序挂起，阻止其他应用程序启动和节点完全启动。在我的系统中，这可能是由mnesia数据库的错误名称引起的。如果您使用ps aux（或系统上的等效工具），您应该能够看到兔子节点是如何启动的。还可以查看启动脚本。您想知道日志或shell文件的路径在哪里。您使用

to_erl

命令连接到shell。@Amiramix

to_erl

命令说它找不到erlang.pipe。我添加了“编辑我的帖子”，显示我的rabbitmq日志和aux命令（如果我找不到其他erlang日志）。选项

-noshell

表示节点启动时没有shell访问。您可以尝试从ps输出复制整个命令，并手动启动节点，忽略

-noshell

参数（当然还要确保原始节点已停止）。您还可以尝试检查节点在启动时应该写入的日志-确切的文件名在该长命令中。顺便问一下，为什么在输出中节点会启动两次，一次是pid 19849，一次是19711？他们都试图访问同一个mnesia数据库，对吗？@Amiramix我已经发布了rabbit@192.168.0.1.log及rabbit@192.168.0.1-log只给我提供了

祖先：[]消息：[{'EXIT'，normal}]链接：[，]字典：[]陷阱_退出：真实状态：运行堆_大小：1598堆栈_大小：27减少：203邻居：

看起来某个进程正在接收来自另一个进程的退出信号。您需要从正在退出的进程中捕获日志。那时候好像是。您可以grep该PID的日志，希望该进程已被记录。另一方面，退出类型为

normal

，因此流程可能没有问题。您是否尝试使用shell访问权限启动节点？您需要在启动的节点上访问shell或查看其日志以调试问题。此时，您的节点正在启动（epmd显示它正在运行），但应用程序挂起，阻止其他应用程序启动和节点完全启动。在我的系统中，这可能是由mnesia数据库的错误名称引起的。如果您使用ps aux（或系统上的等效工具），您应该能够看到兔子节点是如何启动的。还可以查看启动脚本。您想知道日志或shell文件的路径在哪里。您使用

to_erl

命令连接到shell。@Amiramix

to_erl

命令说它找不到erlang.pipe。我添加了“编辑我的帖子”，显示我的rabbitmq日志和aux命令（如果我找不到其他erlang日志）。选项

-noshell

表示节点启动时没有shell访问。您可以尝试从ps输出复制整个命令，并手动启动节点，忽略

-noshell

祖先：[]消息：[{'EXIT'，normal}]链接：[，]字典：[]陷阱_退出：真实状态：运行堆_大小：1598堆栈_大小：27减少：203邻居：

normal

，因此流程可能没有问题。是否尝试使用shell访问权限启动节点？