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

[AWIPS #NTZ-805469]: Data Disk Completely full!

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: [AWIPS #NTZ-805469]: Data Disk Completely full!
  • Date: Mon, 26 Oct 2015 12:37:20 -0600
> Good news. Sorry, but I didn't run the LDM scour on Friday and decided
> to try that today. That reclaimed a LOT of the free space. 

This is good to hear.  I am working on having cron set up on RPM install 
automatically.



> Before I started the EDEX server I thought I'd apply the outstanding
> updates. I had an dependency error -- see attached console log.
> I removed the _x64 version,  which unfortunately took some packages
> with it and installed the i686 version. The remainder of the updates went
> in OK.

The errors I see:

---> Package wxGTK.x86_64 0:2.8.12-1.el6.centos will be an update
--> Processing Dependency: wxBase = 2.8.12-1.el6.centos for package: 
wxGTK-2.8.12-1.el6.centos.x86_64
--> Finished Dependency Resolution
Error: Package: wxGTK-2.8.12-1.el6.centos.x86_64 (awips2repo)
           Requires: wxBase = 2.8.12-1.el6.centos
           Installed: wxBase-2.8.12-1.el6.x86_64 (@epel)
               wxBase = 2.8.12-1.el6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
...


are from leftover wxGTK packages which can be uninstalled:

yun remove wxGTK -y

and then 

yum update

should resolve this.




> Then when I ran the "edex setup" I saw:
> 
> [root@flurry data_store]# edex setup
> 
> 
> [edex] EDEX IP and Hostname Setup
> 
> [Error] ** /awips2/ldm/etc/ldmd.conf not found.
...
> 
> edex_ldm: unrecognized service
> 
> 
> I can start LDM manually, but I'm not sure it's the best thing
> to do.


Notice the location of this message is "/awips2/ldm", and the service called 
"edex_ldm" which is not found.  You are seeing these because of the updates 
made to the "edex" service wrapper, and these messages are save to ignore.

I am moving the LDM over to that directory on a soon-to-be-released EDEX 
update.   You do not have the LDM installed in this directory which is OKAY.  
You should start/stop the LDM manually through the LDM account (su ldm -c 
"ldmadmin start/stop").    When I get this update out, the ldm will start and 
stop from the "edex start/stop" command. 


It sounds like with LDM scour enabled in the cron and free space on your disk 
you are ready to roll.  



Ticket Details
===================
Ticket ID: NTZ-805469
Department: Support AWIPS
Priority: High
Status: Open