You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on a reader node you might get this message every block. For blockchains that have 4 blocks/second, this is a lot of spam generated to the log.
Limit log messages to once every 30 seconds or so.
2024-06-15T15:19:07.323Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
INFO [06-15|15:19:07.534] created block l2Block=54,957,887 l2BlockHash=14b928..1229b6
2024-06-15T15:19:07.569Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:07.569Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:07.812Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:07.812Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:08.069Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:08.069Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:08.322Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:08.322Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
INFO [06-15|15:19:08.535] created block l2Block=54,957,891 l2BlockHash=cde599..c17e66
2024-06-15T15:19:08.610Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:08.610Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:08.878Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:08.878Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:09.117Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:09.117Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:09.356Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:09.356Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
INFO [06-15|15:19:09.535] created block l2Block=54,957,895 l2BlockHash=68d31f..b29a7f
2024-06-15T15:19:09.620Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:09.620Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:09.843Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
2024-06-15T15:19:09.843Z INFO (reader-node.sub.relayer) not pushing block to a closed subscription
The text was updated successfully, but these errors were encountered:
on a reader node you might get this message every block. For blockchains that have 4 blocks/second, this is a lot of spam generated to the log.
Limit log messages to once every 30 seconds or so.
The text was updated successfully, but these errors were encountered: