Kent W

I am trying to run a job and it completes, but then it errors at the end.. I am using the Docker 13.3.9 implementation of JSMaster and JOC and the regular agent. Nothing changed from the deployment setup by Andreas on the SOS-Berlin page. Containerized MySQL 5.7 I do have a dockervolume (followed the steps on the SOS Berlin' guide as well) and they are all on the same network. I did a search and it seems this error hasn't come up on the discussions before? Impartial Log: 2021-05-19 11:24:11.175Z...

Hi Andreas, Thank you for that info and it makes sense. But I do have a question regarding the DB Host address value, if you could please comment. Upon setup, I noticed the host address key value in the batch .xml files could not be localhost or 127.0.0.1 for example, I was forced to use the machine's IP address. To do a sanity check, I could use the mysql client on command line and perform $mysql --host=localhost or $mysql --host=127.0.0.1 and I could connect. But re-reading your response, I suspect...

EDIT: Fixed it....turns out it really did need the network flags. A bit strange but I guess a sure fireway to force it to work. The Master became reachable once I put all three containers in a user defined network I followed Andreas's Docker Build and Deploy steps here: https://kb.sos-berlin.com/display/PKB/JobScheduler+Master+for+Docker I only changed - Dockerfile build reference to 13.3.9 from 13.3.3 - Removed network flags for JS since I am deploying this as a single node I have a Master, the...

I followed Andreas's Docker Build and Deploy steps here: https://kb.sos-berlin.com/display/PKB/JobScheduler+Master+for+Docker I only changed - Dockerfile build reference to 13.3.9 from 13.3.3 - Removed network flags for JS since I am deploying this as a single node I have a Master, the JOC cockpit, and a MySQL 5.7 database. Everything installs fine on the Master and the mysql tables are written/made. The containers are running. Upon logging in with JOC, I see the error....i'm a bit confused because...

I followed Andreas Docker Build and Deploy steps here: https://kb.sos-berlin.com/display/PKB/JobScheduler+Master+for+Docker I only changed - Dockerfile build reference to 13.3.9 from 13.3.3 - Removed network flags for JS since I am deploying this as a single node I have a Master, the JOC cockpit, and a MySQL 5.7 database. Everything installs fine on the Master and the mysql tables are written/made. The containers are running. Upon logging in with JOC, I see the error....i'm a bit confused because...

I followed Andreas Docker Build and Deploy steps here: https://kb.sos-berlin.com/display/PKB/JobScheduler+Master+for+Docker I only changed - Dockerfile build reference to 13.3.9 from 13.3.3 - Removed network flags for JS since I am deploying this as a single node I have a Master, the JOC cockpit, and a MySQL 5.7 database. Everything installs fine on the Master and the mysql tables are written/made. The containers are running. Upon logging in with JOC, I see the error....i'm a bit confused because...

EDIT: Fixed it by putting the machine private IP into the host address key instead of using localhost or 127.0.0.1 Edit: In my logs, I am getting a A database connection error occurs: Could not connect to address=(host=localhost)(port=3308)(type=master) : Connection refused (Connection refused) I am using the docker build and deploy files from the SOS Berlin page, only modified the docker file to use 13.3.9 and removed the network flag options. I am using the following mysql docker-compose, I read...

Edit: In my logs, I am getting a A database connection error occurs: Could not connect to address=(host=localhost)(port=3308)(type=master) : Connection refused (Connection refused) I am using the docker build and deploy files from the SOS Berlin page, only modified the docker file to use 13.3.9 and removed the network flag options. I am using the following mysql docker-compose, I read there's issues with 8 so I am using 5.7 I set the no root password and I can successfully connect to the mySQL via...