Troubleshooting

deadline has elapsed

Problem

When trying to fund your requestor on the testnet using yagna payment fund, you may encounter the following error message:

Error: deadline has elapsed

Solution

The testnet might be experiencing heavy traffic, leading to increased gas fees. This can slow down the transaction process and cause Yagna to timeout.

To resolve the issue:

  1. Retry the command. If it doesn't work retrying 3 times, then please reach out to us on discord

yagna is already running

Problem

When attempting to run the commands yagna service run or golemsp run, you receive an error message that reads:

Error: yagna is already running

Solution

This indicates that the Yagna service, which could be acting as a provider or requestor daemon, is already active on your system.

To resolve the issue:

  1. If your system supports the killall command, execute:

    killall yagna

    1.1 If killall isn't supported or you'd prefer a manual method:

    ps aux | grep yagna

    From the output, note the PID (Process ID) of the yagna service.

    1.2 Terminate the identified service with:

    kill -9 <PID>

  2. Once you've terminated the running instance(s), you can start Yagna or the provider as you normally would.

Enabling DEBUG Log Level in Yagna

Problem

If you're experiencing issues with Yagna, enabling DEBUG level logs can be crucial for diagnosing the problem. This process helps in identifying the specific area where the issue lies.

Solution

To enable DEBUG logs in Yagna, you need to start the Yagna service with a specific command. Here’s how you can do it:

  1. Open your terminal.
  2. Start Yagna using the following command:
RUST_LOG=debug yagna service run