After a few day jira stoped

[serg ivanov]

Jira on premise version 7.10.1

Works for a while (a couple days!) and after our leads starting to fill it with tasks it stops. Http 404 error(.

Deployed on Ubuntu 16.04 with nginx (https proxy), here conf file

server {

    listen       443 default ssl;

    server_name  217.74.43.163;

    access_log  off;

    ssl on;

    ssl_certificate /etc/nginx/certs/server.cert;

    ssl_certificate_key /etc/nginx/certs/server.key;

    location /jira {

            #rewrite ^/jira(.*) /$1 break;

            proxy_set_header Host $host;

            proxy_set_header X-Real-IP $remote_addr;

            proxy_set_header X-Forwarded-Proto https;

            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

            proxy_pass http://127.0.0.1:8080/jira;

    }

    location /conf {

            #rewrite ^/conf(.*) /$1 break;

            proxy_set_header Host $host;

            proxy_set_header X-Real-IP $remote_addr;

            proxy_set_header X-Forwarded-Proto https;

            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

            proxy_pass http://127.0.0.1:8090/conf;

    }

    location / {

            root /var/www/Y;

    }

}

In server.xml use nginx proxying connector:

        <Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="60000" enableLookups="false"

                   maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"

                   acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"

                   proxyName="217.74.43.163" proxyPort="443"/>

And also setup path: <Context path="/jira" ….

Our guess – gadget plugin. Because when jira works (a day ago) there were some info messages that jira couldnot connect to gadget or smth like this.

The last attempt was to get dashboard: /secure/Dashboard.jspa. After this jira out of order, 404 error. Always(. Jira restart and server restart did not help(

Please, help!

Here is atlassian-jira.log (last records):

2018-06-20 16:25:21,435 http-nio-8080-exec-2 ERROR Serega 972x297x3 1naw7aa 217.74.47.6,127.0.0.1 /secure/Dashboard.jspa [c.a.g.r.internal.http.HttpClientFetcher] Unable to perform a request to: https://217.74.43.163/jira/rest/gadgets/1.0/g/messagebundle/ru_RU/gadget.common%2Cgadget.activity.stream

org.apache.http.conn.ConnectTimeoutException: Connect to 217.74.43.163:443 [/217.74.43.163] failed: Connection timed out

                at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:157)

                at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)

                at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)

                at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)

                at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)

                at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)

                at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)

                               ...  and more

2018-06-20 16:25:21,450 http-nio-8080-exec-2 ERROR Serega 972x297x3 1naw7aa 217.74.47.6,127.0.0.1 /secure/Dashboard.jspa [c.a.j.web.filters.CommittedResponseHtmlErrorRecoveryFilter] Exception occurred after HTTP response was already committed: Cannot create a session after the response has been committed

2018-06-20 16:25:21,484 http-nio-8080-exec-2 ERROR Serega 972x297x3 1naw7aa 217.74.47.6,127.0.0.1 /secure/Dashboard.jspa [c.a.j.web.servlet.InternalServerErrorServlet] {errorId=3967a852-22b7-453a-a22a-78d12dec495a, interpretedMsg=, cause=java.lang.IllegalStateException: Cannot create a session after the response has been committed, stacktrace=java.lang.IllegalStateException: Cannot create a session after the response has been committed

                at org.apache.catalina.connector.Request.doGetSession(Request.java:2953) [catalina.jar:8.5.6]

                at org.apache.catalina.connector.Request.getSession(Request.java:2367) [catalina.jar:8.5.6]

                at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:896) [catalina.jar:8.5.6]

                at com.atlassian.plugin.servlet.PluginHttpRequestWrapper.getSession(PluginHttpRequestWrapper.java:122) [atlassian-plugins-servlet-4.5.1.jar:?]

                at com.atlassian.plugin.servlet.PluginHttpRequestWrapper.getSession(PluginHttpRequestWrapper.java:122) [atlassian-plugins-servlet-4.5.1.jar:?]

                at com.atlassian.plugin.servlet.PluginHttpRequestWrapper.getSession(PluginHttpRequestWrapper.java:122) [atlassian-plugins-servlet-4.5.1.jar:?]

                at .. and more

    , referer=Unknown, servletErrorMessage=Cannot create a session after the response has been committed}

By the way, confluence work fine.

[Timothy · Accepted solution]

Jira restart and server restart did not help

This should have allowed you to get back into your Jira.

• Make sure Jira is stopped
• Clear out your logs
• Start Jira
• Check what is the error that stops Jira from starting

If there are no errors, then you can do a:

curl -LO http://127.0.0.1:8080/jira

to check if its really up or not.

[serg ivanov]

Hi, did it!

in browser still 404 error.

from atlassian-jira-security.log:

2018-06-21 09:17:42,426 JIRA-Bootstrap JIRA 7.10.1 build: 710002 started. You can now access JIRA through your web browser.

and from atlassian-jira.log

2018-06-21 09:18:57,794 HealthCheck:thread-4 ERROR [c.a.t.j.healthcheck.support.GadgetFeedUrlHealthCheck] An error occurred when performing the Gadget feed URL healthcheck
org.apache.http.conn.ConnectTimeoutException: Connect to 217.74.43.163:443 [/217.74.43.163] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)

...

[serg ivanov]

After some tomcat tuning it successufully started and its work!

But still couldnot get access to dashboards: /jira/secure/Dashboard.jspa

217.74.47.6,127.0.0.1 /secure/Dashboard.jspa [c.a.g.r.internal.http.HttpClientFetcher] Unable to perform a request to: https://217.74.43.163/jira/rest/gadgets/1.0/g/messagebundle/und/gadget.common%2Cgadget.issuetable%2Cgadget.assignedtome%2Cgadget.issuetable.common
org.apache.http.conn.ConnectTimeoutException: Connect to 217.74.43.163:443 [/217.74.43.163] failed: Connection timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:157)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)

...

[serg ivanov]

and this question also solved: by default datahoster did not provide the access from local host to public interface