· Aug 2, 2022

System Alerting and Monitoring (SAM) installation

I am trying to investigate whether the SAM component will give us metrics that we are looking for when it comes to # of messages, etc... I have IRIS 2022.1 running on Red Hat 8, but noticed that SAM was bundled as a docker-compose image. REL 8 doesn't install docker off the bat, but has podman which reading podman 3 versions and later, I should be able to call docker-compose.yml images. After installing Apache and making some modifications to docker-compose.yml, I tried executing the script after verifying podman was running and podman-compose was installed. 

I am seeing the following errors....

  • ConnectionRefusedError: [Errno 111] Connection refused
  • urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused'))
  • docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused'))
  • [1962443] Failed to execute script docker-compose

By looking at those error, it makes me think that the server needs access to the internet. Is this true? The server I am trying to install SAM on is isolated from the network so we don't risk PHI information. Can someone confirm that the server I install SAM on needs access to the outside world (internet)? Has anyone used podman to execute the docker image for SAM?



Product version: IRIS 2022.1
$ZV: IRIS for UNIX (Red Hat Enterprise Linux 8 for x86-64) 2022.1 (Build 209U) Tue May 31 2022 12:13:24 EDT
Discussion (5)2
Log in or sign up to continue

The script just calls docker-compose up.  You should be able to do podman-compose up to start SAM.  The first time it runs, it needs to download the containers (you can see what they are in the docker-compose.yaml file) if you don't already have them in your local podman cache.

During normal runtime, SAM doesn't require access to the internet.  That said, I haven't personally tested SAM without internet access.

Good luck!  Let us know how it goes.

As I mentioned to Bob in ISC Discord chat, I'm in the midst of writing a tech article on podman w/ SAM - there are a few tricks to know even beyond the container download issue you may have. Sorry for the delay on the article - switched companies in the last week or two and my ISC Developer Community account is in transition!

For that download issue, if you can grab the containers its after on another machine and upload to /tmp or wherever, podman lets you specify a local folder to source them from - podman import is the command to look at - so podman has a copy and when compose is ran, as long as the tags match it'll pull em right in!

Edit: doc reference for podman-import: