Description of problem: On a new mail server F19 x86_64 I get (2013-05-17): useradd: group 'clamupdate' does not exist Installing : clamav-filesystem-0.97.8-1.fc19.noarch warning: user clamupdate does not exist - using root warning: group clamupdate does not exist - using root ... Installing : clamav-update-0.97.8-1.fc19.x86_64 /usr/bin/chown: invalid group: ‘root:clamupdate’ and later # /usr/bin/freshclam WARNING: Can't get information about user clamupdate. and freshclam can't update the virus list. Version-Release number of selected component (if applicable): clamav-filesystem-0.97.8-1.fc19.noarch How reproducible: On a F19 text only install # yum install amavisd-new spamassassin clamav > clamav-data clamav-server clamav-server-sysvinit clamav-update Steps to Reproduce: 1. yum install amavisd-new spamassassin clamav > clamav-data clamav-server clamav-server-sysvinit clamav-update 2. execute /usr/bin/freshclam (does not update) 3. Actual results: freshclam does not work, /var/lib/clamv with root permissions, Expected results: Additional info: Reported on the test list http://lists.fedoraproject.org/pipermail/test/2013-May/115532.html with details and a fix (better one needed) Tested on F19 alpha with Gnome it was working.
On the working install (F19 alpha & updates, with Gnome, in virtual) we have [root at s198 ~]# cat /etc/passwd | grep 989 clamupdate:x:992:989:Clamav database update user:/var/lib/clamav:/sbin/nologin [root at s198 ~]# cat /etc/group | grep 992 ccache:x:992: That explain why was used GID=989 but now (F19 beta1 TC4 & updates, netinstall, without graphics) we have: [root at physics ~]# cat /etc/group | grep ccache ccache:x:996: and nothing with 992, so GID=989 is not necessary anymore and I used 992 for UID and GID and works. To have UID different from GID the group clamupdate must be created before the user clamupdate. Maybe that is failing.
This is also affecting new installs of F18... needs to be fixed ASAP. Installing: clamav-update x86_64 0.97.8-1.fc18 updates 83 k Installing for dependencies: clamav-filesystem noarch 0.97.8-1.fc18 updates 17 k Transaction Summary ========================================================================================================================================================================================== Install 1 Package (+1 Dependent package) Total download size: 100 k Installed size: 165 k Is this ok [y/N]: y Downloading Packages: (1/2): clamav-filesystem-0.97.8-1.fc18.noarch.rpm | 17 kB 00:00:00 (2/2): clamav-update-0.97.8-1.fc18.x86_64.rpm | 83 kB 00:00:00 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Total 140 kB/s | 100 kB 00:00 Running Transaction Check Running Transaction Test Transaction Test Succeeded Running Transaction Usage: groupadd [options] GROUP Options: -f, --force exit successfully if the group already exists, and cancel -g if the GID is already used -g, --gid GID use GID for the new group -h, --help display this help message and exit -K, --key KEY=VALUE override /etc/login.defs defaults -o, --non-unique allow to create groups with duplicate (non-unique) GID -p, --password PASSWORD use this encrypted password for the new group -r, --system create a system account -R, --root CHROOT_DIR directory to chroot into useradd: group 'clamupdate' does not exist Installing : clamav-filesystem-0.97.8-1.fc18.noarch 1/2 warning: user clamupdate does not exist - using root warning: group clamupdate does not exist - using root Installing : clamav-update-0.97.8-1.fc18.x86_64 2/2 /usr/bin/chown: invalid group: ‘root:clamupdate’ Verifying : clamav-filesystem-0.97.8-1.fc18.noarch 1/2 Verifying : clamav-update-0.97.8-1.fc18.x86_64 2/2 Installed: clamav-update.x86_64 0:0.97.8-1.fc18 Dependency Installed: clamav-filesystem.noarch 0:0.97.8-1.fc18
A workaround is to install an older versions which don't have the bug: yum install clamav-0.97.5-1802.fc18.x86_64 clamav-update-0.97.5-1802.fc18.x86_64 Then do a yum upgrade afterwards to get the current version. It appears the bug only affects the user/group creation process.
Still no fix?
*** This bug has been marked as a duplicate of bug 963920 ***