Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Gadgets problem

Mathieu Lebougre
Contributor
January 2, 2020

Good morning,


The server that hosts the solution is outsourced.
At the moment I access the software from a public IP. We can also access it from the VPN in ip LAN.
When I access the application from the IP LAN I don't encounter the problem.

Do you have more information about this problem?

Thank you in advance for your help

 

Capture.PNGCapture1.PNG

2 answers

1 accepted

0 votes
Answer accepted
Tinker Fadoua
Community Champion
January 2, 2020

Good morning @Mathieu Lebougre 

In general it is a server issue (DNS).

You will have to contact the system admin or network admin.

There is nothing you can do at the application level.

Did you just start encountering this problem? If yes, what was the most resent change made in the server?

Erreurs des liens -> Status 503 (https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503)

Best,

Fadoua

Mathieu Lebougre
Contributor
January 2, 2020

Hello,

Thank you for your response. Indeed the error does not appear on another network. On the other hand, the gadgets still do not load. Do you have an idea?

Mathieu Lebougre
Contributor
January 2, 2020

At times I manage to load them but here's how they appearCapture3.PNG

Tinker Fadoua
Community Champion
January 2, 2020

Yes broken Gadget Title. Typical error when there is DNS issue.

Are you able to access the Marketplace from Jira @Mathieu Lebougre ?

Mathieu Lebougre
Contributor
January 2, 2020

Yes: Capture4.PNG

Tinker Fadoua
Community Champion
January 2, 2020

Is there anything in particular that changed? Or did you always have this problem?

Mathieu Lebougre
Contributor
January 2, 2020

The problem has been present since we migrated the solution to another server.

Tinker Fadoua
Community Champion
January 2, 2020

Where are you hosting Jira? On an internal server or AWS?

Mathieu Lebougre
Contributor
January 2, 2020

A server at CentOS at OVH. It used to be a CENTOS before as well and it worked very well.

Tinker Fadoua
Community Champion
January 2, 2020

I am not a System Admin, but may be something wasn't configured properly.

I am more than sure that when I have issues with Gadgets it is a Network issue.

What do you see on the logs? Not the application log but the Catalina one

Like Mathieu Lebougre likes this
Mathieu Lebougre
Contributor
January 2, 2020

I'm not in the office to watch that anymore. I'll look at it tomorrow. Yeah, I think there's a network problem, too. We have a VPN in place between our infrastructure and the OVH server. So we have an IP LAN to access the application in addition to the public IP. When I go through the VPN (in LAN) I do have access to the gadgets. Really strange.

Mathieu Lebougre
Contributor
January 2, 2020

Are the gadgets linked to a port to be authorized?

Tinker Fadoua
Community Champion
January 2, 2020

Ok please let me know once you check your logs.

Bonne chance et à bientôt 

Mathieu Lebougre
Contributor
January 2, 2020

Merci beaucoup pour le temps passé à m'aider ! A demain.

Tinker Fadoua
Community Champion
January 2, 2020

Avec plaisir! J'attendrai votre message @Mathieu Lebougre 

Concernant votre question: Notre Ingénieur AWS avait mentionné une fois SSL resolution qui peut être derriere ce problème de Gadget. Quant il l'a résolu je n'ai plus eu ce problème. Malheureusement je n'ai aucune idée du travail qui a été fait derriere les coulisses 😉

Mathieu Lebougre
Contributor
January 3, 2020

Bonjour Fadoua,

 

Voici l'erreur qui remonte tous les jours dans le catalina.out :

03-Jan-2020 08:45:37.861 WARNING [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8080-exec-19] (id=[39]) has been active for [126,536] milliseconds (since [1/3/20 8:43 AM]) to serve the same request for [http://51.   .  .   :8080/rest/config/1.0/directoryitems/local.json?_=1578037324923] and may be stuck (configured threshold for this StuckThreadDetectionValve is [120] seconds). There is/are [3] thread(s) in total that are monitored by this Valve and may be stuck.
java.lang.Throwable
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
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)
etc..

 

Tinker Fadoua
Community Champion
January 3, 2020

Bonjour @Mathieu Lebougre ,

Quand vous lisez un "log", il faut toujours se concentrer sur les "Errors" erreurs, warning est juste une alerte.

Je vous suggère de demander à votre ingénieur des réseaux ou un administrateur des systèmes comment vous pouvez remédier à ce problème car il est au dessus des compétences d'un administrateur des applications.

Sachez que je suis la pour vous assister de mon mieux. Si jamais on vous dit qu'il n'y a aucun problème de leur coté(meme si j'en douterai). Je vous aiderai à ouvrir un ticket avec Atlassian.

A+

Fadoua

Like Mathieu Lebougre likes this
Mathieu Lebougre
Contributor
January 3, 2020

Merci pour votre retour !

Je viens de voir avec lui. Pourriez vous me confirmer les ports à autoriser pour Jira ? J'en ai peut être oublié un ?

Merci

Tinker Fadoua
Community Champion
January 3, 2020

En general Atlassian suggère d'utiliser le port externe  8080 for Jira 

Tomcat Default 8000

https://confluence.atlassian.com/kb/ports-used-by-atlassian-applications-960136309.html

Mathieu Lebougre
Contributor
January 3, 2020

Je vois que celui utilisé pour le Marketplace c'est 443... C'est du TCP ? Je crois que c'est celui la qu'il manque

Tinker Fadoua
Community Champion
January 3, 2020

443 c'est pour SSL et oui il se peut que ce soit celui qui cree tout ses problèmes.

Mathieu Lebougre
Contributor
January 3, 2020

Pourtant le Marketplace fonctionne ? De la part de l'admin réseau, il y a quelque chose d'autre a faire ? A part autoriser ces ports ?

Tinker Fadoua
Community Champion
January 3, 2020

Est ce que vous pouvez télécharger du Marketplace sans problèmes?

Vous avez mentionne que vous accédez a Jira en utilisant un autre réseau sans problèmes. Qu'elle est la difference de configuration entre les deux réseaux? Est ce qu'il y a un "Firewall", Proxy?

Mathieu Lebougre
Contributor
January 3, 2020

Il y a un Firewall depuis l'IP publique mais pas depuis le LAN (via VPN)

Donc via VPN tout fonctionne correctement mais en passant par l'ip publique (et donc le firewall) le problème est présent..

Tinker Fadoua
Community Champion
January 3, 2020

Ok ca explique maintenant le problème.

Est ce que ca peut attendre jusqu'a ce soir? Je vous promets de chercher des articles qui vous seront utiles.

Like Mathieu Lebougre likes this
Mathieu Lebougre
Contributor
January 3, 2020

Oui ca peut attendre ce soir ! Merci encore pour votre aide

Tinker Fadoua
Community Champion
January 3, 2020

C'est un plaisir de vous assister!

Je vous enverrai des liens ce soir.

A+

Fadoua

Mathieu Lebougre
Contributor
January 3, 2020
Mathieu Lebougre
Contributor
January 4, 2020

Super, merci ! Je regarde ca à partir de Lundi.
Bon week end !

lingmaaki
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 9, 2020

A 503 Service Unavailable Error is an HTTP response status code indicating that your web server operates properly, but it can't temporarily handle the request at the moment. This error happen for a wide variety of reasons. Normally, this error can be due to a temporary overloading or maintenance being performed on the server and it is resolved after a period of time or once another thread has been released by web-server application. The subsequent points serve as a possible fix, aimed toward resolving the potential root causes.

Reload (Refresh) the page
Scan for Malware
Visiting the website later
Contact server admin

0 votes
Tinker Fadoua
Community Champion
January 2, 2020

Merci beaucoup d'avoir accepté ma réponse!

Suggest an answer

Log in or Sign up to answer