Skip to content
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 with running bot: AttributeError: 'NoneType' object has no attribute 'fully_qualified_name' when using local instance #4337

Open
Fahnenfluchtige opened this issue Oct 18, 2024 · 0 comments

Comments

@Fahnenfluchtige
Copy link

Hello!
I'm trying to run a ClusterFuzz bot in a local instance but encountering an error. I made a few changes to the files to adapt the setup to my environment.

I modified the following files:

diff --git a/local/emulators/gcs.go b/local/emulators/gcs.go
--- a/local/emulators/gcs.go
+++ b/local/emulators/gcs.go
-       http.ListenAndServe(fmt.Sprintf("localhost:%d", port), nil)
+       http.ListenAndServe(fmt.Sprintf("0.0.0.0:%d", port), nil)


diff --git a/src/local/butler/constants.py b/src/local/butler/constants.py
--- a/src/local/butler/constants.py
+++ b/src/local/butler/constants.py
-LOCAL_GCS_SERVER_HOST = 'localhost:' + str(LOCAL_GCS_SERVER_PORT)
+LOCAL_GCS_SERVER_HOST = 'http://<my-public-ip>:' + str(LOCAL_GCS_SERVER_PORT)

I started the server using the command:
python3.11 butler.py run_server --name test --server-storage-path ~/clusterfuzz/test/

Then I loaded my job (openssl heartbleed example). I verified that the binary and the zip archive are set up correctly.

And after that, I ran the bot:
python3.11 butler.py run_bot --name test --server-storage-path ~/clusterfuzz/test/ ~/clusterfuzz/test/bot_dir/

The bot fails to run correctly and throws the following error:

 run_bot - ERROR - Error occurred while working on task.
Traceback (most recent call last):
...
AttributeError: 'NoneType' object has no attribute 'fully_qualified_name'

It seems that the FuzzTarget object is not being initialized correctly, resulting in this error. The job and the files appear to be set up properly, but the bot is unable to proceed.

Editing env.yaml in the bot directory did not help me: the same error is occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant