This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Yes! Definitely! I was scratching my head about this one. But you did mention the same setup works on your Solaris machines? You may simply be getting lucky with something about Solaris I/O (this is all a presumption and a wild guess) that allows multiple processes to write to the same file without corrupting it. -MJ > > Well, sorry for being so thick headed. I see what you mean now..WRITING to > the same file.. So if I have two dcgrib2 going, decoding two different > forecast hours, but writing to the same output file there could be issues? > Is that right? > > Thanks, > Robert > > > > > -----Original Message----- > From: Unidata GEMPAK Support [mailto:address@hidden] > Sent: Tue 3/15/2011 5:42 PM > To: Robert Mullenax > Cc: address@hidden > Subject: [GEMPAK #PGK-898839]: dcgrib2 issues on Cent OS 5.5 and GEMPAK 6.2.0 > > I'm not able to recreate this problem on my end, and don't know of any > problems with dcgrib2 on systems similar to yours. However in the past when > users experience issues similar to those you're seeing (FL -4 error, missing > grids in gem file) it tends to be caused by multiple instances of the decoder > (dcgrib2) running at the same time, attempting to write to the same file. > The log snippet you posted doesn't show this, but are you seeing different > process IDs in the dcmetr log elsewhere? > > Can you upload a copy of one of these gem files which show correct grids in > GDINFO but don't display? > > http://motherlode.ucar.edu/repository/alias/gempakuploads/ > > -Michael > > > > > > ..actually I am now finding cases where the correct output is not present > > in the .gem file for a given forecast hour, but dcgrib2.log does not show > > the Cannot read file error. > > > > > > -----Original Message----- > > From: Unidata GEMPAK Support [mailto:address@hidden] > > Sent: Tue 3/15/2011 10:18 AM > > To: Robert Mullenax > > Subject: [GEMPAK #PGK-898839]: dcgrib2 issues on Cent OS 5.5 and GEMPAK > > 6.2.0 > > > > > > Robert Mullenax, > > > > Your Ticket has been received, and a Unidata staff member will review it > > and reply accordingly. Listed below are details of this new Ticket. Please > > make sure the Ticket ID remains in the Subject: line on all correspondence > > related to this Ticket. > > > > Ticket ID: PGK-898839 > > Subject: dcgrib2 issues on Cent OS 5.5 and GEMPAK 6.2.0 > > Department: Support GEMPAK > > Priority: Normal > > Status: Open > > > > > > > > Please let us know how we can assist you further. > > > > Unidata User Support > > > > > > > > > > > Ticket Details > =================== > Ticket ID: PGK-898839 > Department: Support GEMPAK > Priority: Normal > Status: Open > > > > Ticket Details =================== Ticket ID: PGK-898839 Department: Support GEMPAK Priority: Normal Status: Open