| Summary: | mga6: crond[1086]: (/usr/bin/python) ERROR (getpwnam() failed) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dbitouze |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | python-2.7.11-1.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Bit Twister
2016-01-30 22:09:39 CET
Could you identify what cron script causes this error message?
Samuel Verschelde
2016-02-02 14:32:41 CET
Keywords:
(none) =>
NEEDINFO Oops, missed adding "|" to Steps. Should have been journalctl | grep -i failed as root (In reply to Samuel Verschelde from comment #1) > Could you identify what cron script causes this error message? Finally, two network installs later, found it. /etc/cron.d/php One of my automated install scripts was removing it from cron.d and installing my kludge into my cron hourly directory. If you run /etc/cron.d/php's find command from a terminal you should see find: warning: you have specified the -depth option after a non-option argument -type, but options are not positional (-depth affects tests specified before it as well as those specified after it). Please specify options before other arguments. Someone who knows what is going on will need to see if the "-depth -mindepth 1 -maxdepth 1" arguments are needed. I remember writing up a bug report in Mandrake or Mandriva and wrote my own kludge to run in /etc/cron.hourly to run in 32 or 64 installs to get rid of the error messages. Here is my script minus the /etc/cron.d/php comments. #!/bin/bash if [ $(uname -m) = "x86_64" ] ; then _lib=lib64 else _lib='lib' fi if [ -d /var/lib/php ] ; then find /var/lib/php/ -type f -mmin +$(/usr/$_lib/php/maxlifetime) -print0 | xargs -r -0 rm fi Keywords:
NEEDINFO =>
(none) problem was caused by /etc/cron.d/mailman not removed. *** This bug has been marked as a duplicate of bug 17522 *** Status:
NEW =>
RESOLVED Bug still present with an up to date Mageia 7.
> Could you identify what cron script causes this error message?
I don't know how to do that.
Currently:
# ll /etc/cron.d/
total 16K
-rw-r--r-- 1 root root 163 juin 15 14:37 e2scrub_all
-rw-r--r-- 1 root root 1,4K sept. 22 09:32 mailman
-rw-r--r-- 1 root root 485 août 29 15:51 php
-rw-r--r-- 1 root root 108 oct. 28 2011 raid-checkCC:
(none) =>
dbitouze |