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.
Unidata Support wrote: > ------- Forwarded Message > > >To: address@hidden > >From: Tom McDermott <address@hidden> > >Subject: Wierd ldm behavior > >Organization: SUNY Brockport > >Keywords: 200007111633.e6BGXpT27805 LDM 5.0.10 > > Hello, > > I have been running ldm v. 5.0.10 since the end of May on our Sparc > Solaris 7 server, vortex.weather.brockport.edu, with no problems. > Yesterday one of my downstream feeds, Colgate University, which had not > connected to our server since the beginning of May, attempted to connect > from their server, gissun.colgate.edu. The response was literally > thousands of RECLASS messages within seconds and, later on, continual > 'pq_sequence failed' messages (See BELOW for sample). This continued until > I was able to reinstall v. 5.0.9 and restart. That took care of the > problem. But I ended up with a 4.5MB log file from yesterday. > > So this doesn't require immediate attention as I can run 5.0.9 > indefinitely. But I wanted to let you know about this problem as it may > possibly affect other sites. I communicated with Adam Burnett at Colgate > about the problem. He said he is running v. 5.0.6 of ldm (I believe he is > running under Solaris 2.6) and was willing to upgrade to a more recent > version of ldm if necessary, but in the event, it wasn't needed. But it > would be interesting to find out if upgrading would solve the problem. > > Tom McDermott Email: address@hidden > System Administrator Phone: (716) 395-5718 > Earth Sciences Dept. Fax: (716) 395-2416 > SUNY College at Brockport > > ----------------------------------------------------------------------------- > Jul 10 14:09:57 vortex gissun[19214]: Connection from gissun.colgate.edu > Jul 10 14:09:57 vortex gissun(feed)[19214]: Starting Up: > 20000710131652.867 TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:57 vortex gissun(feed)[19214]: topo: gissun.colgate.edu > UNIDATA > Jul 10 14:09:57 vortex gissun(feed)[19214]: RECLASS: 20000710131653.553 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:57 vortex gissun(feed)[19214]: RECLASS: 20000710131653.673 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:57 vortex gissun(feed)[19214]: RECLASS: 20000710131653.702 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:57 vortex gissun(feed)[19214]: RECLASS: 20000710131653.732 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:57 vortex gissun(feed)[19214]: RECLASS: 20000710131653.791 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131653.870 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131653.917 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131653.997 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131654.032 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131654.072 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131654.093 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131654.113 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131654.150 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131654.173 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 14:09:58 vortex gissun(feed)[19214]: RECLASS: 20000710131654.208 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > > ............... > > Jul 10 15:54:37 vortex gissun(feed)[17130]: RECLASS: 20000710150133.476 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 15:54:38 vortex gissun(feed)[17130]: pq_sequence failed: I/O error > (errno = 5) > Jul 10 15:54:38 vortex gissun(feed)[17130]: Exiting > Jul 10 15:54:44 vortex rpc.ldmd[13349]: child 17130 exited with status 1 > Jul 10 15:55:08 vortex gissun[17214]: Connection from gissun.colgate.edu > Jul 10 15:55:08 vortex gissun(feed)[17214]: Starting Up: > 20000710150203.780 TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 15:55:08 vortex gissun(feed)[17214]: topo: gissun.colgate.edu > UNIDATA > Jul 10 15:55:08 vortex gissun(feed)[17214]: RECLASS: 20000710150204.592 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 15:55:09 vortex gissun(feed)[17214]: pq_sequence failed: I/O error > (errno = 5) > Jul 10 15:55:09 vortex gissun(feed)[17214]: Exiting > Jul 10 15:55:15 vortex rpc.ldmd[13349]: child 17214 exited with status 1 > Jul 10 15:55:40 vortex gissun[17261]: Connection from gissun.colgate.edu > Jul 10 15:55:40 vortex gissun(feed)[17261]: Starting Up: > 20000710150234.750 TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 15:55:40 vortex gissun(feed)[17261]: topo: gissun.colgate.edu > UNIDATA > Jul 10 15:55:40 vortex gissun(feed)[17261]: RECLASS: 20000710150235.811 > TS_ENDT {{UNIDATA, "(^[A-OQ-X])|(^YZ].[^AHIJRU])"}} > Jul 10 15:55:40 vortex gissun(feed)[17261]: pq_sequence failed: I/O error > (errno = 5) > Jul 10 15:55:40 vortex gissun(feed)[17261]: Exiting > Jul 10 15:55:46 vortex rpc.ldmd[13349]: child 17261 exited with status 1 > > ------- End of Forwarded Message Hi Tom, This sounds odd. The changes made between 5.0.9 and 5.0.10 were minimal, and none applied to the portions of the code to which these messages pertain. There are usually a few (not thousands!) of RECLASS messages upon start up of an upstream or downstream site while the sites renegotiate what products to send. Otherwise, by themselves, the RECLASS and pq_sequence error messages usually indicate network problems. Can you duplicate this problem? I.e., if you switch back to 5.0.10 does it happen again? I'm wondering if now that gissun is caught up these problems won't appear again... Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************