My guess is that while database structural integrity is restored, there is invalid information in the database such as information about processes that no longer exist since they died with the crashing system.
There must be a procedure in VistA to clean out this type of information. -- Bhaskar On Sun, 2006-01-15 at 11:21 -0600, Marc Krawitz wrote: > I corrected the database problems based on the gt.m administration > guide. Re-ran mupip integ and I received a clean report. However, > when I start TaskMan, I get the following. What does this mean and > how do I fix it. > > Thanks, > > Marc > > [EMAIL PROTECTED]:~> gtm > > GTM>D ^ZTMON > Checking Taskman. Current $H=60280,40611 (Jan 15, [EMAIL PROTECTED]:16:51) > RUN NODE=60280,40605 (Jan 15, [EMAIL PROTECTED]:16:45) > Taskman is current.. > Checking the Status List: > Node weight status time $J > Recording A Trapped [EMAIL PROTECTED]:16:4510447 > > Checking the Schedule List: > Taskman has 9 tasks scheduled. > 8 of them are overdue. First task is 694817 seconds late. > > Checking the IO Lists: > There are no tasks waiting for devices. > > Checking the Job List: > There are no tasks waiting for partitions. > > Checking the Task List: > There are no tasks currently running. > On node ROU:vistaserver there are no free Sub-Manager(s). Status: > Run > > Enter monitor action: UPDATE// > > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
