Curl commands executed with the Control-M/Agent user account fail with the error: "curl: (48) An unknown option was passed in to libcurl"

Knowledge Article

Article Number

000363308

Old Article Number

000193515

Article Type

Solutions to a Product Problem

Title

Curl commands executed with the Control-M/Agent user account fail with the error: "curl: (48) An unknown option was passed in to libcurl"

Summary

Product

Control-M/Agent for UNIX and Microsoft Windows

Component

Control-M/Agent for UNIX and Microsoft Windows

Applies to

Control-M/Agent for UNIX and Microsoft Windows on Linux with the cm/cm_shared directory present (installed by some Control Module)

Problem

The execution of the "curl" command performed from the Control-M/Agent owner account fails with the error:

curl: (48) An unknown option was passed in to libcurl

Checking for "curl" version you get the following:

myserver% curl -V
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.44.0 zlib/1.2.8
Protocols: dict file ftp gopher http imap pop3 rtsp smtp telnet tftp
Features: IPv6 Largefile libz unix-sockets

myserver% ldd /usr/bin/curl
libcurl.so.4 => <agenthome>/ctm/exe/libcurl.so.4 (0x00007f750ee04000)

myserver% ls -l <agenthome>/ctm/exe/libcurl*
lrwxrwxrwx 1 ctmagent controlm 57 5. Dez 11:36 libcurl.so -> <agenthome>/ctm/cm/cm_shared/curl/7.44.0/libcurl.so
lrwxrwxrwx 1 ctmagent controlm 57 5. Dez 11:36 libcurl.so.4 -> <agenthome>/ctm/cm/cm_shared/curl/7.44.0/libcurl.so

We see that the curl command uses the libcurl.so library located in the directory:
<agenthome>/ctm/cm/cm_shared/curl/7.44.0/

This behavior occurs since the libcurl library supplied in the cm_shared directory is pointed to by a symbolik link in the Control-M/Agent executable directory which is listed in the LD_LIBRARY_PATH for the Control-M owner account. Due to this, ALL curl commands executed by the Control-M/Agent owner will use the BMC supplied library which doesn't implement all the curl features leading to the "unknown option" error messages.For instance, it doesn't implement the "https" protocol.

Cause

CTM-3554 - When using a curl command in the job type the AP libcurl is activated instead of the machine's libcurl

Solution

CTM-3554 has been created for this issue and is implemented in version 9.0.21
Apply the latest available version to fix the issue.

In the short term, you can temporarily modify the LD_LIBRARY_PATH before executing each curl command like the following example (based on C Shell):

setenv LD_LIBRARY_PATH /usr/lib64:$LD_LIBRARY_PATH ; <your original curl command here>

For reference, this is the output of the "curl -V" command that is using the operating system library (real versions may vary among different systems):

myserver% curl -V
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.44 zlib/1.2.7 libidn/1.28 libssh2/1.8.0
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp scp sftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz unix-sockets

The list of Protocols and Features is wider.

Attachment(s):