Jeff,
No. You probably didn't miss anything. It's likely there's something
about your system that the new database doesn't like.
I'll drive this into the support-email system so that others can benefit.
In the meantime, think about whether or not you can let me on the system
in question as the LDM user.
Talk to you soon.
--Steve
On 09/24/2012 03:35 PM, Jeff Lake wrote:
> did I miss something??
>
> I installed it with no problems on my main server,
> when I installed it on my secondary servers,
> I had to restart LDM on the main to get data flowing
>
> here is what was in the logs of the main server
>
> Sep 24 21:30:02 ldm 10.225.60.229[5762] ERROR: [semRWLock.c:430]
> Couldn't lock for writing: semId=885227533
> Sep 24 21:30:02 ldm 10.225.60.229[5763] ERROR: [semRWLock.c:430]
> Couldn't lock for writing: semId=885227533
> Sep 24 21:30:02 ldm 10.225.60.229[5764] ERROR: [semRWLock.c:430]
> Couldn't lock for writing: semId=885227533
> Sep 24 21:30:02 ldm 10.225.60.229[5765] ERROR: [semRWLock.c:430]
> Couldn't lock for writing: semId=885227533
> Sep 24 21:30:02 ldm 10.225.60.229[5766] ERROR: [semRWLock.c:430]
> Couldn't lock for writing: semId=885227533
> Sep 24 21:30:02 ldm 10.225.60.229[5767] ERROR: [semRWLock.c:430]
> Couldn't lock for writing: semId=885227533
> Sep 24 21:30:04 ldm 10.225.60.229[5762] ERROR: [uldb.c:1367] Couldn't
> lock database for writing
> Sep 24 21:30:04 ldm 10.225.60.229[5763] ERROR: [uldb.c:1367] Couldn't
> lock database for writing
> Sep 24 21:30:04 ldm 10.225.60.229[5764] ERROR: [uldb.c:1367] Couldn't
> lock database for writing
> Sep 24 21:30:04 ldm 10.225.60.229[5765] ERROR: [uldb.c:1367] Couldn't
> lock database for writing
> Sep 24 21:30:04 ldm 10.225.60.229[5766] ERROR: [uldb.c:1367] Couldn't
> lock database for writing
> Sep 24 21:30:04 ldm 10.225.60.229[5767] ERROR: [uldb.c:1367] Couldn't
> lock database for writing
> Sep 24 21:30:04 ldm ldmd[2555] NOTE: child 5784 exited with status 2
> Sep 24 21:30:04 ldm 10.225.60.229[5762] ERROR: [uldb.c:1766] Couldn't
> lock database
> Sep 24 21:30:04 ldm 10.225.60.229[5763] ERROR: [uldb.c:1766] Couldn't
> lock database
> Sep 24 21:30:04 ldm 10.225.60.229[5764] ERROR: [uldb.c:1766] Couldn't
> lock database
> Sep 24 21:30:04 ldm 10.225.60.229[5765] ERROR: [uldb.c:1766] Couldn't
> lock database
> Sep 24 21:30:04 ldm 10.225.60.229[5766] ERROR: [uldb.c:1766] Couldn't
> lock database
> Sep 24 21:30:04 ldm 10.225.60.229[5767] ERROR: [uldb.c:1766] Couldn't
> lock database
> Sep 24 21:30:04 ldm 10.225.60.229[5762] ERROR: [ldm6_server.c:353]
> Problem with new upstream LDM process
> Sep 24 21:30:04 ldm 10.225.60.229[5763] ERROR: [ldm6_server.c:353]
> Problem with new upstream LDM process
> Sep 24 21:30:04 ldm 10.225.60.229[5764] ERROR: [ldm6_server.c:353]
> Problem with new upstream LDM process
> Sep 24 21:30:04 ldm 10.225.60.229[5765] ERROR: [ldm6_server.c:353]
> Problem with new upstream LDM process
> Sep 24 21:30:04 ldm 10.225.60.229[5766] ERROR: [ldm6_server.c:353]
> Problem with new upstream LDM process
> Sep 24 21:30:04 ldm 10.225.60.229[5767] ERROR: [ldm6_server.c:353]
> Problem with new upstream LDM process
>
> -Jeff Lake
> MichiganWxSystem.com
> AllisonHouse.com
> TheWeatherCenter.net
> GRLevelXStuff.com
>
> On 9/24/2012 13:25, Steve Emmerson wrote:
>> Hi,
>>
>> Version 6.11.0 of the LDM package has just been released.
>>
>> The main new feature of this minor release is the addition of a
>> transitory database of information on local upstream LDM processes. The
>> database is transitory because it only exists while an LDM server is
>> running. The database is primarily used to determine whether or not an
>> incoming data-request duplicates or otherwise overlaps with an existing
>> data-request from the same downstream host. If it does, then the request
>> will be rejected.
>>
>> The motivation for this new feature is to prevent an accidental or
>> deliberate denial-of-service (DOS) attack on an LDM server (believe it
>> or not, an accidental DOS attack did occur at the Unidata Program Center
>> -- causing some legitimate downstream sites to be denied data).
>>
>> This release has a new utility, uldbutil(1), for listing the contents of
>> the database. The LDM user can use this utility to easily determine what
>> data they're getting from which upstream LDM-s. Naturally, this utility
>> has a manual-page.
>>
>> No similar database exists for downstream LDM processes because there is
>> a one-to-one correspondence between such processes and the REQUEST
>> entries in the LDM configuration-file, etc/ldmd.conf. If you want to
>> know about locally-executing upstream LDM processes, then just grep(1)
>> the LDM configuration-file (e.g., "grep -i ^request
>> $HOME/etc/ldmd.conf").
>>
>> Version 6.11.0 can be downloaded at
>> <http://www.unidata.ucar.edu/downloads/ldm/>.
>>
>> This version's homepage is
>> <http://www.unidata.ucar.edu/software/ldm/ldm-6.11.0/index.html>.
>>
>> Regards,
>> Steve Emmerson
>> LDM Developer
>>
>> _______________________________________________
>> ldm-users mailing list
>> ldm-users@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> http://www.unidata.ucar.edu/mailing_lists/
>>
>
> _______________________________________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
