Remote UNIX connection

[FitnessPlus]

My log is filling up with a bunch of junk and I need some help figuring out why.
The following comes from /var/log/asterisk/full

[Aug 11 12:38:33] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:33] VERBOSE[3639] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:34] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:34] VERBOSE[3645] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:37] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:37] VERBOSE[3651] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:37] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:37] VERBOSE[3657] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:38] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:38] VERBOSE[3663] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:41] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:41] VERBOSE[3669] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:41] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:41] VERBOSE[3675] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:42] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:42] VERBOSE[3681] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:45] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:45] VERBOSE[3687] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:45] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:45] VERBOSE[3693] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:46] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:46] VERBOSE[3699] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:49] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:49] VERBOSE[3705] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:49] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:49] VERBOSE[3711] logger.c:     -- Remote UNIX connection disconnected
[Aug 11 12:38:50] VERBOSE[8205] logger.c:     -- Remote UNIX connection
[Aug 11 12:38:50] VERBOSE[3717] logger.c:     -- Remote UNIX connection disconnected

I searched the forums and I found a post that had the "Remote UNIX connection" line in it that related to the daily backups which I do have installed...not sure if it could be causing this or not.

What exactly is the asterisk/full log logging? Is it asterisk activity? or would it be logging samba activity as well?

 

[byersjus]

I realize this is an old thread, but I'm getting the same thing.

Anyone know the solution?

 

[randy7376]

The `Remote UNIX connection` message is a normal part of Asterisk operations. The original poster doesn't mention how much "junk" or how excessive these messages are. In short, yes - it logs Asterisk's activities.

My largest full log file on a relatively busy system is around 8M. What gets logged depends upon verbosity -

 core set verbose XXX

- where XXX is a numeric value. A higher number means to be more verbose. See also, core set debug as this can cause large log files to be generated. How large is /var/log/asterisk/full on your system?

When you first connect to the Asterisk CLI, you should see something along the lines of Verbosity is at least 3. Default verbosity level on Asterisk 1.4 & 1.6 is set to 3. I believe this changed in Asterisk 1.8 to almost 0, if I remember correctly.

Activity for SAMBA is kept in a separate set of log files which can be found in /var/log/samba/ .

EDIT: From nerdvittles.com:

Asterisk CLI Change. Finally, just a heads up that (once again) the Asterisk Dev Team appears to have changed the default behavior of the Asterisk CLI. With Asterisk 1.8.2, if you make outbound calls after loading the CLI, you will notice that call progress no longer appears in the CLI. To restore the standard behavior (since Moses), issue the following command: core set verbose 3.

 

[jeffmac]

You'll probably find more of this is "FreePBX" normal operations than "Asterisk" normal operations.

You probably have a FreePBX "system status" web page up, and its auto updating is driving those connections - and filling your log (slowly)....

Jeff

 

[FitnessPlus]

Yes, this is an old post, and I found that it was FreePBX that was causing this. It was all grouped together because at that point there wasn't any other activity on the system.

I do have some full logs that are over 30 MB, so I guess my system is a little more on the busy side (inbound call center with 5 lines and 4 other lines used for other business).

 

[randy7376]

You'll probably find more of this is "FreePBX" normal operations than "Asterisk" normal operations.

That would be correct and thanks for the clarification. I had Asterisk on the brain when I wrote the above. Thinking more of /var/log/asterisk/full versus the actual message showing up in the logfile.

 

[byersjus]

Well, I was getting two lines every 4 seconds so it was filling up pretty fast. I turned the verbosity(?) down and now I no longer see it in there.

I had my tinfoil hat on for a minute thinking it was someone trying to brute force my box over ssh despite not having the port open...

Glad it was nothing.

Thanks!