Skip to main content
commvault.com commvault.com

I’m trying to get a list of Jobs from the Rest API.

It was working stable for a few month and now its not working anymore. Any other query works fine.

This is what i found in the WebServer.log:

27444 40    10/20 10:09:36 40  backupeagle  - Processing gPOST] request : /Jobs : Headers : Content-Type=application/json]nAccept=application/json,application/json]nAccept-Encoding=gzip,deflate]eExpect=100-continue]eHost=127.0.0.1:81]1Content-Length=156]6SkipOldJsonConverter=true]eCVRequestRouted=true]eMS-ASPNETCORE-TOKEN=a122a259-c6b4-42d5-b3b7-97685bda87aa]aX-Original-Proto=http]ptrace-id=ws87c5dfa042cf]fX-Original-For=127.0.0.1:51335] : Parameters : (empty) : AdditionalInfofClientIPI127.0.0.1] ConsoleTypepUnknown] OperationoCV.WebServer.Controllers.Job.GetJobsListSummary (CVWebControllerJobs)] isTokenSupplied?dTrue] Usernamembackupeagle]]
27444 26    10/20 10:12:47 26  backupeagle Invoke - POST /Jobs : HTTP code 'OK'
35084 252   10/20 10:12:55 ### ### WebServerRoute::HandleRequest - Exception : The remote host closed the connection. The error code is 0x80070040.
35084 252   10/20 10:12:55 ### ### WebServerRoute::HandleRequest - Exception Stack Trace :    at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
   at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
   at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async)
   at CVInfoMgmtService.RemoteWebServiceHelperExtensions.CopyTo(HttpWebResponse source, HttpResponse target)
   at CVInfoMgmtService.WebServerRoute.HandleRequest()

I already increased the maxMemory settings for the tomcat but it didn’t helped.

What can i check to find the problem?

 

Hi @Bjoern_SRZC , hope all is well!

I checked our internal database and only found a few instances of this Stack trace error.

The solutions all involve the .NET framework (note each bullet is a separate solution):

  • For this server just make sure the Windows patching is up to date and make sure theres no pending reboots. Check to see the last time it was rebooted and if possible run Windows Updates and retry the recall from the web console. Found numourous .NET Framework errors coiciding with the errors in the webconsole.
  • Performed a repair of the web console on the separate web server. This required uninstalling .Net from the windows control panel only and then launching the repair which installed the necessary .Net components for FR25 web console client. The only components reinstalled were the .net hosting (x64) and .Net core (x64), no x86 binaries were reinstalled. 

Let me know if either of these work for you.

Unfortunately i can’t perform any major changes on the system because it’s a customer production server.

We checked the Windows Updates and there was no pending reboot.

The customer performed an update to version 11.24.21. and now the error message has changed.

4588  365   11/26 10:19:11 365 backupeagle  - Processing cpost] request : /Jobs : Headers :eContent-Type=application/json]oAccept=application/json,application/json]oAccept-Encoding=gzip,deflate]dHost=DE00SRVMGT106R2.emea.dir:81].Content-Length=156]gSkipOldJsonConverter=true]eMS-ASPNETCORE-TOKEN=581dd248-3bb4-485e-8535-a6b5a8c1e12b]8X-Original-Proto=http]ttrace-id=wsfc8bd7d97a6e]7X-Original-For=127.0.0.1:59811]1WEBSERVERCORE-FLAG=true] : Parameters : (empty) : AdditionalInfooClientIPC10.137.37.21] ConsoleTypesUnknown] OperationpCV.WebServer.Controllers.Job.GetJobsListSummary (CVWebControllerJobs)] isTokenSupplied?uTrue] UsernameUbackupeagle]]

 

4588  365   11/26 10:29:11 365 backupeagle ExecuteSelect - exception : source Core .Net SqlClient Data Provider, message : Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding., System.Linq.Enumerable+<TakeWhileIterator>d__216`1rSystem.Char]. inner exception : source , message : The wait operation timed out., stack is unavailable]

 

Should i increase the timeout and where can i change this setting?

Any idea?

Hi @Bjoern_SRZC , apologies for the delay (I was out of the office last week).

I would suggest opening a case at this point because of the complexity of the issue, but also due to being unable to implement potential solutions.

The timeout MIGHT be the answer, or it might be a band-aid at best.  I’d rather find a nice, solid, reliable solution for you.

Can you share the case number once created?

Hi @Bjoern_SRZC hope all is well.

Following up to see if you ended up creating a case for this one (I searched, but am not seeing anything under your name).

Thanks!

@Bjoern_SRZC , following up on this thread.  Did you set the timeout and if so, did it resolve the issue?  I don’t see any tickets in your name at this time.

Reply


Terms & ConditionsCookie settings