• Posts

  • Joined

Everything posted by PTRFRLL

  1. The password should change, Pulseway hashes it for you so it's not stored in plaintext. As for the username, that shouldn't change. I suppose the simplest way to troubleshoot is: Disable the Pulseway service: /etc/rc.d/rc.pulseway stop Edit the config.xml located here: /etc/pulseway/config.xml Re-enable service: /etc/rc.d/rc.pulseway start Check if config.xml is still "intact" with your edits/Unraid machine is showing in Pulseway
  2. That all looks good to me. The contents of /boot/pulseway/config.xml are what you'd expect? With your info, etc?
  3. Are you sure your config.xml file is being copied to the correct location on boot? What's in your /boot/config/go file?
  4. How long has it been running? Most sites calculate your hashrate by averaging over a 24 hr period
  5. It should be listed under the Nvidia Driver section in Settings or you can run nvidia-smi -q in your console
  6. Add the NVIDIA_VISIBLE_DEVICES variable to the docker container and specify the GUID of the GPU you want to use (see the Specify GPU section in the first post)
  7. I haven't had much time to dedicate to this but it is still on my list. I hesitate to add it directly to this docker as the current method requires a specific version of nVidia drivers to be installed and I prefer to not force that decision on people (it also makes support a nightmare). My current plan is to create a separate docker that contains the over/under-clocking options which will persist those settings across all dockers. That way you could use that docker in conjunction with the T-rex one or any others.
  8. The WALLET variable on the docker is passed to the -u flag of T-Rex, so just enter everything in that field:
  9. Yes, you should be able to run two instances, just expose one GPU to each.
  10. Thanks for the link for NSFMiner, I hadn't seen that container before. I'll see if I can integrate the OC capabilities into this image as well.
  11. you could always route the Trex container through a VPN container:
  12. I see your server is set to but does it have the stratum+tcp part at the beginning like so: stratum+tcp://
  13. You should be able to mine Raven using the kawpow algorithm. Did it throw a specific error message?
  14. I updated the Docker to include a PASS env variable, so you can now override the default
  15. I'll add a PASS variable that you can set for the container.
  16. Not that I'm aware of, I would love to do this too. You might try setting the --low-load flag in T-rex but I'm not sure if it will work:
  17. What's your config.json look like? I'm guessing the URL prop is missing. { "pools" : [ { "pass" : "x", "url" : "stratum+tcp://", "user" : "WALLET_ADDRESS", "worker" : "Rig" } ], "api-bind-http" : "" }
  18. Try adding the devices flag to your config.json with a comma-separated list like so: { ... "devices": "0,1" }
  19. Shoot. I updated the CUDA base image (to CUDA 11.2) in the latest update. The "easy" answer is to update your nvidia drivers. That said, I know that's not an acceptable answer for everyone. I guess I'll downgrade the base image back to 11.1 which should be compatible for all/most nvidia drivers.
  20. I believe current hashrate is based of a 24hr period. More here
  21. I have not seen that before. You might try raising an issue on the T-Rex Github:
  22. Thanks for the heads up. I think that's an issue with the CA templates, they assume all Dockers are hosted on docker hub but in this case it's hosted on Github's Container registry
  23. You need to exclude the 660. There's two ways to accomplish that. 1. In the Trex config.json, there's a devices property that you can use to specify which devices to use: { ... "devices": "0,1", ... } You have two devices (0 and 1), the 660 is #1 so remove the 1 from the devices list: { ... "devices": "0", ... } OR 2. You can add the NVIDIA_VISIBLE_DEVICES variable on the docker and only enter the UUID of the 1650 you want to use
  24. I believe you can view the min/max power limits of your card with the following command: nvidia-smi -q -d POWER Otherwise, you might play around with the memory tweak (--mt) setting for T-rex
  25. I understand there will be a new docker with the ES/ML modules pre-configured but is there a way to get the now legacy docker working again? I receive the error "Cannot download the ES server bundle" on container startup. It was working great until recently.