Not yet, I don’t have a public or private repos at github/gitlab websites or an account there. The Grafana JSON as is will be useless without the underlying schema / database medium, log extraction & conversion process, required setup components, and the relevant configuration files. There is a bunch of moving pieces here. I need to think about this some more. This was all done very rapidly in the past 5-10 days.
I am really hoping in the long run there is more standardization at the source of the log files creation from safenode. Its currently a mix of structured and unstructured data, so extracting info was a challenge, as the collector, converter, and forwarder had to handle multiple different scenarios and input/output formats on a case by case basis.
If we can at least move towards say all JSON log entries or whatever standard format the team decides, it will help reduce the edge cases and the complexity in the ETL process, otherwise it will remain very brittle, death by a , as I just noticed today, and with it a constant support headache, .
It seems the --json-output disappeared at some point, . Will it ever come back? .
I’d imagine this is something that we just haven’t carried over from the previous node implementation, and it was probably something being provided from the tracing library. Let me look into that for you. Should hopefully not be too much hassle to get that going again.
If you have anything to suggest here that you’d like to see, I’d be happy to take it to the team. Please feel free to provide any concrete examples.
I think it would be cool if you thought about how we could perhaps get it in a repository. It could potentially be very useful to either PR this to one of our infrastructure repos, or perhaps have it in a community repo:
Ah, that PID should be gone in a follow up PR! Sorry about that.
on log standardisation. We could start moving towards more useful logs wherever makes sense. If there’s something you’d like to see feel free to open an issue speccing something (i see no reason we can’t bring back json btw… ).
I’m wondering atm how useful it would be to be to pipe all logs to a public aws bucket eg. Might be nice for everyone to be able to pull logs from any running droplet/node (although perhaps maid ones might not be json to allow for clearer debugging… or maybe they should be )
Well I was hopeful, I got further than using Termux. Can’t figure out what the issue is, not sure if it is app permissions or what, it just wont play ball.
I’ll call it a night tonight, but will check back in tomorrow.
If there are any Windows and/or macOS users out there, it would be great if you could participate and tell us your experiences with the installation stuff!
Worked properly since the above script triggers safeup node .
For others, just a reminder to not run safenode command from the --log-dir path specified being your current pwd, since it deletes the current directory, leaving you with the ash: getcwd: no such file or directory error and an invalid or stale handle to the current pwd.
See below:
safe-build-122:/mnt/x/y/z# SN_LOG=all safenode --log-dir=/mnt/x/y/z/ --root-dir=/mnt/a/b/c/ --port 12000 --rpc 127.0.0.1:12002 &
safe-build-122:/mnt/x/y/z# Removed old logs from directory: "/mnt/x/y/z/"
Logging to directory: "/mnt/x/y/z/"
Using SN_LOG=all
RPC Server listening on 127.0.0.1:12002
ash: getcwd: No such file or directory
safe-build-122:(unknown)# exit
The safenode pid still spawned up and started operating properly. One would just need to re-navigate the shell to a proper directory path again.
The filesize (integer) part, should I just add the bytes?
Btw I get this
“Invalid uploaded URL. Must be exactly 65 hexadecimal characters.”
Should that not be 64 hex?
eddy@Hal9000:~$ safe files download Fw.jpeg 963b94deadf9d840f38d35db0cb18cd833f3958c4dcd178cfd365f03f24ab766
Removed old logs from directory: "/tmp/safe-client"
Logging to directory: "/tmp/safe-client"
Built with git version: f5e6ab7 / main / f5e6ab7
Instantiating a SAFE client...
🔗 Connected to the Network Downloading file "Fw.jpeg" with address 963b94deadf9d840f38d35db0cb18cd833f3958c4dcd178cfd365f03f24ab766
Successfully got file Fw.jpeg!
Writing 132454 bytes to "/home/eddy/.safe/client/Fw.jpeg"
What does this mean in very matter of fact way? Could someone give some example where I could find such directory? Or how to know if I have been using them or not?
So if I’d like to do anything else with this testnet than just install, I should have a specific version? What is it? Can someone post a command for copy-pasting, please?
PS C:\Users\John> safeup node ************************************** * * * Installing safenode * * * ************************************** Installing safenode.exe for x86_64-pc-windows-msvc at C:\Users\John\safe... Error: Release sn_node-v0.83.38 has no asset for platform x86_64-pc-windows-msvc
Also - there are no Windows instructions for using the env variable. Guessing it should be set instead of export
# using the SAFE_PEERS variable
set SAFE_PEERS=/ip4/68.183.44.129/tcp/38921/p2p/12D3KooWN3P9exk23WW7naW7Kb1rdzZeLpZRHXtF5ntyQtJrsiF7
But after doing that I still can’t connect
PS C:\Users\John> set SAFE_PEERS=/ip4/68.183.44.129/tcp/38921/p2p/12D3KooWN3P9exk23WW7naW7Kb1rdzZeLpZRHXtF5ntyQtJrsiF7
PS C:\Users\John> safe files download 361adff80ea7efb05cbf865803a7bfa134b9137fd02efec724f6cad2cf20414d
Logging to directory: "C:\\Users\\John\\AppData\\Local\\Temp\\safe-client"
Built with git version: f725637 / main / f725637
Instantiating a SAFE client...
Error: No peers given. As `local-discovery` feature is disabled, we will not be able to connect to the network.
Location:
sn_cli\src/main.rs:54:24
Will retrieve safeup for x86_64-apple-darwin architecture
Latest version of safeup is 0.3.4
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
100 2472k 100 2472k 0 0 3038k 0 --:–:-- --:–:-- --:–:-- 14.0M
safeup installed to /Users/imac27/.local/bin/safeup
Now running safeup to install the safe client…
*
Installing safe *
*
Installing safe for x86_64-apple-darwin at /usr/local/bin…
Error: Permission denied (os error 13)
.
. Will it ever come back? 
)
