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.
>From: David Garrana Coelho <address@hidden> >Organization: UFRJ >Keywords: 200405241627.i4OGRitK025144 McIDAS scripts cron hang Hi David, Sorry I couldn't respond yesterday, but we just finished two day's of meetings here at Unidata. > Hi! Everything ok? Everything is OK so far. I have not heard if the paper I submitted to CBMET has been accepted yet. > Long time since last email, Im writing to pose a question I >believe may have something relationed to the issue Robert Mullenax posted >on the list, but I don't want to add noise to discussion, because I can be >wrong. >Brisa is hanging up on some McIDAS non-interactive scripts I made >to update our page, but its recent. The processes (imgdisp.k, sfgram.k, >etc) just use the max CPU time available for hours and hours till they are >manually killed. It's becoming annoying because it competes with our >mesoscale model runs, delaying it for 4 to 5 hours sometimes. This is a bad situation that we need to understand and fix. >This >behavior is being observed almost daily in the past 8 to 9 days. Can it be >relationed to some "garbage" along the feeds? The question is what ADDE server is being accessed for the data used by IMGDISP and SFCMG? >My guess its the machine >workload and age playing tricks on me, but the post Robert did raise >other possibilities. Robert's inquiry was about a decoder hanging. What are the names of scripts that are hanging? Which account are they running out of? Can I get on to troubleshoot? > Just FYI, I made a visit to Waldenio past monday to know his team >and what they been doing. Its interesting to see how different focus >change everything. We ended exchanging info about other problems they had >and I was able to pose some solutions to that. Trading know-how feels >better than I thought....lol. Anyway, what I mean is thats very good to >have a "link" or common ground to serve as an opportunity to share info >and lend some help where its needed. It's something we didn't have here >before, and I wanted to thank you for providing that to us. I am glad to hear that having a link to CPTEC is proving to be useful to you. Your observation that having another site to talk to about issues being useful is exactly what we mean by community building. Getting folks talking about common needs and issues helps build a strong community that can easily be extended to others if the exchanges are made accessible. This is the concept behind our inquiry tracking system, a system that makes available the transactions between our User Support and educators/researchers at sites available online. Anyway, back to your problem. If the scripts that are hanging are run out of the 'mcidas' account on brisa, I should have login information. If they are being run from a different account, then I need the login information in order to troubleshoot. Also, I need the names of the scripts that are hanging (if not all). Lastly, I assume that the scripts are being run out of cron; is this true? Cheers, Tom -- +-----------------------------------------------------------------------------+ * Tom Yoksas UCAR Unidata Program * * (303) 497-8642 (last resort) P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/* +-----------------------------------------------------------------------------+