** Changed in: asterisk (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909816
Title:
asterisk spams console output to syslog due to systemd
** Changed in: asterisk (Debian)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909816
Title:
asterisk spams console output to syslog due to systemd
FTR, this has caused a regression:
https://bugs.launchpad.net/debian/+source/asterisk/+bug/1958259
I have proposed a fix to the Debian maintainer; hopefully we should see
it appear in Ubuntu soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Marking as fix released since this was sync'd and has already landed in
jammy
** Changed in: asterisk (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Cool, Debian accepted my patch:
```
asterisk (1:16.16.1~dfsg-4) unstable; urgency=medium
.
[ Utkarsh Gupta ]
* Set default systemd config to avoid console output to syslog.
(Closes: #985314, #971090)
```
I'll take this and prep a fix.
** Changed in: asterisk (Ubuntu)
Assignee:
** Changed in: asterisk (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909816
Title:
asterisk spams console output to syslog due to systemd
On Wed, Oct 6, 2021 at 10:40 PM Athos Ribeiro
<1909...@bugs.launchpad.net> wrote:
>
> Note that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971090 may
> be somewhat related to this one.
it probably is, because even asterisk doesn't log ansi to its own
logs, but does print it to console.
>
** Changed in: asterisk (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909816
Title:
asterisk spams console output to syslog due to systemd
misconfiguration
Note that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971090 may
be somewhat related to this one.
It would be nice to hear from the Debian maintainer on this one before
we move forward with applying the tty patch. Moreover, is there any
change we could break users workflow by no longer
** Bug watch added: Debian Bug tracker #985314
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985314
** Also affects: asterisk (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985314
Importance: Unknown
Status: Unknown
--
You received this bug notification
OK, thanks for replying back. I think it is clear that I don't know
much about asterisk; my comment was based on a general feeling that
standard error messages should not be silenced. But I will step back
and let you guys decide what is best in this scenario :-). Thanks.
--
You received this
Hi Sergio,
> In any case, I still think it's not a good idea to silence the
> stderr input in journalctl, so while I think the proposed patch
> makes sense, I would remove the "StandardError=null" line from
> it.
If use safe_asterisk (for allowing easy access to the asterisk CLI w/o logging
Heya,
Yes, remotely attaching to console is basically the standard way of
doing anything with asterisk, the headless thing runs and accepts calls
etc but if you want to check current call status, registration, reload
dialplan, or pretty much do anything, you'll need to `asterisk -r`
to get to
@timecop, yes, that would mean that, if you want to see output when
executing asterisk "by hand", then you would have to reenable the
console logging in the configuration file.
OK, that was a good point, and I'm not an asterisk expert so I have no
idea whether "attaching to remote console" is a
@sergiodj,
> I'm not sure I agree with it. I think a better approach would be to
comment out the line I mentioned by default, since it doesn't seem to be
useful, given that the logs are already recorded in the log file under
/var/log/asterisk.
Wouldn't that remove any kind of output when you
The attachment "asterisk+lp1909816.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
Thanks for the patch, Utkarsh.
I'm not sure I agree with it. I think a better approach would be to
comment out the line I mentioned by default, since it doesn't seem to be
useful, given that the logs are already recorded in the log file under
/var/log/asterisk. This way, we won't need to mess
Patch attached; forwarded to Debian (cf: #985314), and X-Debbugs-Cc'ed
this bug.
** Patch added: "asterisk+lp1909816.patch"
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1909816/+attachment/5476861/+files/asterisk+lp1909816.patch
--
You received this bug notification because you
> Does anyone give a rat's ass about this? I'm guessing not,
> but some kind of notification about it would have been nice.
I am sorry but this kind of attitude doesn't help.
Anyway, I took a look at this and when installing this package in Debian or
Ubuntu, I see:
Created symlink
Just to clarify something here: if Debian fixes the problem, the change
will show up *in a next release of Ubuntu*. We will still have to SRU
the fix to Focal/Groovy/Hirsute as applicable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for taking the time to report a bug, and sorry for not getting
back to you sooner. This must have fallen through the cracks and we
didn't process it during our daily triages.
I can confirm here that asterisk will output its logs to two places:
- The console (which is what ends up in
Does anyone give a rat's ass about this? I'm guessing not, but some kind
of notification about it would have been nice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909816
Title:
asterisk spams
22 matches
Mail list logo
