Repo Options OK-button

[rrussell]

Can you send me a screen shot of the Mongo service settings in your registry? It should be here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MongoDB

I just want to see if it’s being created properly, since it fails when it tries to start it.

Also, I just remembered that we currently don’t try to uninstall the launcher service if it already exists, which means that if it was messed up, the only way to fix it would be to remove it manually before running the repository installer:
stackoverflow.com/a/197885

We should try to fix this so that we always remove it. I recall that the mongo service likes to throw errors when stopping it, which means a reboot is necessary before it can be removed. Kind of a PITA… maybe we can workaround it somehow.

[m_hinks]

This screen grab shows the service running from a different folder, because I have reverted back to the mongo install from beta 1 to get it to work.

I did have the issue that I could not delete the original service to start the new one.

I did install the slaves locally as you suggested in case that messed it up.

The 3dsmax jobs still do not pick up though. Bit confused why! Uninstalled everything now, except Mongo.

[rrussell]

Okay, I think that explains the service problem. Since you already had a Mongo service, Deadline wouldn’t have updated it with the new paths. Try stopping the service, and then running that command line I linked to previously to delete it. After restarting the computer, the service should be gone. Then delete your c:\mongodb and c:\data folders, as well as the c:\mongo folder if it’s still around. Now, everything should be clean and you can run the repository installer again and test that the service is set up properly.

If all this goes well, submit a new job and see if the slave picks it up. If it doesn’t, I’ll need you to open a command prompt on the machine and run this:

c:\mongo\application\bin\mongo.exe 127.0.0.1

This will connect you to the mongo database. Then type this, where DBNAME is the name of the Deadline database you specified in the Mongo config settings in the repo installer (ie: DeadlineDB):

use DBNAME

Then enter this:

db.Jobs.find()

This will dump the JSON of all jobs. You should just have the one Max job, so it shouldn’t be too messy. Just copy and paste this output here. We can take a look to see if there is anything wrong with the job.

Oh, just to confirm, did you update the machine you’re submitting from to beta 2?

[rrussell]

Just looked into the service stuff. I think the best we can do for now is not let the installer install a new MongoDB service if there is already one on the machine. This is because we can’t reliably stop and uninstall an existing MongoDB service due to a bug that exists in Mongo when running it as a service. I’d rather it do this, then try to reinstall the service and fail with unhelpful error messages.

[rrussell]

Just an FYI that we will be handling the problem with the slave not picking up jobs here:
viewtopic.php?f=86&t=8298

Just want to keep it all in one spot.

Thanks!