nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze nostr:npub1wnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqq3n3wr I am having issues connecting a miner to datum on StartOS. I suspect it has to do with simpleproxy configuration as I had issues initially with the simpleproxy setup and had to redo it once already. (Datum gateway seems to be running ok)
Is there a way to validate that simpleproxy is running as expected?
It sounds like you're having a proxy-related headache
To validate SimpleProxy's status, you can try the following:
1. **Check the logs**: Look for any error messages or warnings related to SimpleProxy in the miner's logs. If it's running, you should see some activity.
2. **Verify the configuration**: Double-check that your SimpleProxy setup is correct and matches the documentation. Make sure all settings are accurate, including the gateway URL (which is already reported to be working by Datum).
3. **Run a diagnostic test**: Run the miner with the `--diagnostic` flag followed by `simpleproxy`. This will help you identify if SimpleProxy is actually running or not.
Example:
```bash
miner --diagnostic simpleproxy
```
If you're still stuck, feel free to share more details about your setup and I'll do my best to guide you through the process
ssh back in and run
sudo systemctl status simpleproxy.datum.service (or whatever you called it)
Thanks! I see that is where the issue is. ExecStartPre has invalid argument (status 2). That should be dynamically pulling the IP address, correct? Or should the simpleproxy.datum.service file be populated with the actual ip address (192.168.x.y)
Just hit another snag as it seems Knots is now not starting due to an error initializing database… log says to restart with -reindex or -reindex-chainstate to recover, so will need to figure out how to do that as well 😅
there's an action in the Knots service for reindexing you can use that. the simpleproxy service should be grabbing the IP?
Found that earlier today and got it running. Once reindex it is done I’ll just try hard coding the IP in the simpleproxy.datum.sevice file… wasn’t sure if the command to create that file was supposed to plug in the actual IP or if it was supposed to save the script there to dynamically pull it on startup in the event the IP changes? 🤙🤙
the stuff in the instructions was meant to be copied and pasted as is. no need to overthink.
if you want to change the service remember to do the chroot stuff or it wont persist over restarts.
Yeah… that’s where I originally got into trouble… the browser/machine I was sshing in from wouldn’t let me select text/copy so I manually typed it out and found myself needing to edit it after the fact (typos, of course 😅). I did discover after a couple attempts that all steps needed to be performed to update that file. If it doesn’t work after reindexing I’ll just try hardcoding the IP address… pretty sure that command is where my issue is. Appreciate the assistance!!
Appreciate your help…. Reindex finished and simpleproxy is also now working, so am now officially mining with my own templates! 🤙 #datum
Just thought of one more question… from what I can tell you have to choose either pool or non-pool mining from one datum server instance, but not both… is there a way to pool mine with some machines and solo mine with others? Or do you need to run 2 datum servers to do that?
datum can only pool or not pool per instance. cant do both. so yeah, need two instances of the gateway.
