Thanks @fabian for the quick reply. Yes, actually - Windows did touch that file. I wrote out the commands in notepad++ on Windows and copied the file over via sftp.
I trashed the Windows file, created a new one with nano, and it worked! I had to add "bash" before the path to the script in crontab or it wouldn't work, but so far, I'm a few tests deep and firing off backups like a mad-man!
I had no idea there was some sort of Windows germ following that file around. I just assumed text was text, but I guess it could smell the Windows stink on it and said no thanks. I had tried playing with permissions, making it executable, etc. on the pve host, but none of that worked. Thanks for jumping in and saving me more hours of troubleshooting.
I trashed the Windows file, created a new one with nano, and it worked! I had to add "bash" before the path to the script in crontab or it wouldn't work, but so far, I'm a few tests deep and firing off backups like a mad-man!
Code:
21 * * * * bash /root/pbs.shI had no idea there was some sort of Windows germ following that file around. I just assumed text was text, but I guess it could smell the Windows stink on it and said no thanks. I had tried playing with permissions, making it executable, etc. on the pve host, but none of that worked. Thanks for jumping in and saving me more hours of troubleshooting.
