Please tell me it’s reproducible! Don’t do anything, we need to debug this one.
I’m at work atm, so don’t have time to write out the required commands. should be something like: mono --debug --trace=T:System.IO.File /var..../nzbDrone.exe
Been thinking about this one. It most likely has something to do with permission issues on that folder.
Edit the ~/.config/NzbDrone/config.xml file and set loglevel to Trace.
If you run drone again the log will now contain more details about which folder it’s trying to set the date for. Which you should check (for the user that runs drone, of course).
If that doesn’t help:
Running mono --debug --trace=T:System.IO.File /var/NzbDrone/NzbDrone.exe (under the correct user account) should output details about those method calls. (and a bunch of other stuff)
What I’m concerned about is that it’s trying to set the folder date to an invalid value. I want to know what value that is. Not sure if the trace is gonna output it, but it’s worth a shot.
Which folder? I guess it’s NZBGet download folder. This shouldn’t happen as NG and ND run under the same useraccount and the filemask gives any newly created file full permissions for the owner, but I’ve repaired an archive manually there as the root user, so some of the files there would have root as their owner.
I’ve ran ND again last night (just a bit before your last reply, damn…) with the debug switches, with the output redirected to a file. This time ND did not crash. Hmm. I also emptied NG destination folder from all of the leftover files - I remember doing this after starting ND, but I could be mistaken. So if it was a file permissios problem and I’ve erased those files prior to starting ND, this could explain why it is running properly now.
Right, it happened again. It was reproducible, so I have a debug log (over 300KB of it, too large for pastebin). I ran ‘aptitude update’ and got a new version of mono - 3.2.8 - and on a subsequent run, ND did not carsh. So either it does not happen with the new mono version or the two previous crashes had already handled the two new downloaded episodes - I’ll know which is true on Monday, when a new episode is scheduled to be downloaded. IN the meantime, the debg log can be found here: