Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IBM Director Resource Monitors

Status
Not open for further replies.

jsetaro

MIS
Aug 9, 2001
48
US
I recently upgraded my Director server from 4.11 to 4.20. Now, when I right click on an agent (Any Director version), and choose "Resource Monitors" or "All Available Thresholds", the RM console window never opens. I've uninstalled and reinstalled Director. When there is no data (Clean install), the "Resource Monitors" console opens. After I restore my data, it does not open. I cannot re-do everything I've done in Director all over again, that's why I need to restore my data. Any help would be appreciated.
 
Sounds like you have corruption in your source that you are restoring from. what specifically from your old install are you trying to keep? You may be able to export (or copy) the old settings from a particular module, rather that a blanket TWGsave/TWGrestore. As you probably already found out, TWGrestore is not a selective process.
 
I am trying to keep all my users, IP ranges, Console user access, schedules, Event Action Plans, etc. I have almost everything exported except my user list. That is a pain to re-do because all the boxes as you know have to be up defore Director can detect them. I opened a PMR with IBM a few months ago, and they are still working on it.
 
How granular are your Console users rights? My take is that you either make them users, super users, or not. If you can't trust them to use the console responsibly, don't grant them access. If you have multiple users doing the same thing, create a single user account, and have all of them use the same account. You must have more time on your hands than I do.
 
First of all, I work in IT (Insufficient Time) I do not have a lot of free time. I have some users that have access to certain groups, and some to certain functions. Instead of creating new user accounts on my domain for users who need access to "Purchasing Dept." and another account for someone who needs access to "File Transfer, I modify each users account to the functions they need. This way, I do not have more user accounts on my domain that I do not need. That's not my biggest concern. My concern is having to do all that I have put into Director these past three years all over again. I have mostly everything exported. The pain is applying all of it back again.
 
Hello 'jstaro'....I'm having the same problem you are having brining up 'Resource Monitor' screens. I upgraded to 4.2 also.

Have you solved the problem yet?

Thanks
 
Can anyone tell me how to get twgrestore to work. I do a twgsave no problem it creates the save directory. But for the life of me I cannot get twgrestore to work. Here is my syntax
twgrestore -t C:\program files\ibm\director.save.5

Nothing happens except I get the message that shows me the arguments for running the command.

Can anyone help? I have tried running it from different locations I have tried running it without the -t. I have tried running it with the director server service both on and off.??

Thanks in advance!!

 
I did not solve the problem yet with launching "Resource Monitors". IBM is still working on it. They did tell me it's a time out issue. Once I find out, I will post it. As far as doing the twgrestore, put the path in quotes like this; twgrestore -t "C:\Program Files\IBM\Director.Save.5" and that should work. If that does not work, move the saved folder to the root of C: and try it from there.
 
After I upgraded, like you from 4.1.1 to 4.2, I had some save resource monitors.

If you have any saved Resource Monitors.....try dragging one of them on top of a node. For me it brought up the Resource Monitor screen.

I still can't see any 'Available Thresholds' screen...
 
What I did was delete the files Eventpublication.dcf and Eventsubscription.dcf in the Data folder. First, stop the Director service. Then delete or move these files. Start the service, and Director re-creates these files. That got my Resource Monitors working again.
 
Not at all. If you use Event Acion Plans, all the data that you check off to alert you is stored in these files. Once they are deleted, they get re-built. The server will run slow for a while until the files are completely re-built.
 
I just noticed that RM is not available again on both my Director servers. Event though I deleted the two .dcf files, once the servers are re-booted, RM's fail again. When I launch RM on an agent, you will see "Starting Task" in the lower left corner. Most of the times it will take exactly one minute and go back to "Ready" and the RM console does not launch. The other times it will go to "Ready" immediately. I installed Director 4.2 on a test server off of my network and restored my data to it. RM failed once. After I deleted the two .dcf files, the RM console launches. I have re-booted many times and RM's still work. I even copied back the two .dcf files that were 28 MB and 9 MB and they still work. There seems to be a time out issue with both my Director servers. If I put them in debug mode by removing the "#" on each line in twgras.properties, RM's will work even without deleting the two .dcf files first. I don't think the .dcf files are the culprit. I think it's because Director has temporarily slowed down (Also like when it is in debug mode) to rebuild the .dcf files and therefore it can launch the RM console. If anyone has an idea, it would be appreciated.
 
I just got a fix from IBM and it seems to work. The reason why "Resource Monitors" does not launch is because there is a timeout issue. By deleting the two .dcf files, it puts Director into a "Slow Down" state because it has to rebuild these two files. While in that state, RM's will launch. IBM told me to do the following:

1. Stop Director Services.
2. Modify the file twgserver.prop located in the data folder of Director.
3. Add this line:
twg.task.svcnode.timeout=600000
This increases the timeout from 60 seconds to 10 minutes.

 
Thanks for the tip!!! I updated the twgserver.prop file as you stated.....and now I see my Resource Monitors!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top