Skip to main content
commvault.com commvault.com
Solved

Unable to upload log files

  • February 14, 2023
  • 3 replies
  • 1090 views
Ken_H
Byte
Forum|alt.badge.img+15

Hello everyone,

I’ve got four support tickets open and I just realized I’m no longer able to upload log files.  I just tried to upload just the CommVault log and the job ran for 8 minutes then failed with the following:

> Error Code: [35:1193]
> Description: Failed to upload log files to web server

> [https://logs.commvault.com/webconsole].
> Source: inf-srv57, Process: sendLogFiles
> 
> Failed to upload log files to web server [https://logs.commvault.com/webconsole].
> Source: inf-srv57, Process: sendLogFiles
> 
> Failed to upload log files to web server [https://logs.commvault.com/webconsole].
> Source: inf-srv57, Process: sendLogFiles

Has anyone seen this before?  Do you have any suggestions on what to check?

Ken

Best answer by Gil S

@Ken_H 

There are a few things you can check:

  1. Can you open a browser to see if you can reach https://logs.commvault.com/webconsole to ensure that is not being blocked? 
  2. There also could be a timeout when trying to upload the logs.  Do you get the error right away or it takes a few hours?  In a previous case development suggested adding the additional setting on the CommServe CurlTimeOutInSec as documented here: http://documentation.commvault.com/additionalsetting/details?name=%22CurlTimeOutInSec%22&id=4779.  If this doesn’t work I would suggest opening a Support case with Commvault to further troubleshoot.
View original
Did this answer your question?

3 replies

G
Vaulter
Forum|alt.badge.img+6
  • Gil SVaulter
  • Vaulter
  • 13 replies
  • Answer
  • February 15, 2023

@Ken_H 

There are a few things you can check:

  1. Can you open a browser to see if you can reach https://logs.commvault.com/webconsole to ensure that is not being blocked? 
  2. There also could be a timeout when trying to upload the logs.  Do you get the error right away or it takes a few hours?  In a previous case development suggested adding the additional setting on the CommServe CurlTimeOutInSec as documented here: http://documentation.commvault.com/additionalsetting/details?name=%22CurlTimeOutInSec%22&id=4779.  If this doesn’t work I would suggest opening a Support case with Commvault to further troubleshoot.
S
1 person likes this
  • S
    Sebastien Merluzzi
Ken_H
Byte
Forum|alt.badge.img+15
  • Ken_H
  • Author
  • Byte
  • 219 replies
  • February 15, 2023

Thanks @Gil S,

I think we’ve found the problem.  From my Commserver host:

I’ve asked my network guy to take a look.

Ken

Ken_H
Byte
Forum|alt.badge.img+15
  • Ken_H
  • Author
  • Byte
  • 219 replies
  • February 15, 2023

OK, a bit of a long story that I’ll share for everyone’s information.

We recently had a problem with our telephony system that was traced to CommVault swamping our internet connection when it ran aux copy jobs to replicate backups to cloud storage.  Putting throttling on the cloud copy of the storage policy didn’t help as there were still brief periods where CommVault would flood the network.

The solution my network guy came up with was to direct CommVault internet traffic through the pipe to our DR site and then out to the internet from there.  This totally removes CommVault traffic from the primary internet connection used by email, clients accessing our web servers, and out telephony system.  Unfortunately, a side effect of this was that my CommServer lost access to https://logs.commvault.com/webconsole.

The situation has been fixed and log uploads are working normally once again. 

Thanks for the help.

Ken

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings