Cli Spam: Remote UNIX connection disconnected - unwanted

How do you stop this from polluting your cli. As soon as the manager.conf was settup it began it’s annoying spree.

Update after several months: This appears to be a harrowing bug that many people are struggling with, no answers have been given.

displayconnects = no

what more does it want to be quiet?

-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection
-- Remote UNIX connection disconnected
-- Remote UNIX connection

Here is the same issue unanswered:

readlist.com/lists/lists.digium. … 16383.html

viewtopic.php?t=10574&highlight=remote+unix+connection+disconnected

This is still a present and annoying issue.

Google does not seem to reveal how to shut this one up.

That shows up when you have a console connected with a verbosity of 3 or higher. Do you have Asterisk started like “asterisk -vvvc” or are you connected like “asterisk -vvvr” ?

Ok lets get this clear

What you describe as Cli Spam is NOT a bug , a Bug is an error in code, this is a perfectly acceptable and correct verbose output to the console screen. It is designed to be there at certain verbose levels and as such acts correctly displaying what is expected.

It also is not Spam, spam is as described by wikipedia [quote]Spam is the use of electronic messaging systems (including most broadcast media, digital delivery systems) to send unsolicited bulk messages indiscriminately[/quote] This is not any of those.

if you dont want any cli output set verbose and debug to 0 . Just because something doesnt work as YOU expect it is not a Bug.

Ian

I agree with Ian’s sentiments. “Spam” is getting devalued by being used to refer to frequent diagnostic messges that the user doesn’t like. It isn’t a bug.

This message relates to console connections, not to AMI ones. If you are getting lots of them, it is because you are shelling to asterisk -r with commands on the command line. To suppress the message:

  1. find a better way of doing what you want to do: starting up asterisk -r is relatively expensive;
  2. reduce the console verbosity;
  3. edit the source code to remove it or change its verbosity level - neither of these changes should require any significant understanding of programming or the source code;
  4. live with it.

I realize this thread is ancient but nobody actually answered this question and I just ran into this on Asterisk v13.

The solution is to edit /etc/asterisk.conf

[options] hideconnect=yes

1 Like