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

[LDM #NVM-507161]: Fwd: ldmd.log question



Michael,

[Your inquiry is fairly generic, so I drove it into our tracking system so that 
others might benefit.]

> I'm going through my ldmd.log files cleaning up any errors I find. One I've
> encountered has me puzzled. The error is this:
> 
> 20181113T144856.869685Z pqact[2652] ERROR filel.c:1005:unio_open()
> unio_open: /home/COETEST/RR1MSR
> 20181113T144856.869706Z pqact[2652] ERROR filel.c:1289:unio_prodput()
> Couldn't get entry for product "SRUS53 KMSR 131448 /pRR1MSR"
> 20181113T144856.869715Z pqact[2652] ERROR palt.c:1234:prodAction() Couldn't
> process product: feedtype=IDS|DDPLUS, pattern="/p(.*)", action=file,
> args="-close   -overwrite      /home/COETEST/\1"
> 20181113T144856.872385Z pqact[2652] ERROR filel.c:1005:unio_open()
> Permission denied
> 
> ...and the pqact entry is this:
> 
> # Public Products Service
> PPS     /p(.*)
> FILE    -close  -overwrite      /home/COETEST/\1
> 
> I'm not sure if I'm having a file permission problem, directory permission
> issue....what it might be. What should I check on this?

It looks like you don't have permission to create the file 
"/home/COETEST/RR1MSR". I would check the file-protection modes of "/", "/home" 
(if it exists), and "/COETEST" (if it exists).

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NVM-507161
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.



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.