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

[LDM #VLF-828955]: ldm-6.11.5 pqinsert problems



Julie & Stephen,

We'll, I guess I don't know what's causing the pqinsert problem, then. As I 
indicated,  I didn't have any problem. 

The SIGSEGV problem will be fixed in the next release.  For the moment,  the 
workaround is not to use an invalid option.

> Unidata LDM Support wrote, On 06/12/2013 04:43 PM:
> > Julie,
> >
> > Well, I logged onto Puffin and the LDM user and was able to add 
> > data-products to the product-queue using pqinsert(1) and receive 
> > notifications of their addition.
> 
> Steve, fwiw, there's still clearly a programming bug causing Segfaults in the 
> 'usage()' function of pqinsert that needs to be addressed regardless of the 
> functionality of pqinsert in this case.
> Can you enter that bug internally?  see my backtrace report in the earlier 
> e-mail.
> Subject: #61818: Fwd: [LDM #VLF-828955]: ldm-6.11.5 pqinsert problems
> Let me know if you need that output again...
> 
> > The LDM user account information is non-standard:
> >
> >     fgrep ldm /etc/passwd
> >     +ldm:x:::::
> >
> > This means no home-directory or user-shell. This might cause problems. I 
> > just don't know because we've never tried that.
> 
> The '+' indicates that this is an NIS account, and to retrieve any empty 
> fields from the NIS server:
> 
> puffin:~# getent passwd ldm
> ldm:x:11101:10012:Local Data Manager:/home/ldm:/bin/csh
> 
> puffin:~# getent -s files passwd ldm     (use local files to lookup user 
> entry = nothing found)
> puffin:~# getent -s nis passwd ldm       (use the YP/NIS system to lookup the 
> user = full record)
> ldm:x:11101:10012:Local Data Manager:/home/ldm:/bin/csh
> 
> So, that's not an issue.
> 
> > I did have to add $HOME/bin to the LDM-user's PATH environment variable in 
> > order to get things to work.
> >
> > I recommend completing the LDM user account information and setting the LDM 
> > user's profile-files according to the installation instructions.
> 
> again, not an actual issue.
> 
> > Be advised that if the pqinsert(1) process is run outside of the LDM 
> > process-group, then the upstream LDM-s will not receive a SIGCONT when a 
> > new product is added to the product-queue. In this case, the fail-safe 
> > behavior of the upstream LDM processes is to check the product-queue every 
> > 30 seconds for new data-products.
> >
> > Most sites that use pqinsert(1) execute it indirectly via an EXEC entry in 
> > the LDM configuration-file (etc/ldmd.conf) to avoid this delay.
> 
> I'll let Julie figure out if this addresses her original issue (i'm just the 
> sysadmin here)
> 
> >
> > Regards,
> > Steve Emmerson
> >
> > Ticket Details
> > ===================
> > Ticket ID: VLF-828955
> > Department: Support LDM
> > Priority: Normal
> > Status: Closed
> >
> 
> thanks for checking in,
> 
> --stephen
> 
> --
> Stephen Dowdy  -  Systems Administrator  -  NCAR/RAL
> 303.497.2869   -  address@hidden        -  http://www.ral.ucar.edu/~sdowdy/
> 
> 

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: VLF-828955
Department: Support LDM
Priority: Normal
Status: Closed


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.