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

[LDM #DLI-905086]: Can't get logging to work with LDm 6.11.6 on VM's



Gilbert,

> > BTW, this is the first time I've seen "$HOME/ldm". Is that truly a 
> > subdirectory?
> 
> That's by accident ($HOME/ldm), I changed it to read $HOME.
> 
> I then typed "rehash", logged out, logged back in, restarted the LDM,
> and...
> 
> Aug 21 11:06:19 vm-weather3 pqact[17783] ERROR: child 18828 exited with
> status 1
> 27 (PIPE decoders/dcgrib2 -d data/gempak/logs/dcgrib2_GFSthin.log -e
> GEMTBL=/hom
> e/gempak/GEMPAK6.8.0/gempak/tables)
> Aug 21 11:06:19 vm-weather3 pqact[17783] ERROR: [filel.c:305] Deleting
> failed PI
> PE entry: pid=18828, cmd="decoders/dcgrib2 -d
> data/gempak/logs/dcgrib2_GFSthin.l
> og -e GEMTBL=/home/gempak/GEMPAK6.8.0/gempak/tables"
> Aug 21 11:06:19 vm-weather3 pqact[17783] ERROR: child 18829 exited with
> status 1
> 27 (PIPE decoders/dcgrib2 -d data/gempak/logs/dcgrib2_GFSthin.log -e
> GEMTBL=/hom
> e/gempak/GEMPAK6.8.0/gempak/tables)
> Aug 21 11:06:19 vm-weather3 pqact[17783] ERROR: [filel.c:305] Deleting
> failed PI
> PE entry: pid=18829, cmd="decoders/dcgrib2 -d
> data/gempak/logs/dcgrib2_GFSthin.l
> og -e GEMTBL=/home/gempak/GEMPAK6.8.0/gempak/tables"

I was mistaken. Sorry for leading you down a blind alley.

Tom just pointed-out to me that the execvp(2) function, which pqact(1) uses to 
execute decoders, treats program pathnames that have a slash in them specially: 
they're used as the pathname of the program and the PATH environment variable 
isn't consulted at all. Consequently, your pqact(1) process -- which should 
have the LDM user's home-directory as its current working directory -- should 
be able to locate decoders like "decoders/dcmsfc".

I'm unable to imagine a scenario that explains these two facts:
  1. The parent pqact(1) process logs that the decoder-related child-process 
exited with status 127;
  2. There is no log message from the decoder-related child-process;

I would like to log onto the system in question to investigate. Unfortunately, 
I don't keep passwords for remote user's systems. I've attached my public 
ssh(1) key. If you'll add it to ~ldm/.ssh/authorized_keys on the system in 
question, then I should be able to access it.

> *******************************************************************************
> Gilbert Sebenste                                                    ********
> (My opinions only!)                                                  ******
> Staff Meteorologist, Northern Illinois University                      ****
> E-mail: address@hidden                                  ***
> web: http://weather.admin.niu.edu                                      **
> Twitter: http://www.twitter.com/NIU_Weather                            **
> Facebook: http://www.facebook.com/niu.weather                           *
> *******************************************************************************

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: DLI-905086
Department: Support LDM
Priority: Normal
Status: Closed

Attachment: authorized_keys
Description: Binary data