Thanks for the info.
The second “docker ps -a” shows that the docker container started 15 minutes before, and exited 4 minutes before the docker ps command, with exit status 2. Exit status 2 is a general purpose error code for our product.
Please run the following to retrieve the shutdown message from the container:
docker cp solace:/var/lib/solace/diags/shutdownMessage .
Please run the following to get another log file:
docker cp solace:/usr/sw/loads/currentload/.lastRespawnsAction .
Please return those files. Thanks!
Because you are running Ubuntu, with AppArmor, try adding the following to the docker run command, to give your container more privileges
--security-opt apparmor:unconfined
Some errors related to Solace are generated by the Linux kernel in the regular log files in /var/log. Look for things that happen at the time of the exit, approximately.
Examples:
/var/log/syslog- general errors/var/log/kern.log- various kernel errors, including Out Of Memory (OOMkills) where the kernel killed the process, rather than something inside the container if it ran out of memory.
Some processes that run in our container, and might show up in log files, are:
- multipathd
- solsyslogtee
- solacedaemon
- watchdog
- dataplane
- controlplane
- smrp
- trmmanager
- msgbusadapter
- solcachemgr
Of course 10-50 lines of context before and after is always helpful.
We aren’t sure what specific errors to look for here, sorry. However, those logs should help.