Hello communities,
I have tested all cases in storj-sim but I have one doubt is storj-sim able to do reputaion, payout and audit services?
If yes then when it get triggered?
From which side it will done satellite or storage node?
I am so confused between these…
Please help me regarding this.
I am tagging you all because I know I can get needed from you all and yes others are also most welcome to discuss on this.
Thanks all in advance… 
Payout service is a part of the satellite in case of storj-sim, so it’s running. You may check parameters in the satellite’s config.yaml file:
grep "payout" ~/.local/share/storj/local-network/satellite/**/config.yaml
for Windows PowerShell:
sls "payout" $env:AppData/Storj/local-network/satellite/**/config.yaml
or with the setup --help command:
satellite setup --help | grep "payout"
for Windows PowerShell:
satellite setup --help | sls "payout"
Audit workers and repair workers are part of the satellite in case of storj-sim, so they running.
There is no concept of “how often”, they are checks pieces in the infinite loop across all segments, more segments - longer the whole cycle, to fill gaps you may increase concurrency (number of parallel workers).
You may check audit workers’ parameters in the satellite’s config.yaml:
grep "worker" ~/.local/share/storj/local-network/satellite/**/config.yaml
for Windows PowerShell:
sls "worker" $env:AppData\Storj\local-network\satellite\**\config.yaml
or with the setup --help command:
satellite setup --help | grep worker
for Windows PowerShell:
satellite setup --help | sls worker
The same deal with the repair workers - they are running in the infinity loop too.
Parameters of the repair workers you may check in the satellite’s config.yaml file:
grep "repair" ~/.local/share/storj/local-network/satellite/**/config.yaml
for Windows PowerShell:
sls "repair" $env:AppData/Storj/local-network/satellite/**/config.yaml
or with the setup --help command:
satellite setup --help | grep "repair"
for Windows PowerShell:
satellite setup --help | grep "repair"
I got this error after running above command
Environment: win32, node 16.16.0, framework 3.29.0, plugin 6.2.3, SDK 4.3.2
Docs: docs.serverless.com
Support: forum.serverless.com
Bugs: github.com/serverless/serverless/issues
Error:
Serverless command "payout" not found. Run "serverless help" for a list of all available commands.
write /dev/stdout: The pipe has been ended.
I do not know what is responding like this. I do not have such an error.
Did you run this command from PowerShell?
I have ran this on cmd…
Please use a PowerShell instead.
I have just tried on powershell but it doesn’t give me any output…
You are correct, you need to search for compensation, not payout, I was wrong.
In PowerShell:
sls "compensation" $env:AppData/Storj/local-network/satellite/**/config.yaml
and
satellite setup --help | sls "compensation"
The payout itself is executed separately, I do not know the exact procedure.
You may check these commands:
satellite billing --help
satellite compensation --help
Hey @Alexey ,
Thanks for your reply but I still get the error
Environment: win32, node 16.16.0, framework 3.29.0, plugin 6.2.3, SDK 4.3.2 Docs: docs.serverless.com Support: forum.serverless.com Bugs: github.com/serverless/serverless/issues Error: Serverless command "compensation" not found. Run "serverless help" for a list of all available commands.
on running satellite setup --help | sls "compensation"
What should I do?
Is there any other way to do that…!
You need to run it in PowerShell, not cmd.
For cmd you may replace sls with findstr
Thanks for your reply @Alexey ,
Yes it works…
One more question that How many times or when satellite pings the node?
Is there any specific time period for that (same for reputation and audit )?
I can see this is working in storj-sim but can not figure out who(which process/module specifically) triggers that?
One more thing from where I found the system diagram(system flow) for storj-sim network ?
As I said before, there is no time intervals. Auditors and repair workers working in infinity loop across all segments.
Satellites did not ping the node until it check-in. So it’s reverse - the node contact satellites (“check-in”) and updates it with its free and used space, send orders and receive a ping back from the satellite using node’s external address to check availability and provide collected Stat to the node back (disk and registered bandwidth usage).
The node contact satellite once a hour by default
storagenode setup --help | findstr "contact"
--contact.external-address string the public address of the node, useful for nodes behind NAT
--contact.interval duration how frequently the node contact chore should run (default 30s)
storj-sim high level diagram:
common diagrams:
