Unable to start rabbitmq-server via sudo service rabbitmq-server start after maintenance
2,322 views
Skip to first unread message
Thomi
Dec 13, 2016, 5:56:31 PM12/13/16
to rabbitmq-users
Hi
We are having a rabbitmq cluster (2 nodes) running since quite a while and it works really fine. Just recently our company forced to restart our servers due to maintenance reasons.
Since then I am unable to start rabbitmq-server via "sudo service rabbitmq-server start" command. I am still able to start it via rabbitmq user and command "rabbitmq-server -detached" but
I don't really understand what is different and why does it work for rabbitmq user but not for the root user.
I was trying to dive into the startup script and realised that rabbitmqctl status is giving different return codes depending if I run it as root or as rabbitmq.
Any help which point me in a direction is greatly appreciated.
Thanks
Thomi
Details:
[sys_eventhub1@nrchbs-slt0038 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.8 (Santiago)
[sys_eventhub1@nrchbs-slt0038 ~]$ yum list installed | grep rabbitmq
rabbitmq-server.noarch 3.6.0-1 @rabbitmq_rabbitmq-server
[sys_eventhub1@nrchbs-slt0038 ~]$ yum list installed | grep erlang.x86
erlang.x86_64 18.3-1.el6 @erlang_solutions
[sys_eventhub1@nrchbs-slt0038 ~]$ sudo service rabbitmq-server stop
Stopping rabbitmq-server: rmdir: failed to remove `/var/run/rabbitmq': No such file or directory
rabbitmq-server.
[sys_eventhub1@nrchbs-slt0038 ~]$ ps -ef | grep rabbit
93687439 8500 3485 0 23:37 pts/0 00:00:00 grep rabbit
rabbitmq 18012 1 0 Nov07 ? 00:00:37 /usr/lib64/erlang/erts-7.3/bin/epmd -daemon
[sys_eventhub1@nrchbs-slt0038 ~]$ sudo service rabbitmq-server start
Starting rabbitmq-server: RabbitMQ is currently running
rabbitmq-server.
[sys_eventhub1@nrchbs-slt0038 ~]$ sudo service rabbitmq-server status
Status of node 'rabbit@nrchbs-slt0038' ...
Error: unable to connect to node 'rabbit@nrchbs-slt0038': nodedown
DIAGNOSTICS
===========
attempted to contact: ['rabbit@nrchbs-slt0038']
rabbit@nrchbs-slt0038:
* connected to epmd (port 4369) on nrchbs-slt0038
* epmd reports: node 'rabbit' not running at all
no other nodes on nrchbs-slt0038
* suggestion: start the node
current node details:
- node name: 'rabbitmq-cli-6538@nrchbs-slt0038'
- home dir: /var/lib/rabbitmq
- cookie hash: 3VSUcIMHTgxY2zqMy228jw==
[sys_eventhub1@nrchbs-slt0038 ~]$ sudo su - rabbitmq
-bash-4.1$ rabbitmq-server -detached
Warning: PID file not written; -detached was passed.
-bash-4.1$ ps -ef | grep rabbit
root 8545 3485 0 23:39 pts/0 00:00:00 sudo su - rabbitmq
root 8546 8545 0 23:39 pts/0 00:00:00 su - rabbitmq
rabbitmq 8547 8546 1 23:39 pts/0 00:00:00 -bash
rabbitmq 8841 1 99 23:39 ? 00:00:08 /usr/lib64/erlang/erts-7.3/bin/beam.smp -W w -A 64 -P 1048576 -K true -- -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib/rabbitmq/lib/rabbitmq_server-3.6.0/ebin -noshell -noinput -s rabbit boot -sname rabbit@nrchbs-slt0038 -boot start_sasl -config /etc/rabbitmq/rabbitmq -kernel inet_default_connect_options [{nodelay,true}] -sasl errlog_type error -sasl sasl_error_logger false -rabbit error_logger {file,"/var/log/rabbitmq/rab...@nrchbs-slt0038.log"} -rabbit sasl_error_logger {file,"/var/log/rabbitmq/rab...@nrchbs-slt0038-sasl.log"} -rabbit enabled_plugins_file "/etc/rabbitmq/enabled_plugins" -rabbit plugins_dir "/usr/lib/rabbitmq/lib/rabbitmq_server-3.6.0/plugins" -rabbit plugins_expand_dir "/apps/rabbitmq/mnesia/rabbit@nrchbs-slt0038-plugins-expand" -os_mon start_cpu_sup false -os_mon start_disksup false -os_mon start_memsup false -mnesia dir "/apps/rabbitmq/mnesia/rabbit@nrchbs-slt0038" -kernel inet_dist_listen_min 25672 -kernel inet_dist_listen_max 25672 -noshell -noinput
rabbitmq 8919 8841 0 23:39 ? 00:00:00 inet_gethost 4
rabbitmq 8920 8919 0 23:39 ? 00:00:00 inet_gethost 4
rabbitmq 8936 8547 1 23:39 pts/0 00:00:00 ps -ef
rabbitmq 8937 8547 0 23:39 pts/0 00:00:00 grep rabbit
rabbitmq 18012 1 0 Nov07 ? 00:00:37 /usr/lib64/erlang/erts-7.3/bin/epmd -daemon
[sys_eventhub1@nrchbs-slt0038 ~]$ sudo service rabbitmq-server status
Status of node 'rabbit@nrchbs-slt0038' ...
[{pid,7142},
{running_applications,
[{rabbitmq_management_visualiser,"RabbitMQ Visualiser","3.6.0"},
{rabbitmq_management,"RabbitMQ Management Console","3.6.0"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","3.6.0"},
{rabbit,"RabbitMQ","3.6.0"},
{os_mon,"CPO CXC 138 46","2.4"},
{rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.6.0"},
{webmachine,"webmachine","git"},
{mochiweb,"MochiMedia Web Server","2.13.0"},
{ssl,"Erlang/OTP SSL application","7.3"},
{public_key,"Public key infrastructure","1.1.1"},
{crypto,"CRYPTO","3.6.3"},
{amqp_client,"RabbitMQ AMQP Client","3.6.0"},
{rabbit_common,[],"3.6.0"},
{asn1,"The Erlang ASN1 compiler version 4.0.2","4.0.2"},
{syntax_tools,"Syntax tools","1.7"},
{ranch,"Socket acceptor pool for TCP protocols.","1.2.1"},
{xmerl,"XML parser","1.3.10"},
{compiler,"ERTS CXC 138 10","6.0.3"},
{inets,"INETS CXC 138 49","6.2"},
{mnesia,"MNESIA CXC 138 12","4.13.3"},
{sasl,"SASL CXC 138 11","2.7"},
{stdlib,"ERTS CXC 138 10","2.8"},
{kernel,"ERTS CXC 138 10","4.2"}]},
{os,{unix,linux}},
{erlang_version,
"Erlang/OTP 18 [erts-7.3] [source-d2a6d81] [64-bit] [smp:6:6] [async-threads:64] [hipe] [kernel-poll:true]\n"},
{memory,
[{total,61192760},
{connection_readers,0},
{connection_writers,0},
{connection_channels,0},
{connection_other,2808},
{queue_procs,536624},
{queue_slave_procs,638768},
{plugins,567160},
{other_proc,19804088},
{mnesia,492720},
{mgmt_db,58584},
{msg_index,84672},
{other_ets,1479240},
{binary,244408},
{code,27352402},
{atom,992409},
{other_system,8938877}]},
{alarms,[]},
{listeners,[{clustering,25672,"::"},{amqp,5672,"::"}]},
{vm_memory_high_watermark,0.6},
{vm_memory_limit,20201019801},
{file_descriptors,
[{total_limit,10140},
{total_used,4},
{sockets_limit,9124},
{sockets_used,0}]},
{processes,[{limit,1048576},{used,362}]},
{run_queue,0},
{uptime,52},
{kernel,{net_ticktime,60}}]
Packages they installed or updated during maintenance:
Nov 07 01:47:45 Updated: openssl-1.0.1e-48.el6_8.3.x86_64 Nov 07 01:47:46 Updated: libudev-147-2.73.el6_8.2.x86_64 Nov 07 01:47:46 Updated: 1:net-snmp-libs-5.5-57.el6_8.1.x86_64 Nov 07 01:47:47 Updated: grep-2.20-5.el6_8.x86_64 Nov 07 01:47:47 Updated: 32:bind-libs-9.8.2-0.47.rc1.el6_8.1.x86_64 Nov 07 01:47:49 Updated: samba-common-3.6.23-36.el6_8.x86_64 Nov 07 01:47:50 Updated: samba-winbind-clients-3.6.23-36.el6_8.x86_64 Nov 07 01:47:51 Updated: samba-winbind-3.6.23-36.el6_8.x86_64 Nov 07 01:47:51 Updated: cronie-1.4.4-16.el6_8.2.x86_64 Nov 07 01:47:51 Updated: cronie-anacron-1.4.4-16.el6_8.2.x86_64 Nov 07 01:47:55 Updated: kernel-firmware-2.6.32-642.6.1.el6.noarch Nov 07 01:47:55 Updated: nginx-filesystem-1.10.1-1.el6.noarch Nov 07 01:47:55 Installed: nginx-mod-stream-1.10.1-1.el6.x86_64 Nov 07 01:47:55 Installed: nginx-mod-http-perl-1.10.1-1.el6.x86_64 Nov 07 01:47:55 Installed: nginx-mod-http-xslt-filter-1.10.1-1.el6.x86_64 Nov 07 01:47:55 Installed: nginx-mod-http-image-filter-1.10.1-1.el6.x86_64 Nov 07 01:47:55 Installed: nginx-mod-http-geoip-1.10.1-1.el6.x86_64 Nov 07 01:47:56 Updated: nginx-1.10.1-1.el6.x86_64 Nov 07 01:47:56 Installed: nginx-mod-mail-1.10.1-1.el6.x86_64 Nov 07 01:47:56 Installed: nginx-all-modules-1.10.1-1.el6.noarch Nov 07 01:47:56 Updated: libtirpc-0.2.1-11.el6_8.x86_64 Nov 07 01:47:56 Updated: udev-147-2.73.el6_8.2.x86_64 Nov 07 01:47:56 Updated: device-mapper-libs-1.02.117-7.el6_8.1.x86_64 Nov 07 01:47:57 Updated: device-mapper-1.02.117-7.el6_8.1.x86_64 Nov 07 01:47:57 Updated: device-mapper-event-libs-1.02.117-7.el6_8.1.x86_64 Nov 07 01:47:57 Updated: device-mapper-event-1.02.117-7.el6_8.1.x86_64 Nov 07 01:47:57 Updated: lvm2-libs-2.02.143-7.el6_8.1.x86_64 Nov 07 01:47:57 Updated: lvm2-2.02.143-7.el6_8.1.x86_64 Nov 07 01:47:58 Updated: 1:nfs-utils-1.2.3-70.el6_8.2.x86_64 Nov 07 01:48:03 Installed: kernel-2.6.32-642.6.1.el6.x86_64 Nov 07 01:48:05 Updated: samba-client-3.6.23-36.el6_8.x86_64 Nov 07 01:48:05 Updated: 32:bind-utils-9.8.2-0.47.rc1.el6_8.1.x86_64 Nov 07 01:48:06 Updated: tcsh-6.17-35.el6_8.1.x86_64 Nov 07 01:48:06 Updated: 1:net-snmp-utils-5.5-57.el6_8.1.x86_64 Nov 07 01:48:06 Updated: 1:net-snmp-5.5-57.el6_8.1.x86_64 Nov 07 01:48:06 Updated: libgudev1-147-2.73.el6_8.2.x86_64 Nov 07 01:48:06 Updated: perl-Net-SSLeay-1.35-10.el6_8.1.x86_64 Nov 07 01:48:07 Updated: openssl-devel-1.0.1e-48.el6_8.3.x86_64 Nov 07 01:48:08 Updated: kernel-headers-2.6.32-642.6.1.el6.x86_64 Nov 07 01:48:08 Updated: avahi-libs-0.6.25-15.el6_8.1.x86_64 Nov 07 01:48:08 Updated: tzdata-java-2016g-2.el6.noarch Nov 07 01:48:09 Updated: tzdata-2016g-2.el6.noarch
Michael Klishin
Dec 13, 2016, 6:15:55 PM12/13/16
to rabbitmq-users
See server and service management system logs.
> rmdir: failed to remove `/var/run/rabbitmq
Does this CentOS version use systemd by any chance?
Message has been deleted
Thomi
Dec 15, 2016, 2:28:15 AM12/15/16
to rabbitmq-users
Thanks Michael for the quick reply.
I did run on the other cluster node where I have the same issue
[sys_eventhub1@nrchbs-slt0037 ~]$ sudo service rabbitmq-server stop
Stopping rabbitmq-server: rmdir: failed to remove `/var/run/rabbitmq': No such file or directory
rabbitmq-server.
[sys_eventhub1@nrchbs-slt0037 ~]$ sudo service rabbitmq-server start
Starting rabbitmq-server: RabbitMQ is currently running
rabbitmq-server.
Then I checked /var/log/messages and /var/log/syslog
In /var/syslog I think nothing unusual when stopping or starting..
Dec 15 08:04:39 nrchbs-slt0037 sudo: sys_eventhub1 : TTY=pts/1 ; PWD=/apps/sys_eventhub1 ; USER=root ; COMMAND=/sbin/service rabbitmq-server stop
Dec 15 08:04:39 nrchbs-slt0037 su: pam_unix(su:session): session opened for user rabbitmq by sys_eventhub1(uid=0)
Dec 15 08:04:40 nrchbs-slt0037 su: pam_unix(su:session): session closed for user rabbitmq
Dec 15 08:04:40 nrchbs-slt0037 su: pam_unix(su:session): session opened for user rabbitmq by sys_eventhub1(uid=0)
Dec 15 08:04:41 nrchbs-slt0037 su: pam_unix(su:session): session closed for user rabbitmq
COMMAND=/sbin/service rabbitmq-server start
Dec 15 08:06:41 nrchbs-slt0037 su: pam_unix(su:session): session opened for user rabbitmq by sys_eventhub1(uid=0)
Dec 15 08:06:42 nrchbs-slt0037 su: pam_unix(su:session): session closed for user rabbitmq
/var/log/messages is empty which I don't understand why ??!
The error
rmdir: failed to remove `/var/run/rabbitmq': No such file or directory
appears when I stop rabbitmq-server
For the start command it looks like rabbitmq-server is running but it is not.
We are not using systemd on this redhat box.
Still confused. Wondering if there is something I can check on rabbitmq/erlang side which checks if rabbitmq-server is running or not.
Thanks a lot
Thomi
Michael Klishin
Dec 15, 2016, 2:44:59 AM12/15/16
to rabbitm...@googlegroups.com, Thomi
The issue is almost certainly in the init script or init.d service state, that's why I asked about
systemd. RabbitMQ RPM package prior to 3.6.6 didn't have systemd scripts
and we concluded that the only reasonable way to support both classic init.d and systemd
was to provide two separate RPM packages (for CentOS 6 and 7, the latter targets systemd).
I couldn't find a similar issue reported for or since 3.6.0. In fact, I only see
this particular error message (where /var/run/rabbitmq removal fails) in on thread on our legacy list:
http://rabbitmq.1065348.n5.nabble.com/The-problem-about-installing-rabbitmq-server-on-CentOS-6-3-td27987.html
As a workaround you can try to `mkdir -p /var/run/rabbitmq` and changing its owner to "rabbitmq".
Perhaps that would be able to get the service start command to succeed, which may reset some of its state.
Also, please consider upgrading to 3.6.6.
> --
> You received this message because you are subscribed to the Google Groups "rabbitmq-users"
> group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
> To post to this group, send an email to rabbitm...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
MK
Staff Software Engineer, Pivotal/RabbitMQ
systemd. RabbitMQ RPM package prior to 3.6.6 didn't have systemd scripts
and we concluded that the only reasonable way to support both classic init.d and systemd
was to provide two separate RPM packages (for CentOS 6 and 7, the latter targets systemd).
I couldn't find a similar issue reported for or since 3.6.0. In fact, I only see
this particular error message (where /var/run/rabbitmq removal fails) in on thread on our legacy list:
http://rabbitmq.1065348.n5.nabble.com/The-problem-about-installing-rabbitmq-server-on-CentOS-6-3-td27987.html
As a workaround you can try to `mkdir -p /var/run/rabbitmq` and changing its owner to "rabbitmq".
Perhaps that would be able to get the service start command to succeed, which may reset some of its state.
Also, please consider upgrading to 3.6.6.
> You received this message because you are subscribed to the Google Groups "rabbitmq-users"
> group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
> To post to this group, send an email to rabbitm...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
MK
Staff Software Engineer, Pivotal/RabbitMQ
Thomi
Dec 15, 2016, 2:49:15 AM12/15/16
to rabbitmq-users, thomas....@ikey.ch
I see and this helps a lot. I will do the upgrade since this is anyway planed.
Thanks a lot for quick and valuable feedback.
Thomi
Thomi
Jan 10, 2017, 11:16:49 AM1/10/17
to rabbitmq-users, thomas....@ikey.ch
Finally I upgraded a cluster to
[sys_eventhub1@nrchbs-slt0037 run]$ yum list installed | grep rabbitmq
rabbitmq-server.noarch 3.6.6-1.el6 @rabbitmq_rabbitmq-server
[sys_eventhub1@nrchbs-slt0037 run]$ yum list installed | grep erlang.x86
erlang.x86_64 19.2-1.el6 @erlang_solutions
and re-created /var/run/rabbitmq folder with following permissions
[sys_eventhub1@nrchbs-slt0038 run]$ ls -ld rabbit*
drwxr-xr-x 2 rabbitmq rabbitmq 4096 Jan 10 17:06 rabbitmq
but still no success to start via startup script...
[sys_eventhub1@nrchbs-slt0038 run]$ sudo service rabbitmq-server stop
Stopping rabbitmq-server: rabbitmq-server.
[sys_eventhub1@nrchbs-slt0038 run]$ sudo service rabbitmq-server status
Status of node 'rabbit@nrchbs-slt0038' ...
Error: unable to connect to node 'rabbit@nrchbs-slt0038': nodedown
DIAGNOSTICS
===========
attempted to contact: ['rabbit@nrchbs-slt0038']
rabbit@nrchbs-slt0038:
* connected to epmd (port 4369) on nrchbs-slt0038
* epmd reports: node 'rabbit' not running at all
no other nodes on nrchbs-slt0038
* suggestion: start the node
current node details:
- node name: 'rabbitmq-cli-85@nrchbs-slt0038'
- home dir: /var/lib/rabbitmq
- cookie hash: 3VSUcIMHTgxY2zqMy228jw==
[sys_eventhub1@nrchbs-slt0038 run]$ sudo service rabbitmq-server start
Starting rabbitmq-server: RabbitMQ is currently running
rabbitmq-server.
[sys_eventhub1@nrchbs-slt0038 run]$ ps -ef | grep rabbit
93687439 3204 23620 0 17:14 pts/1 00:00:00 grep rabbit
rabbitmq 25532 1 0 12:16 ? 00:00:00 /usr/lib64/erlang/erts-8.2/bin/epmd -daemon
Any idea somebody?
Thanks
Thomi
Startup Script I am using. Hope that's the right one ?!
#!/bin/sh
#
# rabbitmq-server RabbitMQ broker
#
# chkconfig: - 80 05
# description: Enable AMQP service provided by RabbitMQ
#
### BEGIN INIT INFO
# Provides: rabbitmq-server
# Required-Start: $remote_fs $network
# Required-Stop: $remote_fs $network
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: RabbitMQ broker
# Short-Description: Enable AMQP service provided by RabbitMQ broker
### END INIT INFO
# Source function library.
. /etc/init.d/functions
PATH=/sbin:/usr/sbin:/bin:/usr/bin
NAME=rabbitmq-server
DAEMON=/usr/sbin/${NAME}
CONTROL=/usr/sbin/rabbitmqctl
DESC=rabbitmq-server
USER=rabbitmq
ROTATE_SUFFIX=
PID_FILE=/var/run/rabbitmq/pid
RABBITMQ_ENV=/usr/lib/rabbitmq/bin/rabbitmq-env
START_PROG="daemon"
LOCK_FILE=/var/lock/subsys/$NAME
test -x $DAEMON || exit 0
test -x $CONTROL || exit 0
RETVAL=0
set -e
[ -f /etc/default/${NAME} ] && . /etc/default/${NAME}
RABBITMQ_SCRIPTS_DIR=$(dirname "$RABBITMQ_ENV")
. "$RABBITMQ_ENV"
ensure_pid_dir () {
PID_DIR=`dirname ${PID_FILE}`
if [ ! -d ${PID_DIR} ] ; then
mkdir -p ${PID_DIR}
chown -R ${USER}:${USER} ${PID_DIR}
chmod 755 ${PID_DIR}
fi
}
remove_pid () {
rm -f ${PID_FILE}
rmdir `dirname ${PID_FILE}` || :
}
start_rabbitmq () {
status_rabbitmq quiet
if [ $RETVAL = 0 ] ; then
echo RabbitMQ is currently running
else
RETVAL=0
ensure_pid_dir
set +e
RABBITMQ_PID_FILE=$PID_FILE $START_PROG $DAEMON \
> "${RABBITMQ_LOG_BASE}/startup_log" \
2> "${RABBITMQ_LOG_BASE}/startup_err" \
0<&- &
$CONTROL wait $PID_FILE >/dev/null 2>&1
RETVAL=$?
set -e
case "$RETVAL" in
0)
echo SUCCESS
if [ -n "$LOCK_FILE" ] ; then
touch $LOCK_FILE
fi
;;
*)
remove_pid
echo FAILED - check ${RABBITMQ_LOG_BASE}/startup_\{log, _err\}
RETVAL=1
;;
esac
fi
}
stop_rabbitmq () {
status_rabbitmq quiet
if [ $RETVAL = 0 ] ; then
set +e
$CONTROL stop ${PID_FILE} \
> ${RABBITMQ_LOG_BASE}/shutdown_log \
2> ${RABBITMQ_LOG_BASE}/shutdown_err
RETVAL=$?
set -e
if [ $RETVAL = 0 ] ; then
remove_pid
if [ -n "$LOCK_FILE" ] ; then
rm -f $LOCK_FILE
fi
else
echo FAILED - check ${RABBITMQ_LOG_BASE}/shutdown_log, _err
fi
else
echo RabbitMQ is not running
RETVAL=0
fi
}
status_rabbitmq() {
set +e
if [ "$1" != "quiet" ] ; then
$CONTROL status 2>&1
else
$CONTROL status > /dev/null 2>&1
fi
if [ $? != 0 ] ; then
RETVAL=3
fi
set -e
}
rotate_logs_rabbitmq() {
set +e
$CONTROL rotate_logs ${ROTATE_SUFFIX}
if [ $? != 0 ] ; then
RETVAL=1
fi
set -e
}
restart_running_rabbitmq () {
status_rabbitmq quiet
if [ $RETVAL = 0 ] ; then
restart_rabbitmq
else
echo RabbitMQ is not runnning
RETVAL=0
fi
}
restart_rabbitmq() {
stop_rabbitmq
start_rabbitmq
}
case "$1" in
start)
echo -n "Starting $DESC: "
start_rabbitmq
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
stop_rabbitmq
echo "$NAME."
;;
status)
status_rabbitmq
;;
rotate-logs)
echo -n "Rotating log files for $DESC: "
rotate_logs_rabbitmq
;;
force-reload|reload|restart)
echo -n "Restarting $DESC: "
restart_rabbitmq
echo "$NAME."
;;
try-restart)
echo -n "Restarting $DESC: "
restart_running_rabbitmq
echo "$NAME."
;;
*)
echo "Usage: $0 {start|stop|status|rotate-logs|restart|condrestart|try-restart|reload|force-reload}" >&2
RETVAL=1
;;
esac
exit $RETVAL
Michael Klishin
Jan 11, 2017, 1:43:43 AM1/11/17
to rabbitm...@googlegroups.com
See systemd (or similar) logs; make sure the right kind of package is used
(CentOS 6 and 7 have different packages as of recently).
Check SELinux logs.
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
Thomi
Jan 11, 2017, 4:40:25 AM1/11/17
to rabbitmq-users
Hi Michael
Thanks. Found this in the meantime...
In /usr/sbin/rabbitmqctl at line #40
su rabbitmq -s /bin/sh -c "/usr/lib/rabbitmq/bin/${SCRIPT} ${CMDLINE}"
This command on my affected boxes does not give exit code 69 back to the original session if rabbitmq-server is down. I've checked on my virtual CentOS box and there all is fine.
I was able to fix it like so. Not so nice but at least all is working now.
su rabbitmq -s /bin/sh -c "/usr/lib/rabbitmq/bin/${SCRIPT} ${CMDLINE}; echo \$? > /tmp/rabbit_exit_code"
exit `cat /tmp/rabbit_exit_code`I still don't understand why suddenly "su" command is beahving differently and not passing exit code back.
I am also checking with our enterprise admins at the moment regarding changes in this direction.
Ever seen such an issue?
Thomi
Michael Klishin
Jan 11, 2017, 5:21:07 AM1/11/17
to rabbitm...@googlegroups.com
What distribution and shell/version do you use (exact values, please)?
Did you install our RPM package?
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thomi
Jan 11, 2017, 7:15:26 AM1/11/17
to rabbitmq-users
Red Hat Enterprise Linux Server release 6.8 (Santiago)
GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)
su (GNU coreutils) 8.4
rabbitmq installed via yum from this repo
name=rabbitmq_rabbitmq-server-source
gpgcheck=0
enabled=1
priority=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RABBITMQ
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt
[sys_eventhub1@nrchbs-slt0037 ~]$ yum list installed | grep rabbit
rabbitmq-server.noarch 3.6.6-1.el6 @rabbitmq_rabbitmq-server
Do you need more?
Reply all
Reply to author
Forward
0 new messages