Transmission-remote runs from CLI not from cron.d

[rbmattis]

this is what my cron.d looks like:

*/1 * * * * transmission transmission-remote localhost:9091 --auth user:password -a /var/hda/files/drives/drive1/docs/Dropbox/newtorrents/*.torrent

I get an email every minute that says "localhost:9091 responded: "invalid or corrupt torrent file""

if I type "transmission-remote localhost:9091 --auth user:password -a /var/hda/files/drives/drive1/docs/Dropbox/newtorrents/*.torrent" as root

I get: localhost:9091 responded: "success"

I followed the suggestions in the wiki to adjust the preferences... ideas?

I'm at wits end

[bigfoot65]

I take it you did not get this sorted out last night? Hopefully there is someone in the community who can assist.

Did you try working with the cron job via Webmin. It might help and maybe its a permissions issue. Just a shot in the dark, but since the the manual method works that could be an indication.

We hope to update transmission to the latest version in the near future. We could then make the cron job part of the install. Not sure that will make a difference, but can never hurt.

[rbmattis]

Hmm, my guess is that it has some something to do with permissions.

When I add files to my dropbox they have default permissions of:
-rw-r--r--

any idea why that is?

My dropbox is within my "Docs" share which my user has full access to.

I still don't get why it doesn't work though. cron.d is run as root? right? transmission-remote is run as root? right? if those two things are root, then it should see and add the torrent just fine... weird.

[bigfoot65]

That is odd. Permissions of shares should be set to 775. As for the cron.d being run as root, ensure the file permissions indicates such. As long as that file has the same permissions as others in that directory, in theory it should work.

Permissions are always so tricky with Linux. Did you try changing the permissions of the torrents as indicated in the wiki?