|
On Sep 8, 2021, at 3:55 AM, Don Brown via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Hi All
I am out of my depth with this curl stuff and hoping someone can advise.
I have been searching for curl information - maybe I should be searching
for qsh ?
I am using curl to write to a GreyLog syslog server.
I am using qcmdexc to run the qsh command that uses curl to post to the
syslog server.
This works but I have found if there are many messages to be written I can
get an error
curl: (7) Failed to connect ... connection refused
This message appears in the joblog
My call looks like this;
callp(e) QCmdExc(Cmd:CmdLen);
if %error();
I do get an error but how do I retrieve the actual error that is being
sent to the job log (or the qsh session if run interactively) ?
I think the server is just having a hard time keeping up so if I get this
error I was going to retry sending the post or perhaps put a short sleep
to handle this issue.
Appreciate any suggestions
Thank you
Don
--
This email has been scanned for computer viruses. Although MSD has taken reasonable precautions to ensure no viruses are present in this email, MSD cannot accept responsibility for any loss or damage arising from the use of this email or attachments..
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.