Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12477 - [fcron-2.0.4-1] 'Could not init PAM account management for' error in /var/log/cron.log
Attached to Project:
Community Packages
Opened by solsTiCe (zebul666) - Tuesday, 16 December 2008, 20:59 GMT
Last edited by Sergej Pupykin (sergej) - Sunday, 28 December 2008, 13:49 GMT
Opened by solsTiCe (zebul666) - Tuesday, 16 December 2008, 20:59 GMT
Last edited by Sergej Pupykin (sergej) - Sunday, 28 December 2008, 13:49 GMT
|
DetailsDescription:
since i upgraded today with pacman -Syu i got in /var/cron.log something like this: Dec 16 21:39:50 soho fcron[25382]: Could not init PAM account management for '/home/solstice/bin/rrd_traffic.pl': Module is unknown Dec 16 21:39:50 soho fcron[4552]: read_write_pipe(): read/write returned 0: retrying... (size: 4, size_processed: 0, num_retry: 1): Success Dec 16 21:39:50 soho fcron[4552]: read_write_pipe(): read/write returned 0: retrying... (size: 4, size_processed: 0, num_retry: 2): Success Dec 16 21:39:51 soho fcron[4552]: read_write_pipe(): read/write returned 0: retrying... (size: 4, size_processed: 0, num_retry: 3): Success Dec 16 21:39:52 soho fcron[4552]: Could not read job pid because of closed pipe: setting it to -1 i think it's linked to the glibc upgrade but not sure. here is the list of package upgraded: glibc (2.8-3 -> 2.9-2) binutils (2.18-9 -> 2.19-1) bison (2.3-4 -> 2.4.1-1) devilspie (0.22-2 -> 0.22-3) dhcpcd (4.0.4-1 -> 4.0.7-1) gcc-libs (4.3.2-1 -> 4.3.2-2) kernel-headers (2.6.26.3-1 -> 2.6.27.6-2) may be a simple recompile against latest glibc might cure this ? or it's a problem with pam package ? |
This task depends upon
Comment by solsTiCe (zebul666) -
Tuesday, 16 December 2008, 21:03 GMT
it seems a simple restart of fcron seems to fix this. to be confirmed