Hi Chris, I think this fixed my problem. I know that I do always restart my FM, but I believe that time I did have an existing empty catalog directory. And removing it did help.
Thanks! Val Valerie A. Mallder New Horizons Deputy Mission System Engineer Johns Hopkins University/Applied Physics Laboratory > -----Original Message----- > From: Chris Mattmann [mailto:[email protected]] > Sent: Friday, October 03, 2014 2:56 AM > To: [email protected] > Subject: Re: error ingesting product :( > > Thanks for checking on this Val. > > Did you make sure to restart the File Manager after your policy change? > FM only reads those policy files on start up. > One thing to note too - that catalog folder is created by the FM on its own. > It > shouldn?t be created by you beforehand. > > Try removing catalog. Stopping FM. Then restarting it (trusting it will be > created on > ingest). Did that fix it? > > Cheers, > Chris > > ------------------------ > Chris Mattmann > [email protected] > > > > > -----Original Message----- > From: "Mallder, Valerie" <[email protected]> > Reply-To: <[email protected]> > Date: Thursday, October 2, 2014 at 2:30 PM > To: "[email protected]" <[email protected]> > Subject: RE: error ingesting product :( > > >Hi John, > > > >Thanks for writing! I was just getting close to posting an update on > >my progress, but you beat me to it. I was able to fix the first part > >of this error when I found that I had a typo in my product-types.xml > >file. I scanned that file a thousand times before I posted my message, > >but I never saw the typo so now I feel pretty stupid. > > > >I've made a bunch of progress since this afternoon, but I am still > >stuck and not able to ingest my files. I have been unable to generate > >the correct reference for the final location of the files in the > >archive folder. And, I CatalogExceptions because the > >archive/catalog/segments file does not exist. I think I need to use the > >MetadataBasedFileVersioner, so that I can specify the destination > >folder using values in the metadata, but I can't seem to get that to > >work. So, I am going to post a new topic to see if I can get some help with > >that. > > > >Thanks, > >Val > > > > > > > >Valerie A. Mallder > >New Horizons Deputy Mission System Engineer Johns Hopkins > >University/Applied Physics Laboratory > > > >> -----Original Message----- > >> From: Lewis John Mcgibbney [mailto:[email protected]] > >> Sent: Thursday, October 02, 2014 2:48 PM > >> To: [email protected] > >> Subject: Re: error ingesting product :( > >> > >> Hi Valerie, > >> > >> It looks like you've run into our good old friend 'null' :) > >> > >> A basic question before we go further. > >> Which version of OODT are you using? > >> I ask this because the stack trace is valuable for hopefully stepping > >>throgh code myself. > >> > >> On Thu, Oct 2, 2014 at 9:28 AM, Mallder, Valerie > >><[email protected] > >> > wrote: > >> > >> > > >> > PID file > >> > (/homes/malldva1/project/jedi/users/jedi-pipeline/oodt-deploy/filem > >> > gr/ > >> > run/cas.filemgr.pid) found. Is File Manager still running? Start > >> > aborted. > >> > > >> > >> I don't really like the look of this one? Have you tried killing all > >>processes relating to filemgr before starting the filemgr again? The > >>start aborted in particular is quite worrying. Does anyone know where > >>this message comes from? > >> > >> > >> > org.apache.xmlrpc.XmlRpcException: java.lang.Exception: > >> > org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: > >> > Error ingesting product > >>[org.apache.oodt.cas.filemgr.structs.Product@fb60123] : > >> > null > >> > > >> > >> We really need to sort out these cryptic error messages. I've logged > >>an issue to address this > >> > >> https://issues.apache.org/jira/browse/OODT-755 >
