Jobs stay queued

Deadline
1

Hi there,

I have an issue with deadline, I’m trying to submit a mantra job but it stays queued, it doesn’t even give any errors, so I don’t know what the problem is.
Hope someone can help me,

thank you in advance

2

Since it’s not generating errors, it could be one or more of the following:

  1. The job belongs to a pool that no slaves belong to.
  2. The job belongs to a group that no slaves belong to.
  3. The job has an empty whitelist.
  4. The job has a “full” blacklist (every slave is on it).
  5. The job uses a Limit Group that has a whitelist/blacklist that prevents slaves from getting it.
  6. The job, based on pool and priority, has a lower priority in the queue that prevents it from getting picked up while there are other jobs in the queue.

Do any of these sound like a possibility? A quick way to determine if any slaves can render the job (based on pool, group, machine list, etc) is to use the Slave Availability Filter:
thinkboxsoftware.com/deadlin … Slave_List

Cheers,

  • Ryan
3

Thanks for replying Russel. I’ve checked everything you said but still doesn’t work. Any ideas?

4

Do any other job types work (ie: is it just Mantra jobs)?

5

I’ve just tried with afterFX, but it does the same

6

Hmm, it sounds like it might be a permission issue. Can you double check the repository to make sure that permissions are completely open for reading and writing? Also, can you let us know which OS you have the Repository installed on, and which OS you have the Deadline Clients installed on?

Thanks!

  • Ryan
7

The permissions seem ok. Anyway the repository is installed on a samba share drive and the client on a windows machine

8

Hello,

I am just popping in here, wondering if you are able to read from and write to the jobs folder in the Repository from the slave machine? Doing that will allow us to rule that out completely, as permissions, especially over a network, are often the issue with what you are describing.

Cheers,

Dwight

9

Hi there, I’ve checked the permission from the slave machine. I think everyone has full control.
Here is what I get in the cmd prompt

cmd_prompt.jpg

10

Hello,

Do you happen to have the samba config file handy? I would love to see if it has the proper settings for access.

11

How do I find this file? Sorry for the missing knowledge

12

Hello,

The location of the samba config file depends on the OS of the machine running it. If it is a linux/unix system running samba, you would look in /etc/smb/ or /etc/samba/.

Cheers,

Dwight

13

This is what I’ve found in smb.conf, apparently only comments

This is the main Samba configuration file. You should read the

smb.conf(5) manual page in order to understand the options listed

here. Samba has a huge number of configurable options (perhaps too

many!) most of which are not shown in this example

For a step to step guide on installing, configuring and using samba,

read the Samba-HOWTO-Collection. This may be obtained from:

samba.org/samba/docs/Samba-H … ection.pdf

Many working examples of smb.conf files can be found in the

Samba-Guide which is generated daily and can be downloaded from:

samba.org/samba/docs/Samba-Guide.pdf

Any line which starts with a ; (semi-colon) or a # (hash)

is a comment and is ignored. In this example we will use a

for commentry and a ; for parts of the config file that you

may wish to enable

NOTE: Whenever you modify this file you should run the command “testparm”

to check that you have not made any basic syntactic errors.

#---------------

SELINUX NOTES:

If you want to use the useradd/groupadd family of binaries please run:

setsebool -P samba_domain_controller on

If you want to share home directories via samba please run:

setsebool -P samba_enable_home_dirs on

If you create a new directory you want to share you should mark it as

“samba_share_t” so that selinux will let you write into it.

Make sure not to do that on system directories as they may already have

been marked with othe SELinux labels.

Use ls -ldZ /path to see which context a directory has

Set labels only on directories you created!

To set a label use the following: chcon -t samba_share_t /path

If you need to share a system created directory you can use one of the

following (read-only/read-write):

setsebool -P samba_export_all_ro on

or

setsebool -P samba_export_all_rw on

If you want to run scripts (preexec/root prexec/print command/…) please

put them into the /var/lib/samba/scripts directory so that smbd will be

allowed to run them.

Make sure you COPY them and not MOVE them so that the right SELinux context

is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts

#--------------

14

Just checked it again and it shows more option at the bottom

This is the main Samba configuration file. You should read the

smb.conf(5) manual page in order to understand the options listed

here. Samba has a huge number of configurable options (perhaps too

many!) most of which are not shown in this example

For a step to step guide on installing, configuring and using samba,

read the Samba-HOWTO-Collection. This may be obtained from:

samba.org/samba/docs/Samba-H … ection.pdf

Many working examples of smb.conf files can be found in the

Samba-Guide which is generated daily and can be downloaded from:

samba.org/samba/docs/Samba-Guide.pdf

Any line which starts with a ; (semi-colon) or a # (hash)

is a comment and is ignored. In this example we will use a

for commentry and a ; for parts of the config file that you

may wish to enable

NOTE: Whenever you modify this file you should run the command “testparm”

to check that you have not made any basic syntactic errors.

#---------------

SELINUX NOTES:

If you want to use the useradd/groupadd family of binaries please run:

setsebool -P samba_domain_controller on

If you want to share home directories via samba please run:

setsebool -P samba_enable_home_dirs on

If you create a new directory you want to share you should mark it as

“samba_share_t” so that selinux will let you write into it.

Make sure not to do that on system directories as they may already have

been marked with othe SELinux labels.

Use ls -ldZ /path to see which context a directory has

Set labels only on directories you created!

To set a label use the following: chcon -t samba_share_t /path

If you need to share a system created directory you can use one of the

following (read-only/read-write):

setsebool -P samba_export_all_ro on

or

setsebool -P samba_export_all_rw on

If you want to run scripts (preexec/root prexec/print command/…) please

put them into the /var/lib/samba/scripts directory so that smbd will be

allowed to run them.

Make sure you COPY them and not MOVE them so that the right SELinux context

is applied, to check all is ok use restorecon -R -v /var/lib/samba/scripts

#--------------

#======================= Global Settings =====================================

[global]
log file = /var/log/samba/log.%m
guest account = samba
load printers = no
read raw = no
write raw = no
null passwords = yes
encrypt passwords = yes
passdb backend = tdbsam
wins support = true
cups options = raw
oplocks = no
writeable = yes
server string = Samba Server Version %v
locking = no
path = /ifs
workgroup = MYGROUP
debug level = 0
os level = 20
valid users = samba
max log size = 50000
unix extensions = off
case sensitive = yes

15

Hello,

Ok, so I have looked over what you sent, and I am not sure everything we need is there. What I would like you to do for me is to rename a file, any file, in the Jobs folder for this task in Repository, from the slave. The location you are looking for will be “I:\DeadlineRepository\jobs”, then open the folder for the job there, and rename one of the files. That will conclusively tell us that there is no permissions issues. Thank you.

Cheers,

Dwight

16

I’m able to rename files in the job folder but a very weird thing happened, I’ve uninstall the repository but I couldn’t get rid of the job folder and than tried to reinstall it but it says me “You do not have the permission to write on I:/”

17

Hmm… Well, it does look like there were some permissions issues there. If you like, give us a call today and I can help you through it.

Our support number here is 1-866-419-0283 ext 2. We tend to go out for lunch on Fridays, so if we miss you, leave a name and number and I’ll give you a call back.