rykcod/massa

Massa node + massa-guard

massa's Issues

Reduce log file size if log lines are the same

I'm having a problem with the log file being too large. In about 20h, about 540000 log lines were generated, it takes up about 110Mb, it keeps growing. I checked, it's because my machine has a network error and it keeps generating the INFO log about this error, I think saving the whole log I think is not necessary, we should have 1 more option for full log storage or only shortened storage, in case of log save with shortened, if the same log line is the same, but occurs continuously, can you count it and print out the number of times it occurs? This will significantly reduce the log file size for machines that often output network failures like me.
For example:
If my full log is:
2022-10-18T09:00:18.714239Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.715263Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.716025Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.717184Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.718331Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.719588Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.720694Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.721837Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.723105Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.723974Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.725580Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.726722Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.727859Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.727934Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.729078Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
2022-10-18T09:00:18.730551Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.

Then the abbreviated log would be:
2022-10-18T09:00:18.714239Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.
Counted 14 identical log lines
2022-10-18T09:00:18.730551Z INFO massa_network_worker::network_event::event_impl: Send network event failed An error occurred during channel communication: Failed to send event.

Auto Update ?

does it support auto update?

Error [KO][NODE]TIMEOUT - NODE WILL RESTART

I got the error as shown, here is the log in the file massa-guard/20221017-massa_guard.txt.
How to fix it?

Peers

Hallo, Ryckcod

Do you have bootstrap peers list?

Best Regards

Massa Client Not Listened TEST 16

massa-client

� command · get_status
Error: check if your node is running: error trying to connect: tcp connect error: Connection refused (os error 111)

Logs :

2022-11-01T12:24:45.940315Z  INFO massa_node: Node version : TEST.16.0
2022-11-01T12:24:46.137816Z  INFO massa_bootstrap::client: Start bootstrapping from 149.202.89.125:31245
2022-11-01T12:24:46.170269Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 4270.252398647s ago and you have to wait 38929.7476012s before retrying.
2022-11-01T12:24:46.170603Z  INFO massa_bootstrap::client: Bootstrap from server 149.202.89.125:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:25:46.171770Z  INFO massa_bootstrap::client: Start bootstrapping from 158.69.120.215:31245
2022-11-01T12:25:46.362570Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 4040.514541526s ago and you have to wait 39159.485458428s before retrying.
2022-11-01T12:25:46.362785Z  INFO massa_bootstrap::client: Bootstrap from server 158.69.120.215:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:26:46.364337Z  INFO massa_bootstrap::client: Start bootstrapping from 77.40.50.164:31245
2022-11-01T12:26:46.467851Z  WARN massa_bootstrap::client: Error while bootstrapping: io error: early eof
2022-11-01T12:26:46.468352Z  INFO massa_bootstrap::client: Bootstrap from server 77.40.50.164:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:27:46.470408Z  INFO massa_bootstrap::client: Start bootstrapping from 158.69.23.120:31245
2022-11-01T12:27:46.663659Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 5058.663387752s ago and you have to wait 38141.336612164s before retrying.
2022-11-01T12:27:46.663944Z  INFO massa_bootstrap::client: Bootstrap from server 158.69.23.120:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:28:46.665745Z  INFO massa_bootstrap::client: Start bootstrapping from 154.26.132.217:31245
2022-11-01T12:28:47.003563Z  WARN massa_bootstrap::client: Error while bootstrapping: io error: early eof
2022-11-01T12:28:47.004286Z  INFO massa_bootstrap::client: Bootstrap from server 154.26.132.217:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:29:47.006050Z  INFO massa_bootstrap::client: Start bootstrapping from 149.202.86.103:31245
2022-11-01T12:29:47.051222Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 6454.498238812s ago and you have to wait 36745.501761098s before retrying.
2022-11-01T12:29:47.051564Z  INFO massa_bootstrap::client: Bootstrap from server 149.202.86.103:31245 failed. Your node will try to bootstrap from another server in 60s.
2022-11-01T12:30:47.053462Z  INFO massa_bootstrap::client: Start bootstrapping from 198.27.74.5:31245
2022-11-01T12:30:47.235108Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 4159.5918281s ago and you have to wait 39040.408171797s before retrying.
2022-11-01T12:30:47.235354Z  INFO massa_bootstrap::client: Bootstrap from server 198.27.74.5:31245 failed. Your node will try to bootstrap from another server in 60s.

/massa-guard/massa-guard.sh: line 49: [: -eq: unary operator expected

There seems to be a bug in massa-guard.sh.

I am running the node with Logs enabled (default).
The following line is spammed into logs when running: ```docker logs massa-node -f````

/massa-guard/massa-guard.sh: line 49: [: -eq: unary operator expected
/massa-guard/massa-guard.sh: line 49: [: -eq: unary operator expected
/massa-guard/massa-guard.sh: line 49: [: -eq: unary operator expected
/massa-guard/massa-guard.sh: line 49: [: -eq: unary operator expected
/massa-guard/massa-guard.sh: line 49: [: -eq: unary operator expected
/massa-guard/massa-guard.sh: line 49: [: -eq: unary operator expected

Node does not automatically restart when stopped

Hello, my node is stopped, but it is not restarted automatically, the node log file is like the picture, how to fix it?

Stuck

Mine got stuck in here ,,it didn't create anything... Any solutions ?
tail -f /massa/massa_mount/logs/massa-guard/20220624-massa_guard.txt
[20220624-18H39][INFO][LOAD]LOAD /massa_mount/config.toml as ref
[20220624-18H56][INFO][LOAD]LOAD /massa_mount/config.toml as ref
[20220624-19H19][INFO][INIT]Create your default config.toml with X.X.X.X as routable IP
[20220624-19H49][INFO][INIT]Create your default config.toml with X.X.X.X as routable IP

How do you get discord token?