Hi Jeff,
Glad that you were able to get everything working. Curious as to what you mean
by vtec warnings. I'm currently using GEMPAK gpwarn and GDPLOT3 to display
watches and warnings. Its unfortunate that many of the miscellaneous watches
and warnings can't be displayed such as frost and freeze advisories. Does the
php code you are using have the ability to decode and display all watches and
warnings? Always on the lookout for new ways to process and display the LDM
data.
Thanks,
Evan
Sent from my Verizon Wireless BlackBerry
-----Original Message-----
From: "Jeff Lake - Admin" <admin@xxxxxxxxxxxxxxxxxxxx>
Date: Sat, 23 Jan 2010 19:22:25
To: <ldm-users@xxxxxxxxxxxxxxxx>
Subject: Re: [ldm-users] centos 5.4
Update:
I wish to thank everyone who replied off list and on..
I *think* I have found the problem's, well so far so good..
1) I had a php decoder for each VTEC type Warning/Watch,
and for each non-VTEC type
I had implemented a single decoder for VTEC and for non-VTEC
on my other server and decided
to implement it on this one..
2) decided to trim back what this server had in the
'FILE' action to the data I actually needed/used
3) added '-close' to the PIPE actions for the GEMPAK
decoders, it wasn't in the GEMPAK pqact.gempak
but added to be safe
so far so good..fingers crossed
-Jeff
> >help...
>>all of a sudden one of my LDM installs is logging the following
>>/bin/sh: fork: Resource temporarily unavailable
>>I have spent the last 10hrs with Google trying everything I found
>>to raise LDM's max process's from 20
>>
>>anybody got any idea's???
>>
>>
>>
>> Jeff Lake
>> MichiganWxSystem.com
>> WeatherMichigan.net
>>
>>**********************************************************************
>
> Jeff...
>
> There may be too many processes already running on your system by "ldm" or
> all the users.
>
> You might monitor things with "top". It's possible there is code
> something
> like this:
>
> A: run something
> if error, goto A
>
> Code like this is an intense loop if there error always occurs, and is
> very
> hard go kill off, especially if "run something" spawns a new jobs. For
> scripts like this, I always put in a "sleep 2" to allow a human to get a
> hold of things.
>
> You can tell if you see the same names over and over with "top", but the
> process ID changes.
>
> If there doesn't seem to be very many, you might look around to see if
> your
> system has been hacked. Hackers will replace things like "ps" and "top"
> so
> you can't see what really is going on.
>
> You can always try a reboot and see if that fixes things.
>
> Kevin W. Thomas
> Center for Analysis and Prediction of Storms
> University of Oklahoma
> Norman, Oklahoma
> Email: kwthomas@xxxxxx
_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
