[Support] Machinaris - Chia cryptocurrency farming + Plotman plotting + Unraid WebUI


Recommended Posts

Sigh. I hate to be the squeaky wheel, but now I have a new problem. I seem to be able to self pool on one wallet, by I am unable to self pool on my original wallet, and I can't join a pool on either wallet. I keep getting an error when I try.

 

list index out of range 

 

I deleted and rebuilt my wallet again, thinking that was the issue, but it doesn't seem to have helped. Any other thoughts?

Link to comment
13 minutes ago, DoeBoye said:

Sigh. I hate to be the squeaky wheel, but now I have a new problem. I seem to be able to self pool on one wallet, by I am unable to self pool on my original wallet, and I can't join a pool on either wallet. I keep getting an error when I try.

 

list index out of range 

 

I deleted and rebuilt my wallet again, thinking that was the issue, but it doesn't seem to have helped. Any other thoughts?

 

Sorry about the error.  I just fixed a similar message in the Settings | Pools page just yesterday.  Currently the fix is only in the ":develop" image.  Would you mind giving it a try to see if the problem is corrected for you?

Link to comment

Good day! Machinaris v0.6.9 is now available. Changes include:

  • MMX - support for this new blockchain, which requires its own plot files.
  • HDDCoin - update to version 2.0.0
  • Improved summary display for status.  Estimated price in USD provided by alltheblocks.net
  • Various fixes for issues reported in the Discord.  Thanks to all who reported!

image.png.88cb171f867769c18368b3fef94e8255.png

 

Note: If you're running `:develop` stream, this is a good time to switch to this release (aka `:latest`).  Expect breakage in the `:develop` stream as I start developing the next version.  Thanks!

  • Like 1
Link to comment

Fun Fact of the day.......  Forks.Green Exchange has the terrible customer service and it's staff are rude feckless Russian's that don't give two f's if their response makes sense (If they even bother to send one) 

They won't help you and at the moment just like to pocket your coins and ignore you.

Link to comment

My plotting seems to not work consistent any more…

I start the plotter, it makes a plot, does not start a new one, plotter is still running though…

Stopping and restarting the plotter also does not help…

I am running “test” .. if i switch to “latest” that gives an “internal server error”:

I”nternal Server Error

The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application”


Verzonden vanaf mijn iPhone met Tapatalk

Link to comment
2 hours ago, Helmonder said:

My plotting seems to not work consistent any more…

I start the plotter, it makes a plot, does not start a new one, plotter is still running though…

Stopping and restarting the plotter also does not help…

I am running “test” .. if i switch to “latest” that gives an “internal server error”:

I”nternal Server Error

The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application”

 

Hi, with the recent release of Machinaris v0.6.9 this is a good time to switch to ":latest" as the development and test branches will experience breakage during the next development cycle.

 

Regarding the error you are experiencing with ":latest", please ensure:

1) You switch all Machinaris containers on all systems to ":latest". 

2) For each, ensure the image is up-to-date.  Unraid sometimes "misses" out on upgrades, so be sure to "Check for Updates", and even "Force Upgrade" on the Docker window to be doubly sure you're not running an old image.
3) If you are still experience an "Internal Server Error", please check the logs.  You may have data/file corruption, requiring a reset.

 

If that does not correct the issue, please share the log with the error you are encountering.  Thanks!

Link to comment
 
Hi, with the recent release of Machinaris v0.6.9 this is a good time to switch to ":latest" as the development and test branches will experience breakage during the next development cycle.
 
Regarding the error you are experiencing with ":latest", please ensure:
1) You switch all Machinaris containers on all systems to ":latest". 
2) For each, ensure the image is up-to-date.  Unraid sometimes "misses" out on upgrades, so be sure to "Check for Updates", and even "Force Upgrade" on the Docker window to be doubly sure you're not running an old image.
3) If you are still experience an "Internal Server Error", please check the logs.  You may have data/file corruption, requiring a reset.
 
If that does not correct the issue, please share the log with the error you are encountering.  Thanks!

That solved it !

I set all containers to “latest”, then did a check on updates, installed those, started the containers, let them startup for 15 minutes and now I could start the plotter.

I will keep an eye on it to see if the system keeps plotting !


Verzonden vanaf mijn iPhone met Tapatalk
Link to comment
On 2/1/2022 at 9:03 PM, guy.davis said:

 

Sorry about the error.  I just fixed a similar message in the Settings | Pools page just yesterday.  Currently the fix is only in the ":develop" image.  Would you mind giving it a try to see if the problem is corrected for you?

So just an update. I tried the develop branch, but still couldn't connect.

 

Switched back to stable when you released 0.6.9, and next time I checked, I had started pooling again..... The only caveat is that Machinaris still seems to think that I am not connected (Though my payouts from space pool have restarted)... Weird eh? See attached screenshot... EDIT: Can't seem to attach my screenshot today. Keeps failing. In a nutshell, the radio button beside the 'connected to a pool' option is not selected, though the field is reflecting the url for space pool. At the top of the page in the pinkish alert box, it says: 'Unknown pool save choice provided: None'

 

Link to comment

That solved it !

I set all containers to “latest”, then did a check on updates, installed those, started the containers, let them startup for 15 minutes and now I could start the plotter.

I will keep an eye on it to see if the system keeps plotting !


Verzonden vanaf mijn iPhone met Tapatalk

Unfortunately the same effect:

The first started plot has finished, machinaris shows the plotter as “running” but it is not…

Pretty sure that if I start the start/stop cycle I can the plotter started again but again only for one plot.

What can I send log-wise ? Or is there something else I can do.


Verzonden vanaf mijn iPhone met Tapatalk
Link to comment
8 hours ago, DoeBoye said:

So just an update. I tried the develop branch, but still couldn't connect.

 

Switched back to stable when you released 0.6.9, and next time I checked, I had started pooling again..... The only caveat is that Machinaris still seems to think that I am not connected (Though my payouts from space pool have restarted)... Weird eh? See attached screenshot... EDIT: Can't seem to attach my screenshot today. Keeps failing. In a nutshell, the radio button beside the 'connected to a pool' option is not selected, though the field is reflecting the url for space pool. At the top of the page in the pinkish alert box, it says: 'Unknown pool save choice provided: None'

 

 

Hi, I think this support thread may benefit from the interactive chat of our Discord server.  However, if you prefer to continue here, please share the output of "chia plotnft show" from your Machinaris Docker Console in Unraid.  Please redact any sensitive identifiers.  I am trying to understand the situation you are facing.

Link to comment
3 hours ago, Helmonder said:

The first started plot has finished, machinaris shows the plotter as “running” but it is not…

Pretty sure that if I start the start/stop cycle I can the plotter started again but again only for one plot.

What can I send log-wise ? Or is there something else I can do.

 

Hi, I think this support thread may benefit from the interactive chat of our Discord server.  However, if you prefer to continue here, please share the full logs following from the plotter system.  This sounds like the plotter process (madmax?) is starting but then crashing part-way thru the plot, then Plotman thinks the first plot is finished and starts a second?   Logs are found in /mnt/user/appdata/machinaris/plotman/logs. Sort by most recently created.  Plotter crashing can indicate misconfiguration, lack of resources, stale OS software, etc..

 

Link to comment
57 minutes ago, guy.davis said:

 

Hi, I think this support thread may benefit from the interactive chat of our Discord server.  However, if you prefer to continue here, please share the full logs following from the plotter system.  This sounds like the plotter process (madmax?) is starting but then crashing part-way thru the plot, then Plotman thinks the first plot is finished and starts a second?   Logs are found in /mnt/user/appdata/machinaris/plotman/logs. Sort by most recently created.  Plotter crashing can indicate misconfiguration, lack of resources, stale OS software, etc..

 

 

Hiya !

 

I just joined the discord but sharing the log seems easier this way ?

 

The most recent log ( 2022-02-07T17_40_10.437180+01_00.plot.log ) might point to the issue already, it is only 1KB big and contains one row:

 

Failed to write to finaldir directory: '/plots/'

 

/plots is mapped to /mnt/user/Chia Plots/ this is a user share without cache pool that has 6,20TB Free:

 

1835783374_Screenshot2022-02-07174954.thumb.png.abd5fca2506d4e9308e5e13199e3b889.png

 

2101301788_Screenshot2022-02-07174813.thumb.png.03a15283eeff3cfbda04523474fe6808.png

 

/Plots is writeable, I opened the console for the docker and was able to write to the share:

 

1400392185_Screenshot2022-02-07175719.png.e713fd45ab1742c4fe6ea6c35c990002.png

 

The file underneath is "plotman.log", this is 43,959 KB and is attached, the last few lines:

 

Starting plot job: chia_plot -n 1 -k 32 -r 4 -u 256 -x 8444 -t /plotting/ -d /plots/ -v 256 -K 1 -f a5289fd7f3eb289bae43f58a2dec652369acaf004eb6179dc6fd77053e37d5be9713f3ee3fda01842eaed5c9184ea576 -p 98533421fb01cd3e93bb10c8a3c8a7d1e78d33d577f2a537def7292f89f9918cff12a0fe3ed818b71bfa2821513e9b27 ; logging to /root/.chia/plotman/logs/2022-02-07T17_38_10.286204+01_00.plot.log
Starting plot job: chia_plot -n 1 -k 32 -r 4 -u 256 -x 8444 -t /plotting/ -d /plots/ -v 256 -K 1 -f a5289fd7f3eb289bae43f58a2dec652369acaf004eb6179dc6fd77053e37d5be9713f3ee3fda01842eaed5c9184ea576 -p 98533421fb01cd3e93bb10c8a3c8a7d1e78d33d577f2a537def7292f89f9918cff12a0fe3ed818b71bfa2821513e9b27 ; logging to /root/.chia/plotman/logs/2022-02-07T17_38_30.311255+01_00.plot.log
Starting plot job: chia_plot -n 1 -k 32 -r 4 -u 256 -x 8444 -t /plotting/ -d /plots/ -v 256 -K 1 -f a5289fd7f3eb289bae43f58a2dec652369acaf004eb6179dc6fd77053e37d5be9713f3ee3fda01842eaed5c9184ea576 -p 98533421fb01cd3e93bb10c8a3c8a7d1e78d33d577f2a537def7292f89f9918cff12a0fe3ed818b71bfa2821513e9b27 ; logging to /root/.chia/plotman/logs/2022-02-07T17_38_50.335495+01_00.plot.log
Starting plot job: chia_plot -n 1 -k 32 -r 4 -u 256 -x 8444 -t /plotting/ -d /plots/ -v 256 -K 1 -f a5289fd7f3eb289bae43f58a2dec652369acaf004eb6179dc6fd77053e37d5be9713f3ee3fda01842eaed5c9184ea576 -p 98533421fb01cd3e93bb10c8a3c8a7d1e78d33d577f2a537def7292f89f9918cff12a0fe3ed818b71bfa2821513e9b27 ; logging to /root/.chia/plotman/logs/2022-02-07T17_39_10.361398+01_00.plot.log
Starting plot job: chia_plot -n 1 -k 32 -r 4 -u 256 -x 8444 -t /plotting/ -d /plots/ -v 256 -K 1 -f a5289fd7f3eb289bae43f58a2dec652369acaf004eb6179dc6fd77053e37d5be9713f3ee3fda01842eaed5c9184ea576 -p 98533421fb01cd3e93bb10c8a3c8a7d1e78d33d577f2a537def7292f89f9918cff12a0fe3ed818b71bfa2821513e9b27 ; logging to /root/.chia/plotman/logs/2022-02-07T17_39_30.386354+01_00.plot.log
Starting plot job: chia_plot -n 1 -k 32 -r 4 -u 256 -x 8444 -t /plotting/ -d /plots/ -v 256 -K 1 -f a5289fd7f3eb289bae43f58a2dec652369acaf004eb6179dc6fd77053e37d5be9713f3ee3fda01842eaed5c9184ea576 -p 98533421fb01cd3e93bb10c8a3c8a7d1e78d33d577f2a537def7292f89f9918cff12a0fe3ed818b71bfa2821513e9b27 ; logging to /root/.chia/plotman/logs/2022-02-07T17_39_50.411756+01_00.plot.log

 

This is how Macharis looks on the plotting page, stopping and starting the container does not work, it remains in this state:

 

377103729_Screenshot2022-02-07175147.thumb.png.6f0579734bb51e80f2d8d69b43f4e9ee.png

 

After restarting the container after 15 minutes or so the status changes to "stopped" and I am able to restart the plotter (but after one plot it will fail again)

 

My CPU is running on 50% load (E-2146G CPU) and my memory is at 64% utilisation (64GB)

 

Any idea ?

 

 

plotman.zip

Edited by Helmonder
Link to comment
34 minutes ago, Helmonder said:
Failed to write to finaldir directory: '/plots/'

 

Yes, if the in-container path where the plotter is attempting to write the plots is read-only, then the plotter will fail as you describe.  I'm not an Unraid expert by any stretch, but I would recommend checking folder permissions and settings on the Unraid Docker configuration.

 

Link to comment
 
Yes, if the in-container path where the plotter is attempting to write the plots is read-only, then the plotter will fail as you describe.  I'm not an Unraid expert by any stretch, but I would recommend checking folder permissions and settings on the Unraid Docker configuration.
 

It would… but that is why i checked writing on console within the docker… that worked so the share is not read-only or full..

I have reset security (change permissions) on the share just to be sure and will let know.

Would be weird if it works though, a security should also prevent the first plot to be saved..
Link to comment

It would… but that is why i checked writing on console within the docker… that worked so the share is not read-only or full..

I have reset security (change permissions) on the share just to be sure and will let know.

Would be weird if it works though, a security should also prevent the first plot to be saved..

Nope… it stopped again… one plot got made and transferred to /plots (proving that rights are fine and nothing is read only.

Status is as described above.


Verzonden vanaf mijn iPhone met Tapatalk
Link to comment

This is the output of the log when it is plotting that first plot:

Multi-threaded pipelined Chia k32 plotter - efa5b2a
(Sponsored by Flexpool.io - Check them out if you're looking for a secure and scalable Chia pool)

Network Port: 8444 [chia]
Final Directory: /plots/
Number of Plots: 1
Crafting plot 1 out of 1 (2022/02/08 18:24:20)
Process ID: 185
Number of Threads: 4
Number of Buckets P1: 2^8 (256)
Number of Buckets P3+P4: 2^8 (256)
Pool Public Key: 98533421fb01cd3e93bb10c8a3c8a7d1e78d33d577f2a537def7292f89f9918cff12a0fe3ed818b71bfa2821513e9b27
Farmer Public Key: a5289fd7f3eb289bae43f58a2dec652369acaf004eb6179dc6fd77053e37d5be9713f3ee3fda01842eaed5c9184ea576
Working Directory: /plotting/
Working Directory 2: /plotting/
Plot Name: plot-k32-2022-02-08-18-24-8c67fb12aaac22d05d1a2958c6c0eafc261b6c8a3c4d814fb59c444bba4938a3


Verzonden vanaf mijn iPhone met Tapatalk

Link to comment

Glad to hear in the Discord that Helmonder was able to sort out the problem.   His post there:
 

Quote

I solved my issue. Happy to report is was not related to Machinaris and/or the docker.
It was some weird thing in unraid that I am trying to reproduce. Basically the share reported to space available while in reality there was plenty… i actually removed some assigned (full) drives from the share (plots remain available bit drives are not seen anymore as a potential write location), this solved the issue.

 

Link to comment
On 2/15/2022 at 5:10 PM, guy.davis said:

Glad to hear in the Discord that Helmonder was able to sort out the problem.   His post there:
 

 

 

Yeah it was really super weird... Because this is the unraid forum a bit more context for the unraid people:

 

I had 9 8TB drives in the array only allocated to chia plots. I added a new drive to that share, another 8TB one. Plotting refused to work..

 

I tried messing with the minimum space and allocation method to make sure that did not work out the wrong way (although I have been working with unraid for a long time and I do not think I would have made an error there).

 

What worked in the end is removing all existing Chia drives out of the Chia share and keeping only the new drive, that works...

 

That is not an issue also since the plots are still perfectly readable and the shares are not written to while farming..

  • Like 1
Link to comment

Can I pass an unassigned device/disk to machinaris to farm on?

 

I have started to add some external USB drives and I don't think I'm supposed to put them in the array, but i'd like to use them for farming.

 

If it's possible, how are they added because they won't be in a share.

 

thanks.

Link to comment
2 hours ago, Ystebad said:

Can I pass an unassigned device/disk to machinaris to farm on?

 

I have started to add some external USB drives and I don't think I'm supposed to put them in the array, but i'd like to use them for farming.

 

If it's possible, how are they added because they won't be in a share.

 

thanks.

 

Yes, it's possible to:

1) Plugin the external drive to your Unraid tower.

2) In Unraid UI, format the drive, then mount as an Unassigned Drive.  I mounted mine at "/mnt/disks/plots1", "/mnt/disks/plots2", etc.
3) Then Unraid UI | Docker tab, Machinaris container, add Path mount like "/plots1", "plots2", etc in the container.

Screenshots from Unraid UI: 
image.thumb.png.21a155e6cf823478b5dd4e4b84757164.png

image.png.0476f864da708882053b9bd06dca48e9.png

Hope this helps,

Guy

Link to comment
  • 2 weeks later...

Good day! Machinaris v0.7.0 is now available.

 

20220311_132751.thumb.png.d115779dc6d1176ef8bccbb3dd98c182.png

 

Changes include:
 - Chia v1.3: please note reports of issues in this new Chia release...  double-check your Wallet, Payout, and Pools settings after upgrading!
 - Internationalization for locale-specific text, numbers, and currencies.  Huge thanks to @antcasq (pt_PT) and @fabriziocacicia (it_IT) for providing translations!
 - Geolocation of peer connections for each blockchain by their IP address. Optionally enabled using a free Maxmind account.
 - Silicoin - supported again as per Discord votes.
  
Known Issues:
 - Chiadog will sporadically replay alerts when the Machinaris container is restarted. 
 - Coin prices are unavailable from AllTheBlocks, so no fiat conversion in Machinaris currently.

Edited by guy.davis
  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.