Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 8

changes.mady.by.user Victor Garcia-Beltran

Saved on

compared with

New Version 9

changes.mady.by.user Victor Garcia-Beltran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When setting up a reverse proxy with Apache, you might the following warning when looking at in the log file ssl_error_log (per default you should find this file the file is stored under /var/log/httpd):

Code Block
[ssl:warn] [pid xxx] AH01909: RSA certificate configured for SERVER does NOT include an ID which matches the server name

In that case, follow the instructions as described in this post (have only a look only at the answer marked with a (tick)): http://serverfault.com/questions/578061/rsa-certificate-configured-for-server-does-not-include-an-id-which-matches-the-s

...

When setting up a reverse proxy with Apache, you might the following warning when looking at in the log file ssl_error_log (per default you should find this file the file is stored under /var/log/httpd):

Code Block
[ssl:warn] [pid xxx] AH01906: RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)

...

This might happen because there is an error in the Apache configuration (either in httpd.conf, in conf.d/ssl.conf or in an any extra configuration file you would include). In order to know the reason why the service could not be started, type the following command:

...

Then you have to add the specific port you are doing the configuration for (in our case we use the port 24445 as in the example in the article JobScheduler Universal Agent - connecting via HTTPS) tot to your sistem's system SELinux configuration and allow this port for httpd as follows:

...

This will activate the debug level for SSL and Proxy, which you can then find in the following logs (per default you should find this file these file are stored under /var/log/httpd) :

  • ssl_access_log
  • ssl_error_log
  • ssl_request_log

Logging in JobScheduer Master

All informations you will see find in the JobScheduler logs is Master are located either in the order logs (under Order History) when starting an order for a job chain or in the task logs when starting a standalone job. Possible messages are described below.

...

Info

In this case you might get a HTTP error 408 - request timeout, which means, that the connection from Master to the Proxy has been established, but the redirection from the proxy to the agent can not be done.

Otherwise, the JobScheduler Master is not even reaching the proxy.

[ERROR] Z-JAVA-105 Java exception spray.httpx.UnsuccessfulResponseException: Status: 503 Service Unavailable

If an error like this is thrown in the order log or the task log:

Code Block
[ERROR]  (xxx/job1:147694) Z-JAVA-105  Java exception spray.httpx.UnsuccessfulResponseException: Status: 503 Service Unavailable
[ERROR]  (xxx/job1:147694) Body: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
[ERROR]  (xxx/job1:147694) <html><head>
[ERROR]  (xxx/job1:147694) <title>503 Service Unavailable</title>
[ERROR]  (xxx/job1:147694) </head><body>
[ERROR]  (xxx/job1:147694) <h1>Service Unavailable</h1>
[ERROR]  (xxx/job1:147694) <p>The server is temporarily unable to service your
[ERROR]  (xxx/job1:147694) request due to maintenance downtime or capacity
[ERROR]  (xxx/job1:147694) problems. Please try again later.</p>
[ERROR]  (xxx/job1:147694) </body></html>, method=CallObjectMethodA []

...