DELOG INFO

DELOG INFO

Delog grep info

This file contains various useful grep expressions to use in conjunction with the delog program.

  • To scan for periods with no VC01 messages (will show up as a string of reformat messages with no VC01 telemetry message inbetween.

    delog 2000 | grep -E "REFORMAT|For VC01 SESS" | grep -E "AOCHK2 | 0000 " | more

  • To find transfers from DPS processed by the DPS subsystem (last 2 hours)

    delog -2 | grep DAN | grep Total

    delog -2 | grep DPS | more

  • You can also use grep -v to filter things out

  • To find info only relating to fantine last 24 hours:

    delog -24 | grep fantine | more

  • For machines that also get telemetry files ftp'd, it's often useful to exclude them, compare:

    delog -24 | grep mditlm | more and delog -24 | grep mditlm | grep -v /ftp

    In general, grep for something that you think will catch everything related to a problem, then work on excluding (using grep -v) those things that distract you from a pattern. When you've located the times when interesting things go on, it's a good idea to take a 2nd look without filtering out things, just to make sure you know the context...

    •

    NOTE: When going through the delog on Tuesday and Friday, be sure to double check with the default telemetry list and make sure it is current.

    WHAT TO LOOK FOR:
    Look for the usual telemetry and commanding messages:

    TELEMETRY 9000 Packets Received; Total bytes rcvd: 10071016 From PACOR For MDI SESSION
    TELEMETRY 19000 Packets Received; Total bytes rcvd: 6888494 From PACOR For VC01 SESSION

    Look for the usual end of pass messages and see what failed to connect (look for the word ERROR) -- see the info file called Telemetry Session Restarts

    You can ignore the TLM display error messages that look like this:
    TELEMETRY Error Setting the Telemetry Values in the DataBase VC01 SESSION

    All else may be abnormal and read it carefully

    Location: /u/ecs/soc/info/delog_info.html