PAW services hanging at "/bin/sh -c 'mkdir -p"

[gtonkin]

I had PAW up and running in my Linux CentOS environment. For some reason I cannot connect any longer. I have restarted the VM and the Admin Tool and get:

PAW_AdminTool_Restarting.PNG (23.4 KiB) Viewed 2973 times

If i run docker ps I get:

Code: Select all

CONTAINER ID                                                       IMAGE                                                     COMMAND                                                                                                                                CREATED             STATUS                              PORTS                                      NAMES
cad1133606f9b67538b35b56039d11304157531ef3605a5040137f1db692b978   pa-docker:5000/planninganalytics/admintool:1.0.25         "./start.sh"                                                                                                                           20 minutes ago      Up 20 minutes                       192.168.11.241:8888->8888/tcp              admintool
6385be7cea1613378f8ebaf17712096d7b95a07b2d34ab4a2729d6251f0d0e0d   pa-docker:5000/planninganalytics/wa-proxy:1.0.111         "/bin/sh -c 'mkdir -p ${LOG_FOLDER} && node WAProxy.js'"                                                                               4 days ago          Up 5 minutes                        1338/tcp                                   wa-proxy
206f4355a826b6295a1cb5f9776e705a221e7d5063a9800885fbec9097d36120   pa-docker:5000/planninganalytics/bss:1.0.153              "./start.sh"                                                                                                                           4 days ago          Up 5 minutes                        8082/tcp                                   bss
e844c6500d44c5192f236b4b53dc382c4a04a4921840ff72fccad1331e8c9e2a   pa-docker:5000/planninganalytics/prism-app:1.0.782        "./start.sh"                                                                                                                           4 days ago          Up 5 minutes                        9600/tcp                                   prism-app
1f6feb1391912d5df73b293e6efb7935f08c4cc19b648b6d60c05821152b9640   pa-docker:5000/planninganalytics/neo-idviz:1.0.35         "./start.sh"                                                                                                                           4 days ago          Up 5 minutes                        9060/tcp                                   neo-idviz
d9a4536d5f34181e375e7051561fc26749983ec11e5671183e7242bbfadb602f   pa-docker:5000/planninganalytics/neo-provision:1.0.29     "./start.sh"                                                                                                                           4 days ago          Up 5 minutes                        8083/tcp                                   neo-provision
0b723132d0b60f1cbee8732ffde4a248444e0f628da51f5a24e6d58c7bf55e0e   pa-docker:5000/planninganalytics/bss-init:1.0.41          "./start.sh"                                                                                                                           4 days ago          Up 6 minutes                                                                   bss-init
04d775b9ccef700d4617ce6034f1391c33044ce0aaba3b37036b40b6b1f0a252   pa-docker:5000/planninganalytics/pa-login:1.0.101         "./start.sh"                                                                                                                           4 days ago          Up 5 minutes                        9085/tcp                                   pa-login
46155587e95bd14aa837da61a289e20c371bbb1b7010b232dceb20ef58d96c65   pa-docker:5000/planninganalytics/social:0.0.155           "./start.sh"                                                                                                                           4 days ago          Up 4 minutes                        1341/tcp                                   social
00db99485938be1448c58e6c47031a5597d33fa5b3b1b41ee16de3e9fed9c34c   pa-docker:5000/planninganalytics/share-proxy:1.0.21       "/bin/sh -c 'mkdir -p \"${ShareProxyLogDir}\" && apache2ctl -D FOREGROUND'"                                                            4 days ago          Restarting (0) About a minute ago                                              share-proxy

I have tried stopping and restarting the services via the paw.sh script - the services go back to restarting with the mdkir -p
I saw a reference to /var/log/harmony - created it and gave permissions - no change

Any ideas?

[dr.nybble]

Seems that the Apache-based services are having some issue starting.
Try the command:

docker logs share-proxy

to see if that sheds light on it.
Check the permissions on the log directory in your PAW install. Probably the containers are not able to create their log folders or write to them.
Quick change to see if this is the problem: chmod -R a+rw log
Then restart the containers that are having issues.

It is worth noting that inside the container it logs to /var/log/harmony, but on the host (i.e., your Centos box) the logs are written to the log directory of your PAW install (or whatever is defined in the LOG_DIR configuration setting). Your host directory is mounted inside the container.

[gtonkin]

Thanks for the feedback dr.nybble!
What I noticed with regards to the <pawdir>/log folder is that folders and files were being created with rw------- where the owner and group were '2000'
I checked the /etc/group and /etc/passwd files and did not see any user with that uid.
I stopped the various docker services using the paw.sh stop script
Changed the permissions of <paw>/log using chmod -R 0777 log
Started the services again
Log file were now being written to but was still see Restarting - after about an hour I gave up, shutdown, took a backup of the VM I made after installing docker and re-installed PAW. This time however I created a user called pawadmin with uid=2000.
Early "hours" yet but seems to be up and running - will be playing on the front-end side and will try not to break it.

I definitely need to get to grips with how the containers work, what is running, what is being written to, what the PAW backup script does etc. etc. - feels like a big black box at the moment.