Difference between revisions of "ARS0106E"
Jump to navigation
Jump to search
(Initial edit.) |
m (Formatting) |
||
| Line 6: | Line 6: | ||
There are four scenarios when this error can occur: | There are four scenarios when this error can occur: | ||
* While running [[arsadmin]] unload - CMOD was unable to delete a file during the unload. | |||
* While running [[arsload]] - during a failed load, CMOD was unable to delete the objects it inserted into the cache. | |||
* While running [[arsmaint]] - during regular expiration processing, CMOD couldn't delete an object eligible for expiration. | |||
* While running [[arsload]] - the file already exists in the cache, and CMOD couldn't delete it before overwriting it. | |||
The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]]. | The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your [[Cache Filesystem]]. | ||
The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time *prior* to when the cache filesystem was backed up. | The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time *prior* to when the cache filesystem was backed up. | ||
Revision as of 10:49, 24 March 2015
Message Text: Unlink failed for file >filename< errno=<ErrorNumber> Srvr->ServerName<-
The server couldn't delete a file in the cache filesystem.
There are four scenarios when this error can occur:
* While running arsadmin unload - CMOD was unable to delete a file during the unload. * While running arsload - during a failed load, CMOD was unable to delete the objects it inserted into the cache. * While running arsmaint - during regular expiration processing, CMOD couldn't delete an object eligible for expiration. * While running arsload - the file already exists in the cache, and CMOD couldn't delete it before overwriting it.
The first three errors can likely be resolved by working with your System Administrator to resolve permissions-related issues on files or directories inside your Cache Filesystem.
The last error is a critical error, and may indicate that your cache filesystem is corrupted. This may also occur after the OnDemand database was restored to a point in time *prior* to when the cache filesystem was backed up.