Troubleshooting

Common issues and their solutions.

Agent Issues

Agent won't start

Symptoms: systemctl status ssi-agent shows failed state

Solutions:

1. Check the logs:

   bash

   Copy

   1journalctl -u ssi-agent -n 50

2. Verify configuration file:

   bash

   Copy

   1python3 -m json.tool /etc/ssi-agent/config.json

3. Check if agent is registered:

   bash

   Copy

   1ssi whoami

Agent not connecting to backend

Symptoms: Agent running but no data in mobile app

Solutions:

1. Verify backend URL:

   bash

   Copy

   1cat /etc/ssi-agent/config.json | grep backend_url

2. Test connectivity:

   bash

   Copy

   1curl -I https://api.service-status-indicator.com/api/health/

3. Check for firewall issues:

   bash

   Copy

   1sudo iptables -L -n

4. Restart the agent:

   bash

   Copy

   1sudo systemctl restart ssi-agent

Registration fails

Symptoms: ssi register times out or fails

Solutions:

1. Check network connectivity to backend
2. Verify backend URL is correct
3. Check backend logs for errors
4. Try again after a few minutes

Service Script Issues

Service not running on schedule

Symptoms: Timer exists but script never executes

Solutions:

1. Check timer status:

   bash

   Copy

   1systemctl list-timers | grep ssi_

2. Verify timer is enabled:

   bash

   Copy

   1systemctl is-enabled ssi_my_service.timer

3. Check service status:

   bash

   Copy

   1systemctl status ssi_my_service.service

4. Reload systemd:

   bash

   Copy

   1sudo systemctl daemon-reload

Script runs but status not reported

Symptoms: Log file has output but no update in app

Solutions:

1. Check output format matches expected:

   YYYY-MM-DD HH:MM:SS, STATUS, Message

2. Verify log file exists:

   bash

   Copy

   1ls -la /var/log/ssi-agent/

3. Check agent is watching the file:

   bash

   Copy

   1journalctl -u ssi-agent | grep my_service

"Service script must be a .bash file"

Solution: Rename your script with .bash extension:

1mv my-script.sh my-script.bash

"Service name must be between 3 and 60 characters"

Solution: Update the # name: field in your script.

"Invalid schedule format"

Solution: Verify your schedule using:

1systemd-analyze calendar "your-schedule-here"

Permission Issues

"Permission denied" when adding service

Solutions:

1. Check you're in the admin group:

   bash

   Copy

   1groups

2. Use sudo if needed:

   bash

   Copy

   1sudo ssi add my-script.bash

Can't write to log directory

Solutions:

1. Check permissions:

   bash

   Copy

   1ls -la /var/log/ssi-agent/

2. Fix ownership:

   bash

   Copy

   1sudo chown -R ssi-agent:ssi-agent /var/log/ssi-agent/

Log Inspection

View agent daemon logs

1journalctl -u ssi-agent -f

View service script logs

1tail -f /var/log/ssi-agent/<service_id>.log

View systemd timer logs

1journalctl -u ssi_<service_id>.timer
2journalctl -u ssi_<service_id>.service

Reset and Recovery

Completely reset agent

1# Unregister
2ssi unregister
3
4# Re-register
5ssi register
6
7# Restart
8sudo systemctl restart ssi-agent

Force remove broken service

1ssi remove broken_service --force

Reinstall agent

1cd ssi-agent
2sudo ./install.sh --remove
3sudo ./install.sh