Error while uploading jtl file via curl

[abhayshankar]

I am trying to upload the JMeter test results (.jtl file) to jtlReporter however getting error. Am using curl with the parameters as mentioned in the jtlReporter documentation to upload the jtl file however no success.
Note : jtl file upload via GUI is working fine, its failing via curl.

Below is the curl command I am using.

curl 'http://10.153.139.115:5000/api/projects/CMW/scenarios/cmw_s1>/items' \
   -H 'Connection: keep-alive' \
   -H 'Accept: application/json, text/plain, */*' \
   -H 'x-access-token: at-45e8f960-8a8a-4179-9858-73922835a9bd' \
   -H 'Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryzrlQF8HbBdDOMTyb' \
   -H 'Referer: http://localhost:4200/' \
   -H 'Accept-Language: cs-CZ,cs;q=0.9,en;q=0.8,en-GB;q=0.7,en-US;q=0.6,ja;q=0.5,nl;q=0.4,sk;q=0.3,cy;q=0.2,de;q=0.1,ro;q=0.1' \
   --data-raw $'------WebKitFormBoundaryzrlQF8HbBdDOMTyb\r\nContent-Disposition: form-data; name="kpi"; filename="test.jtl"\r\nContent-Type: text/csv\r\n\r\n\r\n------WebKitFormBoundaryzrlQF8HbBdDOMTyb\r\nContent-Disposition: form-data; name="environment"\r\n\r\ntest\r\n------WebKitFormBoundaryzrlQF8HbBdDOMTyb\r\nContent-Disposition: form-data; name="note"\r\n\r\n\r\n------WebKitFormBoundaryzrlQF8HbBdDOMTyb\r\nContent-Disposition: form-data; name="hostname"\r\n\r\n\r\n------WebKitFormBoundaryzrlQF8HbBdDOMTyb\r\nContent-Disposition: form-data; name="status"\r\n\r\n10\r\n------WebKitFormBoundaryzrlQF8HbBdDOMTyb--\r\n' \
   --compressed

Below is the tailed output of the jtl backend service (docker logs jtlreporter_be_1)

{"level":"info","message":"Starting new item processing for scenario: cmw_s1>"}
{"code":"23502","column":"scenario_id","detail":"Failing row contains (0480451e-6918-4b3e-a961-3978b6a69188, , test, 2022-02-11 11:02:57.149402, null, null, null, null, 10, , in_progress, null, f).","file":"execMain.c","length":321,"level":"error","line":"1947","name":"error","routine":"ExecConstraints","schema":"jtl","severity":"ERROR","table":"items"}
{"data":null,"isBoom":true,"isServer":true,"level":"error","output":{"headers":{},"payload":{"error":"Internal Server Error","message":"An internal server error occurred","statusCode":500},"statusCode":500}}
{"level":"info","message":"POST /api/projects/CMW/scenarios/cmw_s1>/items 500 36ms","meta":{}}
{"level":"info","message":"GET /api/projects/CMW 304 18ms","meta":{}}

[ludeknovy]

Hello @abhayshankar, this morning I updated the curl: https://jtlreporter.site/docs/guides/api-data-upload
so it should look like this:

curl -X POST 'http://<ip_address>:5000/api/projects/<project_name>/scenarios/<scenario_name>/items' \
  -H 'x-access-token: <auth_token>' \
  -F 'kpi=@"/<path_to_file>/result.jtl"' \
  -F 'environment="testenv"' \
  -F 'note="testnote"' \
  -F 'hostname="testhostname"' \
  -F 'status="10"'

[abhayshankar]

Thanks @ludeknovy for the prompt reply. However, I see the same response with the updated command as well.

curl -X POST 'http://<IP>:5000/api/projects/ABC/scenarios/abc1/items' \
  -H 'x-access-token: <auth_token>' \
  -F 'kpi=@"/jtl/jtl-reporter/test.jtl"' \
  -F 'environment="beta"' \
  -F 'note="testnote"' \
  -F 'hostname="testhostname"' \
  -F 'status="10"'

{"message":"An internal server error occurred"}

Docker logs

{"code":"23502","column":"scenario_id","detail":"Failing row contains (2df32c82-af97-40e4-9fa9-d2f958797d2d, testnote, beta, 2022-02-11 13:50:34.206569, null, null, null, null, 10, testhostname, in_progress, null, f).","file":"execMain.c","length":341,"level":"error","line":"1947","name":"error","routine":"ExecConstraints","schema":"jtl","severity":"ERROR","table":"items"}
{"data":null,"isBoom":true,"isServer":true,"level":"error","output":{"headers":{},"payload":{"error":"Internal Server Error","message":"An internal server error occurred","statusCode":500},"statusCode":500}}
{"level":"info","message":"POST /api/projects/ABC/scenarios/abc1/items 500 30ms","meta":{}}

[ludeknovy]

Could you share the anonymized file you are trying to upload, please?

[ludeknovy]

I got the very similar error when I tried to upload to a wrong scenario. And the error actually says the same: scenario_id => ExecConstraints

[abhayshankar]

Sharing a snippet from the jtl file

timeStamp,elapsed,label,responseCode,responseMessage,threadName,dataType,success,failureMessage,bytes,sentBytes,grpThreads,allThreads,URL,Latency,IdleTime,Connect,hostname
1644395682252,566,b-gg,200,OK,Ultimate Thread Group 2-46,text,true,,1751,648,50,50,https://b-gg,566,0,370,host
1644395682219,794,b-gg,200,OK,Ultimate Thread Group 2-35,text,true,,73542,648,50,50,https://b-gg,684,0,468,host
1644395682213,835,b-gg,200,OK,Ultimate Thread Group 2-4,text,true,,70003,648,50,50,https://b-gg,732,0,523,host
1644395682218,851,b-gg,200,OK,Ultimate Thread Group 2-33,text,true,,70011,648,50,50,https://b-gg,692,0,349,host
1644395682161,929,b-gg,200,OK,Ultimate Thread Group 2-26,text,true,,69998,648,50,50,https://b-gg,762,0,406,host
1644395682226,878,b-gg,200,OK,Ultimate Thread Group 2-39,text,true,,71390,648,50,50,https://b-gg,682,0,457,host
1644395682191,914,b-gg,200,OK,Ultimate Thread Group 2-3,text,true,,69982,648,50,50,https://b-gg,724,0,505,host
1644395682208,902,b-gg,200,OK,Ultimate Thread Group 2-1,text,true,,69997,648,50,50,https://b-gg,739,0,525,host
1644395682214,896,b-gg,200,OK,Ultimate Thread Group 2-29,text,true,,75660,648,50,50,https://b-gg,732,0,497,host
1644395682258,865,b-gg,200,OK,Ultimate Thread Group 2-49,text,true,,80426,648,50,50,https://b-gg,687,0,479,host
1644395682162,961,b-gg,200,OK,Ultimate Thread Group 2-7,text,true,,69996,648,50,50,https://b-gg,809,0,598,host
1644395682190,934,b-gg,200,OK,Ultimate Thread Group 2-24,text,true,,68774,648,50,50,https://b-gg,742,0,505,host
1644395682191,941,b-gg,200,OK,Ultimate Thread Group 2-6,text,true,,75645,648,50,50,https://b-gg,768,0,481,host
1644395682213,923,b-gg,200,OK,Ultimate Thread Group 2-31,text,true,,75645,648,50,50,https://b-gg,766,0,556,host
1644395682212,925,b-gg,200,OK,Ultimate Thread Group 2-27,text,true,,70012,648,50,50,https://b-gg,769,0,443,host
1644395682226,912,b-gg,200,OK,Ultimate Thread Group 2-36,text,true,,84226,648,50,50,https://b-gg,752,0,550,host
1644395682165,995,b-gg,200,OK,Ultimate Thread Group 2-21,text,true,,69981,648,50,50,https://b-gg,819,0,501,host
1644395682219,945,b-gg,200,OK,Ultimate Thread Group 2-34,text,true,,69965,648,50,50,https://b-gg,771,0,561,host
1644395682202,962,b-gg,200,OK,Ultimate Thread Group 2-15,text,true,,69998,648,50,50,https://b-gg,779,0,577,host
1644395682199,967,b-gg,200,OK,Ultimate Thread Group 2-23,text,true,,75636,648,50,50,https://b-gg,815,0,559,host
1644395682194,977,b-gg,200,OK,Ultimate Thread Group 2-14,text,true,,70005,648,50,50,https://b-gg,812,0,556,host
1644395682213,983,b-gg,200,OK,Ultimate Thread Group 2-10,text,true,,121972,648,50,50,https://b-gg,801,0,574,host
1644395682232,974,b-gg,200,OK,Ultimate Thread Group 2-42,text,true,,76528,648,50,50,https://b-gg,787,0,563,host
1644395682235,960,b-gg,200,OK,Ultimate Thread Group 2-44,text,true,,80424,648,50,50,https://b-gg,760,0,503,host
1644395682229,959,b-gg,200,OK,Ultimate Thread Group 2-41,text,true,,75658,648,50,50,https://b-gg,791,0,331,host
1644395682201,1009,b-gg,200,OK,Ultimate Thread Group 2-20,text,true,,70005,648,50,50,https://b-gg,841,0,599,host

[abhayshankar]

Am able to upload the same file via jtlReporter GUI

[ludeknovy]

When I try on my localhost:

curl -X POST 'http://localhost:5050/api/projects/ABC/scenarios/abc1/items' \
  -H 'x-access-token: at-b08697fe-f74c-4bef-ad78-fe0b498eb6b2' \
  -F 'kpi=@"result.jtl"' \
  -F 'environment="beta"' \
  -F 'note="testnote"' \
  -F 'hostname="testhostname"' \
  -F 'status="10"'

it returns me:

{"itemId":"bc2bc7a6-d440-44a2-b17b-0a3a9fb5b7da"}%

Which means the file was accepted.

[abhayshankar]

Nice.
I see you are using port# as 5050, is there any update regarding this ?
I am using port 5000 for the curl requests

[ludeknovy]

No, I run it locally in different port. See my answer here #131 (reply in thread)

[abhayshankar]

Got it. Will give it a try again. Is there any constraint that jtlReporter and JMeter should be hosted on the same machine? Currently, my jtlReporter and JMeter are hosted on different servers. Regards, Abhay

…

On Fri, Feb 11, 2022 at 8:16 PM Ludek Novy ***@***.***> wrote: No, I run it locally in different port. See my answer here #131 (reply in thread) <#131 (reply in thread)> — Reply to this email directly, view it on GitHub <#131 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACKUJ5ZBPX3OEZDSHCC6LMLU2UOKZANCNFSM5OEF44ZQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ludeknovy]

No, they do not have to be hosted on the same machine. But you need access from the jmeter host to jtl reporter host of course.

Let me know if you made it work.

[abhayshankar]

I tried again, but now getting the connection refused error. Just to give a background, my JMeter is hosted on Gitlab SAAS and jtlReporter on AWS EC2 instance. Currently, I am running the below command from jtlReporter server (EC2 instance, have manually copied the jtl file from JMeter server to EC2 instance). I believe since I am running the curl from the same server where jtlReporter is hosted, connection refused error should not occur. Not sure what I am doing wrong 🤔 ``` curl -X POST 'http://<IP>:5000/api/projects/SAS/scenarios/test1/items' \ -H 'x-access-token: <auth_token>' \ -F 'kpi=@"/jtl/jtl-reporter/test.jtl"' \ -F 'environment="beta"' \ -F 'note="testnote"' \ -F 'hostname="testhostname"' \ -F 'status="10"' ``` `curl: (7) Failed to connect to <IP> port 80: Connection refused` Docker logs ``` {"level":"info","message":"GET /api/projects/SAS/scenarios 304 33ms","meta":{}} {"level":"info","message":"GET /api/projects 304 4ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2 200 2ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/notifications 200 4ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/items?limit=15&offset=0 200 5ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/trends 200 4ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/processing-items 200 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2 304 2ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/processing-items 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/processing-items 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/processing-items 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects 304 4ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/notifications 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/items?limit=15&offset=0 304 6ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/processing-items 304 6ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/trends 304 28ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios 304 7ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS 304 4ms","meta":{}} {"level":"info","message":"GET /api/projects 304 5ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/notifications 304 2ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2 304 4ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/trends 304 4ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/processing-items 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2/items?limit=15&offset=0 304 10ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios/test2 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS 304 3ms","meta":{}} {"level":"info","message":"GET /api/projects/SAS/scenarios 304 6ms","meta":{}} ``` Regards, Abhay

…

On Fri, Feb 11, 2022 at 8:30 PM Ludek Novy ***@***.***> wrote: No, they do not have to be hosted on the same machine. But you need access from the jmeter host to jtl reporter host of course. Let me know if you made it work. — Reply to this email directly, view it on GitHub <#131 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACKUJ56LK3QDR6HA3OYBQRTU2UQBXANCNFSM5OEF44ZQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ludeknovy]

are you sure that your EC2 / network settings have exposed port 5000?

What's weird is curl: (7) Failed to connect to <IP> port 80: Connection refused why port 80? There is some network issue I guess.

[abhayshankar]

Yes, you are right. Port 5000 seems to be blocked. I will have to try on another machine. Do we have a dockerized way of running jtlReporter? If so, can you please share the instructions? Regards, Abhay

…

On Fri, Feb 11, 2022 at 8:55 PM Ludek Novy ***@***.***> wrote: are you sure that your EC2 / network settings have exposed port 5000? What's weird is curl: (7) Failed to connect to <IP> port 80: Connection refused why port 80? There is some network issue I guess. — Reply to this email directly, view it on GitHub <#131 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACKUJ52DOEMNHJNGZEDSW23U2US6PANCNFSM5OEF44ZQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ludeknovy]

The application is available in docker images - see the docker-compose, or: https://hub.docker.com/u/novyl

[abhayshankar]

Thanks a lot.
Will try out.

[abhayshankar]

Finally resolved.
Thanks @ludeknovy for all the help.

[ludeknovy]

Great! Glad you made it work!