Problem Submitting a new job

Deadline
1

Hi,

I am actually having the exact same issue as in this old post: viewtopic.php?f=11&t=4009&p=16054&hilit=error+file+exists#p16054.
I get the same error: The file exists. (System.IO.IOException) and have tried restarting everything.
I’ve now tried running the files you attached in the previous thread and recieved this output:

Any ideas on what might be causing the error would be much appreciated.

Thanks,
Tristan

2

Hi Tristan,

I think this problem was addressed in Deadline 4.1. Can you upgrade to the latest Deadline Release (4.1 SP1) and let us know if the problem persists?

Cheers,

  • Ryan
3

Hi Ryan,

Thanks for your response. I’ve upgraded deadline on the main machine, but not on the slave machines, and the problem persists. Would it matter that I’ve not upgraded on the slave machines? Any more ideas on how to fix it?

Thanks in advance,
Tristan

4

Hi Tristan,

You should always keep your repository, workstations, and render nodes on the same version, but you wouldn’t need to upgrade your slaves to see if upgrading fixed the problem. Now that you’re upgraded though, we can dig a bit deeper.

So when you submitted those files via the command line, you had no problems right? I just want to confirm this because the output you posted indicates the job was submitted successfully. I should also confirm what application you want to render with (maya, nuke, rendition etc), as well as how you’re normally trying to submit the job when you get this error (via the Monitor, or one of the integrated submission scripts). Maybe a screen shot of the exact error you’re seeing would put things in better context as well.

Thanks!

  • Ryan
5

Hi Ryan,

I’ve now upgraded on the repository as well, and am seeing the same thing.

I’m running Rendition, and submitting the command via a php script. When running the script, it acts as if it’s submitting the job fine, but it just doesn’t appear in the monitor. No error is shown by the script, so I’ve copied the command output from the script and run it directly in command prompt so that I can see the error, which I’ve included a screenshot of.
IOException.jpg

Even when submitting the command directly through command prompt like this, the job does not appear in the Monitor.
Any more ideas?

Thanks,
Tristan

6

Hi Tristan,

I was able to run this command without any problems. I had asked this question previously:

I’m referring to the files you downloaded from the other forum thread. I’m just curious if the problem you’re seeing only occurs when you use the “SubmitCommandLineJob” command line option, or if it’s a larger submission problem.

Cheers,

  • Ryan
7

Ah, sorry, yes the output in the command line from the test files you sent seems positive, but nothing appeared in the Monitor from that. Also I have tried adding a rendition task manually in the Monitor and again nothing happens.

Thanks,
Tristan

8

Thanks. So it definitely seems like a more widespread submission issue. Open up the following folders in separate Explorer windows:

\your\repository\temp
\your\repository\jobs

Now submit a new job, and when it finishes, let me know if you see a new folder appear in either of the folders above. When a job is submitted, it is first created in the temp folder, and then moved to the jobs folder. I’m curious if it makes it to the temp folder, but not the jobs folder, or if it even makes it to the temp folder at all.

Thanks,

  • Ryan
9

Hi,

It seems to not even make it into the temp folder. Nothing appeared in either location.

Cheers,
Tristan

10

Weird. What output do you get when you run this command? Does it match the repository path you’re checking the temp and jobs folder for?

deadlinecommand.exe -getrepositoryroot

Also, what OS do you have the repository installed on?

11

Yeah the output matches the folders I had open. It’s installed on windows server 2003.

12

Thanks for checking that. Is this a brand new installation? Have you ever had success submitting Rendition jobs, or any jobs for that matter?

13

Hey, yeah it’s been working for quite a while, and it’s just stopped working at some point between yesterday and last Friday. really strange.

14

The repository machine isn’t out of disk space, is it? That’s the only reason I can think of that it wouldn’t be accepting new jobs. I was going to ask you to check the permissions for the repository, but if it’s been working in the past, then it’s unlikely that permissions have anything to do with the problem.

15

There’s plenty of space on the repository, and we’ve checked all the permissions on the folders and all is supposedly good.
And more ideas? Sorry to keep bugging you on this.

Thanks,
Tristan

16

Don’t worry about “bugging” us. We want to figure this one out as much as you do! :slight_smile:

Perhaps it’s worth installing a new repository on the same machine (keep the existing one and install to a new location) and switching the machine you’re submitting from over to the new one. Then submit a job and see if it shows up in the new repository. If that works, then we can provide you details with how to migrate your existing jobs, slaves, etc over to the new repository.

Cheers,

  • Ryan
17

Hi Ryan,

The problem is now sorted, and it was down to some pesky temporary files which hadn’t been deleted.

After, much uninstalling and installing of the manager and repositories all over the place to no effect, we found a temporary folder holding thousands of tmp files named from tmp1 to tmpFFFF (Clearly the hex number has reached it’s limit). After deleting all these, everything was fine! I’ve added a check for old temp files in that directory in a php cleanup script which is run on a cron to make sure that folder doesn’t become full again. The temp folder is located here: C:\Documents and Settings[username]\Local Settings\Temp.

Is this a problem that has been addressed in a release of Deadline?

Thanks for all your help. Much appreciated.
Tristan

18

Hi Tristan,

I’m glad to hear you were able to figure this one out, and we really appreciate you passing on that information to us. It’s looks like Deadline isn’t cleaning up the temporary files that it creates, so we’ll go through the code and make sure it does for the next release.

Cheers,

  • Ryan