# Troubleshooting & Debugging
As part of day-2 of 50days of Devops learning journey. Today i tried to install all the required tools via shell script. Able to install with basic script which missed some debugging/error handling capabilities later i modified the script and to test that script i created one more shell script named as `cleanup.sh` to remove all the existing folders and packages related to the project i am working on. Which gave me some learning
**Note :** i am using ubuntu 24 version as OS in an EC2 instance
* It worked perfectly for all the packages except `python` errors and the solutions are provided below 👇 once python removed and tested setup script which throw me an error related to docker installation which is again another learning . How i fixed this issues are listed below
### Docker installation Issue
### python package removal issue
Solution :
The error regarding unmet dependencies when attempting to remove Python indicates a conflict between package versions or held packages
1. Fix broken dependencies `sudo apt-get install -f`
2. Reconfigure packages `sudo dpkg --configure -a`
3. clean package cache
```sh
sudo apt-get clean
sudo apt-get autoclean
```
4. Identify Hold packages `sudo apt-mark showhold` if you find something then use `sudo apt-mark unhold`
5. Force Removal of problematic packages
`sudo dpkg --remove --force-all `
6. use aptitude for dependency resolution
Aptitude is a more advanced package manager that can resolve complex dependency issues
`sudo apt-get install aptitude` `sudo aptitude purge python3.*`
Note : sometimes \* may not work, has to specifically mention our package name i.e; 3.13 etc
7. Retry Removal
`sudo apt-get purge --auto-remove python3.* -y`
8. Verification
```sh
which python3
ls /usr/bin/python*
```
### Git Troubleshooting
The error `src refspec main does not match any` indicates that there is no local branch named `main` in your Git repository
Solution :
1. Verify local branch `git branch`
2. Renamed local branch `git branch -m master main`
3. commit changes to local brqnch `git status` `git add README.md ; git commit -m "initial commit"`
4. Push to remote repository `git push -u origin main`
5. Handling different remote branches `git push -u origin main:develop` here `main` is the local branch and `develop`is the remote branch
6. Check remote repository `git remote show origin`
**Solution :**
Got error due to lack of permissions for the PAT Token. After this error i regenerated token and modified permissions for the token at repository level. We can do it in the github UI . settings --> Developer settings (at the bottom left) --> Generate new fine grained token --> permissions edit
### Ec2 instance is not reachable via ssh
### Maven Build Failure
The error i encounted due to the `junit.framework` package and associated classes like `TestCase`, `Test`, and `TestSuite` are not available in my project project. This is due to missing or incorrect JUnit dependencies in my Maven configuration (`pom.xml`
`./src/test/java/com/ecomm/AppTest.java` This is the path of the Apptest.java by default
As part of fix , i updated my `pom.xml` and `Apptest.java` files. Then ran this `mvn clean install &&`
\
`mvn test`
## git error
* As part of fix, changed branch `git checkout main` and pulled `git pull`
### Python Error
To fix this created venv using `python3 -m venv ./order-service/.`
`pip install requirements`
To activate virtual env, use `source ./bin/activate`
finally ran `sudo pip install flask` It worked
### Go Error
we got this error due to something wrong in the syntax of main.go file. Sometime other possibilities of this error could be of port running for other service
* To check port `netstat -tuln | grep 8081`—if empty, the app isn’t starting.\`
`sudo lsof -i :8081` `sudo kill -9 $(sudo lsof -t -i:8081)`
once it started working, we will see something like below
### Kubernetes Error
While trying to setup kubernetes cluster with minikube locally got below error
Verified docker installation `docker version` and checked docker status with `sudo systemctl status docker` and then created docker group and added user into that group using `sudo usermod -aG docker $USER && newgrp docker` finally i ran `minikube start --driver=docker` It worked
### kubernetes Error
\--> This issue we will get mostly due to not having kubeconfig file. Once you have updated kubeconfig file. Please check and update minikube
### Jenkins Errors
And also not able to setup webhook due to running jenkins locally. Github doesn't accept http it needs https url to function webhook properly. To fix that issue i used ngrok.com to test webhook
The errors you’re seeing when running npx eslint --init and npm run lint stem from two main issues:
1. **UNC Path Issue**: You’re running commands in a **Windows Subsystem for Linux (WSL)** environment, and the path \\\wsl.localhost\Ubuntu-24.04\\... is a UNC (network) path, which Windows’ cmd.exe doesn’t support. This causes ESLint to default to C:\Windows, leading to permission and context errors.
2. **Missing package.json or Permissions**: The npx eslint --init error indicates no package.json in the Product Service directory, and the npm run lint error (EPERM: operation not permitted, scandir 'C:\Windows\appcompat\appraiser') confirms ESLint is trying to operate in the wrong directory (C:\Windows) due to the UNC issue, hitting permission restrictions.
These issues are common when mixing WSL and Windows environments, especially for Node.js workflows
* **Production Context**: In prod, companies avoid such WSL issues by standardizing environments (e.g., Linux containers on Kubernetes), but your dev setup needs this fix to mimic real-world CI
*
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://charan-techjourney.gitbook.io/charan-techjournal/50-days-of-devops-ecommerce-microservices/project-daily-tasks/troubleshooting-and-debugging.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.