Farming flax/chives not visible in GUI ? #416

Enissay · 2021-11-15T20:45:52Z

Enissay
Nov 15, 2021

HI all,

I have an existing wallet with chia, I just moved to machianis (docker-compose) and I want also to farm Flax/Chives...
However, when importing my existing wallet, I do not see any info about the other coins... I do see however that all containers are up and running:

~$ docker ps
CONTAINER ID   IMAGE                                         COMMAND                  CREATED          STATUS          PORTS                                                                                                                                                                        NAMES
f93e13bf9b6a   ghcr.io/guydavis/machinaris-flax:latest       "bash ./entrypoint.sh"   52 minutes ago   Up 52 minutes   0.0.0.0:6885->6885/tcp, :::6885->6885/tcp, 8444/tcp, 8447/tcp, 0.0.0.0:6888->6888/tcp, :::6888->6888/tcp, 0.0.0.0:8928->8928/tcp, :::8928->8928/tcp, 8926-8927/tcp           machinaris-flax
b980a3e6d410   ghcr.io/guydavis/machinaris-chives:latest     "bash ./entrypoint.sh"   52 minutes ago   Up 52 minutes   8444/tcp, 8447/tcp, 0.0.0.0:8931->8931/tcp, :::8931->8931/tcp, 0.0.0.0:9647->9647/tcp, :::9647->9647/tcp, 8926-8927/tcp, 0.0.0.0:9699->9699/tcp, :::9699->9699/tcp           machinaris-chives
9a71e9e53ffd   ghcr.io/guydavis/machinaris:latest            "bash ./entrypoint.sh"   52 minutes ago   Up 52 minutes   0.0.0.0:8444->8444/tcp, :::8444->8444/tcp, 0.0.0.0:8447->8447/tcp, :::8447->8447/tcp, 0.0.0.0:8926-8927->8926-8927/tcp, :::8926-8927->8926-8927/tcp                          machinaris

What am I missing ? should I crate a new wallet that will be linked to all ?

Here's my main page which is still syncing:

Also, it is not detecting any of my existing plots passed to: plots_dir=/hdd01:/hdd02. Will it become visible once syncing has finished or something is wrong ?

I am new to machianis, please let me know if any details needed

Answered by guydavis

Nov 15, 2021

Hi, glad to hear all those questions were answered. Not sure, what you mean by evo, but if you are not plotting, then don't mount a 'Plotting Temp' volume. You're certainly not forced to provide one in-order to generate a docker-compose.yml:

Regarding Chives, please consult the Workers page. If you don't see a row for Chives, then check the following logs:

~/.machinaris-chives/machinaris/logs/apisrv.log
docker logs -f machinaris-chives

EDIT: Typo in my screenshots, obviously don't use /hdd01 twice as I did.

View full answer

guydavis · 2021-11-15T20:56:09Z

guydavis
Nov 15, 2021
Maintainer

Welcome! No, if you followed the Getting Started guide and either created or imported a key during Machinaris setup, then the other fork containers will be able to use it. At this point it looks like you are syncing from scratch the 3 blockchains (Chia, Flax, Chives). That can take a couple of days.

Regarding your plots directories, try this from a shell and let me know what you see:

docker exec -it machinaris bash
env | grep -i plots_dir
chia plots show
ls -1 /hdd001 | wc -l
ls -1 /hdd002 | wc -l

Also, please confirm for me that you chose to override the default in-container path of /plots1, /plots2 instead choosing in-container paths of /hdd001 and /hdd002. Please share with me the exact paths to those volume mounts on your host system. The easiest way to do this would be to paste the full contents of the docker-compose.yml you generated at https://www.machinaris.app. Thanks!

0 replies

Enissay · 2021-11-15T21:35:49Z

Enissay
Nov 15, 2021
Author

@guydavis thank you for the fast reply.
Actually, I have imported my key and I am fine to get a fresh sync.

As of the drives, I found a mistake as I was mounting the drives root folder rather than the subdir which contained the plots. Corrected and relaunched and now all plots are visible.
I confirm also that I am not using the default in-container path of /plots1, /plots2. Is it fine ? It was easier for me this way to use the same naming for my drives...
It is worth noting as well that I am not plotting on this machine, so both evo mounts are not really used (both empty) but I had to fill them else the wizard was not generating the yaml file xD

Here's my docker-compose.yml file:

version: '3.7' 
services: 
    machinaris: 
        image: ghcr.io/guydavis/machinaris:latest 
        container_name: machinaris 
        hostname: chachacha 
        restart: always 
        volumes: 
            - ~/.machinaris:/root/.chia 
            - "/mnt/evo/chia/temp:/evo_temp" 
            - "/mnt/evo/chia/final:/evo_final" 
            - "/mnt/hdd01/chia_final:/hdd01" 
            - "/mnt/hdd02/chia_final:/hdd02" 
        environment: 
            - TZ=Europe/Brussels 
            - mode=fullnode 
            - worker_address=192.168.1.133 
            - plots_dir=/evo_final:/hdd01:/hdd02
            - blockchains=chia 
        ports: 
            - 8926:8926 
            - 8927:8927 
            - 8444:8444 
            - 8447:8447 
             
    machinaris-chives: 
        image: ghcr.io/guydavis/machinaris-chives:latest 
        container_name: machinaris-chives 
        hostname: chachacha 
        restart: always 
        volumes: 
            - ~/.machinaris-chives:/root/.chia 
            - ~/.machinaris/mnemonic.txt:/root/.chia/mnemonic.txt:ro 
            - "/mnt/evo/chia/temp:/evo_temp" 
            - "/mnt/evo/chia/final:/evo_final" 
            - "/mnt/hdd01/chia_final:/hdd01" 
            - "/mnt/hdd02/chia_final:/hdd02" 
        environment: 
            - TZ=Europe/Brussels 
            - mode=fullnode 
            - controller_host=192.168.1.133 
            - worker_address=192.168.1.133 
            - worker_api_port=8931 
            - plots_dir=/evo_final:/hdd01:/hdd02
            - blockchains=chives 
        ports: 
            - 8931:8931 
            - 9699:9699 
            - 9647:9647 
        depends_on: 
            - machinaris

So far, my only remaining question is: Why there's no info about Chives in GUI ?

0 replies

guydavis · 2021-11-15T21:49:09Z

guydavis
Nov 15, 2021
Maintainer

Hi, glad to hear all those questions were answered. Not sure, what you mean by evo, but if you are not plotting, then don't mount a 'Plotting Temp' volume. You're certainly not forced to provide one in-order to generate a docker-compose.yml:

Regarding Chives, please consult the Workers page. If you don't see a row for Chives, then check the following logs:

~/.machinaris-chives/machinaris/logs/apisrv.log
docker logs -f machinaris-chives

EDIT: Typo in my screenshots, obviously don't use /hdd01 twice as I did.

0 replies

Enissay · 2021-11-15T22:36:58Z

Enissay
Nov 15, 2021
Author

Docker logs doesnt say anything:

$ docker logs -f machinaris-chives
Welcome to Machinaris! - v0.6.4 - fullnode
Configuring Chives...
Adding key at path: /root/.chia/mnemonic.txt
Added plot directory "/hdd01".
Added plot directory "/hdd02".
Daemon not started yet
Starting daemon
chives_harvester: started
chives_farmer: started
chives_full_node: started
chives_wallet: started
Configuring Plotman...
Configuring Chiadog...
Starting Chiadog...
Starting Machinaris API server...
Starting Machinaris Web server...
Completed startup.  Browse to port 8926.
Starting farmr for chives in Farmer mode...


============================================

Your id is a27_xxx_cc, visit https://farmr.net to add it to your account.
Alternatively, you can also link it through farmrbot (a discord bot) by running the following command:

!chia link a27_xxx_cc

to link this client to your discord user
You can interact with farmrbot in Swar's Chia Community
Open the following link to join the server: https://discord.gg/fghFbffYsC

============================================

Buy plots from the cheapest automated plotting service in the world at expressplots.com!

Running in headless mode
No plots have been found! Make sure your user has access to the folders where plots are stored.


ID a27_xxx_cc is not linked to an account.
Link it in farmr.net or through farmrbot and then start this program again
Press enter to quit

The logfile however after a while spits a lot of errors, here' a sample:

2021-11-15 23:27:35 [664] [INFO] Job "keys (trigger: interval[0:02:00], next run at: 2021-11-15 23:30:08 CET)" executed successfully
2021-11-15 23:27:35 [664] [INFO] Running job "partials (trigger: interval[0:02:00], next run at: 2021-11-15 23:30:29 CET)" (scheduled at 2021-11-15 23:27:35.401894+01:00)
2021-11-15 23:27:37 [664] [INFO] Running job "pools (trigger: interval[0:02:00], next run at: 2021-11-15 23:30:29 CET)" (scheduled at 2021-11-15 23:27:37.544068+01:00)
2021-11-15 23:27:37 [664] [INFO] Job "pools (trigger: interval[0:02:00], next run at: 2021-11-15 23:30:29 CET)" executed successfully
2021-11-15 23:27:38 [664] [INFO] Running job "connections (trigger: interval[0:02:00], next run at: 2021-11-15 23:30:31 CET)" (scheduled at 2021-11-15 23:27:38.747763+01:00)
2021-11-15 23:27:43 [664] [INFO] Failed to load plotting summary and send.
2021-11-15 23:27:43 [664] [INFO] Failed to load plotting summary and send.
2021-11-15 23:27:43 [664] [INFO] Traceback (most recent call last):
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/util/connection.py", line 96, in create_connection
    raise err
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/util/connection.py", line 86, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 699, in urlopen
    httplib_response = self._make_request(
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 394, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connection.py", line 239, in request
    super(HTTPConnection, self).request(method, url, body=body, headers=headers)
  File "/usr/lib/python3.9/http/client.py", line 1253, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.9/http/client.py", line 1299, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.9/http/client.py", line 1248, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.9/http/client.py", line 1008, in _send_output
    self.send(msg)
  File "/usr/lib/python3.9/http/client.py", line 948, in send
    self.connect()
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connection.py", line 205, in connect
    conn = self._new_conn()
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connection.py", line 186, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7fb0a434df40>: Failed to establish a new connection: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/chives-blockchain/venv/lib/python3.9/site-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 755, in urlopen
    retries = retries.increment(
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/util/retry.py", line 574, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.1.133', port=8927): Max retries exceeded with url: /plottings/192.168.1.133/chives (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fb0a434df40>: Failed to establish a new connection: [Errno 110] Connection timed out'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/machinaris/api/schedules/status_plotting.py", line 45, in update
    utils.send_delete('/plottings/{0}/{1}'.format(hostname, blockchain), debug=False)
  File "/machinaris/api/utils.py", line 42, in send_delete
    response = requests.delete(controller_url + path, headers = headers)
  File "/chives-blockchain/venv/lib/python3.9/site-packages/requests/api.py", line 159, in delete
    return request('delete', url, **kwargs)
  File "/chives-blockchain/venv/lib/python3.9/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/chives-blockchain/venv/lib/python3.9/site-packages/requests/sessions.py", line 542, in request
    resp = self.send(prep, **send_kwargs)
  File "/chives-blockchain/venv/lib/python3.9/site-packages/requests/sessions.py", line 655, in send
    r = adapter.send(request, **kwargs)
  File "/chives-blockchain/venv/lib/python3.9/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.1.133', port=8927): Max retries exceeded with url: /plottings/192.168.1.133/chives (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fb0a434df40>: Failed to establish a new connection: [Errno 110] Connection timed out'))

2021-11-15 23:27:43 [664] [INFO] Traceback (most recent call last):
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/util/connection.py", line 96, in create_connection
    raise err
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/util/connection.py", line 86, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 699, in urlopen
    httplib_response = self._make_request(
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 394, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connection.py", line 239, in request
    super(HTTPConnection, self).request(method, url, body=body, headers=headers)
  File "/usr/lib/python3.9/http/client.py", line 1253, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib/python3.9/http/client.py", line 1299, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.9/http/client.py", line 1248, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.9/http/client.py", line 1008, in _send_output
    self.send(msg)
  File "/usr/lib/python3.9/http/client.py", line 948, in send
    self.connect()
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connection.py", line 205, in connect
    conn = self._new_conn()
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connection.py", line 186, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7fb0a434df40>: Failed to establish a new connection: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/chives-blockchain/venv/lib/python3.9/site-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/connectionpool.py", line 755, in urlopen
    retries = retries.increment(
  File "/chives-blockchain/venv/lib/python3.9/site-packages/urllib3/util/retry.py", line 574, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.1.133', port=8927): Max retries exceeded with url: /plottings/192.168.1.133/chives (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fb0a434df40>: Failed to establish a new connection: [Errno 110] Connection timed out'))

1 reply

guydavis Nov 15, 2021
Maintainer

I would restart both containers. Your Chives container is attempting to reach the main Machinaris container at http://192.168.1.133:8927 and failing, so either the API server is down or the networking is not configured correctly. A restart should rule out one of those. Please review the log output of ~/.machinaris/machinaris/logs/apisrv.log too.

Enissay · 2021-11-16T01:29:12Z

Enissay
Nov 16, 2021
Author

It finally works after opening all ports in my machine's firewall sudo ufw allow 8928:9836/tcp. I have launched all 9 containers and they are all connected and syncing. is this fix OK ?
Well, all except cactus whose blockchain says:

Searching for an initial chain

You may be able to expedite with 'cactus show -a host:port' using a known node.

Blockchain has no blocks yet

I don't get what needs to be done ?

Finally, given I only have free 120GB in main disk in which these containers are deployed, I wonder if this size is enough ? I know that my previous chia folder alone was almost 20GB, so I wonder what the final size will be for all xD
I have another ssd 1TB (D:) that I can use if needed but then how to move the installation ? Or just adapting the left part of the volumes mount will do the trick :

...
        volumes: 
            - ~/.machinaris-cactus:/root/.chia 
            - ~/.machinaris/mnemonic.txt:/root/.chia/mnemonic.txt:ro 
            - ...

1 reply

guydavis Nov 16, 2021
Maintainer

Great! If you want to run all the containers you may need a bit more space on your SSD:

That said, all the forks (except Chia) are optional so pick and choose the ones you actually want to run. Yes, you can move the volume mounts around for sure, but please keep them on an SSD for speed.

For Cactus, it will eventually find nodes. You can also visit xchforks.com, grab some IP_ADDR:11444 nodes from the bottom of the page. Then go to Machinaris, Connections page, Cactus tab, paste the node address:port and click 'Add Connection'. That will get you syncing faster.

Please mark this discussion as Answered. Glad to help.

Enissay · 2021-11-16T01:37:53Z

Enissay
Nov 16, 2021
Author

Gotcha, thank you so much <3 it was quite a ride xD

0 replies

Enissay · 2021-11-16T15:39:55Z

Enissay
Nov 16, 2021
Author

@guydavis I am back for one last question: I am using a small machine for farming and syncing is using all resources (CPU at 100%) and at this pace it might take up to 10 days ty fully sync.
I saw the section on how to speed this up, but I was wondering if I simply replace the mainnet/db with my old one, it should be fine right ?
What if I do the syncing in another machine (more powerful, last time it took 2 days only) then do the swap of that folder, that should work as well right ? I am just hestating since machines have different certificates so I am not sure that moving files across will keep them compatible

2 replies

guydavis Nov 16, 2021
Maintainer

Good question. Yes, the standard sync option where the entire blockchain database is pulled down from various network peers can take days. There are two other options, import your own, or download a blockchain DB file itself. Both have pros/cons. Please see the wiki for details.

If you decide to try the 'Download New' option, you'll need to delete your existing mainnet folder first, before adding environment variable of blockchain_db_download

Alternatively you'll need to import an old blockchain db you may have from an other install. This often works, but not always. Hope this helps!

guydavis Nov 17, 2021
Maintainer

Now that this Github discussion thread has covered numerous questions and answers, would you mind marking the thread as Answered. Also, for such highly interactive Q&A sessions, perhaps you would get more out of the Machinaris Discord server. Thanks!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Farming flax/chives not visible in GUI ? #416

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 7 comments 4 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Farming flax/chives not visible in GUI ? #416

Enissay Nov 15, 2021

Replies: 7 comments · 4 replies

guydavis Nov 15, 2021 Maintainer

Enissay Nov 15, 2021 Author

guydavis Nov 15, 2021 Maintainer

Enissay Nov 15, 2021 Author

guydavis Nov 15, 2021 Maintainer

Enissay Nov 16, 2021 Author

guydavis Nov 16, 2021 Maintainer

Enissay Nov 16, 2021 Author

Enissay Nov 16, 2021 Author

guydavis Nov 16, 2021 Maintainer

guydavis Nov 17, 2021 Maintainer

Enissay
Nov 15, 2021

Replies: 7 comments 4 replies

guydavis
Nov 15, 2021
Maintainer

Enissay
Nov 15, 2021
Author

guydavis
Nov 15, 2021
Maintainer

Enissay
Nov 15, 2021
Author

guydavis Nov 15, 2021
Maintainer

Enissay
Nov 16, 2021
Author

guydavis Nov 16, 2021
Maintainer

Enissay
Nov 16, 2021
Author

Enissay
Nov 16, 2021
Author

guydavis Nov 16, 2021
Maintainer

guydavis Nov 17, 2021
Maintainer