similar to: CentOS-6 Logwatch 7.3.6 behaviour

After some experimenting I have observed that overriding settings from /usr/share/logwatch/default.conf/logwatch.conf in /etc/logwatch/conf/logwatch.conf does not produce consistent results. For example, if I replace the default detail configuration in etc/logwatch/conf/logwatch.conf with: Detail = High It does indeed change the level of detail from the default Low set in

I am trying to get a logwatch summary emailed to a central address from a cron job. The tasd was copied verbatim from a system which does this already. Both are shown below. host1 crontab -l as root 45 7 * * * /usr/sbin/logwatch --service http --service imapd --service pop3 --service sshd --service vsftpd --service zz-disk_space --service zz-network --service zz-sys --mailto support at

CentOS-6.6 Can logwatch be configured to display the system uptime as part of the reporting prologue? If not then what would be the recommended way of including this information in a daily logwatch report? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne

On Mon, September 14, 2015 14:51, James B. Byrne wrote: > The Logwatch imapd service script distributed with CentOS-6 does not > generate anything when I run logwatch --service all on a cyrus-imapd > host. Is this expected behaviour? Is there a separate script for > cyrus-imapd or are their configuration options required to get the > existing script to work. > > I have found

The Logwatch imapd service script distributed with CentOS-6 does not generate anything when I run logwatch --service all on a cyrus-imapd host. Is this expected behaviour? Is there a separate script for cyrus-imapd or are their configuration options required to get the existing script to work. I have found an ancient (2004) logwatch service script for cyrus-imapd but I was sort of hoping that

On Mon, September 14, 2015 21:28, Always Learning wrote: > > On Mon, 2015-09-14 at 14:51 -0400, James B. Byrne wrote: > >> The Logwatch imapd service script distributed with CentOS-6 does not >> generate anything when I run logwatch --service all on a cyrus-imapd >> host. Is this expected behaviour? Is there a separate script for >> cyrus-imapd or are their

This morning I discovered this in the logwatch report for our external MX backup host. STARTTLS: write error=syscall error (-1), errno=32, get_error=error:00000000:lib(0):func(0):reason(0), retry=99, ssl_err=5: 206 Time(s) I also see many entries similar to this: 8: fl=0x802, mode=140777: SOCK inet04.mississauga.harte-lyne.ca/34091->(Transport endpoint is not connected): 1 Time(s)

On Mon, September 21, 2015 15:37, m.roth at 5-cent.us wrote: > Gordon Messmer wrote: >> >>> > In other words, the >>> >hostkeys would be identical. >> >> I think what the error indicates is that a client tried to connect >> to SSH, and the host key there did not match the fingerprint in the >> client's "known_hosts" database.

Am 25.11.2014 um 21:39 schrieb James B. Byrne: > This morning I discovered this in the logwatch report for our external MX > backup host. > > > STARTTLS: write error=syscall error (-1), errno=32, > get_error=error:00000000:lib(0):func(0):reason(0), retry=99, ssl_err=5: 206 > Time(s) > > > > I also see many entries similar to this: > > > > 8:

Recently we began seeing lots of these log entries on our off-site mx smtp host. I have googled this but I am not clear from what I have read if this is something we can stop altogether or should even worry about. Comments? Logwatch. . . --------------------- sendmail Begin ------------------------ SMTP SESSION, MESSAGE, OR RECIPIENT ERRORS ------------------------------------------

My logwatch reported this in this mornings report: --------------------- Kernel Begin ------------------------ WARNING: Kernel Errors Present usb 3-1: can't read configurations, error -71 ...: 1 Time(s) usb 3-1: can't set config #1, error -71 ...: 8 Time(s) usb 3-1: can't set config #1, error -84 ...: 66 Time(s) usb 3-1: device descriptor read/all, error -71

On Mon, June 15, 2015 11:16 am, Pete Geenhuizen wrote: > Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf Thanks a lot! Helps you to be aware that you definitely missed something important if you haven't the box rebooted during more than 45-60 days... Valeri > > Pete > > On 06/15/15 09:58, James B. Byrne wrote: >> CentOS-6.6 >> >> Can

CentOS-6.6 tmux-1.6 (epel) Twice now I have experienced the situation where upon exiting from a tmux initiated session on a remote host instead of returning to the originating session I see this in the session terminal display: <pre> ????????????????????????????????????????????????????????????????????????????????

Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf Pete On 06/15/15 09:58, James B. Byrne wrote: > CentOS-6.6 > > Can logwatch be configured to display the system uptime as part of the > reporting prologue? If not then what would be the recommended way of > including this information in a daily logwatch report? > > -- If money can fix it, it's not

> On Wed, 18 Feb 2015 05:36:48 +1300 > Jegadeesh Kumar wrote: > >> I setup the RPM build server and read some doc to write the spec >> files. but i did get it clearly. So can you guys please help me >> to write a new RPM spec. If you have set up an RPM build server then you should have installed the rpmbuild and rpmdevtools packages. If you have installed the latter

Arch = x86_64 OS = CentOS-6.4 (freepbx) Asterisk = 11.4.0 FreePBX = 2.11.0.2 Snom870 Handsets We are in the process of moving to an Asterisk based PBX. At the moment most things work as we wish. However, I have just notices that when I force a reload using 'amportal a reload' I see this loop start in 'asterisk -rvvvvvvvvvv': > Channel Local/s at tc-maint-000002a4;1

I changed the entries in smb4.conf (smb.conf) to this: [global] . . . dns update command = /usr/local/sbin/samba_dnsupdate nsupdate command = /usr/local/bin/samba-nsupdate -d -g And this is what results when I run: samba_dnsupdate --verbose -d8 --all-names . . . update(nsupdate): SRV _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.brockley.harte-lyne.ca

Logwatch is installed, and I am assuming by how empty /etc/logwatch is that it is running from defaults, which I find in /usr/share/logwatch/default.conf/services I want to customize ONE service. dovecot. Do I copy /usr/share/logwatch/default.conf/services/dovecot.conf to /etc/logwatch/conf/services and edit it there, or do I have to copy ALL default.conf/services/* there and modify

I am testing DC administration using samba-4.10.15 on FreeBSD-12.1p6 and have run across this: [root at smb4-2 ~ (master)]# samba-tool domain join BROCKLEY.HARTE-LYNE.CA DC -U"BROCKLEY\administrator" INFO 2020-06-25 14:26:10,692 pid:47306 /usr/local/lib/python3.7/site-packages/samba/join.py #104: Finding a writeable DC for domain 'BROCKLEY.HARTE-LYNE.CA' INFO 2020-06-25

This is all the diagnostic information I can think of at the moment: [root at smb4-1 ~ (master)]# klist Credentials cache: FILE:/tmp/krb5cc_0 Principal: administrator at BROCKLEY.HARTE-LYNE.CA Issued Expires Principal Jul 2 10:35:11 2020 Jul 2 20:35:11 2020 krbtgt/BROCKLEY.HARTE-LYNE.CA at BROCKLEY.HARTE-LYNE.CA [root at smb4-1 ~ (master)]# grep nsup