Sqlmap in Kali is in version 1.6, so this issue might be caused by the latest update, and that's why it doesn't happen in Ubuntu (with version 1.5.9)
This bug must be filled against the sqlmap project, as we in Kali only provide the package and is actually built by Debian.

Unfortunately in sqlmap they blame Kali Linux for this bug...I already reported the issue, they sent me here.

That's weird, because we don't package sqlmap. We use the package from Debian, as I mentioned.
I'll check if there's anything that could be causing it, but it doesn't make much sense to me. Thanks for reopening it then ;)

Sharing the link to the github issue for sqlmap
https://github.com/sqlmapproject/sqlmap/issues/4972

In the github issue it is said: « this doesn't look like a sqlmap issue, but related to torsocks ». So... did you try without torsocks?

Tried with and without torsocks. And unfortunately again, I managed to replicate the issue again with kali 5.16.0 22-02-10 and sqlmap 1.6.2#stable

Hi, I just started a Kali rolling VM, and I launched the command provided in the GitHub issue, minus torsocks:

<pre>
$ sqlmap -u "http://testphp.vulnweb.com/artists.php?artist=1&quot; --batch --technique=B --threads=10 --dump -D acuart -T artists
</pre>

Works for me, no error.

If you can provide another command that allow me to reproduce the issue, I can try.

same command but without the --batch and it occurs randomly, sometimes it takes an hour sometimes 3 hours.

However, I do have some better news.
Running my command in Kali SQLMap 1.6.2 I still get "too may open files" error, setting ulimit -n to 102400 (seems like a magic number) did not cause the buffer overflow error.

I'm not sure if you can consider it fixed or a workaround.

For the record: I tried again with --batch option, and it works fine. Takes around 30 minutes to run.

Also, to clarify: so far I've never seen any "too may open files" error message, and I never had to touch ulimit. This is with sqlmap 1.6.2-1 from Kali Rolling.

Then I have no idea what's going on, I'm running Kali without any change in settings. now with the new ulimit everything works fine...without it I get too many open files, any other ulimit will give me buffer overflow.

I also tried to run sqlmap as root and as non-root, just to be sure. Still no issue on my side.

So I'm closing this ticket as I can't reproduce the issue, and it seems that it's more or less solved for you as well.