On my production server (Apache+ Tomcat8), after some number of request to servlet, tomcat halts and I cannot access to production server with SSH, and when I try to access web site it gives me connection time out. In catalina.out I cannot find any trace or error log. What are ways to debug this issue?
Thanks.
Related
It's my first time to publish an ASP.Net Core 2.1 so I'm not quite sure what I'm missing. When I try to just run the API from VS2017, I can access all Requests(CRUD) through POSTMAN or even directly the browser by localhost:1111/api/MyRoute.
After I deployed it in IIS and tried mywebsite.com/api/MyRoute, the request shows correct details of the request in Developer Console > Network but shows error in the console of ERR_CONNECTION_RESET 200 (OK)
I also tried Attaching the process in VS2017 through w3wp.exe still doesn't hit the Get Request
What did I miss?
Are your deploying to your local IIS or remote IIS? it seems more like a connection issue, I would suggest that you call your webapi through ip address instead of domain. ERR_CONNECTION_RESET 200 indicate the connection to your server failed, it may result from DNS failure
For ASP.NET project MSBuild gives some files in E:\Build such as:
TestProjectA.deploy.cmd
TestProjectA.SetParameters.xml
TestProjectA.SourceManifest.xml
TestProjectA.zip
To deploy from Windows 7 to Windows Server 2008 R2 (IIS 7)
Executing command gives following error message:
Command
C:\Program Files\IIS\Microsoft Web Deploy V3>msdeploy.exe -verb:sync -source:contentPath='E:\Build' -dest:contentPath='ra/files-to-pub',ComputerName="https://<IP>:8172/msdeploy.axd?site=ra",UserName='DEV\Administrator',Password='MyPassword',AuthType='Basic' -enableRule:DoNotDeleteRule -whatif -allowUntrusted
Error Message:
Info: Using ID 'd1bbee7a-e940-4be1-b41d-1847b3e7022d' for connections to the remote server.
Error Code: ERROR_COULD_NOT_CONNECT_TO_REMOTESVC
More Information: Could not connect to the remote computer ("[IP ADDRESS]") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer.
Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.
Error: The remote server returned an error: (550).
Error count: 1
Given link suggest to do:
Ping the remote machine. *STATUS-OK
The msdepsvc or wmsvc service is started on the remote server. *STATUS-OK
Firewall is not blocking incoming connections of your ports on the destination. If it used the default installation, then it would be 80 for msdepsvc and 8172 for wmsvc. *STATUS-OK
Both of service are running at target server:
Web Management Services
Web Deployment Agent Service
What can do now to solve it?
If you have checked the basic stuff like
Credentials are correct
Website name is spelt correctly everywhere
And have tried the steps mentioned here
And it still didn't work then may I suggest troubleshooting using Web Management Service Failed Request Tracing
This might be too late, but for others checking this error. Verify the Site name too. IE, Default Web Site/SiteDeploy (or whatever you call it)
k
We are having Tridion 2011 SP1 environment up and running with one CMS server and one CDS server. Today we installated new CMS server and pointed it to existing SQL Server database. We used same MTSUser, same database credentials. Installation went smooth, but when we try to access CMS server we are getting 9 error as below.
1) The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
2) Loading list of languages failed.
at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
3) Loading list of locales failed.
at System.Net.HttpWebRequest.GetResponse() at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
How to troubleshoot ?
We are able to access SQL Server database using ODBC.
Use a tool like Fiddler to watch HTTP traffic when you load the Tridion GUI, and find the requests that are failing.
From here you could use WCFTestClient to get more specific details on the errors and the available bindings.
My guess is IIS Configuration.
I would like to suggest you to think a bit out of box. As errors are more specific to WCF service. so configure tracing and see what things are going wrong with the webservice.
This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). After all I will again recommend you to see server logs for more details. I or someone else can better help you , if you can share logs here.
Is the Tcm Service Host (windows service) running?
Trying to get MSDeploy working and it "hangs" on the MSDeployPublish task.
It says
"Start Web Deploy Publish the Application/package to
https://myserver:8172/msdeloy.axd?site=mysite ... Starting Web
deployment task from source: archiveDir(path to archive) to
Destination: auto()."
And it just stops. It will sit like this for 30 minutes, or more I suppose, before I kill the process.
On the server it is deploying to, in this case myserver, there is an error from MSDeploy that reads:
ERROR_SERIALIZER_ALREADY_DISPOSED - An error occurred on a callback
thread. These errors are usually benign and are handled automatically.
The details are below: System.Web.HttpException: The remote host
closed the connection. The error code is 0x800704CD. at
System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32
result, Boolean throwOnDisconnect) at
System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush() at
System.Web.HttpResponse.Flush(Boolean finalFlush) at
System.IO.BufferedStream.FlushWrite() at
System.IO.BufferedStream.Flush() at
System.Xml.XmlTextWriter.Flush() at
Microsoft.Web.Deployment.TraceEventStreamSerializer.WriteKeepAliveEvent()
No other error logs or messages that I can find.
I can hit the url to msdeploy, for example if I go to https://myserver:8172/msdeloy.axd in a browser I get the self signed certificate warning and then get prompted for credentials, so it appears MSDeploy on the server is up and running.
The server (myserver) is Windows 2008R2 with IIS7.
What really sucks, is if I REBOOT the server that I am deploying to (myserver) IT WORKS!
Any ideas on what is going on here?
Just went through the same thing. This is the response from my hosting company that resolved the issue.
"While investigating, we found that the connection attempt was hanging on our end. The Web Management Service needed to be stopped to edit settings for the management service but upon attempting to stop this service, it would not shut down so we force killed the process and after starting it back up (no changes were made to settings), Visual Studio is making connections with Web Deploy without issue."
I have been trying to set-up my recently reimaged workstation for working with one of our ASP.Net applications that consists of a ASP.Net website and some C# Web Services. I can successfully start debug instances of each the services and web site. However as soon as the site attempts to connect to and use one of the web services I get the following exception.
No connection could be made because
the target machine actively refused it
127.0.0.1:80
Description: An unhandled exception occurred during
the execution of the current web
request. Please review the stack trace
for more information about the error
and where it originated in the code.
Exception Details:
System.Net.Sockets.SocketException: No
connection could be made because the
target machine actively refused it
127.0.0.1:80
So it looks like my PC is refusing the connection to itself. My first thought was to to check the windows firewall is disabled and it is disabled (the service is not running). I do not think IT has any other firewall software running on this PC, so I am a bit stumped as to what else could be causing the connection to be refused.
Silly question, but do you actually have IIS installed on your machine? When you run debug instances of your applications, it's running outside of IIS. If you're running debug instances of both your site and your service, your service probably isn't running on port 80.
Double check your IIS installation...and then set up your service running on port 80 properly.