12-05-2018 07:26 AM
i'm having an issue with uploading the fie after collection. i've tried configuring the proxy settings via web GUI -- Appliance Configuration button. Receive the following error:
Appliance Configuration Summary :
✗ Timezone configuration failed to execute
✗ NTP Server configuration failed to execute null
✗ DNS address configuration failed to execute, null
? Hostname was not provided
✗ Proxy Server configuration failed
I logged into server and under root account issued service adminshell restt. then retried the proxy settings, same error.
Solved! Go to Solution.
12-06-2018 08:52 AM
Can you check the inventory you are viewing currently (top left of portal under company name). You may need to switch to the new inventory you created with the new entitlement. I see your instance has received 2 uploads from a new appliance on 12/5.
12-05-2018 07:40 AM
Hey demiller,
What error are you getting when attempting to upload? Is the collector required to traverse a proxy to get out to the internet? You can configure the proxy on the CLI via admin user with conf proxy <ipaddr/host> <port> <user> <passwd>. User and password are optional.
Can you also share output of curl --tlsv1.2 https://concsoweb-prd.cisco.com/HeadEndWebAppServlet/ -v -k as root user?
12-05-2018 08:17 AM
Command output below:
[root@dns5 collectorlogin]# curl --tlsv1.2 https://concsoweb-prd.cisco.com/HeadEndWebAppServlet/ -v -k
* About to connect() to proxy 10.174.34.10 port 3128 (#0)
* Trying 10.174.34.10... connected
* Connected to 10.174.34.10 (10.174.34.10) port 3128 (#0)
* Establish HTTP proxy tunnel to concsoweb-prd.cisco.com:443
> CONNECT concsoweb-prd.cisco.com:443 HTTP/1.1
> Host: concsoweb-prd.cisco.com:443
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
<
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* warning: ignoring value of ssl.verifyhost
* skipping SSL peer certificate verification
* SSL connection using TLS_RSA_WITH_3DES_EDE_CBC_SHA
* Server certificate:
* subject: CN=sora.cisco.com,O="Cisco Systems, Inc.",L=San Jose,ST=CA,C=US
* start date: Nov 30 15:18:43 2017 GMT
* expire date: Nov 30 15:28:00 2019 GMT
* common name: sora.cisco.com
* issuer: CN=HydrantID SSL ICA G2,O=HydrantID (Avalanche Cloud Corporation),C=US
> GET /HeadEndWebAppServlet/ HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: concsoweb-prd.cisco.com
> Accept: */*
>
< HTTP/1.1 302 Found
< Date: Wed, 05 Dec 2018 16:15:45 GMT
< Server: Apache
< Set-Cookie: ObSSOCookie=loggedoutcontinue; path=/; domain=.cisco.com
< Location: https://sso.cisco.com/obrareq.cgi?wh%3DConn-Prod%20wu%3D%2FHeadEndWebAppServlet%2F%20wo%3D1%20rh%3Dhttps%3A%2F%2Fconcsoweb-prd.cisco.com%20ru%3D%252FHeadEndWebAppServlet%252F
< Content-Length: 358
< Cache-Control: max-age=0
< Expires: Wed, 05 Dec 2018 16:15:45 GMT
< Content-Type: text/html; charset=iso-8859-1
<
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="https://sso.cisco.com/obrareq.cgi?wh%3DConn-Prod%20wu%3D%2FHeadEndWebAppServlet%2F%20wo%3D1%20rh%3Dhttps%3A%2F%2Fconcsoweb-prd.cisco.com%20ru%3D%252FHeadEndWebAppServlet%252F">here</a>.</p>
</body></html>
* Connection #0 to host 10.174.34.10 left intact
* Closing connection #0
[root@dns5 collectorlogin]#
12-05-2018 09:47 AM
Also , please check whether you are able to login to adminshell using "su admin" after the restart.
Thanks
12-05-2018 12:32 PM
Are your uploads still failing? Please share screenshot of error message if so. The output of the curl looks good.
12-06-2018 08:42 AM
According to the job logs it was successful, but upload processing in the Cisco Services Connections gui shows the last successful upload from the old 2.4 collector.
12-06-2018 08:52 AM
Can you check the inventory you are viewing currently (top left of portal under company name). You may need to switch to the new inventory you created with the new entitlement. I see your instance has received 2 uploads from a new appliance on 12/5.
12-07-2018 06:20 AM
That worked, thanks for all the assistance.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide