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 Brian,The problem you reported is not the problem I saw on nexraditr.iihr.uiowa.edu. Instead, I saw this:
[ldm@nexraditr ldm]$ hupsyslog hupsyslog: kill -HUP 4800: Permission deniedThis is because of a missing step in the build process, a step you must do as root. That is,
[root@nexraditr src]# make install_setuids which I did. Now, when I run ./ldm-6.2.0/bin/hupsyslog it works fine.You, however, have a nonstandard installation. Instead of runtime being a pointer to ldm-6.2.0, it is a separate directory. And, that runtime/bin/hupsyslog doesn't have the permissions set right and will give you the error above.
I suggest you standardize the installation - it will make your life easier. Take a look at the installation on ldm.iihr.uiowa.edu. (It's my recollection that I changed that installation from something like what you have on your new machine to what's there now, the standard installation.) I think if you standardize the installation then when you follow the installation instructions it should all just work.
Give that a try and let me know if you have any problems. I'm happy to help you accomplish that.
Anne Miller, Brian S wrote:
Anne- Actually it is on another new server that I am setting up. If you want to take a look at it, it is nexraditr.iihr.uiowa.edu Use the same username and password you use for the other ldm server. Brian -----Original Message-----From: Anne Wilson [mailto:address@hidden] Sent: Thursday, February 03, 2005 11:55 AMTo: Miller, Brian S Subject: Re: New LDM server Hi Brian,Are you talking about ldm.iihr? If so, I just went to that machine and saw what would cause that problem.On your system the file that hupsyslog is looking for is /var/run/syslogd.pid. A short, easy fix to that problem is to create a sym link from /var/run/syslog.pid to /var/run/syslogd.pid. I just did that, and ran hupsyslog as user 'ldm' and it seemed to work fine.I will ask the LDM maintainer (STeve Emmerson) about your situation. I'm not sure why configure didn't figure out the right file name for that host - that may be a bug. So, I'll pursue that here, but in the mean time I think you're set to go.Anne Miller, Brian S wrote:Anne-I am setting up an new LDM server for Anton and I got an error when starting it that says:hupsyslog: couldn't open /var/run/syslog.pidI did a search, but couldn't find anything about that error. Do you have any ideas?Brian
-- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://my.unidata.ucar.edu/ ****************************************************