Requestor Troubleshooting

Requestor Issues
Don't miss the debugging section by using the log file.
IO error: No such file or directory
Os: Any
Description: Local service error: Transfer error: IO error: No such file or directory (os error 2)
Solution: Something went wrong with the computation. We have a "Debugging with the use of log files" guide in our requestor tutorials to assist with debugging.
You can also check that you're defining your task's correctly and that you remembered to define a place (or places) in the container file system that will be used for the file transfer, as discussed here.
With ctx.run() make sure that you don't have multiple arguments in one string. Either ctx.run("/bin/sh", "-c", "a", "b", "c" ...) or use the syntax the example gives where it parses in lines.
Send error: send failed because receiver is gone
If you manage to receive a message that says:
Activity failed on provider [..] failed on provider with message 'Local service error: Transfer error: Send error: send failed because receiver is gone'
That most likely means you're trying to send a transfer command (upload_file / download_file) to/from a location that's not a VOLUME. The reason is that only the volumes are accessible to the exe unit runner and other locations in the image simply cannot be read or written to.
Symlink issues
Os: Ubuntu
Description: If you run the Golem Provider one-line installer on a minimal install of Ubuntu and it completes without error but doesn't run then you might have a symlink issue.
Solution: See this guide on setting up and managing Simlinks.
Connectivity issue
Os: All
Description: When someone is not receiving tasks at all, has correct subnet configured, and VM valid, the most probable cause is yagna "connectivity" issue
Solution: Kill and restart the process
Payment driver initialization issue
Os: All, requestor only
Description: Since our newest addition to Golem - the integration with zkSync, layer 2 payment solution - is, so far, a highly experimental feature, it may still sometimes happen that the yagna daemon fails to initialize itself correctly.
This will manifest itself either by a failure of the regular initialization withyagna payment fund or through an error you'll receive when running yagna payment status.
Solution: In such a case, we're providing you with a fallback to normal payments, i.e. regular GLM token transfer on the Ethereum chain.
To enable it run:
1
yagna payment fund --driver erc20
2
yagna payment status --driver erc20
3
yagna payment init --sender --driver erc20
Copied!
After you confirm you have the funds, proceed with running the examples or your own requestor agent code normally. The providers are configured to accept both zkSync and the regular tokens and will adjust accordingly.
Just remember to use https://rinkeby.etherscan.io/ instead of the zkSync explorer, should you wish to verify that the payment went through.
Bind error: already registered
Os: Ubuntu
Description: If the user has an obsolete/incorrect version of gftp in $PATH they will get a repeating error when they try to request a task:
1
[2020-11-27 15:43:11,509 INFO yapapi.summary] Received proposals from 9 providers so far
2
[2020-11-27T14:43:12Z ERROR ya_service_bus::remote_router] bind error: already registered: Service ID '/public/gftp/ee82d5dc7188611da558c76e777a2df7867d9526eac6fa9378728d44ca4a2a10/GetMetadata' already registered
3
[2020-11-27T14:43:12Z ERROR ya_service_bus::remote_router] bind error: already registered: Service ID '/public/gftp/ee82d5dc7188611da558c76e777a2df7867d9526eac6fa9378728d44ca4a2a10/GetChunk' already registered
4
[2020-11-27 15:43:12,434 WARNING yapapi.summary] Activity failed on provider 'odra.3', reason: (-32000, "bad request: No service registered under given address '/private/identity/Get'.", {'jsonrpc': '2.0', 'id': 4622765855815754544, 'error': {'code': -32000, 'message': "bad request: No service registered under given address '/private/identity/Get'."}})
5
[2020-11-27 15:43:12,592 INFO yapapi.summary] Agreement proposed to provider 'ada'
6
[2020-11-27 15:43:13,961 INFO yapapi.summary] Agreement confirmed by provider 'ada'
7
[2020-11-27T14:43:15Z ERROR ya_service_bus::remote_router] bind error: already registered: Service ID '/public/gftp/ee82d5dc7188611da558c76e777a2df7867d9526eac6fa9378728d44ca4a2a10/GetMetadata' already registered
8
[2020-11-27T14:43:15Z ERROR ya_service_bus::remote_router] bind error: already registered: Service ID '/public/gftp/ee82d5dc7188611da558c76e777a2df7867d9526eac6fa9378728d44ca4a2a10/GetChunk' already registered
9
[2020-11-27 15:43:15,199 WARNING yapapi.summary] Activity failed on provider 'ada', reason: (-32000, "bad request: No service registered under given address '/private/identity/Get'.", {'jsonrpc': '2.0', 'id': 1935240589707464482, 'error': {'code': -32000, 'message': "bad request: No service registered under given address '/private/identity/Get'."}})
Copied!
Solution: Type which gftp to find the obsolete version of gftp and then remove it. Then restart your daemon and the issue should be fixed!

Troubleshooting - Previous

Provider Troubleshooting

Next - Developer tutorials

Requestor development: a quick primer

Last modified 1mo ago

Copy link

Contents

IO error: No such file or directory

Send error: send failed because receiver is gone

Symlink issues

Connectivity issue

Payment driver initialization issue

Bind error: already registered