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

Re: 20040805: Howard LDM Feeds



Hi Jason,

Keep in mind the LEAD testbed config is designed for grid computing..

> -> hupsyslog: couldn't open /var/run/syslogd.pid

Check ownership and permissions..should be ldm owned and writeable.


2)

Check your ldmadmin file in ~ldm/bin

Should look something like this:

<snip>

# default number of logs to rotate with the newlog(1) command

$numlogs = "14";

# file paths - everything here is based on the ldmhome variable by
default.

$bin_path = "$ldmhome/bin";
$etc_path = "$ldmhome/etc";
$log_path = "$ldmhome/logs";
$data_path = "$ldmhome/data";
$pq_path = "$data_path/ldm.pq";
$surf_path = "$data_path/pqsurf.pq";

# ldmadmin file locations and names

$pid_file = "$ldmhome/ldmd.pid";
$lock_file = "$ldmhome/.ldmadmin.lck";
$log_file = "$log_path/ldmd.log";
$ldmd_conf = "$etc_path/ldmd.conf";
$pqact_conf = "$etc_path/pqact.conf";
$scour_file = "$etc_path/scour.conf";

# set this to 0 if you don't want the ldm log files rotated whenever you
# start or restart the ldm.

$log_rotate = "1";

###############################################################################
# END OF CONFIGURATION - You should not need to change anything below this
#                        point.
###############################################################################

<snip>



> Aug 16 13:13:15 drizzle pqact[8195]: pipe_dbufput:
>
decoders/bin/metar2ncdecoders/etc/metar.cdldata/pub/decoded/netcdf/surface/04$
> write error

how big is your queue? who owns it?

This is a start...we may need to bump you up to the LDM guru (Steve
Emmerson) if we still have issues :)

Happy Monday,


Jeff
---------------------------------------------------------------------
Jeff Weber                                    address@hidden        :
Unidata Program Center                        PH:303-497-8676        :
University Corp for Atmospheric Research      3300 Mitchell Ln       :
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000  :
---------------------------------------------------------------------

On Mon, 16 Aug 2004, Jason T. Smith wrote:

> Hey Jeff,
>
>    Happy Monday. I've been working on the LDM and i found the LEAD testbed
> installation instructions.  So i migrated my installation closer to the 
> testbed
> installation and i'm having a few problems.
>
> When I start the ldm, i get the error below:
>    bin/ldmadmin start
>    Checking the pqact(1) configuration-file "/home/ldm/etc/pqact.conf"...
>    /home/ldm/etc/pqact.conf is syntactically correct
> -> hupsyslog: couldn't open /var/run/syslogd.pid
>    Starting the LDM server...
>
> The second problem is that the logging is getting confused as in it continues
> to log into the file ldmd.log.1.  My understanding of it is that it should
> always log to ldmd.log and when the ldm is restarted, the rotates the log.
> Even if the rotate was turned off, I would guess that it should log to 
> ldmd.log.
>
> The third problem is with the decoding of the raw data. Below are the lines
> that I am seeing in the log:
>
>
>
> Aug 16 02:43:36 drizzle gribtonc[26358]: can't create or size 0 output netCDF
> file data/pub/decoded/netcdf/GRIB/2004081600_eta_211.nc, exiting
>
> Aug 16 13:13:15 drizzle pqact[8195]: pipe_dbufput:
> decoders/bin/metar2ncdecoders/etc/metar.cdldata/pub/decoded/netcdf/surface/0408
> write error
>
> Aug 16 13:25:22 drizzle pqact[8195]: pipe_dbufput:
> decoders/bin/ua2ncdecoders/etc/raob.cdldata/pub/decoded/netcdf/upperair/0408
> write error
>
> Aug 16 13:26:14 drizzle pqact[8195]: pbuf_flush (4) write: Broken pipe
>
> Aug 16 13:26:14 drizzle pqact[8195]: child 10191 exited with status 2
>
> THe last 2, about the broken pipe and the child exited with status 2, is what
> is filling the log.  Thanks for any help on any of these.
>
> Jason Smith
> Howard University.
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>


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.