Failed to start the main proxy: java.net.BindException Address already in use

41 views
Skip to first unread message

Ieuan Byers

unread,
Oct 2, 2023, 10:19:47 AM10/2/23
to ZAP User Group
Hi,
We're getting this error message intermittently on some of our Jenkins pipelines which use the zap2docker-stable image and call the zap-api-scan.py script. I seen that this can be caused by an outdated network add-on but as far as I can see, we're using the most recent version (0.11.2). 

Here is how we're calling the zap-api-scan.py script:
zap-api-scan.py -t ${TEST_URL}/v2/api-docs -f openapi -S -d -u ${SecurityRules} -P 1001 -z "-config rules.cookie.ignorelist=_ga,_gid,_gat,dtCookie,dtLatC,dtPC,dtSa,rxVisitor,rxvt" -l FAIL -r /zap/wrk/api-report.html

I've also attached a copy of the zap log file, any help would be appreciated.
zap (5).out

Simon Bennetts

unread,
Oct 2, 2023, 10:24:54 AM10/2/23
to ZAP User Group
Could the address actually be in use?

Also - on Linux systems you typically not listen on ports under 1024 unless you are root.

Cheers,

Simon

Ieuan Byers

unread,
Oct 2, 2023, 10:30:53 AM10/2/23
to ZAP User Group
Hi Simon,

I don't think the address is in use. The issue seems to be intermittent and I've found that it will run fine on one build then fail on the next one with no changes made.

Good to know about the ports though, maybe something we can look at changing.

Cheers,
Ieuan

Reply all
Reply to author
Forward
0 new messages