Gui looks like this on my computer.
Slave names are gone and sometimes the tasks are just black.
What’s version of Deadline 6.1 are you running? Also, can you open the Console panel from the View menu and see if there are any error messages?
Thanks!
Ryan
It is RC 2. The console panel gives me this error. 2014-01-24 09:12:45: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
It is RC 2. The console panel gives me this error. 2014-01-24 09:12:45: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
That’s strange. Is it JUST your computer that this problem occurs on, or do you see it on other machines? If it works fine on other machines, that would indicate that the data in the database is fine. If it happens on multiple machines, then the data itself could be corrupt.
Also, have you always had this problem with 6.1? Or is it something that just started recently?
Finally, one thing you could try is to select View -> Reset Layout. Maybe something is messed up with the current layout, and resetting it would fix that if that’s the case.
Thanks,
Ryan
Right now its just my machine. I’ve always had this problem on my computer so I rolled back to 6.0 for that reason, but now when I installed 6.1 the problem is back.
I have also tried to reset the layout without success.
Is there any kind of log or anything I can send you?
The console log is really the only thing that can help here, so at this point all we know is that your machine is having an issue with the format of the data that is coming in.
I wonder if it’s a localization thing. What’s the current language and format settings you’re using on your machine? It looks like you’re on Windows 7, so you can find this information by typing in Region and Language in the Start search box. You’ll see this information under the Formats tab:
Look like this. I am located in Sweden.
Just a note, I am also using a roaming profile under windows.
Thanks! I tried switching a machine here to Swedish, but I wasn’t able to reproduce the problem, so it doesn’t appear to be a region/language issue.
When you mentioned profiles, it reminded me of something you could try:
- Close the Monitor if it’s currently running.
- In Windows Explorer, go to this path: %APPDATA%\Thinkbox
- Delete this file: Deadline Monitor 6.ini
- Restart the Monitor.
This file stores the Monitor layout settings, so blowing it away will do a “true” reset. Hopefully that does the trick.
Cheers,
Ryan
I deleted the Deadline Monitor 6.ini file but the problem i still there.
This is what the Console gives me now.
2014-01-28 09:05:43: Deadline Monitor 6.1 [v6.1.0.54482 R]
2014-01-28 09:05:43: The current PYTHONPATH environment variable will be modified to avoid potential Python conflicts
2014-01-28 09:05:43: Time to initialize: 187.000 ms
2014-01-28 09:05:43: Time to connect to Repository: 530.000 ms
2014-01-28 09:05:43: Time to check user account: 0.000 s
2014-01-28 09:05:43: Time to purge old logs: 0.000 s
2014-01-28 09:05:43: Time to synchronize plugin icons: 328.000 ms
2014-01-28 09:05:43: Time to initialize main window: 124.000 ms
2014-01-28 09:05:43: Main Window shown
2014-01-28 09:05:43: Time to show main window: 31.000 ms
2014-01-28 09:05:43: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
2014-01-28 09:05:43: Error occurred while updating task cache: Input string was not in a correct format. (System.FormatException)
2014-01-28 09:05:43: Error occurred while updating task cache: Input string was not in a correct format. (System.FormatException)
2014-01-28 09:05:43: Error occurred while updating slave ping cache: Input string was not in a correct format. (System.FormatException)
2014-01-28 09:05:43: WARNING: disabling profiling because of error begin profiling section twice without ending the first one (Slave Importer).
2014-01-28 09:05:43: WARNING: disabling profiling because of error begin profiling section twice without ending the first one (Task Importer).
2014-01-28 09:05:54: Traceback (most recent call last):
2014-01-28 09:05:54: File “DeadlineUI\UI\Models\SlaveListProxyModel.py”, line 77, in onRowsInserted
2014-01-28 09:05:54: KeyError: u’’
2014-01-28 09:06:00: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
2014-01-28 09:06:53: Traceback (most recent call last):
2014-01-28 09:06:53: File “DeadlineUI\UI\Models\SlaveListProxyModel.py”, line 77, in onRowsInserted
2014-01-28 09:06:53: KeyError: u’’
2014-01-28 09:06:58: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
Ok I think I found the problem. When I set the region and language to English Canada it works again!
When I first installed Deadline 6.1 it worked for a couple of days before the bug appeared.
That’s interesting. I’m surprised I didn’t see any issues when I switched to the Swedish format. Would you be willing to send us a dump of the SlaveInfo collection in your database? We could import it here and see if we can reproduce that way.
To do this, open up a command prompt on the machine that your database is running on, and switch directories to the mongo bin folder. Here are typical locations of this folder for each OS:
- windows: C:\DeadlineDatabase6\mongo\application\bin
- linux: /opt/Thinkbox/DeadlineDatabase6/mongo/application/bin
- osx: /Applications/Thinkbox/DeadlineDatabase7/mongo/application/bin
Once in the bin folder, run this command:
mongoexport -d deadline6db -c SlaveInfo -o "path\to\output\file.txt"Note that if your database name is something other than “deadline6db”, you’ll have to change it in the command above. If you’re not sure the name of your database, you can check the dbConnect.xml file in \your\repository\settings to see what the name is. Finally, change the path to the output file in the command to point to a valid path.
After running this command, post the text file and we’ll take a look.
Thanks!
Ryan
I think I figured this out, after a bit of poking around knowing the problem lie in Swedish settings vs English ones.
The problem likely stems from one of our parsing functions, it’s assuming that a period ( . )is used as the decimal symbol, which is obviously incorrect for many languages! If you switch back to Swedish, and change the Decimal Symbol to ‘.’ (under ‘Additional Settings’ in the Windows Region dialog), does the Monitor behave properly still?
Since I switched back and forth the problem seems to be gone.
Interesting…
Glad to hear it’s working now. We’ll still run some tests against the exported slaves you sent us to see if we can figure out why it was happening in the first place.
Cheers,
Ryan
Now when I logged on to my computer via windows remote desktop, the problem is back again. Could it be remote desktop that breaks it?
Weird. I wouldn’t expect Remote Desktop to break it, but maybe it provides a clue as to what the problem is. Maybe it’s related to simply logging out and logging in.
The 6.2 beta should be starting up very soon, and the fix Jon made which targets what we think is causing this problem will be included in the initial beta. So you’ll be able to test it and let us know if the problem still persists.
Cheers,
Ryan
Couple of things I remembered which might help or hinder here:
-
Windows Remote Desktop into a remote machine in another region, it will change that remote machine’s region/language/keyboard layout to your local region temporarily. Can be very annoying in a Microsoft trying to be helpful way. Exit the session and it should leave the remote machine still operating as per before you visited it.
-
Various Registry hacks can be followed on the web to disable/hack the action of the above variables.
-
There might be a difference between ‘normal’ RDC and using the /console flag to enter session:0 when crossing regions?