• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

In need of a logwatch how-to

C

criticman

Guest
So logwatch is installed properly already with the OS I guess since I know I didn't install it and running a yum update logwatch shows it is up to date.

Well, how the heck do I use it? I configured the logwatch.conf file to have my email address and I confirmed it had valid log file paths.

I tried running "example" commands from the MAN on logwatch.org and nothing happens, it just pauses for a second then goes back to command prompt. I even specified --print to output anything for me to see but nope, nothing.

Any pointers to a better config would be great!
 
Ok, I've run into this problem myself. The easy fix for me was as follows..

Create a forwarding domain for the box (i.e. if your box name is "my.box.name", you create the standard-redirect website for my.box.name to go to your website. Configure the e-mail. Any unknown e-mail, forward to [email protected]. This will send any e-mail sent to *@my.box.name to [email protected]. (This will help with cronjobs and e-mails for them)...

Next, this is important.. Remove the e-mail address you added to logwatch. It doesn't do any good there. It's still going to send to the same place when run from [email protected]. (Again, this is why you set up the above standard-redirect).

Now, my reasons for saying use a standard redirect are as follows: Keeps your traffic to the right place, gives you options for e-mail, (i.e. accounts at my.box.name.).

Anyway, I hope this helps with what you were trying to do. Let me know if you need anything else.

-John
 
Without actually doing anything else, I saw this morning that I had an e-mail from LogWatch. So, just by putting my email in the config, it worked.
 
Back
Top