-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error_unknown (Reason for termination: badarg) #324
Comments
ping @nniclausse. Can you maybe help so that I can locate or even fix the problem? |
Hello, I have same problem here, this error seems randomly occurred, but more load I gave, this error appear more frequently. The tsung are running on the AWS EC2 instances. I've configured two t3.small instances as node and one t3.medium as a controller. These tsung nodes are running under Amazon Linux 2. Erlang version is OTP21, and OpenSSL 1.0.2k-fips. Our XMPP servers are running Ejabberd 18.09.19, OTP 21, and OpenSSL 1.1.0f. Here is my log file from one of tsung cluster.
and here is my config file
Please help, thank you. |
@victorqhong you actually have a pretty "good" error message. Have you tried to update OpenSSL to 1.1.1a or even the latest 1.1.1b? Depending on how your target host is configured, this might help. If you can give this a try without TLS it should work (AFAIK). Actually, the launched Tsung Client is dying while trying to translate the error message. #343 contains a fix for the error reporting, but won't resolve the underlying issue you are seeing. |
Hi All, ts_client:(5:<0.949.0>) Stop in state think, reason= {badarg, Tsung.log Connections drops from 297 to 0 I also posted an issue #358, Pls help |
@testcoderepo123 that's a different error. The TLS alert indicates that there is an issue with the TLS connection with your target. |
What could be the reason for this issue? Attached is my config. Can you pls check if I am missing out anything? I am really blocked on this....Could you pls help? ts_client:(5:<0.195.0>) Stop in state think, reason= {badarg, |
From time to time we see
error_unknown
intsung.log
. In the node logs we see errors like this:The error happens every so often, but I currently have not a good clue how to reproduce it or were to start digging :-/
The text was updated successfully, but these errors were encountered: