树莓派搭载OpenCV的Python脚本无法开机自启动求助

Hey there, let's tackle this head-on—your script runs fine manually but goes silent on boot? I’ve debugged tons of Raspberry Pi + Python/OpenCV startup issues, so let’s break down the most likely fixes:

That sys.path.append('/home/pi/.lo...') line is a clue: your manual terminal session has access to extra Python packages, but the boot-time environment doesn’t.

• First, confirm exactly which Python you’re using manually: run which python3 in your terminal (it’ll look like /usr/bin/python3 or /home/pi/.local/bin/python3). Use this full absolute path in your boot command instead of just python3—boot environments have a stripped-down PATH, so it might be calling a different Python version.
• Fill in that truncated path in sys.path.append to the full absolute path (e.g., /home/pi/.local/lib/python3.7/site-packages—adjust for your Python version). Vague paths fail when the working directory isn’t what you expect on boot.

Boot scripts often run as root or a restricted user, which can block access to the camera or Dropbox auth files:

• If you’re using @reboot in crontab, make sure the pi user has camera access: run sudo usermod -a -G video pi and reboot.
• Dropbox’s auth token is probably stored in pi’s home directory. Avoid running the script as root—use the pi user explicitly in your boot setup (systemd is great for this, more on that below).

Raspberry Pi boots fast, but the camera and network (critical for Dropbox) might not be ready when your script fires up:

• If using crontab’s @reboot, add a delay: @reboot sleep 30 && /usr/bin/python3 /home/pi/your_script.py >> /home/pi/boot_log.txt 2>&1. The sleep 30 gives hardware and network time to initialize.
• For systemd services, add After=network.target multi-user.target to the service file to ensure dependencies are ready first.

The biggest mistake here is not checking error logs—"no reaction" almost always means an error that’s just not being shown:

• Redirect all output to a log file, no matter which boot method you use. For crontab, that’s the >> /home/pi/boot_log.txt 2>&1 part I mentioned earlier (it captures both regular output and errors).
• If your script uses any GUI-related OpenCV calls (unlikely for just capturing photos, but worth checking), add export DISPLAY=:0 to your boot command—boot environments don’t have a default display set.

rc.local and crontab are prone to environment quirks. Systemd is the modern, stable way to run boot scripts:

1. Create a service file: sudo nano /etc/systemd/system/camera_upload.service
2. Paste this (adjust paths to match your setup):

[Unit]
Description=Camera Upload to Dropbox
After=network.target

[Service]
User=pi
WorkingDirectory=/home/pi
ExecStart=/usr/bin/python3 /home/pi/your_script.py
Restart=on-failure
RestartSec=10
StandardOutput=append:/home/pi/camera_upload.log
StandardError=append:/home/pi/camera_upload.log

[Install]
WantedBy=multi-user.target

3. Enable and test the service:

   sudo systemctl daemon-reload
   sudo systemctl enable camera_upload.service
   sudo systemctl start camera_upload.service
   

4. Check logs anytime with cat /home/pi/camera_upload.log to spot issues.

You mentioned the camera occasionally fails even manually—boot time makes this worse. Add a robust retry loop to your script:

import cv2
import time
import sys
from datetime import datetime

cap = None
# Retry 10 times with 1-second gaps
for attempt in range(10):
    cap = cv2.VideoCapture(0)
    if cap.isOpened():
        break
    time.sleep(1)

if not cap or not cap.isOpened():
    with open("/home/pi/camera_failure.log", "a") as f:
        f.write(f"Failed to initialize camera at {datetime.now()}\n")
    sys.exit(1)

This gives the camera extra chances to wake up on boot.

内容的提问来源于stack exchange，提问作者zeo takall