faulting module name: libcurl-wintls.dll

I need a solution

Hi!

I have just upgraded my SEPM and some clients from 14.0.3876.1100 to 14.2.3332.1000. I noticed that most of my windows 2012 R2 and windows 2008 servers either having system freezed or SEP clients crashed with the following application error in the event logs:

faulting application name: ccSvcHst.exe, version: 13.4.0.26
faulting module name: libcurl-wintls.dll, version 7.64.0.0
Exception Code: 0xc0000005
fault offset: 0x00000b3ac

I had opened a Support Case with symantec, but still no solution..

Does anyone out there having the same issue? how did you manage to resolve?

Regards,
Isaac

0

Related:

Re: ESRS Network Connectivity (NAT)

Hi,

Sometimes the network check is reporting incorrect results. A meaningful test from the VM itself would be a

curl -v -k https://esrs3.emc.com

curl -v -k https://esrs3-core.emc.com

if these two work (the second will probably end in a SSL handshake failure, but SSL handshake will at least be started), please follow fix 1 in KB article 503235 to be able to skip the network check. There will be an option in the GUI to skip the network check in a future version, unfortunately not in 3.32 yet.

If provisioning does not work, indicating a real issue with the network connectivity, please open a SR with support to get assistance.

Regards

Frank

Related:

Re: Networker 9.1.x with RestApi DELETE option

Hi

Has any one worked with RESTAPI + CURL + Networker , getting HTTP error while using it for DELETE other options like GET and POST works with no issues

root@Server:LAB:~> /usr/bin/curl -k -X DELETE -H “Content-Type: application/json” -H “Authorization:Basic YWRt=” -d ‘{ “hostname” : “nmcserver.nwielab.net” }’ “https://networkerserver.net:9090/nwrestapi/v2/global/clients” -k -1 | python -mjson.tool

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 469 0 425 100 44 3987 412 –:–:– –:–:– –:–:– 4009

{

message”: “HTTP 405 Method Not Allowed”,

“status”: {

“code”: 405,

“codeClass”: “Client Error”,

“reasonPhrase”: “Method Not Allowed”

},

“timestamp”: “2017-05-10T15:35:55-04:00”,

“userAgentRequest”: {

“contentLength”: 44,

“headers”: [

{

“name”: “Accept”,

“value”: “*/*”

},

{

“name”: “Content-Type”,

“value”: “application/json”

}

],

“method”: “DELETE”,

“url”: “https://networkerserver.net:9090/nwrestapi/v2/global/clients“

},

“version”: “9.1.1.0.Build.140”

}

Related:

Re: Unable to obtain backup status from vProxy after 5 attempts

Hello guys,

Some backups are failing with the following error :

164541 10/01/2017 03:37:45 AM nsrvproxy_save NSR error “vmname”: Unable to obtain backup status from vProxy after 5 attempts, failing the backup: Received an HTTP code: 404, libCURL message: “Operation timed out after 1800618 milliseconds with 0 out of -1 bytes received”, vProxy message: “Error received from vProxy =”-404: Resource not found: c92f57e4-8c25-4cc4-a081-562b8c39e4dd”.

“, url: “https://vproxy:9090/api/v1/BackupVmSessions/c92f57e4-8c25-4cc4-a081-562b8c39e4dd“, body: ” “.

156203 10/01/2017 03:37:51 AM nsrvproxy_save NSR warning “vmname”: Unable to download vProxy Session log into file ‘/nsr/logs/policy/WF/Policy/358869-vmname-2017-10-1-3-37-45.log’: Possible wrong vProxy hostname or port, resource path not found. Received an HTTP code: 404, libCURL message: “Operation timed out after 1800618 milliseconds with 0 out of -1 bytes received”, url: “https://vproxy:9090/api/v1/BackupVmSessions/c92f57e4-8c25-4cc4-a081-562b8c39e4dd/log“.

164546 10/01/2017 03:37:51 AM nsrvproxy_save NSR error vmname: Backup failed.

146000 10/01/2017 03:37:51 AM nsrvproxy_save SYSTEM critical The size of proxied data written has not been set.

142169 10/01/2017 03:37:51 AM nsrvproxy_save NSR warning Save-set ID ‘399523354’ (client ‘vcenter’: save-set ‘vm:5034b93a-c988-b3ef-a823-8a650f5a5421:vcenter’) is aborted.

0 10/01/2017 03:37:51 AM nsrmmd NSR error 10/01/17 03:37:51 ddirasm: save set vm:5034b93a-c988-b3ef-a823-8a650f5a5421:vcenter for client vcenter was aborted and removed from volume

Looks like it’s a timeout issue but the vProxy is not overloaded and is handling other backups successfully.

In this config, i have :

3 vProxys for around 150 VMs

Max 30 VMs per group

Parallelism set to 15

timeout set to 60

1 hour delay between each VMs group

Any idea what could cause this ?

thanks

Julien

Related:

Backup jobs

Article Number: 487208 Article Version: 2 Article Type: Break Fix



ViPR Controller Controller 3.0

ViPR 3.0

Scheduled backup jobs run as expected but are failing to upload file to remote location. This occurred after the upgrade from 2.4 to 3.0

From audit log:

17:20 UTC 2016 auth root SUCCESS “Authenticate root succeed.”

Fri Jul 01 13:21:57 UTC 2016 backup FAILURE Upload Vipr backup (name=vipr-3.0.0.0.814-3-20160630170000) failure on vipr3 of site Default Site,Reason=(curl: (21) QUOT command failed with 550

47:22 UTC 2016 backup FAILURE Upload Vipr backup (name=vipr-3.0.0.0.814-3-20160629201740, vipr-3.0.0.0.814-3-20160630170000) failure on vipr2 of site Default Site,Reason=(Cannot find target backup set ‘vipr-3.0.0.0.814-3-20160629201740’., curl: (9) Server denied you to change to the given directory)

The user has full read and write access to the FTP site but it can’t rename the file.

Edit the FTP share for that user to have “append” rights to the FTP location.

Edit the users default permissions of READ and WRITE on files on the directory to allow “APPEND”, which now allows the rename of the file to occur.

Related:

ECS:Unable to add new authentication provider via UI; Error 30026 (http: 503): Service is busy. The Data services system is busy. Please try again later

Article Number: 489611 Article Version: 3 Article Type: Break Fix



ECS Appliance

Unable to add new authentication provider via UI.

Gets the following error message when attempting to add it:

Error 30026 (http: 503): Service is busy. The Data services system is busy. Please try again later.

Vnest key in transition caused DT unready result in adding authentication provider failed.



1. Check /opt/emc/caspian/fabric/agent/services/object/main/log/provisionsvc.log* around the issue time-stamp with keyword REQUEST_AUTHPROVIDER on all nodes.

In this case, found error below, which indicates cannot reach remote VDC :

016-09-19 10:46:00,672 [pool-69-thread-1] ERROR ResourceClient.java (line 322) request id 0a7e0c8e:1569e3f4366:22:2404, command type REQUEST_AUTHPROVIDER_CREATE failed with error code ERROR_TIMEOUT and message 'failed to get enough responses voters [urn:storageos:VirtualDataCenterData:xxxxxxx-4385-4484-b13a-1cd0cb159c94, urn:storageos:VirtualDataCenterData:xxxxxxx-0e80-490d-82bc-093895c796b9], responded [urn:storageos:VirtualDataCenterData:xxxxxxx-4385-4484-b13a-1cd0cb159c94], failed to reach [urn:storageos:VirtualDataCenterData:xxxxxx-0e80-490d-82bc-093895c796b9], type AUTH_PROVIDER_KEY, request 0a7e0c8e:1569e3f4366:22:2404' 

2. Check DT status, found unready

#curl http://`hostname -i`:9101/stats/dt/DTInitStat/ | grep “<unready_dt_num>”

curl http://`hostname -i`:9101/stats/dt/DTInitStat/ | grep "<unready_dt_num>" % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed100 188 100 188 0 0 12 0 0:00:15 0:00:15 --:--:-- 48<?xml version="1.0" encoding="UTF-8" standalone="yes"?><result><entry><total_dt_num>2048</total_dt_num><unready_dt_num>0</unready_dt_num><unknown_dt_num>0</unknown_dt_num></entry></result> 

3. Check vnest-error.log, if there is “vnest key in transition”

Example:

# viprexec -i 'grep -i "key in transition" /opt/emc/caspian/fabric/agent/services/object/main/log/vnest-error.log' Output from host : 192.168.219.1 com.emc.storageos.data.object.exception.ObjectControllerException: key in transition, request 0a7e9511:156c26c97a7:13a:23533 ip 10.126.149.xx:9204 

4. If you see this issue please open a SR with ECS support, reference this KB and post the output of the logs you found.

Related:

7022736: Event and Alert dashboards are not loading when the sentinel is upgraded to 8.2

This document (7022736) is provided subject to the disclaimer at the end of this document.

Environment

Sentinel 8.2

Situation

Update to Some of the Sentinel dashboards that leverage Kibana do not load after you upgrade to Sentinel 8.2.

The exception called “mapper[hits] cannot convert from long to integer” is being thrown.

Resolution

To fix this issue, you must manually delete the existing Kibana index file and recreate a new Kibana index file using the following instructions:
1)Back up your existing data. Copy the Kibana index to a file with a different name, .kibana-temp using the following commands:
curl -XPOST “http://<elasticsearch ip>:9200/_reindex” -H ‘Content-Type: application/json’ -d’
{
“source”: {
“index”: “.kibana”
},
“dest”: {
“index”: “.kibana-temp”
}
}’
2)Stop the Sentinel server using the command:
rcsentinel stop.
3)Start the Security Intelligence database using the following command:
rcsentinel startSIdb.
4)Delete the existing .kibana index from ElasticSearch using the following command:
curl -XDELETE <elasticsearch ip>:9200/.kibana
5)Delete the configuration details of the existing kibana index:

1)Go to /<sentinel_install_directory>/opt/novell/sentinel/3rdparty/kibana/config.

2)Open kibana.yml.

3)Delete the following:

pid.file: /test/home/novell/sentinel/kibana.pid
server.host: 127.0.0.1
kibana.defaultAppId: dashboard/Event-Summary-Dashboard
server.port: 5601
server.basePath: /visual-analytics/proxy
elasticsearch.requestTimeout: 3600000
elasticsearch.url: http://<elasticsearch-ip>:9200
6) Start Sentinel using the command:
rcsentinel start.
7) To restore existing data, transfer the data from the temporary index (.kibana-temp) to the new .kibana index, using the following commands:
curl -XPOST “http://<elasticsearch-ip>:9200/_reindex” -H ‘Content-Type: application/json’ -d’
{
“source”: {
“index”: “.kibana-temp”
},
“dest”: {
“index”: “.kibana”
}
}’
8) Delete the temporary index using the following command, curl -XDELETE ‘<elasticsearch-ip>:9200/.kibana-temp’


Sentinel now launches the dashboards successfully.

Cause

This issue occurs because Elasticsearch and Kibana versions have been upgraded in Sentinel 8.2, and the existing Kibana index file is not compatible with the upgraded versions of Elasticsearch and Kibana.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Re: Re: Change Password for Access Key by Object User

If you have configured the AD authentication provider correctly in ECS, any AD user within the search base should be able to authenticate into the management API and obtain a X-SDS-AUTH-TOKEN token.

curl -L –location-trusted -k https://10.247.100.247:4443/login -u “my_ad_user@domain.com:ChangeMe” -v

The curl command above will work without my_ad_user@domain.com existing as a local object user in ECS. This will at least confirm if you have AD configured correctly in ECS. If you can’t get the X-SDS-AUTH-TOKEN, you likely have something configured incorrectly in the AD Auth Provider within ECS.

Once you have a token, you can attempt to generate a secret key. However, you first need to configure the domain portion of a namespace so that when my_ad_user@domain.comgenerates a secret key, ECS can map them to your desired namespace and insert them as a local object user.

Have a look here at example of what the curl commands would look like using an AD user and obtaining a secret key: https://130820690509421904.public.ecstestdrive.com/share/BagOfTricks-CurlWithLDAPUsers.docx

Related: