Home / user-235324

Alexander Tarasov's questions

Martin Hope
Alexander Tarasov
Asked: 2016-05-01 13:36:43 +0800 CST
  • 0

I have single RabbitMQ 3.6.1-1 installed on CentOS 7.2.1511, with Erlang R16B-03.16.el7. Today I cleaned it up:

rabbitmqctl stop_app
rabbitmqctl force_reset
rabbitmqctl start_app

It worked for some time and now (maybe, after 8 hours of data processing) it doesn't respond to application requests and status check:

# rabbitmqctl status
Status of node 'rabbit@RabbitMQ-Server' ...
^C
Session terminated, killing shell... ...killed.

Also, I have a lot of messages in /var/log/rabbitmq/startup_log. These messages are repeating in infinite loop: http://pastebin.com/38AXyw4n

There are nothing in other logs:

# ls -lS
total 6481664
-rw-r--r-- 1 root     root     2365375398 Apr 30 21:34 startup_log
-rw-r--r-- 1 rabbitmq rabbitmq          0 Apr 30 14:18 [email protected]
-rw-r--r-- 1 rabbitmq rabbitmq          0 Apr 30 20:45 [email protected]
-rw-r--r-- 1 root     root              0 Apr 30 14:18 startup_err

What's wrong with RabbitMQ? How I could restore it back to working state?

centos rabbitmq
Martin Hope
Alexander Tarasov
Asked: 2014-08-05 08:14:30 +0800 CST
  • 1

I have CUCM 7.1.5 with a lot of CIPCs connected to it. Each CIPC has 3 directory numbers (for example 107, 207, 307) and incoming call can arrive on any of these lines.

I have managed to allow only one call for each line by setting Busy Trigger = 1 in settings of each directory number.

What I want to do, is to allow only one call for the whole device (for all lines together). That is, when phone is already answered call from line 107, then if call is arriving on 207 or 307, CUCM should put 'busy' signal to new caller.

cisco