Windows命令行：FTP上传前重命名本地文件脚本故障排查

Hey there! Without seeing your actual script code, it’s hard to nail down the exact bug, but let’s break down the most common issues that usually derail this kind of daily rename + FTP upload workflow. Here’s what to check first:

1. Invalid Date Format in Filenames #

Filenames can’t have characters like /, :, or unescaped spaces—if your date string includes these, the rename will fail instantly.

• Linux/macOS: Avoid date +%Y/%m/%d (this creates subdirectories instead of a valid filename). Use something like date +%Y-%m-%d (hyphens) or %Y%m%d (clean numeric format) instead.
• Windows: The default %DATE% variable often has slashes. Fix it with something like set "today=%DATE:/=-%" to swap slashes for hyphens.

2. FTP Connection/Authentication Failures #

This is one of the most frequent culprits:

• Double-check your FTP username, password, and server address—typos here are way too easy to make.
• If you’re behind a firewall, ensure your script uses passive FTP mode. Most default FTP clients use active mode, which gets blocked by firewalls. Tools like lftp (Linux) or WinSCP (Windows) let you enable passive mode explicitly.
• Confirm you’re using the right port (21 for standard FTP, 990 for FTPS if you’re using secure transfer).

3. Permission Issues (Linux/macOS) #

If the script runs manually but not when scheduled:

• Check that the user running the script has read access to Feed.txt and write access to the directory where you’re renaming it. Run ls -l Feed.txt to verify ownership/permissions, and adjust with chmod if needed.
• Always use absolute paths for files/commands in scheduled jobs (e.g., /home/you/Feed.txt instead of Feed.txt)—cron doesn’t use your regular user’s PATH.

4. Scheduler Quirks (Cron/Windows Task Scheduler) #

• Linux/macOS Cron: Cron runs with a minimal PATH, so never rely on relative commands. Use full paths like /usr/bin/mv instead of mv, and specify the full path to Feed.txt.
• Windows Task Scheduler: Make sure the task is set to run as the user who has access to Feed.txt, and set the "Start in" directory to the folder where the file lives. Otherwise, the script might look for the file in the wrong place.

5. Script Syntax & Edge Cases #

• Quotes for Spaces: If your renamed filename has spaces (e.g., Feed 2024-05-20.txt), wrap the filename in quotes to avoid errors. For example: mv "Feed.txt" "Feed_$(date +%Y-%m-%d).txt".
• Check for Missing File: Add a check to make sure Feed.txt exists before trying to rename it. On Linux: if [ -f Feed.txt ]; then ... fi; on Windows: if exist Feed.txt ( ... ).

If you can share your script (just redact any sensitive info like FTP passwords!), I can help you spot the exact issue right away.

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