FortiSOAR Knowledge Base
FortiSOAR: Security Orchestration and Response software provides innovative case management, automation, and orchestration. It pulls together all of an organization's tools, helps unify operations, and reduce alert fatigue, context switching, and the mean time to respond to incidents.
ycho
Staff
Staff
Article Id 286270
Description This article describes how to fix an issue where, when attempting to install the Connector after installing the FortiMonitor Agent on the FortiSOAR, an error message appears that causes the installation to fail.
Scope FortiSOAR v7.x.
Solution

Error messages:

 

sudo yum install cyops-connector-splunk
FortiMonitor Repository 900 B/s | 346 B 00:00
Errors during downloading metadata for repository 'fortimonitor.repo':
- Status code: 404 for https://repo.fortimonitor.com:443/rpm8-stable/repodata/repomd.xml (IP: xx.xxx.xxx.xx)
Error: Failed to download metadata for repo 'fortimonitor.repo': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

DNF log:

 

yum install cyops-connector-splunk

2023-11-14T10:50:08+0000 DDEBUG Installroot: /

2023-11-14T10:50:08+0000 DDEBUG Releasever: 8

2023-11-14T10:50:08+0000 DEBUG cachedir: /var/cache/dnf

2023-11-14T10:50:08+0000 DDEBUG Base command: install

2023-11-14T10:50:08+0000 DDEBUG Extra commands: ['install', 'cyops-connector-splunk']

2023-11-14T10:50:08+0000 DEBUG User-Agent: constructed: 'libdnf (Rocky Linux 8.8; generic; Linux.x86_64)'

2023-11-14T10:50:08+0000 DEBUG repo: downloading from remote: fortimonitor.repo

2023-11-14T10:50:09+0000 DEBUG error: Status code: 404 for https://repo.fortimonitor.com:443/rpm8-stable/repodata/repomd.xml (IP: xx.xxx.xxx.xx) (https://repo.fortimonitor.com:443/rpm8-stable/repodata/repomd.xml).

2023-11-14T10:50:09+0000 WARNING Errors during downloading metadata for repository 'fortimonitor.repo':

  - Status code: 404 for https://repo.fortimonitor.com:443/rpm8-stable/repodata/repomd.xml (IP: xx.xxx.xxx.xx)

2023-11-14T10:50:09+0000 DDEBUG Cleaning up.

2023-11-14T10:50:09+0000 DDEBUG Plugins were unloaded.

2023-11-14T10:50:09+0000 SUBDEBUG

Traceback (most recent call last):

  File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 573, in load

    ret = self._repo.load()

  File "/usr/lib64/python3.6/site-packages/libdnf/repo.py", line 397, in load

    return _repo.Repo_load(self)

libdnf._error.Error: Failed to download metadata for repo 'fortimonitor.repo': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

 

During handling of the above exception, another exception occurred:

 

Traceback (most recent call last):

  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 67, in main

    return _main(base, args, cli_class, option_parser_class)

  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 106, in _main

    return cli_run(cli, base)

  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 122, in cli_run

    cli.run()

  File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 1038, in run

    self._process_demands()

  File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 741, in _process_demands

    load_available_repos=self.demands.available_repos)

  File "/usr/lib/python3.6/site-packages/dnf/base.py", line 405, in fill_sack

    self._add_repo_to_sack(r)

  File "/usr/lib/python3.6/site-packages/dnf/base.py", line 140, in _add_repo_to_sack

    repo.load()

  File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 580, in load

    raise dnf.exceptions.RepoError(str(e))

dnf.exceptions.RepoError: Failed to download metadata for repo 'fortimonitor.repo': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

 

Take the following steps to eliminate possible causes of the error:

  1. Verify that the Fortimonitor.repo Repository URL is correct.
  2. Check if there is a problem with the network connection.
  3. Check if port 443 is blocked or if the corresponding Repository IP address is blocked by the Firewall.
  4. Check if there is a problem with the Fortimonitor.repo mirror server.

 

Upon reviewing the logs in this particular example, the 4th cause was determined to be responsible.

Upon changing the baseurl of fortimonitor.repo as follows, the installation was successful.

 

vi fortimonitor.repo(Default settings of fortimonitor.repo)

[fortimonitor.repo]

name=FortiMonitor Repository

baseurl=http://repo.fortimonitor.com/rpm8-stable/

enabled=1

gpgcheck=1

gpgkey=https://repo.fortimonitor.com/fortimonitor.pub

 

The baseurl was changed to:

 

cat fortimonitor.repo

[fortimonitor.repo]

name=FortiMonitor Repository

baseurl=https://rocky-linux-asia-south1.production.gcp.mirrors.ctrliq.cloud/pub/rocky//8.8/BaseOS/x86_64/os/

enabled=1

gpgcheck=1

gpgkey=https://repo.fortimonitor.com/fortimonitor.pub

 

Contributors