使用ncftpput上传树莓派相机图片至Lightspeed服务器，上传中刷新异常求解决方案

Great question—this is a super common race condition where your browser tries to pull the image while ncftpput is still writing it to the server, resulting in broken or partial renders. Let’s walk through the most reliable fixes tailored to your setup:

1. Upload to a Temp File, Then Atomically Rename (Best Solution) #

The root problem is that ncftpput writes directly to your target image file, leaving it in an incomplete state mid-upload. The fix? Upload to a temporary filename first, and only rename it to your browser-accessible filename once the upload is 100% successful.

Filesystem renames are atomic on nearly all server systems (including Lightspeed’s Linux environment), meaning the switch from temp to live file happens instantly—your browser will never see a half-written image.

Here’s how to update your script:

# Capture the photo (keep your existing command here)
raspistill -o /home/pi/camera/latest_shot.jpg

# Upload to a temporary file on your Lightspeed server
ncftpput -u YOUR_USER -p YOUR_PASS YOUR_LIGHTSPEED_HOST /path/to/webroot/ camera_temp.tmp /home/pi/camera/latest_shot.jpg

# Check if the upload succeeded (ncftpput returns 0 when it works)
if [ $? -eq 0 ]; then
    # Option 1: Use ncftp to rename the file if SSH isn't available
    ncftp -u YOUR_USER -p YOUR_PASS YOUR_LIGHTSPEED_HOST << EOF
    rename /path/to/webroot/camera_temp.tmp /path/to/webroot/live_camera.jpg
    quit
EOF
    # Option 2: Use SSH for a cleaner command (if your server allows it)
    # ssh YOUR_USER@YOUR_LIGHTSPEED_HOST "mv /path/to/webroot/camera_temp.tmp /path/to/webroot/live_camera.jpg"
fi

Note: If your Lightspeed server restricts SSH access, the inline ncftp rename command is a perfect alternative.

2. Upload to a Non-Web Directory First #

If renaming feels cumbersome, upload your images to a directory that’s not served by Lightspeed, then move them to the web root once the upload finishes. For example:

• Upload to /var/tmp/camera_uploads/ (a directory not mapped to your website)
• After confirming the upload worked, move the file to /var/www/html/ (your web root)

This achieves the same goal as the temp file method—your browser can’t access the incomplete upload.

3. Client-Side Retry Logic (Fallback) #

If server-side changes aren’t an option, add a simple JavaScript retry to your webpage. This handles the rare case where a refresh hits mid-upload by automatically reloading the image until it loads correctly:

function loadLiveCameraImage() {
    const img = document.getElementById('camera-feed');
    // Keep your existing cache-busting query string
    const freshUrl = `live_camera.jpg?cache=${Date.now()}`;
    
    img.src = freshUrl;
    img.onerror = () => {
        console.log("Partial image detected—reloading...");
        setTimeout(loadLiveCameraImage, 1000); // Retry after 1 second
    };
}

// Start loading when the page loads
window.onload = loadLiveCameraImage;

This ensures users never see a broken image for more than a second.

4. Always Validate Upload Success #

Don’t skip checking ncftpput’s exit code (like we did in the first script). This prevents partial or failed uploads from ever being promoted to the live filename, even if the transfer gets interrupted mid-way.

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