T.R | Title | User | Personal Name | Date | Lines |
---|
885.1 | FILLM? | SLINK::HOOD | I'd rather be surfing | Wed Apr 06 1994 11:53 | 13 |
| Double-check the FILLM (file limit) parameter on the process in AUTHORIZE.
Make it at least 100. If that still doesn't fix it, increase it to about 120.
The FILLM is the number of open files for the process and for all its
subprocesses. If your customer has any subprocesses from the process that's
running HUBwatch, they'll hit this limit.
I'd guarantee there's nothing special about the particular file X is
complaining about. It's just unable to open *any* more files.
Tom Hood
HUBwatch
|
885.2 | Had to reinstall VMS | KERNEL::WARDJO | | Fri Apr 08 1994 05:43 | 15 |
| Tom,
Thanks for the reply.
I got the customer to increase the FILLM to 150 - this made no
difference.
The customer reinstalled VMS and its now working!
The customer can still boot off the problem disk, so if you can suggest
anything else to check & think it is worth trying to get to the bottom
of this, it can be done. However, the customer is happy with his working
system.
Jon
|
885.3 | Problem returns to haunt me! | KERNEL::WARDJO | | Mon May 23 1994 11:38 | 31 |
| Hello,
Well, I now have another customer with the same problem after he
rebooted. The system is a VAX3800 with 32mb of memory and running VMS 5.4-2
Hubwatch is V2.0.1.
$ watch/agent agent1
HUBwatch for OpenVMS VAX, Revision V2.0.1
(I) HUBWATCH$LIBRARY = SYS$LOGIN
(W) Using community public
X Toolkit Warning: I18NOpenFile: Couldn't open file
decw$system_defaults:hub_gui
_brut_sum.uid - MrmFAILURE
Failed to fetch UID files for hub type 3
Have checked FILLM & its set to 255 - other system parameters also
checked with those in installation guide.
Customer gets the problem regardless of the agent he useses (agent 90
V1.1 or Agent 900).
Can anyone suggest anything else to check on the system.
Any help appreciated,
Regards,
Jon
|
885.4 | CHANNELCNT too low! | KERNEL::WARDJO | | Fri May 27 1994 13:52 | 11 |
| If anyone is intersted:-
Having been assured that the customer had checked the required sysgen
parameters specified in the installation guide it turned out to be that the
CHANNELCNT had been set down to 212 instead of the 512 required.
As usual it was claimed that nothing had been changed.
Jon
|