I am trying to use a dict in an Ansible task, which is defined like this:
in vars/main.yml file:
username: user1
userpass: pass1
users:
"{{ username }}":
pass: "{{ userpass }}"
This doesn't work in Ansible 2.9: Ansible seems to not interpolate the value for "{{ username }}"
IIRC this worked fine around Ansible 2.5
What has changed? How should I rewrite my roles and playbooks now?
In the default exim4 install on Debian with split configuration files I have created a custom file at /etc/exim4/conf.d/acl/33_conf with the following content:
acl_not_smtp:
defer log_message = testing defer or deny
Then I am testin the setup with the date|mail -s test [email protected] command on the exim box and the email gets sent no problem.
Why the email isn't deferred or denied?
Is it OK to use the serviceescalation Nagios facility to reduce frequency of the notifications sent?
The idea is to setup a generic service template with frequent notifications by default and provide means to automatically reduce Nagios' peskiness when the particular service' outage is ignored long enough.
Any drawbacks to this approach?
I have two Asterisk servers in a chain like this:
SIP client (G.729) <-SIP-> Asterisk 1 (converting G.729 to G.711) <-IAX2-> Asterisk 2 -> terminated to analog line.
When no buffering was configured on either of Asterisks, the sound was terrible when received on the analog line (it was perfectly OK in the other direction - I assume the SIP client has buffering enabled for reception.)
As the two Asterisk servers are on LAN, I thought buffering will make most sense on Asterisk 1 facing the remote SIP client.
However, enabling buffering on Asterisk 1 made no difference to sound quality. Enabling buffering on Asterisk 2 somehow did the trick.
Watching the stats on Asterisk 2 confirms this:
CLI> iax2 show netstats
-------- LOCAL --------------------- -------- REMOTE --------------------
Channel RTT Jit Del Lost % Drop OOO Kpkts Jit Del Lost % Drop OOO Kpkts FirstMsg LastMsg
IAX2/ast1-5936 1 60 140 79 0 43 16712 64 0 40 0 0 0 0 0 Rx:NEW Rx:ACK
As you can see about 25% of received packet are Out-of-order (OOO), which I suppose is fixed by the configured jitterbuffer.
So my question is:
CsipSimple - as other SIP clients sound much better without buffering than this one) and why jitterbuffer on the closer server couldn't do that?
Is it possible to improve the quality of reports from logwatch?
Like make it not just report disk usage which doesn't even change much in daily operation, but report significant changes in usage or approaching critical capacity levels?
If I cannot do that with logwatch and instead have to write custom scripts to produce such reports, logwatch appears to be pretty useless, or even dangerous, as many users reportedly grow to ignore emails from it knowing they are so boring.