python process pileup, needs reproduction steps. about clusterfuzz HOT 11 CLOSED

It already found the heartbleed, see logs

2019-02-08 14:40:40,543 - run_bot - INFO - Process the crash group (file=fuzz-1, fuzzed_key=25002300-d91f-4b14-b894-6e2a5f4ed858, return code=1, crash time=4, crash type=Heap-buffer-overflow
READ {*}, crash state=tls1_process_heartbeat
ssl3_read_bytes
ssl3_get_message

and there should be testcase on localhost:9000.

can you paste the job definitions you have, maybe some processes are piling up. Did you modify any templates or anything ? Are you running AFL or libFuzzer ? Need more reproducer instructions.

from clusterfuzz.

can you also start from a clean slate and see if you can reproduce. like try pkill -9 -f clusterfuzz and pkill -9 -f gcloud.

from clusterfuzz.

I followed the steps exactly for heartbleed, should be the same as on the wiki. It says it found heartbleed right away - but I was checking the test cases in the UI and it was empty from 2pm - 12am. Did not change any templates.

from clusterfuzz.

this could be related to your broken config as in #136. your ports seem to be not free, can you try a restart and see if you can still reproduce.

from clusterfuzz.

also which platform and os version you are running.

from clusterfuzz.

I'm doubtful I have those ports blocked, as I showed checking the ports right after clusterfuzz tried using them revealed them to be unused. I restarted anyway!

I'm on Ubuntu 18.04 LTS.

from clusterfuzz.

I've restarted and heartbleed indeed now shows up in the test cases. Should I do anything else?

from clusterfuzz.

Metadata says the following:

	[2019-02-08 13:06:35 UTC] mudlet1: Fuzz task : Fuzzer libFuzzer_handshake-fuzzer generated testcase crashed in 3 seconds (r1). 
	[2019-02-08 13:09:01 UTC] mudlet1: Minimize task started. 
	[2019-02-08 13:24:16 UTC] mudlet1: Minimize task finished. 
	[2019-02-09 00:19:37 UTC] mudlet1: Progression task started. 
	[2019-02-09 00:19:39 UTC] mudlet1: Progression task finished. 

Which could explain why I didn't see the test case for many hours.

from clusterfuzz.

Something was up with clearing ports. Basically, run_bot could not send testcase to run_server since run_server wasn't running and failing on not being able to find the port. run_bot was finding the crash fine, but run_server didnt get it.
Right now, your log in last message is correct. so everything should be working fine. if you ever hit this again, try remembering the steps. use ctrl+c to kill run_server and run_bot, not kill a particular process id. we can reopen the bug if you hit this again.

from clusterfuzz.

I'm also running into this, but with less impact.

I did a fresh install on an Ubuntu 18.04 LTS VM. Followed the pre-requisites: https://google.github.io/clusterfuzz/getting-started/prerequisites/

I then ran the local server, went to the web UI, and created a bot instance a few minutes later in a separate tab. I see the port error in my logs, though interestingly enough things work (I see the test case in the testcases UI).

My full server logs are here: https://pastebin.com/JKya8WNB - bot logs are here: https://pastebin.com/YN6vCRBZ

Hope this helps!

from clusterfuzz.

@mhlakhani - this should get fixed as part of #197. these never happen in production since we use appengine cron. locally, we create some threads to run every 60 secs. we can make them more reliable.

@oliverchang as fyi.

from clusterfuzz.