You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,9 @@
1
1
# Linux-Troubleshooting-Scenarios-with-solutions
2
2
Linux Troubleshooting Scenarios based question with solutions
3
3
4
-
Its crucial to understand the problem statement before proceeding to any action.
4
+
Its crucial to understand the problem statement before proceeding for any action. The first action should not be to rush out to server side and try to troubleshoot the issue. The first approach would be is to try to understand the issue and ask the user/client follow up questions to understand the problem properly. Its often happen that the issues are on the client/user side who reported it and lot of the time get spend into understand or even become impossible to get it resolved. So don't preassume that your client/user would be technical and whatever the shared information is 100% right. We have to ask the questions to build the facts for the formation of right direction.
5
+
6
+
In the below cases, we tried to expand and understand the problem statement. As it would provide us the clear crystal clear image to brain that whats happening and in which direction we have to move forward.
5
7
6
8
<details>
7
9
<summary>Server is not reachable or cannot connect</summary>
0 commit comments