I finally figured it out. I had to cd into the directory the script runs from, then run the command. So in the command line I put this:
cd /home/hts/zap2xml; perl zap2xml.pl -u username -p password -F 4Ran it and saw the date/time stamp on the file matched the current date/time.
So why wouldn't a manually added cron job added to the system via crontab -e work then?
No dice. Still not running. It says it is, but the files never update. Not sure what it is doing, but if I run the command from the command line it works just fine.
I'll give it a try.
Here it is.
Not working again. Checked the log and it says it ran, but my EPG is blank. Works just fine if I run it manually.
Ok, now it looks like it's working. Very strange. Banged my head against the wall for two weeks trying to get this to work! Never even made a change!
Because I am trying to find something relating to this cron job. Any suggestions what I should be looking for if not cron?
doing grep cron /tmp/test.log gave me this:
cron-like program that doesn't go by time
Manually it works.
Yes, if I am logged in as the user I can run the command from the command line.
That's the problem, scheduled doesn't work. I get permission denied creating a directory. Hence why I was trying command line crontab. With Zap2xml, it has to run as user hts. I've tried running it as hts and as root, but neither one works. My EPG doesn't get updated. I've checked /var/log/messages and there is absolutely nothing in there for zap2xml so I have no way of tracking down where it's failing. It's as if I never even created the cron job.
Really!? No one knows why OMV won't run a cron job??
So I have a media setup using tvheadend, plex etc. I also use zap2xml for my EPG. The problem I am having is I cannot get my cron job to run. I set it from my hts user and I can see it using crontab -l. But it doesn't run. I even tried to use scheduled tasks, but that doesn't work either. I get a permission denied creating directory. Not sure what directory it is trying to create. Is there something I am missing in creating this cron job? I have to run it periodically to get my EPG data.
I did a df -h and saw where /dev/sda1 was mounted, and it should not have been. I unmounted it and recreated my rsync and all is good in the world. Still puzzled as to why rsync was trying to write to /dev/sda1 when I had /dev/sdh1 specified as the drive to use. Very weird. But it's fixed for now, so I'll keep an eye and see if this happens again. Might be a bug.
Nope. sda1 is /media/f3863d78-6648-4e5e-98f2-5041b810ba35 according to your mount output and your error says it can't make a directory on /media/f3863d78-6648-4e5e-98f2-5041b810ba35
I understand that, however the drive I am trying to write the files to is /dev/sdh1. When I try to rsync that drive, I get the RO error. I don't know why. According to fstab, /dev/sdh1 is rw. This has nothing to do with /dev/sda1.
It is definitely mounted read only. Something might be wrong with it. Try mount -o remount,rw /dev/sda1
Ahh, but the drive with the issue is /dev/sdh1, not /dev/sda1.
And I do realize the drive is read-only. I'm trying to figure out how it got to be read-only, and how to stop it from happening again.
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=4113366,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmod e=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3292416k,mode=755)
/dev/disk/by-uuid/f06d42b2-7418-477d-947e-1e901cab19bb on / type ext4 (rw,relati me,errors=remount-ro,user_xattr,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
/dev/sda1 on /media/f3863d78-6648-4e5e-98f2-5041b810ba35 type ext4 (ro,noexec,re latime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjq uota=aquota.group,_netdev)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=7227280k)
/dev/md0 on /media/5ebb5ec3-7ce4-4373-b133-a6c1f6061779 type ext4 (rw,noexec,rel atime,user_xattr,barrier=1,stripe=256,data=ordered,jqfmt=vfsv0,usrjquota=aquota. user,grpjquota=aquota.group,_netdev)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sdg1 on /media/6b6c361e-501b-4081-af84-98ec59cdae70 type ext4 (rw,noexec,re latime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjq uota=aquota.group,_netdev)
/dev/sdh1 on /media/81df27e5-5a7b-4444-a6ae-aa9f145820dc type ext4 (rw,noexec,re latime,user_xattr,barrier=1,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjq uota=aquota.group,_netdev)I have an rsync job that is supposed to back up data to a USB drive. WHen I try to run it, I get an error
rsync: mkdir "/media/f3863d78-6648-4e5e-98f2-5041b810ba35/Backup2" failed: Read-only file system (30)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]What changed to make it read only? How do I fix this?