Unable to start the Solace pubsub in podman

vase18

I am trying to start the pusub in podman, but when I run the below command the container is in running state and I am unable to access the console in browser.

Command:

podman run -u 1000:1000 --ulimit nofile=524288:524288 -p 1943:1943 -p 55555:55555 --shm-size=1g --env username_admin_globalaccesslevel=admin --env username_admin_pass
word=admin --name=solace --net slirp4netns:port_handler=slirp4netns -v ~/podman/solace:/var/lib/solace:Z docker.io/solace/solace-pubsub-standard

Logs:

Starting PubSub+ Software Event Broker Container: Sun Apr 14 06:17:31 UTC 2024
Setting umask to 077
SolOS Version: soltr_10.7.1.51
2024-04-14T06:17:34.952+00:00 <syslog.info> 379f5cf66a53 rsyslogd: [origin software="rsyslogd" swVersion="8.2402.0" x-pid="160" x-info="https://www.rsyslog.com"] start
2024-04-14T06:17:35.949+00:00 <local6.info> 379f5cf66a53 appuser[158]: rsyslog startup
2024-04-14T06:17:36.972+00:00 <local0.info> 379f5cf66a53 appuser: EXTERN_SCRIPT  INFO: Log redirection enabled, beginning playback of startup log buffer
2024-04-14T06:17:36.987+00:00 <local0.info> 379f5cf66a53 appuser: EXTERN_SCRIPT  INFO: /usr/sw/var/soltr_10.7.1.51/db/dbBaseline does not exist, generating from confd template
2024-04-14T06:17:37.007+00:00 <local0.info> 379f5cf66a53 appuser: EXTERN_SCRIPT  INFO: repairDatabase.py: no database to process
2024-04-14T06:17:37.020+00:00 <local0.info> 379f5cf66a53 appuser: EXTERN_SCRIPT  INFO: Finished playback of log buffer
2024-04-14T06:17:37.035+00:00 <local0.info> 379f5cf66a53 appuser: EXTERN_SCRIPT  INFO: Updating dbBaseline with dynamic instance metadata
2024-04-14T06:17:37.221+00:00 <local0.info> 379f5cf66a53 appuser: EXTERN_SCRIPT  INFO: Generating SSH key
ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
2024-04-14T06:17:37.409+00:00 <local0.info> 379f5cf66a53 appuser: EXTERN_SCRIPT  INFO: Starting solace process
2024-04-14T06:17:38.109+00:00 <local0.info> 379f5cf66a53 appuser: EXTERN_SCRIPT  INFO: Launching solacedaemon: /usr/sw/loads/soltr_10.7.1.51/bin/solacedaemon --vmr -z -f /var/lib/solace/config/SolaceStartup.txt -r -1
File: /
Size: 18              Blocks: 0          IO Block: 4096   directory
Device: 53h/83d Inode: 1482782     Links: 1
Access: (0555/dr-xr-xr-x)  Uid: (    0/ appuser)   Gid: (    0/    root)
Access: 2024-04-14 06:17:42.222114439 +0000
Modify: 2024-04-14 06:17:31.844012298 +0000
Change: 2024-04-14 06:17:34.127034767 +0000
Birth: 2024-04-14 06:17:31.844012298 +0000
2024-04-14T06:17:47.433+00:00 <local0.warning> 379f5cf66a53 appuser[1]: /usr/sw                        main.cpp:759                          (SOLDAEMON    - 0x00000000) main(0)@solacedaemon                          WARN     Determining p
latform type: [  OK  ]
2024-04-14T06:17:47.462+00:00 <local0.warning> 379f5cf66a53 appuser[1]: /usr/sw                        main.cpp:759                          (SOLDAEMON    - 0x00000000) main(0)@solacedaemon                          WARN     Generating li
cense file: [  OK  ]
2024-04-14T06:17:47.578+00:00 <local0.warning> 379f5cf66a53 appuser[1]: /usr/sw                        main.cpp:759                          (SOLDAEMON    - 0x00000000) main(0)@solacedaemon                          WARN     Running pre-s
tartup checks: [  OK  ]
unknownEarlyBirdLogPrefix: /opt/sbox/loadbuild/jenkins/slave/workspace/pubsubplus_git_10.7.1/solcbr/dataplane/sw/assuredDelivery/common/include/adCmnRuntime.hpp:104 WARN IOV_MAX is 1024

After this no logs are printing and the container is running.
When I stop the container getting the below log:

consul: no process found
consul: no process found

Please help on this issue!!!

pkondrat

Hi @vase18,

It looks like you have mapped port 1943 (for HTTPS access to the PubSub+ Manager) through but, you have not configured a server certificate. Try mapping through port 8080 and accessing the Manager via HTTP or configure a server certificate. I think either of those will get you going.

Best Regards,

Paul

pkondrat

Hi @vase18,

It looks like you have mapped port 1943 (for HTTPS access to the PubSub+ Manager) through but, you have not configured a server certificate. Try mapping through port 8080 and accessing the Manager via HTTP or configure a server certificate. I think either of those will get you going.

Best Regards,

Paul