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

Failed to sync ephemeral account when no price table found #801

Closed
mike76-dev opened this issue Dec 7, 2023 · 2 comments · Fixed by #906
Closed

Failed to sync ephemeral account when no price table found #801

mike76-dev opened this issue Dec 7, 2023 · 2 comments · Fixed by #906
Assignees

Comments

@mike76-dev
Copy link
Contributor

mike76-dev commented Dec 7, 2023

Describe the bug

The autopilot fails to sync an EA when the host reports that no price table is found.

2023-12-07T10:41:57+01:00	ERROR	autopilot.accounts	autopilot/accounts.go:166	failed to sync account's balance: couldn't sync account: unable to fetch revision with contract: LatestRevision: ReadResponse: failed to read price table: no price table found
	{"accountID": "ed25519:486a8ec1183e1c85514e8c555d5f1280ea5c84274e3433bb8dced401ded8efe5", "hostKey": "ed25519:c235ba78d874a3906ff3db6afc2e364f9b77e805acbccc1f6ec61a91f0b238b2"}

There are also related errors. Looks like the latest revision can't be fetched for the same reason:

2023-12-07T11:04:22+01:00	ERROR	autopilot.accounts	autopilot/accounts.go:166	failed to sync account's balance: couldn't sync account: unable to fetch revision with contract: LatestRevision: ReadResponse: failed to read price table: no price table found
	{"accountID": "ed25519:46def458567cc80edcf45962317907e52dbacb560328e6c82b732011a524fea9", "hostKey": "ed25519:9501d2bc7d622f387c23630388e43339f02389aa45e709f9c5ef1a9ac51356b3"}

Expected behaviour

If the host can't find the price table, a new price table should be requested.

Additional context

The contracts were imported from the satellite, this is probably why no price table is found.

General Information

Are you running a fork of renterd? Yes, but the errors appear on the master branch as well
Are you on the mainnet or on the testnet? Mainnet

Renterd Config

Please provide us the following information:

Autopilot Config

{
	"contracts": {
		"set": "autopilot",
		"amount": 20,
		"allowance": "1000000000066666666666666667",
		"period": 1008,
		"renewWindow": 202,
		"download": 93333333333,
		"upload": 9333333333,
		"storage": 10000000000
	},
	"hosts": {
		"allowRedundantIPs": false,
		"maxDowntimeHours": 1440,
		"minRecentScanFailures": 10,
		"scoreOverrides": null
	},
	"wallet": {
		"defragThreshold": 1000
	}
}

Bus Config

{
	"minShards": 3,
	"totalShards": 9
}

{
	"hostBlockHeightLeeway": 6,
	"maxContractPrice": "1000000000000000000000000",
	"maxDownloadPrice": "1200000000000000000000000000",
	"maxRPCPrice": "1000000000000000000000",
	"maxStoragePrice": "69444444444",
	"maxUploadPrice": "100000000000000000000000000",
	"migrationSurchargeMultiplier": 10,
	"minAccountExpiry": 86400000000000,
	"minMaxCollateral": "10000000000000000000000000",
	"minMaxEphemeralAccountBalance": "1000000000000000000000000",
	"minPriceTableValidity": 300000000000
}

Contract Set Contracts

11

Renterd Logs

If applicable, upload your renterd.log file or part of the file you think is relevant to the issue.

@ChrisSchinnerl
Copy link
Member

What commit are you on? We merged. a PR (#792) yesterday which might have fixed this issue.

@mike76-dev
Copy link
Contributor Author

The last commit is 23cb783 (parents e876aa5 + 6da810d), so looks like I merged the #792.

@ChrisSchinnerl ChrisSchinnerl moved this to Todo in Sia Dec 7, 2023
@peterjan peterjan moved this from Todo to In Review in Sia Jan 18, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in Sia Jan 19, 2024
@ChrisSchinnerl ChrisSchinnerl moved this from Done to Released in Sia Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants