dpa container bug

[hernandanielg]

What's the issue?
Restarting dpa container causes forever service restarts
This causes high writes IOPS to stdout

How to reproduce
Launch a DPA container
docker run -i -t -p 8123:8123 -p 8124:8124 --name=dpainstance solarwinds/dpa:latest

Check container logs
docker logs dpainstance

Restart the container
docker restart dpainstance

Check container logs again
docker logs dpainstance

You'll see a lot of service restarts

2017-08-22 15:03:27,825 INFO success: dpa entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-22 15:03:27,825 INFO exited: dpa (exit status 127; not expected)
2017-08-22 15:03:27,828 INFO spawned: 'dpa' with pid 24767
2017-08-22 15:03:27,833 INFO success: dpa entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-22 15:03:27,833 INFO exited: dpa (exit status 127; not expected)
2017-08-22 15:03:27,835 INFO spawned: 'dpa' with pid 24768
2017-08-22 15:03:27,839 INFO success: dpa entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-22 15:03:27,839 INFO exited: dpa (exit status 127; not expected)
2017-08-22 15:03:27,841 INFO spawned: 'dpa' with pid 24769

Root cause

This line keeps replacing /usr/local/dpa for target version over and over again after a restart

containers/dpa/run.sh

Line 10 in ec4fe49

sed -i "s,$DPA_SOURCE_HOME,$DPA_TARGET_HOME,g" /home/docker/dpa/supervisord.conf

Follow these steps

• Spin up a new dpa container docker run -d solarwinds/dpa
• Change log level to debug like this docker exec 3a3e39753e31 sed -i 's,info,debug,g' /home/docker/dpa/supervisord.conf

After a restart docker restart 3a3e39753e31 and check logs docker logs 3a3e39753e31

2017-08-29 14:09:26,922 INFO spawned: 'dpa' with pid 1442
2017-08-29 14:09:26,924 DEBG 'dpa' stdout output:
nohup: failed to run command '/usr/local/dpa_10_2_579_10_2_579/startup.sh': No such file or directory

2017-08-29 14:09:26,924 INFO success: dpa entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-29 14:09:26,924 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139723234350216 for <Subprocess at 139723234340520 with name dpa in state RUNNING> (stdout)>
2017-08-29 14:09:26,924 INFO exited: dpa (exit status 127; not expected)
2017-08-29 14:09:26,924 DEBG received SIGCLD indicating a child quit
2017-08-29 14:09:26,925 INFO spawned: 'dpa' with pid 1443
2017-08-29 14:09:26,927 DEBG 'dpa' stdout output:
nohup: failed to run command '/usr/local/dpa_10_2_579_10_2_579/startup.sh': No such file or directory

2017-08-29 14:09:26,927 INFO success: dpa entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-29 14:09:26,927 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139723234350216 for <Subprocess at 139723234340520 with name dpa in state RUNNING> (stdout)>
2017-08-29 14:09:26,927 INFO exited: dpa (exit status 127; not expected)
2017-08-29 14:09:26,927 DEBG received SIGCLD indicating a child quit

After a 2nd restart docker restart 3a3e39753e31 and check logs again docker logs 3a3e39753e31

2017-08-29 14:09:28,130 INFO spawned: 'dpa' with pid 1827
2017-08-29 14:09:28,133 DEBG 'dpa' stdout output:
nohup: failed to run command '/usr/local/dpa_10_2_579_10_2_579/startup.sh': No such file or directory

2017-08-29 14:09:28,133 INFO success: dpa entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-29 14:09:28,133 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139723234350216 for <Subprocess at 139723234340520 with name dpa in state RUNNING> (stdout)>
2017-08-29 14:09:28,133 INFO exited: dpa (exit status 127; not expected)
2017-08-29 14:09:28,133 DEBG received SIGCLD indicating a child quit
2017-08-29 14:09:28,134 INFO spawned: 'dpa' with pid 1828
2017-08-29 14:09:28,136 DEBG 'dpa' stdout output:
nohup: failed to run command '/usr/local/dpa_10_2_579_10_2_579/startup.sh': No such file or directory

2017-08-29 14:09:28,136 INFO success: dpa entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-08-29 14:09:28,136 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139723234350216 for <Subprocess at 139723234340520 with name dpa in state RUNNING> (stdout)>
2017-08-29 14:09:28,136 INFO exited: dpa (exit status 127; not expected)
2017-08-29 14:09:28,137 DEBG received SIGCLD indicating a child quit

You can see it keeps replacing /usr/local/dpa with /usr/local/dpa_10_2_579 over and over again.

[isathish]

ERROR [2/3] RUN yum clean all && yum install -y jre wget && wget --progress=dot:mega http://downloads.solarwinds.com/solarwinds/Release/DatabasePeformanceAnalyzer-DPA/2021.1.775/SolarWinds-DPA-2021.1.775-64bit.tar.gz -O /dpa.t 1.8s