Jump to content

danktankk

Members
  • Posts

    187
  • Joined

  • Last visited

Posts posted by danktankk

  1. On 5/13/2021 at 12:19 AM, Trinity said:

    For me it works :D 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.

    all good.  im truly glad someone has it working in unraid.  I loaded a basic ubuntu VM and it is plotting 7 staggered plots perfectly  with Swar plot manager which is another thing I cant get to work right in unraid at all.

  2. 1 hour ago, Trinity said:

    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

     

    thanks but none of this will work.  its best to just go to a VM and be done with the docker component

  3. 4 minutes ago, Trinity said:


    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>

     

    this would need to be in a yaml file for the locaiton of the executable.  how would we do that?

     

    I am trying to run a script against this container.  So the location of the executable or a way to point to it is necessary.

     

    Here is the link to it:  https://github.com/swar/Swar-Chia-Plot-Manager

  4. 25 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, this is correct..  I have tried a few different things...  none have worked

     

    last try was:  /usr/bin/docker exec -it chia venv/bin/chia  

     

    this didnt work.  I have pretty much everything else ready to go with this one exception.  I wonder if I can point to a networked *.exe to ge this running lol

  5. If the node and harvester are on another machine besides unraid, what would the port need to be?  It doesnt appear that it is connecting properly.

     

    root@baconator:~# tail -f /mnt/user/appdata/chia/mainnet/log/debug.log
    2021-05-11T11:50:45.197 harvester harvester               : INFO     Reconnecting to peer {'host': '192.168.1.45', 'port': 8448}
    2021-05-11T11:51:19.205 harvester harvester               : INFO     Reconnecting to peer {'host': '192.168.1.45', 'port': 8448}
    2021-05-11T11:51:53.202 harvester harvester               : INFO     Reconnecting to peer {'host': '192.168.1.45', 'port': 8448}

     

    Also, is there a plotting log somewhere?  Its useful to track plots while you are out with an app I use.  It doesnt use debug.log for that.   In windows, the folder for it is here:

     

    C:\Users\<user>.\.chia\mainnet\plotter

  6. 25 minutes ago, Partition Pixel said:

     

    saw it here lol :

    image.png.ecc529fb2776efb15a7861597ae96469.png

     

    You don't really need to change anything on the unraid share side, your appdata is still going to be in /mnt/user/appdata/chia, it's just that the container will have it called '/root/.chia' for itself. Then you'll have to change other place where you used /config for /root/.chia (like for the mnemonic), After that I'm betting it will work if you change your log host folder for /mnt/user/appdata/chia/mainnet/log

    I did everything remotely from my phone. Changing it back to /root/.chia does make the logfile appear now.   I have no idea why and wish that wasn't the case, but it did work.  Thank you for the help!  

     

    Is there anyway that /root/.chia can be altered in a  future update?  I prefer using /config...  Not a deal breaker obviously ☺️

    • Like 1
  7. 7 minutes ago, Partition Pixel said:

     

    Try this in your Host Path for logs

    
    /config/mainnet/log

    instead of

    
    config/mainnet/log

    (missing first /).

     

    If that still doesnt work I would try going back to the /root/.chia for your appdata

    log-path.png.3c555079b45608df3086364166ec782f.png

    my config does havce the leading `/` in it.  Im not sure where you saw that it didnt?

     

    Im not sure how to use /root/.chia for appdata or where it would be moved to.  I am not that great with unraid.

  8. 3 minutes ago, Partition Pixel said:

     

    Just did a re read of what you said and if your appdata container path is in /config, it's possible there is some confusion with the /config folder inside of the chia appdata. Check if there's any log file in chia/config. Other than that the only difference I have with you is the appdata location (mine is /mnt/user/appdata/chia ) 🤔

    I dont see it anywhere.  i added more to my initial statement as well with an edit

  9. 6 minutes ago, Partition Pixel said:

     

    Oh I see, then yes I think this is possible, didnt test with only harvester but that might be the case ! Do you have any debug.log file at all in your mainnet/log/ ? If not then I guess that's the case

     

    I cant get a logfile to show up no matter what.  In windows it logs without anything but a plotter running

     

    In the console when this container starts I see the following: 

     

    Chia directory /root/.chia/mainnet
    Can't find private CA, creating a new one in /root/.chia/mainnet to generate TLS certificates
    No keys are present in the keychain. Generate them with 'chia keys generate'

     

    None of my appdata works in this way and I use /config to map my appdata paths.  Could this be an issue?  Further down in that log it does go to the proper directory and reads my mnemonic and start the chia_harvester.

     

    Im just astonished at this not giving me log files lol

  10. 13 minutes ago, Partition Pixel said:

     

    The config yml seems good, now for the path on the docker template if you want the path you gave me earlier your 'Host Path' should be '/mnt/user/appdata/logs/' or '/mnt/user/appdata/chia/mainnet/log/' for the default one

     

    I have appdata Container Path: set as /config  and Host Path: set as /mnt/user/appdata/chia 

     

    However, I did try it adding the path your way and I still am not getting a debug.log file in the default location of /mnt/user/appdata/mainnet/log/debug.log

     

    I am only using this to make plots so maybe that is why?

  11. 3 minutes ago, Partition Pixel said:

     

    Can't see your url (it says access denied) 😢 log_stdout must be false otherwise it won't work (it will write to the console instead of the file), other than that you need to restart your docker after making the changes in the config.yml. It is very important that the container path value be '/log' with no S (unless you put one in the config.yml). Other than that it should work ! Don't hesitate if you still have problems

     

    I changed the URL to an Image.  Try to refresh the page?

     

    `  logging: &id001
        log_filename: /log/debug.log
        log_level: INFO
        log_maxfilesrotation: 7
        log_stdout: false`

  12. 36 minutes ago, Partition Pixel said:

     

    I'm adding this to the template right now,

     

    If you want to add it manually, do the following (create a new path and type this):

     

    image.png.740d0d13cbcbb6f5a5c5aa7198c7ef17.png

     

    I didnt test it but I don't see why it wouldnt work, feel free to report back ! (testing on my side now)

     

    Edit: managed to make it work, but I also had to change something in the config.yml :

    image.png.895ad296e483f4f57f45bc912c053574.png

     

    You will need to add the first '/' before the 'log/debug.log'

     

    Don't know if there's another way without modifying the config.yml but I this is how I managed to make it work (got limited time can't check any further)

     

    Thank you for the reply.  I have tried everything you have there already.  At this point,  I don't mind it going to the default location.  I just need the log files to give some output and then I can worry with where they go.   I also added the leading `/` in the yaml file as well.

     

    Here is my path setup for it:

     

    log-path.png.9cf4d46992719aedf00858a94cfa1889.png

    I have also tried `log_stdout` both true & false

     

    Any other ideas?  Many thanks!

×
×
  • Create New...