Hi,
mainnet-grid3_client-1 | yarn run v1.22.19
Hi,
the .env file but make sure to cover up your secret
the markdown file containing your farmerbot configuration
the docker-compose file
Did you properly setup your .env file? Here is how it should look like:
SECRET="MNEMONIC_OR_HEX_SECRET_OF_YOUR_FARM"
NETWORK=main
RELAY=wss://relay.grid.tf:443
SUBSTRATE=wss://tfchain.grid.tf:443
Has the configuration changed from the previous farmerbot? Because I have been running it for several months…
The .env has always been required. Though as it starts with a dot you won’t be able to see it by doing ls. You need to type ls -a
found it! it is just a .env file without a name
root@erwin-Inspiron-1750:~/mainnet# sudo docker compose up
[+] Running 5/5
✔ Network mainnet_default Created 0.6s
✔ Container mainnet-redis-1 Created 1.9s
✔ Container mainnet-grid3_client-1 Created 0.8s
✔ Container mainnet-rmbpeer-1 Created 0.8s
✔ Container mainnet-farmerbot-1 Created 0.9s
Attaching to mainnet-farmerbot-1, mainnet-grid3_client-1, mainnet-redis-1, mainnet-rmbpeer-1
mainnet-redis-1 | 1:C 15 Sep 2023 14:26:24.209 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
mainnet-redis-1 | 1:C 15 Sep 2023 14:26:24.209 # Redis version=7.0.8, bits=64, commit=00000000, modified=0, pid=1, just started
mainnet-redis-1 | 1:C 15 Sep 2023 14:26:24.209 # Configuration loaded
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.210 * Increased maximum number of open files to 10032 (it was originally set to 1024).
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.210 * monotonic clock: POSIX clock_gettime
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.212 * Running mode=standalone, port=6379.
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.212 # Server initialized
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.212 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.213 * Loading RDB produced by version 7.0.8
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.213 * RDB age 13 seconds
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.213 * RDB memory usage when created 3.39 Mb
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.245 * Done loading RDB, keys loaded: 1425, keys expired: 0.
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.245 * DB loaded from disk: 0.032 seconds
mainnet-redis-1 | 1:M 15 Sep 2023 14:26:24.246 * Ready to accept connections
mainnet-grid3_client-1 | yarn run v1.22.19
mainnet-grid3_client-1 | warning package.json: No license field
mainnet-grid3_client-1 | $ /node_modules/.bin/grid_http_server -c /root/config.json
mainnet-grid3_client-1 | 2023-09-15 14:28:43 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-15 14:30:56 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
dependency failed to start: container mainnet-grid3_client-1 is unhealthy
root@erwin-Inspiron-1750:~/mainnet#
Can you confirm if you have updated the docker compose file?
Hello farmers,
Due to a communication hiccup, we released Grid 3.11 yesterday without a timely notification that this release requires an update to the farmerbot. Thanks to all the farmers who let us know as soon as they saw an issue.
If you haven’t done it yet, please update your farmerbot by applying the latest Docker Compose file using the commands shown below:
x64 (AMD/Intel)
docker compose rm -f -s -v
rm docker-compose.yaml
wget https://raw.githubusercontent.com/threefoldtech/farmerbot/…
scott
September 18, 2023, 9:14pm
10
Please double check that your .env uses a SECRET field rather than MNEMONIC. The latter was the old form that’s been deprecated.
Hi Scott, it does use the SECRET property, and I removed docker-compose.yaml again and and re-did all the removal and installation but when doing compose up it keeps throwing the error after the
The previous version of the farmerbot worked fine for the last couple of weeks, no hicups, but I cannot get this version to work…
Amanda
September 20, 2023, 8:20am
12
Hello @TFFarmer ! Can you also send the complete log file to us, please? You can get the log file by going to docker-compose logs > containers.log
I have no idea where to find those logs, but if I do a docker compose logs, this is what I get:
root@erwin-Inspiron-1750:~/mainnet/config# docker compose logs
mainnet-redis-1 | 1:C 19 Sep 2023 07:09:03.942 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
mainnet-redis-1 | 1:C 19 Sep 2023 07:09:03.942 # Redis version=7.0.8, bits=64, commit=00000000, modified=0, pid=1, just started
mainnet-redis-1 | 1:C 19 Sep 2023 07:09:03.942 # Configuration loaded
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.944 * Increased maximum number of open files to 10032 (it was originally set to 1024).
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.944 * monotonic clock: POSIX clock_gettime
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.947 * Running mode=standalone, port=6379.
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.947 # Server initialized
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.948 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.949 * Loading RDB produced by version 7.0.8
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.949 * RDB age 200 seconds
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.949 * RDB memory usage when created 3.39 Mb
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.978 * Done loading RDB, keys loaded: 1425, keys expired: 0.
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.979 * DB loaded from disk: 0.030 seconds
mainnet-redis-1 | 1:M 19 Sep 2023 07:09:03.979 * Ready to accept connections
mainnet-grid3_client-1 | yarn run v1.22.19
mainnet-grid3_client-1 | warning package.json: No license field
mainnet-grid3_client-1 | $ /node_modules/.bin/grid_http_server -c /root/config.json
mainnet-grid3_client-1 | 2023-09-19 07:11:24 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:13:37 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:15:50 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:18:03 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:20:16 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:22:30 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:24:43 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:26:56 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:29:09 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:31:22 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:33:35 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:35:48 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:38:01 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:40:15 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:42:28 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:44:41 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
mainnet-grid3_client-1 | 2023-09-19 07:46:54 API-WS: disconnected from wss://tfchain.grid.tf/ws: 1006:: connection failed
Shang4u
September 22, 2023, 11:05am
14
Hi TFFarmer, If you can send/share the complete docker compose logs > containers.log that will be helpful for troubleshooting.
Hi, yes I did run all commands, making sure .yaml file was relaced.
Farm has been down for over 2 weeks now… sorry but that is not what I would expect in terms of support!
Shang4u
September 26, 2023, 9:13am
17
It may be removed/deleted. Please check with the default location for container.log files on your Docker host. On Linux: /var/lib/docker/containers/<container_id>. On Windows: C:\ProgramData\Docker\containers<container-id>-json.log. Also, please get in touch with our support here . We will be glad to help you.