Wasabi Cloud NAS (WCN) can log most events related to bucket and source connectivity events using a standard Windows output console, such as DebugView. By default, WCN logs whenever the status of a directory is changed (replicated or nearline). You can configure WCN to trigger event notifications, log, and output log files in the Windows Event Viewer for the following events:
Replicate file
Reclaim space
Retrieve file
When any of these events occur, there are three log types that report the event:
Information Logs — Logs a successfully performed operation. For more detail, review Information Logs, below.
Warning Logs — Logs an unsuccessful attempt to perform an operation. Warning logs signify a temporary problem. WCN will attempt to perform the operation again until the operation either succeeds or reaches the threshold of scheduled attempts. If the threshold of scheduled attempts is reached, WCN will log an error. For more detail, review Warning Logs, below.
Error Logs — Logs a failure to perform an operation. Error logs signify a problem, which requires user intervention to resolve the error. For more detail, review Error Logs, below.
Unlike warning messages (that signify a temporary problem), error messages report that WCN has reached the threshold of scheduled attempts to accomplish the operation. Once the threshold is reached, you must restart the computer running WCN to attempt to accomplish the operation(s) anew.
Information Logs
Information Log Message | Description |
|---|---|
Source <source path> connected to <bucket type> bucket. | WCN uccessfully connected the specified source to its bucket. |
Replication bucket for source <source path> is online now. | This is displayed after an unsuccessful attempt(s) to connect the specified source to the bucket, once the bucket is accessible to WCN and it can perform data management operations on it. |
File <path to file on source> is successfully replicated on the bucket. | The specified file has been successfully replicated on the bucket by the automatic or manual Data Replication mechanism. |
Replication of file <path to file on source> has been aborted due to requested write access to it. | The replication of the specified file has been aborted because a user or application opened it on the source. If the file has been scheduled for automatic Data Replication, once it is no longer in use, it will be queued for replication anew. |
File <path to file on source> is replaced with a stub file on the source. | The specified replicated file has been successfully replaced by a nearline file on the source by the automatic or manual Space Reclaiming mechanism. |
File <path to file on source> <process name> is successfully retrieved on the source. | The specified nearline file on the source has been successfully retrieved from the bucket. If the nearline file has been retrieved manually through the shell extension, the process name is “user operation.” If the nearline file has been retrieved by attempting to open it on the source, the message displays the name of the process. |
Warning Logs
Warning Log Message | Description |
|---|---|
Source <path to source> failed to connect to <bucket type> bucket. | The bucket of the specified source is currently inaccessible. The reason for the problem may be a lost connection or changed credentials for access to the bucket. WCN attempts to connect to the bucket and displays an error message if it fails to do so within a specified time period. |
Replication bucket for source <path to source> is not accessible. | The specified source has been disconnected from its bucket, because it is currently inaccessible. The reason for the problem may be lost a connection or changed credentials for access to the bucket. WCN attempts to reconnect to the bucket and displays an error message if it fails to do so within a specified time period. |
Replication of file <path to file on source> failed. | A WCN attempt failed to replicate the specified file to the bucket. The reason for the failed operation may be temporary inaccessibility of the bucket, for example. The message is displayed until the operation succeeds or until WCN reaches the maximum number of attempts in which case it displays an error message. |
Replacing file <path to file on source> with a stub file on the source failed. | A WCN attempt failed to automatically reclaim space on the source by replacing the specified file with a nearline file. The message is displayed until the operation succeeds or until WCN reaches the maximum number of attempts in which case it displays an error message. |
Adding file <file name> failed. | A WCN attempt failed to synchronize the contents of two sources through a common bucket by creating a nearline file in the source of one computer upon receiving notification for replicated file from another computer. The reason for the failed operation may be temporary inaccessibility of the bucket, for example. The message is displayed until the operation succeeds or until WCN reaches the maximum number of attempts in which case it displays an error message. |
Removing file <file name> failed. | A WCN attempt failed to synchronize the contents of two sources through a common bucket by removing a nearline file in the source of one computer upon receiving notification for removed file from another computer. The reason for the failed operation may be temporary inaccessibility of the bucket, for example. The message is displayed until the operation succeeds or until WCN reaches the maximum number of attempts in which case it displays an error message. |
Renaming file <current file name> to <updated file name> failed. | A WCN attempt failed to synchronize the contents of two sources through a common bucket by renaming a nearline file in the source of one computer upon receiving notification for file rename on another computer. The reason for the failed operation may be temporary inaccessibility of the bucket, for example. The message is displayed until the operation succeeds or until WCN reaches the maximum number of attempts in which case it displays an error message. |
Failed to parse sync notification <notification ID>. | A WCN attempt failed to parse a notification for updated contents on one computer when synchronizing it with the contents of another computer through a common bucket (Active Sync). The message is displayed until the operation succeeds or until WCN reaches the maximum number of attempts in which case it displays an error message. |
Failed to process notification <notification ID>. | A WCN attempt failed to process a notification for updated contents on one computer when synchronizing it with the contents of another computer through a common bucket (Active Sync). The message is displayed until the operation succeeds or until WCN reaches the maximum number of attempts in which case it displays an error message. |
Error Logs
Error Log Message | Description |
|---|---|
Source location is missing. Volume with guid <volume GUID> is not mounted. | WCN failed to load a source because the GUID of the volume on which it is stored does not match the GUID of any volume accessible to WCN. |
Source location <path to source> is missing. | WCN managed to load the volume on which the specified source is stored, but failed to load the source itself because the path to it has changed (a folder is renamed, for example) or is missing (the folder added as a source has been deleted). |
Source <path to source> cannot be loaded. | WCN failed to load a source because its file system is not supported. For example, a Wasabi Store-managed volume added as a source is now mounted as a Wasabi Client. |
Replication of file <path to file on source> failed. | All attempts to replicate the specified file on the bucket have failed, for example, because the bucket is inaccessible. To let WCN attempt to replicate the file again, you must restart WCN. |
Retrieving file <path to file on source> <process name> from the bucket failed. | All attempts to retrieve the specified file from the bucket have failed because, for example, the bucket is inaccessible. To let WCN attempt to retrieve the file again, you must restart WCN. |
Wasabi recommends that you keep track of the number of log files generated by WCN to avoid running out of disk space.
Configuring Wasabi Cloud NAS Logs
The Wasabi Cloud NAS Configuration interface enables you specify which of the following events should be outputted as logs in the Windows Event Viewer:
File is replicated
File is replaced with a nearline file
Nearline file is retrieved from the bucket
To configure WCN logs in the Configuration Interface, follow the steps below.
Click Global Settings.
Under Event Viewer Logs, click the checkbox to select one or more of the following events for which to have WCN output logs:
Replicate file
Reclaim space
Retrieve file
Optionally, to prevent WCN from outputting logs for an event, click
to deselect an event.Click Apply all.
A message will notify you that WCN must restart to apply the changes. Click Yes.
A message will confirm that the changes have been applied and that WCN is now paused. Click OK.
.png)
To resume operations, click Wasabi Cloud NAS.
Click Resume.
To preview the event logs, navigate to Applications and Services Logs > OpenSSH > Wasabi Cloud NAS. Optionally, use a third-party tool to automate the processing of notifications about important events.