Solace not running with Docker 4.3

Options
karthikv
karthikv Member Posts: 6

Hello Experts,

I updated the Docker to latest version 4.3, and then suddenly solace stops working with "Determining platform type: [ FAIL ]"

`08T10:09:49.334+00:00 <local0.warning> c9eb454fa901 appuser[1]: /usr/sw main.cpp:1007 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Child terminated with failure status: command: '$SOLENV_ORIG_CURRENTLOAD_REALPATH/scripts/post -a -f /var/lib/solace/config/sol-platform-audit.json' PID: 161 status: 512 sigRxd: 0

2021-12-08T10:09:49.334+00:00 <local0.warning> c9eb454fa901 appuser[1]: /usr/sw main.cpp:754 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Determining platform type: [ FAIL ]

2021-12-08T10:09:49.415+00:00 <local0.info> c9eb454fa901 appuser[172]: /usr/sw/loads/soltr_9.8.1.35/scripts/vmr-solredswitch:11 WARN Running vmr-solredswitch

2021-12-08T10:09:49.422+00:00 <local0.warning> c9eb454fa901 appuser[1]: /usr/sw main.cpp:754 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Monitoring SolOS processes: [ OK ]

2021-12-08T10:09:49.429+00:00 <local0.warning> c9eb454fa901 appuser[1]: /usr/sw Generated_commonReturnCodes.cpp:135 (BASE - 0x00000000) main(0)@solacedaemon WARN Unknown exit value 1, defaulting it to 'fail'.

2021-12-08T10:09:49.429+00:00 <local0.warning> c9eb454fa901 appuser[1]: /usr/sw main.cpp:1094 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Child terminated with failure status: command: 'pkill -P $PPID dataplane-linux' PID: 174 rc: fail status: 256 sigRxd: 0

2021-12-08T10:09:49.442+00:00 <local0.warning> c9eb454fa901 appuser[1]: /usr/sw main.cpp:3542 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Syncing filesystem before shutdown ...

2021-12-08T10:09:49.448+00:00 <local0.warning> c9eb454fa901 appuser[1]: /usr/sw main.cpp:3547 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Shutting down router

2021-12-08T10:09:49.448+00:00 <local0.err> c9eb454fa901 appuser[1]: /usr/sw main.cpp:3526 (SOLDAEMON - 0x00000001) main(0)@solacedaemon ERROR ######## System shutdown complete (Version 9.8.1.35) ########`

Does any one have any suggestions ?.

Regards,
Karthik

Best Answers

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 541 admin
    #2 Answer ✓
    Options

    Hi @karthikv I checked with some R&D staff and they said you'll to upgrade the broker to SolOS version 9.10 or greater. Something related to this new version of Docker Desktop on Windows, requires cgroups v2, and support for that was released SolOS 9.10.

  • karthikv
    karthikv Member Posts: 6
    #3 Answer ✓
    Options

    Hello @Aaron , Thanks for the response.

    https://hub.docker.com/_/solace-pubsub-standard -> 9.11.0.9 worked for me, none of the lower releases mentioned there worked.

    Regards,
    Karthik

Answers

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 541 admin
    #4 Answer ✓
    Options

    Hi @karthikv I checked with some R&D staff and they said you'll to upgrade the broker to SolOS version 9.10 or greater. Something related to this new version of Docker Desktop on Windows, requires cgroups v2, and support for that was released SolOS 9.10.

  • karthikv
    karthikv Member Posts: 6
    #5 Answer ✓
    Options

    Hello @Aaron , Thanks for the response.

    https://hub.docker.com/_/solace-pubsub-standard -> 9.11.0.9 worked for me, none of the lower releases mentioned there worked.

    Regards,
    Karthik

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 541 admin
    Options

    Good to know. And actually, I made an error above: cgroups v2 support was added in 9.11 (not 9.10), so that totally makes sense why that version worked for you.

  • Tripti
    Tripti Member Posts: 8
    Options

    Hello, @Aaron I am facing the above-mentioned issue with docker v3.6 and Solace -> 9.9.0.28 and 9.12.0.15 (even intermediate tags). Has the support for docker v3.6 totally stopped?
    The error is as follows -
    `2022-01-07T17:54:36.534+00:00 <local0.warning> one-solace-network appuser[1]: /usr/sw main.cpp:1005 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Child terminated with failure status: command: '$SOLENV_ORIG_CURRENTLOAD_REALPATH/scripts/post -a -f /var/lib/solace/config/sol-platform-audit.json' PID: 167 status: 512 sigRxd: 0

    2022-01-07T17:54:36.534+00:00 <local0.warning> one-solace-network appuser[1]: /usr/sw main.cpp:752 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Determining platform type: [ FAIL ]

    2022-01-07T17:54:36.597+00:00 <local0.info> one-solace-network appuser[225]: /usr/sw/loads/soltr_9.12.0.15/scripts/vmr-solredswitch:11 WARN Running vmr-solredswitch

    2022-01-07T17:54:36.602+00:00 <local0.warning> one-solace-network appuser[1]: /usr/sw main.cpp:752 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Monitoring SolOS processes: [ OK ]

    2022-01-07T17:54:36.610+00:00 <local0.warning> one-solace-network appuser[1]: /usr/sw Generated_commonReturnCodes.cpp:135 (BASE - 0x00000000) main(0)@solacedaemon WARN Unknown exit value 1, defaulting it to 'fail'.

    2022-01-07T17:54:36.610+00:00 <local0.warning> one-solace-network appuser[1]: /usr/sw main.cpp:1092 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Child terminated with failure status: command: 'pkill -P $PPID dataplane-linux' PID: 227 rc: fail status: 256 sigRxd: 0

    2022-01-07T17:54:36.619+00:00 <local0.warning> one-solace-network appuser[1]: /usr/sw main.cpp:3540 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Syncing filesystem before shutdown ...

    2022-01-07T17:54:36.622+00:00 <local0.warning> one-solace-network appuser[1]: /usr/sw main.cpp:3545 (SOLDAEMON - 0x00000000) main(0)@solacedaemon WARN Shutting down router

    2022-01-07T17:54:36.622+00:00 <local0.err> one-solace-network appuser[1]: /usr/sw main.cpp:3524 (SOLDAEMON - 0x00000001) main(0)@solacedaemon ERROR ######## System shutdown complete (Version 9.12.0.15) ########`