Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,045
Community Members
 
Community Events
176
Community Groups

Jira DC new node - Refused to connect

Hi All,

We have multiple servers (clustering) already configured with Jira data center version. We are adding another 3-4 nodes. I was able to successfully built the servers and added to cluster properties as well and site was working on 8080 (original site is in HTTPS and need to add new nodes to HTTPS and load balancer).

All of a sudden, starting this week.. all new nodes are not accessible on 8080 and giving error as "Refused to connect". when i try to restart the jira service using stor-jira.sh, giving below error.

org.apache.catalina.startup.Catalina stopServer
SEVERE: Could not contact [localhost:8005] (base port [8005] and offset [0]). Tomcat may not be running.
org.apache.catalina.startup.Catalina stopServer
SEVERE: Error stopping Catalina
java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:476)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:218)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:394)
at java.net.Socket.connect(Socket.java:606)
at java.net.Socket.connect(Socket.java:555)
at java.net.Socket.<init>(Socket.java:451)
at java.net.Socket.<init>(Socket.java:228)
at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:511)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:391)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:481)

The stop command failed. Attempting to signal the process to stop through OS signal.
Tomcat stopped.

Any help here would be appreciated?

 

Thanks,

Raj

1 answer

0 votes
Benjamin Community Leader Nov 28, 2022

@Rajesh ,

 

The .sh filename does not seem right. "stor-jira.sh".

 

When you stop Jira, make sure that all the java/jira services actually terminated by viewing the process list. If it's still running, then force terminate the process manually. Then run start-lira.sh.

 

-Ben 

@Benjamin using the correct filename only stop-jira.sh.

Can you help with the command using which i can verify the same.

Benjamin Community Leader Nov 30, 2022

Just run a the ps command. For example:

 

ps -ef | grep jre

ps -ef | grep jira

 

If the Jira/java process is still there, make sure to terminate it. One of the ways, is just run the kill command on the proceed id. 

I dont think any service is running.. 

Suggest an answer

Log in or Sign up to answer