# ESET install error on Rocky 8.9 version **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [June 2, 2024, 3:49pm UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380 "2024-06-02T15:49:13Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![jeevanal](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@jeevanal](https://forums.rockylinux.org/u/jeevanal)\ **Post date:** [June 2, 2024, 3:49pm UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380/1 "2024-06-02T15:49:14Z")
Rocky 8.9 local repo is created and the ESET is being installed from Rocky client servers. Perl packages exists on the repo server but still getting the below error. Could someone help on this. ESET installation is failing for Rocky8.9 withe the below error: No available modular metadata for modular package ‘perl-4:5.32.1-472.module+el8.8.0+1134+a197a740.x86\_64’, it cannot be installed on the system No available modular metadata for modular package ‘perl-Algorithm-Diff-1.1903-10.module+el8.6.0+879+823e3012.noarch’, it cannot be installed on the system No available modular metadata for modular package ‘perl-Archive-Tar-2.38-3.module+el8.6.0+879+823e3012.noarch’, it cannot be installed on the system ESET Version 10.2.41.0 for Linux ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [June 2, 2024, 3:51pm UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380/2 "2024-06-02T15:51:36Z")
It appears you synced our repos and ran createrepo. This destroys modular metadata and will cause issues like these. I recommend properly doing a reposync keeping all metadata available. Note: Rocky Linux 8.9 is no linger supported. ---
**Author:** ![jeevanal](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@jeevanal](https://forums.rockylinux.org/u/jeevanal)\ **Post date:** [June 2, 2024, 4:15pm UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380/3 "2024-06-02T16:15:16Z")
Process that we followed to create localrepo was downloading the Rocky 8.9 ISO file and created repo for Appstream and BaseOS. Is there any other process like using reposync commands for Rocky as well similar to Centos. If so could you please provide the details of reposync commands. To create Rocky 8 repo server, we have downloaded the Rocky 8.9 ISO and copied Appstream and baseos folders to /var/www/html and then created repodata there. We have used this localrepo URL on repo clients to get updates. We are using 9.4 for all other roles. Rocky 8.9 is used for 1 role which is product dependent. ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [June 2, 2024, 4:28pm UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380/4 "2024-06-02T16:28:25Z")
The correct way to sync any repository is to maintain its repodata. Do not run createrepo. When syncing from our mirror: ```auto # rocky 8 dnf reposync -g --delete -p /path/to/baseos --download-metadata --repoid=baseos dnf reposync -g --delete -p /path/to/appstream --download-metadata --repoid=appstream dnf reposync -g --delete -p /path/to/powertools --download-metadata --repoid=powertools dnf reposync -g --delete -p /path/to/extras --download-metadata --repoid=extras # rocky 9 dnf reposync -g --delete -p /path/to/baseos --download-metadata --repoid=baseos dnf reposync -g --delete -p /path/to/appstream --download-metadata --repoid=appstream dnf reposync -g --delete -p /path/to/crb --download-metadata --repoid=crb dnf reposync -g --delete -p /path/to/extras --download-metadata --repoid=extras ``` When syncing from an ISO. ```auto mount -o loop /path/to/iso /mnt rsync -vrlptDSH --delete /mnt/AppStream/ AppStream rsync -vrlptDSH --delete /mnt/BaseOS/ BaseOS ``` ---
**Author:** ![jeevanal](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@jeevanal](https://forums.rockylinux.org/u/jeevanal)\ **Post date:** [June 2, 2024, 5:55pm UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380/5 "2024-06-02T17:55:27Z")
Thanks a lot for the above details. I have tried reposync commands on reposerver as below. dnf reposync -g --delete -p /var/www/html/Rocky8/OS/ --download-metadata --repoid=BaseOS dnf reposync -g --delete -p /var/www/html/Rocky8/OS/ --download-metadata --repoid=AppStream dnf reposync -g --delete -p /var/www/html/Rocky8/OS/ --download-metadata --repoid=extras drwxr-xr-x 4 root root 38 Jun 2 13:10 AppStream drwxr-xr-x 4 root root 38 Jun 2 13:05 BaseOS drwxr-xr-x 4 root root 56 Jun 2 13:25 extras Below is the error when doing yum update ROCKY-BaseOS 116 MB/s | 2.2 MB 00:00 ROCKY-AppStream 143 MB/s | 7.9 MB 00:00 ROCKY-extras 3.9 MB/s | 15 kB 00:00 Modular dependency problems: Problem 1: conflicting requests - nothing provides module(platform:el8) needed by module container-tools:rhel8:8090020240429144526:e7857ab1.x86\_64 from @modulefailsafe Problem 2: conflicting requests - nothing provides module(platform:el8) needed by module llvm-toolset:rhel8:8090020240110182619:b46abd14.x86\_64 from @modulefailsafe Problem 3: conflicting requests - nothing provides module(platform:el8) needed by module perl:5.26:8050020211109115414:b4937e53.x86\_64 from @modulefailsafe Problem 4: conflicting requests - nothing provides module(platform:el8) needed by module perl-DBD-MySQL:4.046:8090020231016064114:0aad9023.x86\_64 from @modulefailsafe Problem 5: conflicting requests - nothing provides module(platform:el8) needed by module perl-DBD-SQLite:1.58:8090020231016064426:0aad9023.x86\_64 from @modulefailsafe Problem 6: conflicting requests - nothing provides module(platform:el8) needed by module perl-DBI:1.641:8090020231016030935:88fd4976.x86\_64 from @modulefailsafe Problem 7: conflicting requests - nothing provides module(platform:el8) needed by module perl-IO-Socket-SSL:2.066:8090020231016070024:88fd4976.x86\_64 from @modulefailsafe Problem 8: conflicting requests - nothing provides module(platform:el8) needed by module perl-libwww-perl:6.34:8090020231016070052:8af8375c.x86\_64 from @modulefailsafe Problem 9: conflicting requests - nothing provides module(platform:el8) needed by module python36:3.6:8090020231214163110:ed68999d.x86\_64 from @modulefailsafe Problem 10: conflicting requests - nothing provides module(platform:el8) needed by module virt:rhel:8090020240110182221:b46abd14.x86\_64 from @modulefailsafe Error: ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [June 2, 2024, 6:09pm UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380/6 "2024-06-02T18:09:39Z")
You are getting that error because your repos are configured to point to your local ones already that have the wrong metadata. You should use the repo ids that are default in our rocky-repos package. Look for them here: - Rocky 8: Rocky-BaseOS.repo, Rocky-AppStream.repo, Rocky-Extras.repo - Rocky 9: rocky.repo, rocky-extras.repo You will find the ID’s are the same as the ones in my example above. ---
**Author:** ![jeevanal](https://avatars.discourse-cdn.com/v4/letter/j/258eb7/32.png) [@jeevanal](https://forums.rockylinux.org/u/jeevanal)\ **Post date:** [June 4, 2024, 11:31am UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380/7 "2024-06-04T11:31:53Z")
Thanks for your inputs. That resolved my issue when syncing from files with ISO using the below method. mount -o loop /path/to/iso /mnt rsync -vrlptDSH --delete /mnt/AppStream/ AppStream rsync -vrlptDSH --delete /mnt/BaseOS/ BaseOS ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [August 3, 2024, 11:32am UTC](https://forums.rockylinux.org/t/eset-install-error-on-rocky-8-9-version/14380/8 "2024-08-03T11:32:10Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.