Looking for debug help, Gupaxx basically sending to much/all hasrate to XvB

[Maverik26]

Not sure what i should include. Kindly request additional information as needed please
Am not sure if this migth even be a bug.
The issue being Hero behavior instead of auto
Its nonstop mining to XvB in 10 Min intervallseeven when posting mining to XvB for 0s

Whats your take on where to look for what (error)

[2025-01-07 15:25:37.819]  Algorithm of HR distribution started for the next 10 minutes.
[2025-01-07 15:25:37.819]  estimated external HR on XvB: 31.545kH/s
[2025-01-07 15:25:37.819]  estimated external HR on P2pool: 7.694kH/s
[2025-01-07 15:25:37.819]  24H avg XvB target not achieved. Sending all hashrate to XvB!

The Proxy has between 40 and 70 KH/s accumulated
No chance to get to 100KH/s for whale
In fact the behavior is more like Hero`

Gupaxx Version 1.71 on Windows
Node starts Advanced with

--zmq-pub tcp://127.0.0.1:18083 --out-peers 32 --in-peers 64 --add-priority-node p2pmd.xmrvsbeast.com:18080 --add-priority-node nodes.hashvault.pro:18080 --disable-dns-checkpoints --enable-dns-blocklist --data-dir H:\gupaxx-v1.7.0-rc3-windows-x64-bundle\Node\.bitmonero

Additionally it uses 127.0.0.1:18081 for RPC

P2Pool starts witrh advanced

--wallet 43sxydP2HZoY1E9hxxEgxEEjypytooSwoNnyAHHbqEGb5PV38EGe3RAHzpWZPEiu42KURiBV6gAwb3m9Ct6eLXgy253EHHt --host 127.0.0.1 --rpc-port 18081 --zmq-port 18083 --loglevel 1 --out-peers 10 --in-peers 10 --data-api H:\gupaxx-v1.7.0-rc3-windows-x64-bundle\P2Pool --local-api --no-color --light-mode --mini

Additional RPC 18089 and ZMQ 18083

XMRig is set to Advanced

--no-color --http-access-token=xxxxxxxxx--http-no-restricted --threads 4 --user Mav --rig-id Gupaxx_v1_7_0 --url 127.0.0.1:3334 --http-host 127.0.0.1 --http-port 18088

first brings 127.0.0.1:3355 write error: "software caused connection abort"
then switches to localhost and mines

The Proxy is for the non local miners, starting Advanced

--http-access-token=xxxxxxxxxx--http-no-restricted --user  --rig-id Gupaxx_v1_7_0 -o 127.0.0.1:3333 -b 0.0.0.0:3334 -b 0.0.0.0:3355 --http-host 127.0.0.1 --http-port 18089 --no-color

-b 0.0.0.0:3355 didnt help but didnt hurt either
Whats API actually doing?
The Proxy mines to what XvB tells it to. If i shut down XvB it goes to local

XvB is set to Advanced and Auto with 25% P2Pool Buffer
I have the feeling that 24H avg XvB is achieved when 1h Average is at or above 24h Average.
At this moment 33.8KH/s last hour and 23.88KH/s 24h Round VIP Donor

[Maverik26]

Another example as i restarted just now:

[2025-01-07 20:18:48.415]  XvB is now started because p2pool and Xmrig-Proxy came online.
[2025-01-07 20:18:49.100]  Algorithm of HR distribution started for the next 10 minutes.
[2025-01-07 20:18:49.100]  estimated external HR on P2pool: 36.714kH/s
[2025-01-07 20:18:49.100]  There are no shares in p2pool. Sending all hashrate to p2pool!

On XvB Menu it says mining to EU XvB
The Proxy thought is directing to P2Pool

[Cyrix126]

It is choosing the EU XvB node based on latency. It will be using it when it will send HR to it.
Here you don't have any share yet, so it will send everything to P2Pool.

[Maverik26]

This one aspect may be a misunderstanding on my part. It says EU XvB on the XvB tab
Can you comfirm this is the node it sends to WHEN sending?

[Cyrix126]

This one aspect may be a misunderstanding on my part. It says EU XvB on the XvB tab Can you comfirm this is the node it sends to WHEN sending?

Yes. It is using the XvB node only when sending.

[Cyrix126]

(I edited your post to use 3 commas instead of one to displaying the command arguments, better readability).

[Maverik26]

Mhhc appreciated

[Cyrix126]

[2025-01-07 15:25:37.819]  Algorithm of HR distribution started for the next 10 minutes.
[2025-01-07 15:25:37.819]  estimated external HR on XvB: 31.545kH/s
[2025-01-07 15:25:37.819]  estimated external HR on P2pool: 7.694kH/s
[2025-01-07 15:25:37.819]  24H avg XvB target not achieved. Sending all hashrate to XvB!

You would need to watch the 24H average to understand the decision. If the algo decides to go for the 10kH/s round, as it surely should here, and the 24H average is still under 10kH/s, it will send everything to XvB to join the round faster (except if you have no shares). After the 24H average is at 10kH/s, it will send normally between p2pool and XvB.

[Maverik26]

Additionally the Proxy does not follow the decission made.
In the log i noticed ports 3355 being atempted. No clue where its set or used.
-b 0.0.0.0:3355 was only a test and had been removed.

Do you have more info ? Are you talking about the Proxy tab ? what is exactly the console output ?

This was in the Proxy Tab.
By luck found the source for port 3355
Its the auto redirection of XMRig to XMRig Proxy

[Maverik26]

[Maverik26]

Token removed for Foto only.
Thats after about 5-10 Minutes running

[Cyrix126]

If it says miners connected 0, check the connection between your miners and the Proxy. In the Proxy tab, input the command "w" to see any connected miners.

If you are using a different version of xmrig-proxy than the on bundled in Gupaxx, you will have a 15mn delay bug to get the first hashrates.

[Maverik26]

As you probably suspect, miners actually connected are 14.
This morning still the same picture.

[Cyrix126]

I removed the HTTP port from config and it randomly takes a port now

You shouldn't. This option is a must.
If in trouble, reset to start options with simple mode to see what's required.

[Maverik26]

I did before but will repeat it. Time's running short to do it now.
You reminded me: Is there a documented "basic" config? And i cant use simple for the node (main drive full)
How does the http / API work?
Does the program "see" the port i set?

[Cyrix126]

And i cant use simple for the node (main drive full)

Simple does not prevent using remote nodes.

Is there a documented "basic" config?

config of what ? Gupaxx ? xmrig-proxy ?

How does the http / API work?

https://github.com/xmrig/xmrig/blob/master/doc/API.md

Does the program "see" the port i set?

I just checked and there is currently a bug if you set another port for Proxy. Just let it at 18089 until a new release.

[Maverik26]

Thank you for helping me to find the cause.
It apparently was a port 19089 issue. Time will show. See below

[Maverik26]

Allright, the 19089 comment made it.

The node used 19089 for RPC default? In the configurator i used anyway.

Settings now:
Node: (deviating data directory) + RPC and ZMQ

--data-dir H:\gupaxx-v1.7.0-rc3-windows-x64-bundle\Node.bitmonero
--rpc-bind-ip 127.0.0.1
--rpc-bind-port 18081
--zmq-pub tcp://127.0.0.1:18083
--out-peers 8 --in-peers 16 --log-level 0 --sync-pruned-blocks --enable-dns-blocklist --disable-dns-checkpoints

P2pool (the same (of course) 18081 + 18083)
If you use them, replace your wallet adress.

--wallet 43sxydP2HZoY1E9hxxEgxEEjypytooSwoNnyAHHbqEGb5PV38EGe3RAHzpWZPEiu42KURiBV6gAwb3m9Ct6eLXgy253EHHt
--host 127.0.0.1
--rpc-port 18081
--zmq-port 18083
--loglevel 1
--out-peers 10
--in-peers 10
--data-api H:\gupaxx-v1.7.0-rc3-windows-x64-bundle\P2Pool
--local-api --no-color --light-mode --mini

XMRig

--no-color
--http-access-token=xxxxxxx
--http-no-restricted --threads 4
--user xxxx
--rig-id Gupaxx_v1_7_0
--url 127.0.0.1:3334
--http-host 127.0.0.1
--http-port 18088

Proxy: I disabled Auto Redirect. Iit can be enable too.

--http-access-token=xxxxxx
--http-no-restricted --no-color --user xxxx --rig-id Gupaxx_v1_7_0
-o 127.0.0.1:3333
-b 0.0.0.0:3334
--http-host 127.0.0.1
--http-port 18089

Xvb

Auto 20% , Watch P2Pool if you have external hashes

Seems to work for now thought -- looking curious.
There is a share in p2pool and 24H avg XvB is achieved. Sending 0 seconds to XvB!
In the Proxy it is showing it's mining to p2pool

[Cyrix126]

Just let it run at least an hour. Does it seems to be sending correctly now ?

[Maverik26]

Sadly not as intended. Just looked. But running it is.
Its letting the share run out.
"In luck" it is a whale round but had it been a VIP round i would of been left out.

Text windows says sending all hash to P2P but its staying on XvB

[Cyrix126]

Sadly not as intended. Just looked. But running it is. Its letting the share run out. "In luck" it is a whale round but had it been a VIP round i would of been left out.

Text windows says sending all hash to P2P but its staying on XvB

In what mode are you for XvB tab (Auto, Hero,Manual...) ?
Does it work alright if you put everything to simple mode ?

[Maverik26]

Worked too well except for the share miss. Set all but node to simple now and testing.
Noticed right away i need to keep proxy at advanced to get the workers port to my firewall setting.
Will report in an hour or so

[Maverik26]

Seems to be working either well.

What i find not so nice are big players tend to win the small rounds. Could be bad luck on our side thought.

Edit: I manually sent 5 minutes to XvB now. Not risking dropping out.
Apart from that it works nice

Appendix:
Its apparently working now. Sometimes i need to tell it to spend 13kH/s when the total is close but thats another matter.
Otherwise it would go down a donor level