Server closed connection without sending any data back (500)

I cannot seem to get the RT CLI to work. We are using 4.0.18. Any ideas
as to what is going on?

The Apache httpd logs show nothing of any use. If I use the web UI
(which works fine, and we’ve been using it for 10+ years now), I can
logout + login with the following username and password fine. The user
has full create privs for the foo-help queue (it is our day-to-day queue
we use all the time).

[rt-tickets:~]$ cat .rtrc
server https://rt-tickets.our.org/
user jblaine@our.org
passwd mypassword
queue foo-help
debug 3
[rt-tickets:~]$

[rt-tickets:~]$ /rt/bin/rt create -o -t ticket set subject=foo
POST https://rt-tickets.our.org//REST/1.0/show
Content-Length: 281
Content-Type: multipart/form-data; boundary=xYzZY

–xYzZY
Content-Disposition: form-data; name=“format”

l
–xYzZY
Content-Disposition: form-data; name=“id”

ticket/new
–xYzZY
Content-Disposition: form-data; name=“user”

jblaine@our.org
–xYzZY
Content-Disposition: form-data; name=“pass”

mypassword
–xYzZY–
500 Server closed connection without sending any data back
Content-Type: text/plain
Client-Date: Thu, 09 Jan 2014 20:54:30 GMT
Client-Warning: Internal response

500 Server closed connection without sending any data back
rt: Server error: Server closed connection without sending any data back
(500)

If anyone has any ideas how I might go about making RT
more informative about what is going on in this failure,
I would love to hear them.On 1/9/2014 4:01 PM, Jeff Blaine wrote:

I cannot seem to get the RT CLI to work. We are using 4.0.18. Any ideas
as to what is going on?

The Apache httpd logs show nothing of any use. If I use the web UI
(which works fine, and we’ve been using it for 10+ years now), I can
logout + login with the following username and password fine. The user
has full create privs for the foo-help queue (it is our day-to-day queue
we use all the time).

==================================================================
[rt-tickets:~]$ cat .rtrc
server https://rt-tickets.our.org/
user jblaine@our.org
passwd mypassword
queue foo-help
debug 3
[rt-tickets:~]$

==================================================================
[rt-tickets:~]$ /rt/bin/rt create -o -t ticket set subject=foo
POST https://rt-tickets.our.org//REST/1.0/show
Content-Length: 281
Content-Type: multipart/form-data; boundary=xYzZY

–xYzZY
Content-Disposition: form-data; name=“format”

l
–xYzZY
Content-Disposition: form-data; name=“id”

ticket/new
–xYzZY
Content-Disposition: form-data; name=“user”

jblaine@our.org
–xYzZY
Content-Disposition: form-data; name=“pass”

mypassword
–xYzZY–
500 Server closed connection without sending any data back
Content-Type: text/plain
Client-Date: Thu, 09 Jan 2014 20:54:30 GMT
Client-Warning: Internal response

500 Server closed connection without sending any data back
rt: Server error: Server closed connection without sending any data back
(500)

If anyone has any ideas how I might go about making RT
more informative about what is going on in this failure,
I would love to hear them.

You showed an Internal Server Error

500 Server closed connection without sending any data back

But didn’t show the logs created by the server for this error. Nobody
can help without logs of what happened on the server.

-kevin

If anyone has any ideas how I might go about making RT
more informative about what is going on in this failure,
I would love to hear them.

You showed an Internal Server Error

500 Server closed connection without sending any data back

But didn’t show the logs created by the server for this error. Nobody
can help without logs of what happened on the server.

That’s because there is no 500 error information logged to
/var/log/httpd/*log by Apache when I make this request
via the RT CLI tool using the settings previously shown
in .rtrc.

Honest. In fact, there is zero trace of the IP address
in all of the Apache logs, even using 'LogLevel debug’
for Apache.

I can request /sdfkdaslfdskldsfkla and see a 404 just fine
and all other normal info is in those logs. It’s standard
Apache 2.x on RHEL 6.

Does the RT CLI tool support SSL/TLS ‘server’ settings?

Solved:

unset http_proxy
unset https_proxy

sighOn 1/15/2014 3:08 PM, Jeff Blaine wrote:

On 1/15/2014 11:22 AM, Kevin Falcone wrote:

On Wed, Jan 15, 2014 at 09:23:41AM -0500, Jeff Blaine wrote:

If anyone has any ideas how I might go about making RT
more informative about what is going on in this failure,
I would love to hear them.

You showed an Internal Server Error

500 Server closed connection without sending any data back

But didn’t show the logs created by the server for this error. Nobody
can help without logs of what happened on the server.

That’s because there is no 500 error information logged to
/var/log/httpd/*log by Apache when I make this request
via the RT CLI tool using the settings previously shown
in .rtrc.

Honest. In fact, there is zero trace of the IP address
in all of the Apache logs, even using 'LogLevel debug’
for Apache.

I can request /sdfkdaslfdskldsfkla and see a 404 just fine
and all other normal info is in those logs. It’s standard
Apache 2.x on RHEL 6.

Does the RT CLI tool support SSL/TLS ‘server’ settings?