on July 31st 21:58 UTC
"https://akash-01.crono.co:8443"
"https://d3akash.cloud:8443"
"https://provider.akash.rocks:8443"
"https://provider.akash.world:8443"
"https://provider.akt.computer:8443"
Andrey Arapov andy108369
🎯
andy108369
/ sign-new-provider-attributes.md
Last active
August 21, 2022 20:02
andy108369
/ akash-recover-from-apphash-error.md
Last active
November 12, 2023 01:11
Recovering from the AppHash error without having to use snapshot / state-sync
Follow this doc https://gist.github.com/andy108369/da1279257c018be6370310c990c25738
With the 0.14.x client's TX create certificate transaction sent over 0.16.4 RPC causing the majority of 0.16.3 to reject that TX, it in turn caused the minority of 0.16.4 validators halt at 6955214 block.
This is due to this commit in 0.16.4 which allowed old type of TX be present in the block whilst 0.16.3 - did not.
andy108369
/ sleep-beta3.md
Created
July 29, 2022 12:06
beta3 NVME persistent storage deployment manifest example
It deploys an app with the 10GiB of persistent storage mounted over /opt/data path.
The image used ubuntu:22.04 with sleep infinity, so it does nothing, just sleeps..
So you can akash provider lease-shell into your deployment and inspect the storage.
---
andy108369
/ api-error.md
Created
July 28, 2022 10:17
— forked from aursu/api-error.md
ACPI Error: AE_NOT_EXIST, Evaluating _PMM (20190816/power_meter-325)
The same problem on an HP server and there is a smarter solution found here: https://www.novell.com/support/kb/doc.php?id=7010449
Instead of disabling sensors in netdata altogether, you can just disable the acpi_power_meter kernel module, which doesn't work anyway on affected HP servers due to a BIOS bug. This way netdata can still get the temperature readings.
This is how you can disable the module immediately:
sudo modprobe -r acpi_power_meter
And this is how you make it permanent:
NewerOlder