Uploading: Screenshot_20220628-030700.png…
This is node 0
I like your idea and i’ll contribute as well.
I’ll throw in some of my EU fibernodes, just ping me if you need my support.
1 Like
@1qazx If our test nodes can be small (e.g. 10GB) to start with, maybe I’ll join too to see how it goes.
1 Like
Stupid question, how do you “Add” a satelite to your node? Is there a documented procedure to do so?
1 Like
wondering the same thing
1 Like
It’s a config change. Example…
if true, uses peer ca whitelist checking
server.use-peer-ca-whitelist: false
list of trust sources
storage2.trust.sources: 1GGZktUwmMKTwTWNcmGnFJ3n7rjE58QnNcRp98Y23MmbDnVoiU@satellite.qa.storj.io:7777, 12ZQbQ8WWFEfKNE9dP78B1frhJ8PmyYmr8occLEf1mQ1ovgVWy@testnet.satellite.stefan-benten.de:7777
server address to check its version against
version.server-address: https://version.qa.storj.io
Interval to check the version
version.check-interval: 5m0s
The first config will disable the signed indentity. Yes you don’t need to sign your identify for the test network. If you have a signed identity you still need to add this config change because otherwise your node will refuse to talk to a satellite that can also not provide a signed idenity. The identity signature check works in both directions. This config change will disable it.
The second config will tell your storage node to trust the QA satellite. The QA satellite is currently behaving like production. We have full control over the config. Feel free to request any config change you want us to try out.
The third config will tell your storage node updater to install pre-release binaries early. On my system I am running a test node inclusive updater as systemd service. With this config, the test node will follow its own rollout cycle. If you are running a docker node please also add that config even if it currently doesn’t affect the docker rollout.
The fourth config will reduce the update interval from 15 minutes to 5 minutes. If there is a problem it is a bit painful to wait 15 minutes.
Info taken from - Please join our public test network
Thanks for being willing to try everyone and yes tiny nodes are fine
@littleskunk I got some data in it how would i export it to a readable format
ATM it looks like below (using docker postgres)
-±---------------±-------------------±-----------------±-----------------±-
--------------±-------------±----------------------±-------------
(0 rows)
teststorj=# | interval_precision | character_set_catalog | cha
racter_set_schema | character_set_name | collation_catalog | collation_schema | SELECT * FROM information_schema.columns WHERE table_schema = ‘satellite/0’ AND table_name = ‘accounting_rollups’;
table_catalog | table_schema | table_name | column_name | ordinal_
position | column_default | is_nullable | data_type | character_m
aximum_length | character_octet_length | numeric_precision | numeric_precision_r
adix | numeric_scale | datetime_precision | interval_type | interval_precision |
character_set_catalog | character_set_schema | character_set_name | collation_c
atalog | collation_schema | collation_name | domain_catalog | domain_schema | do
main_name | udt_catalog | udt_schema | udt_name | scope_catalog | scope_schem
a | scope_name | maximum_cardinality | dtd_identifier | is_self_referencing | is
_identity | identity_generation | identity_start | identity_increment | identity
_maximum | identity_minimum | identity_cycle | is_generated | generation_express
ion | is_updatable
---------------±-------------±-------------------±-----------------±--------
---------±---------------±------------±-------------------------±-----------
--------------±-----------------------±------------------±-------------------
-----±--------------±-------------------±--------------±-------------------+
-----------------------±---------------------±-------------------±-----------
-------±-----------------±---------------±---------------±--------------±–
----------±------------±-----------±------------±--------------±-----------
–±-----------±--------------------±---------------±--------------------±–
----------±--------------------±---------------±-------------------±--------
---------±-----------------±---------------±-------------±------------------
----±-------------
teststorj | satellite/0 | accounting_rollups | node_id |
…skipping 1 line
teststorj | satellite/0 | accounting_rollups | start_time |
2 | | NO | timestamp with time zone |
| | |
| | 6 | | |
| | |
| | | | |
| teststorj | pg_catalog | timestamptz | |
| | | 2 | NO | NO
| | | |
| | NO | NEVER |
| YES
teststorj | satellite/0 | accounting_rollups | put_total |
3 | | NO | bigint |
| | 64 |
2 | 0 | | | |
| | |
| | | | |
| teststorj | pg_catalog | int8 | |
| | | 3 | NO | NO
| | | |
| | NO | NEVER |
| YES
teststorj | satellite/0 | accounting_rollups | get_total |
…skipping 1 line
teststorj | satellite/0 | accounting_rollups | get_audit_total |
5 | | NO | bigint |
| | 64 |
2 | 0 | | | |
| | |
| | | | |
| teststorj | pg_catalog | int8 | |
| | | 5 | NO | NO
| | | |
| | NO | NEVER |
| YES
teststorj | satellite/0 | accounting_rollups | get_repair_total |
6 | | NO | bigint |
| | 64 |
2 | 0 | | | |
| | |
| | | | |
| teststorj | pg_catalog | int8 | |
| | | 6 | NO | NO
| | | |
| | NO | NEVER |
| YES
teststorj | satellite/0 | accounting_rollups | put_repair_total |
…skipping 1 line
teststorj | satellite/0 | accounting_rollups | at_rest_total |
8 | | NO | double precision |
| | 53 |
2 | | | | |
| | |
| | | | |
| teststorj | pg_catalog | float8 | |
| | | 8 | NO | NO
| | | |
| | NO | NEVER |
| YES
(8 rows)
Just making sure. Don’t use production nodes for this testing. If you have test nodes already, use those. Or spin up new ones.
If I start a new node, how do I make it not talk to official Storj satellites and only to this (or some other) satellites?
If you follow the steps @Knowledge linked you see that you have to edit the trust sources setting. That normally points to a hosted list of production satellites here https://www.storj.io/dcs-satellites . Replacing that already tells the node not to use production satellites.
1 Like
Thank you. If the community satellite needs nodes, I can start a new node for it, I have some space in my pool.
Ok guys the info to connect is here People to participate in a currently UNPAID community experiment
i’m interested, but i do wonder…
what are the security implications of adding community satellites to existing storagenodes?
We are explicitly cautioning against testing this with your existing production nodes.
5 Likes
They recommend separate hardware so it’s highly unlikely it will affect anything
BUT DEFINITELY DON’T USE PRODUCTION NODES
2 Likes
@Pentium100 is it still working alright today the satellite had a db issue hopefully it is now up while tonight(probably a long one hahah) I write a script to make more continuous backups and store my db back up on a us1 bucket
If your node has one of these node id’s I will have to maybe restart the satellite and work on back ups
“unhealthy node IDs”: “1WicS4XMDJ7BJCF8KpFMxE5C9CVFSfWRFwSgYXNCSt82qdgX3M,128iYF45nrxyxEy3js5n3qs24fjrDbSthH1NSz3rW2aBA8SYLmq,12aAy3EwCp2ZAEyzrbsymW8Vc35pM4KgBGAijhvYRYpFwMxxjpd,1vHXuNum36SkWpQLRE3HxpfDGB2EWMzn5TuJCRBNGs9g8k28uD,12CbCyxquDqprrtUr2fVZV8CJweL2CinTzyoqARYqrp3TJhCT9z,1HcnbK2gtsGFJ2FnFMDaaAoYhbDJ3gTTVvdEmELkanYbv3wf4N,1SbCEMhmBaWNDK1iGhq14giXR2z1dzJbxTvgTFVANwDfutJnJn,1rN1tTB3spi3r4PSHucAkX682WMZt2NFquBqyCkrCNbNUWYDy4”}
Btw if your Id is in here I’m sorry it’s not your fault it’s mine
My node says online, but there is no traffic.
Not even the old traffic?
Also is your node Id in that list if so that explains it(no traffic) and the sat will need to be started again and I will make it better by enabling us1 backup
Available Used Egress Ingress
Bandwidth N/A 11.48 MB 0 B 11.48 MB (since Jun 1)
Disk 0.80 TB 11.48 MB
In total my node got one piece 11.48MB and that was it, nothing else, no other uploads, downloads or audits.
My node ID is 1CM9eKV8x6oqYYmjLmg3PGF3Dm7bxChbySAipBdNt3WEaVpJcf, I did not see it on that list.