7

When installing the discovery service I receive the following issue while trying to start the service

WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
WARNING: TCP connect to localhost:9082 failed
ERROR: Unable to start service during timeframe of 60s
Please check logs and configuration files.

The service is installed correctly.

If I try to start it from the Services dialog, I get the following error

enter image description here

There is very little information in the Event Viewer, only one error

The SDL Web Discovery Service - Staging service terminated with the following service-specific error: 
Incorrect function.

There are no log files created by the service itself.

I first suspected a firewall, but have been assured the firewall is turned off on the server.

Confirmed via Resource Monitor that no other service is running on 9082

Improve this question
1
  • 4
    You mean Port 9082? Try running the Discovery Service on the command-line first using the start.ps1 PowerShell script (specifying the same port).
    – Rick Pannekoek
    May 11, 2016 at 20:12

4 Answers 4

Reset to default
6

I'd forgotten to install one of the prerequisites. It was my own fault.

Java was not installed on the Content Delivery Server.

Improve this answer
3
  • 1
    Which prerequisites are you talking about as we are also facing the same issue. Thanks
    – SumitK
    Jul 13, 2016 at 7:03
  • 1
    +1 to Sumit, am facing the same issue, would be interested to know what pre-req was missed.
    – GAG
    Jul 14, 2016 at 19:26
  • 2
    Updated my answer
    – Chris Morgan
    Jul 14, 2016 at 19:53
3

I had a similar problem and got the same initial PowerShell error message:

WARNING: TCP connect to localhost:8082 failed
WARNING: TCP connect to localhost:8082 failed
WARNING: TCP connect to localhost:8082 failed
WARNING: TCP connect to localhost:8082 failed
...
WARNING: TCP connect to localhost:8082 failed
ERROR: Unable to start service during timeframe of 60s
Please check logs and configuration files.

And the Windows Services wouldn't start.

However, my problem was caused because I didn't deploy the cd_licenses.xml file to the target (C:\SDL\Web) folder before running the quickinstall.ps1 PowerShell script.

Not the solution to your issue, Chris, but may help someone else that encounters this problem and finds your question here!

Improve this answer
1

I had issues because of following reasons.

  • Port was not opened on the server
  • Incorrect version of java
  • Lately when i unzipped my services, i forgot to unblock it from properties.
  • License was not there, or incorrect no of cpu.
Improve this answer
-2

I faced same issue and found that logback.xml file was missing some tags which was creating the problem. We used standard file and it started working.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.