• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Orphan (no passwd entry)

M

MikeUN

Guest
What does this mean coming out of the Log Watch emails I get daily?


--------------------------------------
**Unmatched Entries**
ORPHAN (no passwd entry)
ORPHAN (no passwd entry)
ORPHAN (no passwd entry)
ORPHAN (no passwd entry)
ORPHAN (no passwd entry)
ORPHAN (no passwd entry)
ORPHAN (no passwd entry)

-------------------------------------

I'm getting several more each day (started with one or two, going up to about 12 now)

Thanks,
Mike
 
These are orphaned cron jobs, that were not removed when users were deleted from the system. when using redhat OS's have a look in the following locations for any jobs that are setup for which actual users do not exist anymore:

/var/spool/cron
/etc/crontab
/etc/cron.hourly
/etc/cron.daily
/etc/cron.weekly
/etc/cron.monthly
 
A possible reason as to why these cron jobs got orphaned may be that your manually remove a user, or you renamed a user or domain which had a cron job running.
 
You might have this also if you manually edited the root cron file in /var/spool/cron as redhat systems will create a backup file named root~ and this will be executed as a job, but since there is no user named root~ it is considered an orphan.

You can easily find these with this command in console or SSH:

grep ORPHAN /var/log/cron
 
Back
Top