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.
Hi Martha, Here are the steps provided to another user to setup MySQL use for GRIB serving in McIDAS. Note that I assume that you have already performed the first stem... 1) install the MySQL pieces needed for the McIDAS ADDE GRIB server: yum install mysql-server yum install mysql-client yum install mysql-devel 2) change the password for the MySQL installation to 'xxxxx' as per instructions in http://lists.mysql.com/mysql/171366: <as 'root'> service mysql stop mysqld_safe --skip-grant-tables & mysql -uroot mysql mysql> use mysql; mysql> UPDATE user SET password=PASSWORD("xxxxx") WHERE user="root"; mysql> FLUSH PRIVILEGES; -- exit the mysqld_safe invocation chkconfig --level 345 mysqld on /etc/init.d/mysqld start At this point, you should be able to create the MySQL database from the 'mcidas' account: <logged in as 'mcidas'> cd $MCDATA decinfo.k SET DMBIN INACTIVE -- wait until DMBIN has exited gribadmin makedb <- you will be asked to provide the password you set above Assuming that this went smoothly, then you should be able to turn GRIB filing back on: decinfo.k SET DMBIN ACTIVE After GRIB/GRIB2/BUFR processing is working via DMBIN, you will need to attend to scouring of the model data being received and processed by DMBIN: - in a previous setup you ran 'mcxconfig' from the Linux command line from the 'mcidas' account. One of the things that 'mcxconfig' creates is an example file of crontab additions that are needed for the 'ldm' account. The items relevant to the model data processing are: # # Prune McIDAS-XCD produced BURR/GRIB files 10 08,20 * * * util/xcdscour BUFR 1 /machine/data/ldm/mcidas/bufr 20 08,20 * * * util/xcdscour GRIB 1 /machine/data/ldm/mcidas/grib NB: the times that are configured for these invocations to be run, and the directory in which to run the scouring will have been set to match your setup by the 'mcxconfig' invocation on your XCD processing machine. The entries I show above are relevant to my workstation only! So, you will need to: - copy the utility '~mcidas/bin/xcdscour' to a directory in your 'ldm' account. Typically, that directory is included in the PATH setting for user 'ldm' so you can run the utility by-hand if needed or desired. The Unidata convention is to create the directories ~ldm/decoders and ~ldm/util AND add both of these directories to the PATH of the user 'ldm'. - you will need to edit the copy of 'xcdscour' that you just made and make sure that the PATH setting in the file is correct. The key here is to make sure that the 'mysql' executable can be found. - you will need to insure that the copy of 'xcdscour' that you just made is CHMODded to be executable by the user 'ldm': <as 'ldm'> cd ~ldm mkdir util cd util cp ~mcidas/bin/xcdscour . chmod +x xcdscour vi xcdscour NB: - the scouring of the directories in which GRIB/GRIB2 and BUFR files are written and the scouring of the MySQL database can be a heavyweight operation (meaning that it might take some time and disrupt fast access to the database while running). It is for this reason that it is highly recommended to adjust the times the scouring will run to minimize impact on your system I believe that _if_ there were no snags up to this point, you are ready to configure the RTGRIBS and RTGRIB2 datasets. This is done as follows: <as 'mcidas'> cd $MCDATA batch.k XCDGRIB.BAT batch.k XCDGRB2.BAT -- aside: these may have already been created through your running of 'mcxconfig' previously, but it can't hurt to do it again One last question: - Unidata McIDAS-X/-XCD is now up to v2008c, and it will soon be bumped up to v2008d. What addendum are you running? Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: STG-808468 Department: Support McIDAS Priority: Normal Status: Closed