Hello @CFG - Thanks for reaching out & posting on the MS Q&A!
The Host lock lease acquired by instance ID '0000000000000000000000009DDF0CE1'
log output is not an error but a simple message notifying you that your Function App was started with the quoted instance ID and was also able to acquire a lock lease to the storage defined for the AzureWebJobsStorage
setting. If you're having trouble starting your Functions App locally, the underlying issue is likely agnostic of this message, so if this is the case for you, please share more details in the comments and I'd be happy to help & get you unblocked.
For more context on the lock lease message, Azure Functions require a storage solution for it to run & operate with the features it provides, and these storage solutions vary depending on your unique requirements.
- If you're running locally, you're most likely using the Azurite storage emulator, please refer: Use the Azurite emulator for local Azure Storage development
- If you're running on Azure, there are various considerations: Storage considerations for Azure Functions
Here are a couple of StackOverflow threads on the same question you've raised:
- What is the reason for host lock lease acquired by instance id in Azure function?
- Error in Azure function - Host lock lease acquired by instance ID '0000000000000000000000006000A33F'
I hope this info is helpful, please let me know in the comments if you have any further questions.