[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[LDM #XGQ-958194]: Re: [ldm-users] LDM 6.11.0 released
- Subject: [LDM #XGQ-958194]: Re: [ldm-users] LDM 6.11.0 released
- Date: Mon, 24 Sep 2012 17:00:38 -0600
Jeff,
> 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
May I log onto the main server as the LDM user?
> -Jeff Lake
> MichiganWxSystem.com
> AllisonHouse.com
> TheWeatherCenter.net
> GRLevelXStuff.com
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: XGQ-958194
Department: Support LDM
Priority: Normal
Status: Closed
