There are two situations where it is possible that you can avoid this error by increasing the heap space yourself: If your problem is occurring in a job, you can use the java_options attribute to increase the heap space at the job level. It would, however, be interesting for us to know whether this error occurs with one of the jobs the SOS GmbH has provided or whether it occurs with a custom job? -If a main JobScheduler process is being allocated too little heap space, you can read how to increase...
There are two situations where it is possible that you can avoid this error by increasing the heap space yourself: If your problem is occurring in a job, you can use the java_options attribute to increase the heap space at the job level. It would, however, be interesting for us to know whether this error occurs with one of the jobs the SOS GmbH has provided or whether it occurs with a custom job? -If a main JobScheduler process is being allocated too little heap space, you can read how to increase...
Hello, I have another problem on my docker installation when I run a task, locally or using a local docker I use the same configuration, I have no problem sending the mail, but on sending using docker on a portainer I am no longer locally, I cannot resolve smtp.office365.com. Here is my configuration with my factory.ini. 2021-09-06 20:02:18.520Z [info] Task sos/sendMail/sendMail:718 - Protocol starts in /mnt/jobscheduler/data/scheduler/logs/task.sos,sendMail,sendMail.log 2021-09-06 20:02:18.547Z...
up
Nobody sees where my problem could come from?
Yes, I understood that I had to use postman for my POST request, my question should be more in the sense that I would like to access this kind of url, https://www.sos-berlin.com/JOC/1.13.3/raml-doc/JOC-API, The interface is intuitive while for my part I use Experimental API which has a not great interface.
Here are my container restart logs. At the start we can see that the port is available. Here are also my different containers present on my 3 clusters but none operate port 40444. Node 1: https://i.imgur.com/HpxX6Wq.png Node 2: https://i.imgur.com/aoSSAQY.png Node 3: https://i.imgur.com/BSxNvFH.png
Here are my container restart logs. At the start we can see that the port is available
https://i.imgur.com/HnoQIlg.png No matter how long I wait, at the beginning of the construction of the container, it tells me that the port 40444 is available but at the end of its build I come across the error telling me that it is not available, I am, however, only one instance operating the port.
Bug close [Double topics]
Bug close this topic
I also have a local docker where I test my modifications first and I do not come across this error case.
Hello, I encounter a difficulty when I create a stack on Portainer, it is created, but my problem comes with the creation of the "jobscheduler-master" container I come across an error which is Binding to TCP port /0.0.0.0: 40444 failed. Port is possibly in use and not available. The error will be more visible on the screenshot below. https://i.imgur.com/vUU6M8Q.png No problem on my local docker, but on my Portainer I absolutely do not understand I am only my Master: 40444 / Cockpit: 4446 and my database...
Hello, I encounter a difficulty when I create a stack on Portainer, it is created, but my problem comes with the creation of the "jobscheduler-master" container I come across an error which is Binding to TCP port /0.0.0.0: 40444 failed. Port is possibly in use and not available. The error will be more visible on the screenshot below. https://i.imgur.com/vUU6M8Q.png No problem on my local docker, but on my Portainer I absolutely do not understand I am only my Master: 40444 / Cockpit: 4446 and my database...
Yes, I understood that I had to use postman for my POST request, my question should be more in the sense that I would like to access this kind of url, https://www.sos-berlin.com/JOC/1.13.3 / raml-doc / JOC-API, The interface is intuitive while for my part I use Experimental API which has a not great interface.
up
Hello, as said in the title, I am having a problem when I try to access the REST API. My installation works correctly, I am in version 1.13.9, no worries except on this part. I followed the instructions in the documentation: https://kb.sos-berlin.com/display/PKB/JobScheduler+-+REST+Web+Service My problem occurs when I try to access already basic URL joc / api / security / login I get the result that you can see on the screenshot: 405 Method not allowed. https://i.imgur.com/1SbijCS.png If a person...
There are two situations where it is possible that you can avoid this error by increasing the heap space yourself: If your problem is occurring in a job, you can use the java_options attribute to increase the heap space at the job level. It would, however, be interesting for us to know whether this error occurs with one of the jobs the SOS GmbH has provided or whether it occurs with a custom job? If a main JobScheduler process is being allocated too little heap space, you can read how to increase...
Bug
There are two situations where it is possible that you can avoid this error by increasing the heap space yourself: If your problem is occurring in a job, you can use the java_options attribute to increase the heap space at the job level. It would, however, be interesting for us to know whether this error occurs with one of the jobs the SOS GmbH has provided or whether it occurs with a custom job? -If a main JobScheduler process is being allocated too little heap space, you can read how to increase...
There are two situations where it is possible that you can avoid this error by increasing the heap space yourself: If your problem is occurring in a job, you can use the java_options attribute to increase the heap space at the job level. It would, however, be interesting for us to know whether this error occurs with one of the jobs the SOS GmbH has provided or whether it occurs with a custom job? -If a main JobScheduler process is being allocated too little heap space, you can read how to increase...
Okay, I forgot one thing just to go to services.msc and change the login account on the SOS JobScheduler service.
Hello, New JobScheduler user, I currently have no problem with my installation, except on only a part, I followed the documentation to install JobScheduler locally on my Windows System. There where my concern is, it is at the level of the execution of a job or I provided it with a remote file to execute in sh format. sh autopgsqlbackup.sh / usr / bin / sh no such file or directory So I thought to myself that maybe I had a problem with the route or the environment variable, but on my session cmd it...