Trinity
-
Posts
27 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Trinity
-
-
4 hours ago, Bawb3 said:
I won with 166 plots, so there's still a chance... I don't know how statistically lucky I am at this point. But if you've already got your plots rolling why shut them off, just let them go and see if you win something. Once the plots are done you don't use much energy farming them.
PS thanks to everyone in this thread helping folks, I used this to get my farm set up on UnRaid and couldn't be happier with the results. I was running them in a windows VM prior, and it was terrible.
Yeah, throwing away would hurt indeed. But on the other hand, I could use that space for something else. Tough decision.
But at least it's good to know, it is possible - So I might just continue.
The only thing I am just not sure about is, how to determine, if I could "technically" win. As far as I know, there are some time limits on farm responding time. How do I figure out, if I am fast enough - So that I could win, if I am lucky enough. Would be pretty bad to have the chance but loose it due to the system setup. Any tipps on that?
Thank you
-
Hmm, okay. I am at ~190 Plots and will max out at ~360 Plots when I fill my whole free space. While plotting I am working actively on killing the SSD... If the chances to farm any coin are so unlikely, what's the point in continuing. As far as I know, pools require to throw away all plots and start over again to kill another SSD...
Funny how "Independant currency for everybody" turned into "Rich become leveraged Richer" -
Did anyone here ever "won" anything?
-
1 hour ago, unririd said:
I try to follow all replies here, but different answers seem to be contradicting - is fixing the timezone solving the sync issue for most of the cases?
And a supporting question: I copied all plots to unraid share, but I'm still using the full node on my PC to farm these plots (via network directory on unraid) until the docker will sync. What will happen when 2 devices with the same synced full node (the same mnemonic) will farm the same plots? I assume that I will not have 2x chance to win...
I am still not deep enough into the whole topic, but I for myself can say: Adjusting the clock didn't fix the sync issue. For me it's even worse, the syncing stopped completely. Right now I am far behind the blockchain, which makes farming impossible. Will have to recreate the container.
That's why I still don't understand the official FAQ which states, that the clock shouldn't be more than 5 minutes off. At least for the docker container it seems to be wrong. Or there are additional issues, the docker container have. Because of that I plan to move away from it and don't use the chia docker as a full node for now.
Running two full nodes could be possible, but not with the same ports and keys. And maybe also not with the same plots. I don't know if the plots are portable, I think it's possible to migrate them to another key, but they can not be used of two farmers at the same time. At least it would make sense like that
Not sure, what will happen if there are two full nodes with the same keys and ports running in the network at the same time, but I would expect it will disturb each other.
1 hour ago, adminmat said:I can see INFO items in the log when I'm open the log via the container's icon. But when I look at debug.log there is nothing there other than the inital warnings before I made changes to the .yaml file.
The log_stdout: true writes the logs into the standard output, so it is no longer logging into a file. So of course the log file is empty. If your unraid is not grabbing the stdout and writes logs itself, there's no file to find the logs. If I am not wrong ^^"
-
Thank you again for the very detailed answer! I can't wait to get my hands on the pi, I hope I get it installed - Some things you explain sound pretty complex, like getting the OS on the SSD. I thought I could boot from the SD ans install it on the SSD like in normal computers
Not sure how to flash the SSD on my PC without a external m.2 port ^^
1 hour ago, Gnomuz said:Note that apart from the enclosure, it's highly recommended to buy the matching power supply by Argon with 3.5A output. The default RPi4 PSU is 3.1A, which is fine with the OS on a SD card, but adding a SATA M.2 SSD draws more current, and 3.5A avoids any risk of instability. The Canakit 3.5A power adapter is fine also, but not available in Europe for me.
Oh, I saw that there are bundles at berrybase and ordered it, which includes the official power supply. I searched for the two mentioned ones, but I only found them on amazon, but they are not available. So it seems like, those are pretty hard to get? Sitting in Europe as well, so no idea, where to get it. What if I use the official one, will it give me a headache? What could I do, if I don't find any store selling those PSUs?
-
3 hours ago, MajorTomG said:
@Trinity You seem to have had exactly the same issue that I'm having. My farm is farming, my current blockchain status is "Full Node Synced", but my Wallet status is "Not Synced". Did you or anyone else find a solution in the end?
Only thing I can think of is that I created a wallet on the Windows client, and added it to the docker via the mnemonic.txt method, rather than generating in the docker its self.
Sadly I didn't solve it yet. I ordered a pi4 now and will change my setup, so I'll run the full node on that pi device and using my unraid server for harvesting only. I tried fixing the clock, rebuild the container alot of times but my wallet was never synced since ever. I have no idea, what the ploblem is. I wanted to post my log here, but right know it's again way to large to be helpful. Tonight I will rebuild the container again, clear the log and let it run for some time and see, if I can get back to that point, where the node is fully synced and the farmer is running. If my wallet is then still not synced I will post my log files here and hope someone here has an idea, what the actual issue is.
-
1
-
-
46 minutes ago, abra8c said:
My time is also delayed by exactly 2h but it says everything is synced.
Is everything ok when it is synced or should I worry about the 2h?If everything is in sync, don't worry. For me fixing the time caused a lot of trouble. I still need to confirm it, but there is a change I lost 2 days of plotting due to chaning the clock, because right now the node is not seeing any of the plots I created since I changed the clock, so better don't do it, especially if everything works!
-
10 hours ago, Gnomuz said:
Hi,
Thanks for your interest in my post, I'll try to answer your numerous questions, but I think you already got the general idea of the architecture pretty well 😉
- The RPi doesn't have a M.2 slot out of the box. By default, the OS runs from a SD card. The drawback is that SD cards don't last so long when constantly written, e.g. by the OS and the chia processes writing logs or populating the chain database, they were not designed for this kind of purpose. And you certainly don't want to lose your chia full node because of a failing 10$ SD card, as the patiently created plots are still occupying space, but do not participate in any challenge... So, I decide running the RPi OS from a small SATA SSD was a much more resilient solution, and bought an Argon One M.2 case for the RPi. I had an old 120 GB SATA SSD which used to host the OS of my laptop before I upgraded it to a 512 GB SSD, so I used it. This case is great because it's full-metal and there are thermal pads between the CPU and RAM and the case. So, it's essentially a passive heat dissipation setup. There's a fan if temps go too high, but it never starts, unless you live in a desert I suppose. There are many other enclosures for RPis, but this one is my favorite so far.
- The RPi is started with the 'chia start farmer' command, which runs the following processes : chia_daemon, chia_full_node (blockchain syncing), chia_farmer (challenges management and communication with the harvester(s)) and chia_wallet. chia_harvester is also launched locally, but is totally useless, as no plots are stored on a storage accessible by the RPi. To get a view on this kind of distributed setup, have a look at https://github.com/Chia-Network/chia-blockchain/wiki/Farming-on-many-machines, that was my starting point. You can also use 'chia start farmer-no-wallet', and sync your wallet on another machine, I may do that in the future as I don't like having it on the machine exposed to the internet.
- The plotting rig doesn't need any chia service running on it, the plotting process can run offline. You just need to install chia on it, and you don't even need to have your private keys stored on it. You just run 'chia plots create (usual params) -f <your farmer public key> -p <your pool public key>' , and that's all. The created plots will be farmed by the remote farmer once copied into the destination directory.
- I decided to store the plots on the xfs array with one parity drive. I know the general consensus is to store plots on non-protected storage, considering you can replot them. But I hate the idea of losing a bunch of plots. You store them on high-density storage, let's say 12TB drives, which can hold circa 120 plots each. Elite plotting rigs with enterprise-grade temporary SSDs create a plot in 4 hours or less. So recreating 120 plots is circa 500 hours or 20 days. When you see the current netspace growth rate of 15% a week or more, that's a big penalty I think. I you have 10 disks, "wasting" one as a parity drive to protect the other 9 sounds like a reasonable trade-off, provided you have a spare drive around to rebuild the array in case of a faulty drive. To sum up, two extra drives (1 parity + 1 spare) reasonably guarantee the continuity of your farming process and prevent the loss of existing plots, whatever the size of your array is. Of course with a single parity drive, you are not protected against two drives failing together, but as usual it's a trade-off between available size, resiliency and costs, nothing specific to chia ... And the strength of Unraid is you won't lose the plots on the healthy drives, unlike other raid5 solutions.
- As for the container, it runs only the harvester process ('chia start harvester'), which must be setup as per the link above, nothing difficult. From the container console, you can also optionally run a plotting process, if your Unraid server has a temporary unassigned SSD available (you can also use your cache SSD, but beware of space ...). You will run it just like on your plotting rig : 'chia plots create (relevant params) -f <farmer key> -p <pool key>'. The advantage is that the final copy from the temp dir to the dest dir is much quicker, as it's a local copy on the server from an attached SSD to the Unraid share (10 mins copy vs 20/30 mins over the network for me).
- So yes, you can imagine running your plotting process from a container on the Unraid server if you don't have a separate plotting rig. But then I wouldn't use this early container, and would rather wait for a more mature one which would integrate a plotting manager (plotman or Swar), because managing all that manually is a nightmare on the long run, unless you are a script maestro and have a lot of time to spend on it 😉
Happy farming !
Thank you so much, for the detailed reply
I ordered the pi4 with your recommended case I hope I get it installed easily ^^
May I ask if it would be okay to contact you, in case of questions? ^^"
Generally it should work, I#ll use the sd card to install linux on the ssd and try to get it running - I hope I will be able to move my keys and everything from the docker container to the pi and it will still work. Not sure, if the plots are kind of bound to my keys or if I could just get new ones, since I am in the 0 XCH club anyway Right know, it seems, my node is not getting all my plots right, maybe I broke something by changing the clock to my time zone, I still have some plots running, so I cant rebuild the container to get the default time back. In the worst case I have to delete 16 plots, if they are broken due to the wrong clock...
I hope the new setup will then just work, right now it's pretty frustrating. With every day it doesn't work, it will be less likely to ever win a coin
I can't add parity, since my system is full of HDDs, I am limited to 4x3,5" and thus I don't want to use a quarter of my available space for parity. It's risky, but I just hope the NAS HDDs are just working fine.
One thing I still didn't understand is the plotting with the -f <farmer key> - What key is that? The one the full node prints out when calling chia keys show? Or the one from the harvester container I'll be plotting at?
-
7 minutes ago, mc_handler said:
Thank you so much for this container and for starting such a wonderful thread full of information. I am running into a situation where my Chia Node time is 2 hours off from real time. I've run the date command in console and it's returning the correct time. Because of this time discrepancy, I can't stay synced and therefore I can't do any farming. Has anyone run into this issue? Port 8444 is open and has been checked. Thanks for any help
Yes, around 1-2 pages back, some of us discovered the same issue. Including myself.
I tried to enter the container and to run: apt-get systemd
to set the correct time. Another option would be installing: apt-get tzdata.
There is also an open Pull request on the official chia docker: https://github.com/Chia-Network/chia-docker/pull/50
Not sure if it will solve the issues tbh. Installing it inside the container is only a quick solution, which will be lost when ever the container is rebuild. So not the best solution. Additionally to that, it didn't fix my sync status. I am now kind of more than one hour off and it never reaches the synced status. So it seems to be something different causing these issues. So you can try to get you clock right, but I can't promise it will solve your sync issues. -
12 hours ago, Gnomuz said:
My understanding of the official wiki is that your system clock must not be off by more than 5 minutes, whatever your timezone is, reminded that the clocks (both software and hardware) are managed as UTC by default in Linux.
Anyway, I see that many have problems syncing when running the container as a full node.
Personally I went the Raspberry way and everything is working like a charm so far. The RPi4 4GB boots from an old 120GB SATA M.2 SSD under Ubuntu 20.04.2 (in an Argon One M.2 case which is great btw) and runs the full node. In a first time, I ran the harvester on the RPi and it accessed the plots stored on the Unraid server through a SMB share. Performance was horrible, average was 5-7 seconds to respond, with peaks at more than 30 sec ! I tried NFS which was a bit better, but still too slow, often > 3 sec.
With this container running only the harvester, and connected to the farmer on the RPi, response times are under 0,1 sec at farmer level, it has a negligible footprint on the server and it's rock solid. I also create plots in the container as a bonus, to help my main plotting rig.
If others want to replicate this architecture, I posted a step-by-step a few posts above on how to setup the container as a harvester-only, and connect it to a remote farmer/full node.
An RPi is not a big investment, compared with the storage cost, and as chia was designed as a distributed and decentralised project, I think it's the way to go to have a resilient setup.
This sounds like a really nice setup, but I still didn't fully understand, what you need to extend the farm. Which services do you need running for plotting? Can you plot via the harvesters or via the farmer, which is running together with the full node or does it only require the full node? How many farmers you need, how many harvesters? Right now I am storing the plots on the xfs array, since I don't have unassigned devices yet. I'd maybe invest in a pi4, wanted to buy one for a long time anyway but had no project to use it for in mind, so using it as chia node would be a good enough project. I wasn't aware that the pi has a M.2 slot, are there other options to store the system, like a big sd card or is it better to use a ssd?
So if I get you right:
- There is a pi4 with a m.2 sdd running the full node to accept challenges, syncing the blockchain and handle the wallet and master keys
- You have a special rig for plotting, which stores the plots on your unraid server in a share folder of your array (which is optional) - What services does that rig need to run to plot?
- You are running harvesters on your unraid system via this container, which accesses the plot folder and are connected to the pi, so the pi running the farmer accepting challenges and the harvesters on your unraid server are responding to those?
- You can use the harvesters to create plots from there as well (which is optional)? Or how are you plotting there?
So if I wouldn't have a special plotting rig, I can use the unraid system harvesters to do so or do I need to run something else?
-
2 minutes ago, jaj08 said:
Just to update, but fixing time zone ended up not fixing my syncing issues. In a way that makes sense, as time was proper, just wrong Timezone, and why would chia be broken in specific time zones?
Any way, for now I was forced to migrate my full node back over to my Windows Desktop where I have been synced all day without issues. For now the docker is strictly a harvester for me.
Yes I can confirm, it's the same for me. Fixing the timezone alone didn't do the trick. It was syncing, then it was stopping, then syncing again, but after some time it never reached the fully synced status.
To be honst, I just don't get it. I expected the docker container to just work, but it clearly doesn't. Chagning things inside the container shouldn't be necessary at all, so maybe it's not in a perfect state yet.
It might be a good idea to switch to a GUI. The only issue is, I am a little worried about the performance. When I tried running chia inside a windows vm it was horribly slow. -
36 minutes ago, Gnomuz said:
Hope that can help, although I doubt your sync issues are related with timezone. I'm almost sure everything is managed as UTC time at network level, and the timezone is only used to display timestamps in logs.
If you don't open and forward the port 8444 to the container (in practice to the IP address of your Unraid server) on your router, you will have difficulties to connect to peers on the network, and thus the sync will take ages. It's exactly the same as in Bittorrent and many other P2P protocols. The oldest may remember the "Low Id" in emule 😉
From the official chia docs: https://github.com/Chia-Network/chia-blockchain/wiki/FAQ#i-am-seeing-blocks-and-connections-but-my-node-says-not-synced
QuoteThis is usually a system clock issue, which is causing the display of "Not synced", even though you are. Your clock must be set to the exact time, and cannot be more than 5 minutes off. Check your phone and your computer and ensure the time is the same.
So It can be related, I think. I also have troubles to sync, but even after installing systemd it seems like its not syncing correctly.
I have no idea, why the whole docker is causing so much trouble, but I tried to run the GUI in a windows vm on unraid. This. Was. Horrible. The docker container was synced more than twice as fast as the one in the windows vm. So it doesn't seem to be an option. It must work with docker. Because if everything is to slow, one could have a bazillion plots, and would never win, because the reaction of a challenge is to slow...
But the docker feels very unstable. For me it syncs, then it stops, then it works, right now after fixing the time it's again not syncing... It's a nightmare. Oh and the wallet never ever synced on my end. Not sure, what is going on there. -
1 hour ago, j3rksn said:
I have a problem with fully syncing my node, and I think the problem is that my docker container is in the wrong timezone, even with the correct variable passed (-e TZ="Europe/Berlin").
My containers clock is 2 hours behind and the node only syncs 2 hours behind.
Does anyone have a solution for this?3 minutes ago, jaj08 said:Since migrating to my docker being the full node I have had random times where I drops back into syncing mode. Now that I read your comment I have also noticed the Timezone is clearly wrong in my docker as well. So what's the fix?
I just discovered, it's the same for me. And it seems like it doesn't install some basic stuff inside this ubuntu.
I entered the container and ran apt-get systemd
It will prompt you to enter your timezone.
But The bad thing is, this would be necessary every time the container is rebuild. So that's something the official chia docker needs to fix or we need a custom own docker container to make sure such things are executed on build time...-
1
-
-
10 hours ago, adminmat said:
did you say you were farming in Ubuntu? Have you tried to disable the firewall (UFW) or open a port 8444? I think I read about that in another thread.
I use the official chia docker container, which indeed uses the ubuntu 20.04LTS container as a base, but since it's the official chia container, I'd expect they took care of that. Else, everyone who uses the docker, would have the same problem, wouldn't they?
-
10 minutes ago, Trinity said:
I am litteraly driving nuts with this.
Restarted the container:
>chia wallet show No keys loaded. Run 'chia keys generate' or import a key >chia keys show --show-mnemonic-seed There are no saved private keys
Last time when I ran the second command, it showed my keys, and after that everything was working. Like it should because they are still untouched in the appdata folder...
But it just doesn't work. The full_node was syncing just fine and is synced now. But farmer and wallet are broken due to the missing keys T_T - I am new to unraid, but worked with docker and linux in the past. I feel really dumb, but I just don't get what this container is doing or especially what it is not doing, even tho you would expect it to just work...
Am I the only victim? 😅Port is open, didn't help much. It is syncing, but at some point it just stops. I need to provide the logs, maybe it will help to figure out, what is going on there, but to do that I need to have the deamons running again and right now, the rebuild container again doesn't see my keys... *sigh*
Not sure about the ISP thing, that's way over the top of my level of knowlede about networking
Nevermind, I am just dumb. Somehow I missed an tailing 's' on a file, so it couln'd be found. Now it's up and running, and seems to work. But again the wallet is not synced. Even tho the full node is. I'll wait until tomorrow and see if that changes, now after fixing that one dumb issue it might solved it and it just need some time. If not, I will look for errors in the log and provide them here. Thank you so far for the help!
-
I am litteraly driving nuts with this.
Restarted the container:
>chia wallet show No keys loaded. Run 'chia keys generate' or import a key >chia keys show --show-mnemonic-seed There are no saved private keys
Last time when I ran the second command, it showed my keys, and after that everything was working. Like it should because they are still untouched in the appdata folder...
But it just doesn't work. The full_node was syncing just fine and is synced now. But farmer and wallet are broken due to the missing keys T_T - I am new to unraid, but worked with docker and linux in the past. I feel really dumb, but I just don't get what this container is doing or especially what it is not doing, even tho you would expect it to just work...
Am I the only victim? 😅19 minutes ago, tjb_altf4 said:Make sure you have port 8444 forwarded, if you know your ISP has CGNAT you might need a VPN as the double NAT my be causing the sync issues.
Port is open, didn't help much. It is syncing, but at some point it just stops. I need to provide the logs, maybe it will help to figure out, what is going on there, but to do that I need to have the deamons running again and right now, the rebuild container again doesn't see my keys... *sigh*
Not sure about the ISP thing, that's way over the top of my level of knowlede about networking
-
6 minutes ago, Partition Pixel said:
After setting it to INFO you will need to restart the docker for it to take effect. Anything else is optional (making it stdout to the console ui of unraid is optional, but if you want to do it see OP)
All right, I think I prefer the debug.log over the unraid protocol for now, but I set the INFO level
I already restarted the container and the node synced again, but now it again tells me: "There are no private keys".
Seems like I didn't solve this last time. It just worked after a while. Does it simply take very long to detect them from the appdata folder? Or why is the container not aware of the key files? -
41 minutes ago, Partition Pixel said:
Not that I am aware of, of course I don't know what's inside since it's not my docker (it's the Chia team's docker) so hard to say, for your logs if you don't already have debug level set to INFO that would help the debugging !
if that will help, I will do that. is it enough to just set the INFO level or do I need to adjust anything on the container?
-
7 minutes ago, Partition Pixel said:
If you are farming and plotting correctly I think you will still be able to earn chia. It's just that you won't be able to see it on your wallet since it's not synched (that is until it is synched). That seems weird if everything else is correct, can you show us what your logs looks like ?
4 minutes ago, Partition Pixel said:Your node and wallet are not synched or only the wallet ? Either way I can't say with no other information, we would need to see your logs
Thank you, for the answer
Right now everything is out of sync, I don't understand, what is happening there, all I do is plotting and here and there call chia farm summary, chia show -s -c and chia wallet show. Suddenly everything stopped syncing and there are so many entries inside the debug.log - I'll wait for the plots to finish, then I will restart the container and clear the log, to get only new entries to narrow it a little more down and when it fails again, I'll provide my log here.
Could there by anything inside it, which could leak anything sensitive of my system? -
16 minutes ago, Partition Pixel said:
Yes that should mean that you're good to go, I didnt need to open any ports either. If you check your logs you will see more info on what's happening (and even more if you change the default logs settings, more on that on the topic post)
And if it's not synced, what could I do to fix it?
I was in sync with the node quite some time and it was farming, but the wallet was out of sync and now everything is not synced anymore. I didn't touch anything, any idea what could be the problem and how to solve it?
-
I think I figured it out, so it's up and running again. The only thing remaining is, that the wallet always shows: Not synced
Node is fully synced, farmer is running... But the wallet just refuses to sync. Is this a docker issue, an unraid issue or a chia network issue? As far as I understand, without a synced wallet you wont win anything ever.
Does nobody else got this issue? -
2 minutes ago, danktankk said:
thanks but none of this will work. its best to just go to a VM and be done with the docker component
For me it works
But yes, the whole docker thing is still very hacky, I can execute all commands I want, can start and stop all the services of chia and I am plotting. Non the less I am not synced some times, especially the wallet. It also does not simple load my keys if I restart the container... I hope they will improve on that.
-
8 minutes ago, danktankk said:
this would need to be in a yaml file for the locaiton of the executable. how would we do that?
If the container runs: Click on the icon of the container -> console. Inside that window you are in the shell of the container which runs linux.
Chia is written in python, so it uses virtual env. So to use the correct env, you need to activate it via
. ./activate
Then you can use the chia cli
No sure, what you mean with "be in a yaml file" yaml is a json dialect and used for config files ^^
But usually you can just execute the commands from the konsole of unraid, like:
docker exec -it chia venv/bin/chia show -s -c
-
1
-
-
26 minutes ago, burgess22 said:
I'm trying to find the same thing...haven't had any luck yet must be in the docker it self I reckon...your not looking for the chia.exe here that's windows you want the chia CLI location
Yes it's inside the docker. You can either call it via exec like in the opening post shown or enter the container and use:. ./activate chia <command you want to execute>
Not sure how to flash the SSD on my PC without a external m.2 port 
[Support] Partition Pixel - Chia
in Docker Containers
Posted
Yeah, that's exactly what I did so far, so from that perspective I should be fine. As long as that is the correct messurement
So guess I need to just wait and see and hope for the best ^^ Thank you!