[asterisk-bugs] [JIRA] (ASTERISK-20770) Remote console verbosity implementation causes problems
Tilghman Lesher (JIRA)
noreply at issues.asterisk.org
Mon Dec 17 22:10:45 CST 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200798#comment-200798 ]
Tilghman Lesher commented on ASTERISK-20770:
--------------------------------------------
I'm thinking that if you had set 'core set verbose 5' in 1.6.2, you would have experienced exactly the same issues as you're experiencing now with Asterisk 11. So the change didn't necessarily cause the problem; but it's more evident, now that the remote console receives everything. When your verbose output is near continuous, there's no lull in the output available for tab-generated feedback, which is why you're getting verbose messages mixed in with your tab completion.
I think the ultimate solution is going to involve separating the remote Asterisk instance into two pipes, one for synchronous commands, the other for asynchronous output, and possibly changing the processing of verbose messages to the master process of the Asterisk console.
> Remote console verbosity implementation causes problems
> -------------------------------------------------------
>
> Key: ASTERISK-20770
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20770
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Components: Core/General
> Affects Versions: 11.1.0
> Environment: Any
> Reporter: Pavel Troller
> Assignee: Pavel Troller
> Severity: Minor
>
> The implementation of individual remote console verbosity causes many problems, especially on systems with high traffic load and with complex dialplans.
> Even with remote verbosity set to zero, the following problems are occuring:
> 1) The prompt is being cleared and drawn again and again. This causes the prompt to flicker and it is a primary cause for all the subsequent problems.
> 2) If the prompt contains dynamic components (time etc.), they are changing with every redraw. When the redraws are not in regular intervals (typical for phone traffic), it looks strange.
> 3) If a longer printout is received and the operator wants to view it using Shift-PageUp feature of Linux console, every prompt redraw resets it back, making such viewing impossible.
> 4) If a command completion feature is being used by pressing the Tab key, it inteferes with messages going downstream and fragments of them are dropped to the console, causing strange output, and at least in one case crash of the remote console has been observed in such a case.
> 5) If the remote console is accessed using a network connection (ssh, telnet...), permanent redraws of the prompt may cause increased network traffic, especially when many remote clients are active.
> Any of the problems above taken individually is not too much serious, but all of them together cause substantial discomfort in comparison with previous console behaviour. My opinion is, that the programmer's approach to the individual verbosity implementation must be different - the filtering of messages has to be implemented on the server, not the client. It will solve all the problems, including the one with impossibility to alias the "core set verbose" command, which is already open as a separate issue.
> To illustrate the problem, here is a video from a live system. Sorry for the length, it's 597 MB, I'm not good at compressing videos while keeping frame rate and readability :-).
> http://sinus.cz/~patrol/unsorted/asterisk_remote_console_v11.mp4
> At the beginning, core show calls is issued several times, to see the traffic. Then, core show channels. You can see, how the console is slow. Then, a problem with Tab is demonstrated, you can see unwanted output being printed, including damage od the edited command line (a digit appears in the middle of the line). At the end, an attempt is made to terminate the session, which finally succeeds. The sound is IN SYNC with the video! You can hear me typing, but what I'm typing appears later. It's really THAT BAD.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list