1

I have LogWatch running on a Fedora 20 server. Logwatch gives the following every night:

--------------------- Connections (secure-log) Begin ------------------------

**Unmatched Entries**

CROND: pam_env(crond:setcred): Unable to open env file: /etc/environment: No such file or directory: 199 Time(s)

crond: pam_env(crond:setcred): Unable to open env file: /etc/environment: No such file or directory: 398 Time(s)

---------------------- Connections (secure-log) End -------------------------

What could be generating these errors?

Roger Creasy
  • 861
  • 3
  • 11
  • 18

1 Answers1

3

Crond is triggering these logs. You should suppress them by creating the file

/etc/environment

Though, you should update at least to Fedora 23. If it is a bug, it will not ever get fixed in Fedora 20, because it is years after EOL.

Jakuje
  • 9,715
  • 2
  • 42
  • 45
  • I don't have an F20 system to check, but from the changelog for the `setup` package, the file `/etc/environment` (which is empty by default) was added in 2004 — pre-Fedora! That file should exist. – mattdm Sep 01 '16 at 22:58