Please enter search query.
Search <book_title>...
Veritas Access Release Notes
Last Published:
2020-10-16
Product(s):
Access (7.4.2)
Platform: Linux
- Overview of Veritas Access
- Fixed issues
- Software limitations
- Flexible Storage Sharing limitations
- Limitations related to installation and upgrade
- Limitation related to replication
- Known issues
- Veritas Access known issues
- Admin issues
- Backup issues
- CIFS issues
- Deduplication issues
- FTP issues
- General issues
- GUI issues
- Installation and configuration issues
- Internationalization (I18N) issues
- Networking issues
- NFS issues
- ObjectAccess issues
- OpenDedup issues
- OpenStack issues
- Replication issues
- SDS known issues
- SmartIO issues
- Storage issues
- System issues
- Target issues
- Upgrade issues
- Veritas Data Deduplication issues
- Veritas Access known issues
- Getting help
If you run the Cluster> show command when a slave node is in the restart, shutdown, or crash state, the slave node throws an exception
In a particular flow, if the node that is in the restart, shutdown, or crash state is running, the system calculates the running node list. It returns unreachable on SSH when the command starts to calculate the CPU or network statistics. The internal library throws an exception.
Once the state of the node is in shutdown, restart, or crash state, the slave node changes from RUNNING to FAULTED in Veritas Cluster Server (VCS). The Cluster> show command resumes its normal behavior. That is, it does not show any exception and gives an expected output.
Workaround:
There is no workaround for this issue. The system recovers itself. You need to wait for some time and run the Cluster> show command once again.