[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
3090.0. "probewatch: reporting problem (conversations)" by MFRNW1::SCHUSTER (Karl Schuster @RTO OMS Munich Germany) Wed Dec 20 1995 10:26
Probewatch UNIX V3.3:
I want to create a conversation report from commandline, but it does not work.
Doing (an identical) conversation report from the probewatch application via
domainmanager - reportgenerator works.
error message from $NSHOME/usr/dvreport:
dvreport: No reports available for agent probe1!
Where is the problem ?
Regards, Karl
Following the relevant files:
$NSHOME/usr/dvlog.cfg
---------------------
probe1 ALL 00:15 00:15 00:15
probe2 ALL 00:15 00:15 00:15
dvrep_conversation.cfg
----------------------
started with: $NSHOME/bin/dvreport dvrep_conversation.cfg 951201 951231
#
type: conv
agent: probe1
domain: ALL
header1: "***** Top 10 Conversations LAN Digital RTO *****"
lpp: 66
top: 10
sort: util
output: "dvrep_conversation.txt"
$NSHOME/usr/dvlog.log
---------------------
Dec 20 12:26: New logging daemon started, pid = 9452
Dec 20 12:30: logging segment statistics for agent: probe1, domain: ALL
Dec 20 12:30: logging segment statistics for agent: probe2, domain: ALL
Dec 20 12:30: logging host statistics for agent: probe1, domain: ALL
Dec 20 12:37: logging host statistics for agent: probe2, domain: ALL
Dec 20 12:39: logging conversation statistics for agent: probe1, domain: ALL
Dec 20 12:50: logging conversation statistics for agent: probe2, domain: ALL
Dec 20 13:00: logging segment statistics for agent: probe1, domain: ALL
Dec 20 13:00: logging segment statistics for agent: probe2, domain: ALL
Dec 20 13:00: logging host statistics for agent: probe1, domain: ALL
Dec 20 13:06: logging host statistics for agent: probe2, domain: ALL
Dec 20 13:08: logging conversation statistics for agent: probe1, domain: ALL
Dec 20 13:20: logging conversation statistics for agent: probe2, domain: ALL
Dec 20 13:30: logging segment statistics for agent: probe1, domain: ALL
Dec 20 13:30: logging segment statistics for agent: probe2, domain: ALL
Dec 20 13:30: logging host statistics for agent: probe1, domain: ALL
Dec 20 13:40: logging host statistics for agent: probe2, domain: ALL
Dec 20 13:44: logging conversation statistics for agent: probe1, domain: ALL
Dec 20 13:57: logging conversation statistics for agent: probe2, domain: ALL
Dec 20 14:15: logging segment statistics for agent: probe1, domain: ALL
Dec 20 14:15: logging segment statistics for agent: probe2, domain: ALL
Dec 20 14:15: logging host statistics for agent: probe1, domain: ALL
Dec 20 14:24: logging host statistics for agent: probe2, domain: ALL
Dec 20 14:26: logging conversation statistics for agent: probe1, domain: ALL
Dec 20 14:38: logging conversation statistics for agent: probe2, domain: ALL
T.R | Title | User | Personal Name | Date | Lines |
---|
3090.1 | now o.k. | MFRNW1::SCHUSTER | Karl Schuster @RTO OMS Munich Germany | Tue Jan 02 1996 07:37 | 4 |
| The conversation report now works.
I just did not wait enough to have data for the report.
Karl
|
3090.2 | | MFRNW1::SCHUSTER | Karl Schuster @RTO OMS Munich Germany | Thu Jan 25 1996 03:35 | 8 |
| my current experience:
The conversation report runs only sometimes. Mostly I get: "no data
available for report ...."
I could not find out under what circumstances it works or not.
Karl
|