Support for problematic node

[Alexey]

@support27

2024-08-28T19:57:06-04:00 FATAL Unrecoverable error {"error": "Error opening database on storagenode: database: notifications opening file \"D:\\\\notifications.db\" failed: context canceled

Seems you didn’t move databases to the system drive or SSD and your disk is too slow to respond to allow to start the node.
Please move databases to SSD:

Move databases on Windows storagenode

Yes, you can. Stop the storagenode Move databases to a new place (C:\storagenode\cache\ for example) Add a new path to databases to the storage2.database-dir: option: storage2.database-dir: C:\storagenode\cache\ Save the config Start the storagenode Check that you do not have a new databases in a old place and the dashboard shows a correct numbers. However, keep in mind - you will introduce a new point of failure.

Then monitor your logs for other Unrecoverable or FATAL errors.

@support27

Meaning that your node is offline, as you may notice the indication in the left upper corner of your dashboard.
There are several reasons:

1. The service is restarting or stopped
2. Your external address and/or port are wrong or the address does not match your WAN IP on your router and/or IP on Open Port Check Tool - Test Port Forwarding on Your Router.
   2.1. Make sure that the WAN IP on your router matches the IP on the site above, otherwise the port forwarding rule on your router will not work.
   2.2. You need to update the contact.external-address: with the correct external address and port in the following format: address:port
   2.3. Save the config and restart the node
3. You have a difference between the WAN IP and the IP on yougetsignal site. In that case you need to contact your ISP to enable the public IP, it could be dynamic, but must be a public (the WAN IP will match the IP from yougetsignal).
   3.1. In the case of a static public IP you may use it directly in the contact.external-address: parameter
   3.2. In the case of a dynamic public IP you can register an own DDNS hostname and use it instead of IP address in the contact.external-address: parameter.
4. Your local IP of your PC may changed, but the router still has the old IP in the port forwarding rule, then you need to update the port forwarding rule on your router to use the current local IP of your PC.