[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20060105: LDM unexpected death and logging problems (cont.)



Ben,

>Date: Fri, 06 Jan 2006 12:14:47 -0700
>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>To: Ben Cotton <address@hidden>
>Subject: 20060105: LDM unexpected death and logging problems (cont.)

The above message contained the following:

> Here is the output from Ben's ldmd.log.1 file:
> Jan 03 19:46:41 pqact[32614] NOTE: Starting Up
> Jan 03 19:46:41 pqact[32615] NOTE: Starting Up
> Jan 03 19:46:41 pqact[32616] NOTE: Starting Up
> Jan 03 19:46:41 pqact[32617] NOTE: Starting Up
> Jan 03 19:46:41 pqact[32618] NOTE: Starting Up
> Jan 03 19:46:41 pqact[32619] NOTE: Starting Up
> Jan 03 19:51:34 pqact[32619] WARN: write(11,,4096) to pipe took 12.455922 s
> Jan 03 19:54:06 pqact[32616] WARN: write(6,,4096) to pipe took 2.113214 s
> Jan 03 19:57:45 pqact[32616] WARN: write(6,,4096) to pipe took 2.708293 s
> Jan 03 19:57:52 pqact[32619] WARN: write(17,,4096) to pipe took 4.661930 s
> Jan 03 20:00:55 pqact[32619] WARN: write(7,,4096) to pipe took 10.178098 s
>  ...
> Jan 04 23:10:17 pqact[32619] WARN: write(8,,4096) to pipe took 5.363954 s
> Jan 05 02:10:53 pqact[32619] WARN: write(15,,4096) to pipe took 2.056173 s
> Jan 05 06:18:10 pqact[32614] NOTE: Interrupt
> Jan 05 06:18:10 pqact[32616] NOTE: Interrupt
> Jan 05 06:18:10 pqact[32614] NOTE: Exiting
> Jan 05 06:18:10 pqact[32616] NOTE: Exiting
> Jan 05 06:18:10 pqact[32615] NOTE: Interrupt
> Jan 05 06:18:10 pqact[32615] NOTE: Exiting
> Jan 05 06:18:10 pqact[32618] NOTE: Interrupt
> Jan 05 06:18:10 pqact[32618] NOTE: Exiting
> Jan 05 06:18:10 pqact[32617] NOTE: Interrupt
> Jan 05 06:18:10 pqact[32617] NOTE: Exiting
> Jan 05 06:18:10 pqact[32619] NOTE: Interrupt
> Jan 05 06:18:10 pqact[32619] NOTE: Exiting

It appears that the six pqact(1) processes were each sent a SIGINT
signal from the top-level LDM process.  We need to know why the
top-level LDM process did this.  To diagnose the logging problem, I
suggest

    1.  Going into the directory "src/ulog".

    2.  Executing the command "make ulogger".

    3.  Testing the ability to log to the standard error stream by
        executing the commands

            ./ulogger -l- -p error "NOTICE test"
            ./ulogger -l- -p warning "NOTICE test"
            ./ulogger -l- -p notice "NOTICE test"
            ./ulogger -l- -p info "NOTICE test"
            ./ulogger -l- -p debug "NOTICE test"

    4.  Testing the ability to log to the LDM log file by
        executing the commands

            ./ulogger -p error "ERROR test"
            ./ulogger -p warning "WARNING test"
            ./ulogger -p notice "NOTICE test"
            ./ulogger -p info "INFO test"
            ./ulogger -p debug "DEBUG test"

Please let me know what you discover.

Regards,
Steve Emmerson


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.