storagenode | 2023-11-14T14:28:12Z INFO Configuration loaded “Process”: “storagenode-updater”, “Location”: “/app/config/config.yaml”}
storagenode 2023-11-14T14:28:12Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”
storagenode | 2023-11-14T14:28:12Z INFO Invalid configuration file key “Process”: “storagenode-updater”, “Key”: “server.private-address”}
storagenode 2023-11-14T14:28:12Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”
storagenode | 2023-11-14T14:28:12Z INFO Invalid configuration file key “Process”: “storagenode-updater”, “Key”: “operator.email”}
storagenode 2023-11-14T14:28:12Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”
storagenode | 2023-11-14T14:28:12Z INFO Invalid configuration file value for key “Process”: “storagenode-updater”, “Key”: “log.level”}
storagenode 2023-11-14T14:28:12Z INFO Anonymized tracing enabled {“Process”: “storagenode-updater”
storagenode | 2023-11-14T14:28:12Z INFO Running on version “Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.90.2”}
storagenode 2023-11-14T14:28:12Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”
storagenode | 2023-11-14T14:28:12Z INFO Current binary version “Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.90.2”}
storagenode 2023-11-14T14:28:12Z INFO New version is being rolled out but hasn’t made it to this node yet {“Process”: “storagenode-updater”, “Service”: “storagenode”
storagenode | 2023-11-14T14:28:12Z INFO Current binary version “Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.90.2”}
storagenode 2023-11-14T14:28:12Z INFO New version is being rolled out but hasn’t made it to this node yet {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”
storagenode | 2023-11-14 14:28:13,195 INFO exited: storagenode (exit status 1; not expected)
storagenode | 2023-11-14 14:28:14,196 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
storagenode | 2023-11-14 14:28:14,197 INFO spawned: ‘storagenode’ with pid 88
storagenode | 2023-11-14 14:28:14,197 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
storagenode | 2023-11-14 14:28:14,487 INFO exited: storagenode (exit status 1; not expected)

The “info” level errors don’t seem to be related to the cause of it crashing, or else it wouldn’t be an info level error. right?

Anyone else seeing this behavior?

  • AK_4_Life@alien.topBEnglish
    1·
    10 months ago

    Once a month or so yes. Then I restart it and it will update and die again right away then be fine after a second restart.

  • helmex@alien.topBEnglish
    1·
    10 months ago

    It is likely that you could find more feedback from other node operators regarding your issue if you posted in our forum.

  • Kris_OnReddit@alien.topBEnglish
    1·
    10 months ago

    I used to have this running on QNAP docker. At some point I had this daily. I moved my 2 nodes to a mini pc with Ubuntu and it run flawlessly.