[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #ULR-248893]: AWIPS support

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.

  • Subject: [LDM #ULR-248893]: AWIPS support
  • Date: Mon, 07 Nov 2016 12:41:34 -0700
Kevin,

The problem is that AWIPS thinks it's the only user on whatever system it runs.

Our AWIPS expert had this to say:

"the problem may be that the /etc/profile.d/ files (awips2.sh and awips2.csh)
were sourced (by a non-root account) and the ldmadmin problem is a result of a
python mismatch. 

My suggestion is to copy the attached file to overwrite the existing
/etc/profile.d/awips2.sh, the log out/log in as user ldm again and see if
ldmadmin runs as expected."

> Im having trouble running my ldm system after installing awips cave
> client. This is the output:
> 
> 20161104T201410.601242Z regutil[5357] ERROR backend.c:159:fileLock() No
> such file or directory
> 20161104T201410.601361Z regutil[5357] ERROR backend.c:159:fileLock()
> Couldn't open file "/awips2/ldm/etc/registry.xml" for reading
> 20161104T201410.601365Z regutil[5357] ERROR registry.c:545:sync()
> Couldn't synchronize node "/"
> 20161104T201410.601367Z regutil[5357] ERROR registry.c:858:getValue()
> Couldn't get value of key "/server/config-path"
> 20161104T201410.601370Z regutil[5357] ERROR regutil.c:177:printPath()
> Log messages flushed
> Couldn't get "/server/config-path" at /usr/local/ldm/bin/ldmadmin line
> 97.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ULR-248893
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.