Starting up without network connection leaves HDD engaged

[M-Welsch]

Description

What I observed

• powered up
• forgot to attach network cable
• base docked
• and stayed like that. Probably the program crashed when trying to do some network stuff, gotta check journalctl

What happens if we don't do it (aka Why is it important)?

if network isn't available for some reason, hdd is always docked

• exposed
• consumes excess power

Definition of Ready

no prequisites

Key Tasks

• [ ] check journalctl what the issue is
• [ ] catch that and default to undock and shutdown
• [ ] maybe check network beforehand and don't even dock i.e. when NAS isn't reachable

Acceptance Criteria

• [ ] when I remove the network cable and start up base, it either doesn't dock to begin with or undocks shortly after docking

[M-Welsch]

journalctl -u backupserver

Jan 14 17:47:46 raspberrypi python3[320]: 2024-01-14 17:47:46,045 DEBUG: __main__: obtained IP Address of NAS: 192.168.0.2
Jan 14 17:47:46 raspberrypi python3[320]: 2024-01-14 17:47:46,047 DEBUG: __main__: Backing up with command rsync -aH --stats --delete 192.168.0.2::backup_testdata_source/* /me>
Jan 14 17:47:46 raspberrypi python3[320]: 2024-01-14 17:47:46,069 INFO: __main__: Starting Backup...
Jan 14 17:47:49 raspberrypi python3[320]: 2024-01-14 17:47:49,239 INFO: __main__: Backup finished.
Jan 14 17:47:49 raspberrypi python3[320]: 2024-01-14 17:47:49,240 DEBUG: __main__: Backup output task finished.
Jan 14 17:47:49 raspberrypi python3[320]: 2024-01-14 17:47:49,241 ERROR: __main__: Fehlerausgabe: rsync: [Receiver] failed to connect to 192.168.0.2 (192.168.0.2): No route to>
Jan 14 17:47:49 raspberrypi python3[320]: rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]

[M-Welsch]

just removed the line that tracked #19. It killed the program on purpose on any rsync fault to leave base in the respective state