We have been dealing with unknown behavior in our ScienceLogic Environment, and we would like to explain point wise to keep it clean.
- Application Team has reported us that File system Unavailable events are landing in their SNOW queue in the form of ticket.
- We have investigated and File System unavailable major events have been triggered. Furthermore, we have navigated into Registry » Hardware » searched with specific server name to find out reported File System have been discovered or not.
- We have found that those are not discovered and when connected back to the application team. we have got two types of inputs.
- 1st » multiple File System unavailable event are trigger for user profile for example /home/baljeets [whenever user log into Solaris Server. there profile will be created and once they logoff from the server FS related to their profile will be unmounted and ScienceLogic triggers major]
- 2nd » backup job will be triggering time to time and once the backup job is complete. same kind of file system unavailable major event will be triggered