Anonymous_User Absent Member.
Absent Member.
372 views

LM 1.2 - Issues with LM 1.2 Can not login


Hi,

Long shot here. Our LM decdied to memory dump some time back (it is not
yet in support, from our companies perspective, so I have the unenviable
task of looking after it whilst working on other projects!)

Even though it said all services were running
(/etc/init.d/sentinel_log_manager status) it did not appear to be
getting events. If I tried to Login to the LM GUI it would tell ne
username and password were wrong which I knew was correct. So I rebooted
the thing and I could then log in with the credentials i used earlier
when it told me to go away. I then saw a hideous increase in EPS (3k
plus licensed for 2.5k) as no doubt it was getting the data from the
cache of the collector managers. I would say it is a medium sized estate
5 windows (grrr) CM's two 4 installed locally in ISA servers and approx
350-375 event sources of various types.

After approx 10 minutes the GUI would stop respponding i.e. graph wouls
top moving, I would exit try to log in again and I was back to same
issue sohad to reboot again, this has been going on for hours (9am until
4pm rebooting the thing, still no good).

I tried stopping the Windows CM, but I guess the data is coming from
the cache so, didn't make any difference.

I have checked server.*.log and tomcat.*.log etc and can see no
OutOfMemory errors.

Anyone have any ideas how I can kick this thing back into life. I hope
version 7 is better, had a lot of hassle with this version.

Cheers,

George


--
gfont96
------------------------------------------------------------------------
gfont96's Profile: http://forums.novell.com/member.php?userid=109878
View this thread: http://forums.novell.com/showthread.php?t=452035

0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: LM 1.2 - Issues with LM 1.2 Can not login

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Do you see anything in the logs that would indicate low memory (not out
of memory, just low) which could impact things? If you stop a CM
somewhere then that CM will no longer send data and I do not believe any
caching other than the CM's cache (which would now be stopped) would
cause issues like you are seeing. If you are low on memory somewhere
then that could cause random issues I suppose, but even that's a long
shot. Does the main Log manager machine collect events directly or does
it only receive events from external CMs? If it receives events
directly you may want to see if those event sources are the ones causing
issues. If you have an old memory dump posting that somewhere or
sending it to Novell/NetIQ vi a Service Request (SR) could help isolate
potential issues.

Finally, Log Manager 1.2.0.2 is out; if you have not patched, please do
so as several performance benefits are included. Be sure to patch all
systems... CMs, clients, not only the main server.

One benefit of Sentinel 7 is the removal of windows-based CMs;
everything can now be done (correctly) from Linux servers. For
windows-based event collection there is a small agent that runs on
windows still, but it no longer requires the entire CM to reside there
so it's much lighter and has been better overall from a customer and
support standpoint.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPNTuwAAoJEF+XTK08PnB5u/8P/jlu5U+fYO5uXCO3vIIq44Fx
TGKI+uuJ15viFZ//RHK22TUmnXztN2pRww01y33KiflKE/sJ8z3Oy2VFmo35JflJ
TOK7OFBkDp9pH/4WnpJr/iGe0E0ao/ayyB1Iefz3CwN7q6ebocm6ERkzt1nTcvjF
o8IA55OLmWdFwidGzdDAYLGB/5jhaSkj9uCeNFowZDkUlPF1hKWh1MuWgzIUGn3F
hstbG1ieMZn/E4tKZUa7q0r8c19pzUIQLLKqIkKL4XhnB5F02FFKY1tefr/zobHD
tSi964w+FLvlHbYNdtq/+/OZlP/YvlMxhJaRqA74T0MDGBmV0g0SAdPOCbWO1weA
fRBGlUX1dBZJ1tyPZ4S0p7/GmMrJdRviS0rHcg1qcUi1CYsOAQVSMQZiJQ3b/P8e
sRfyyC22R22x2gtwIMhPYGW0IjU4pJrH2sw0q9VrDSh0UNjy22z8THZPpl6qkuG2
uiLgNFtuSUHAIYO18g5gmuigbjn8j4jY2cQ3aTKlz0kskxVZJYoPzJzOjFVH8JXB
HSMpXL1i8ALhmvcbapsGOFdaoj2N6YG43zJfQ3PTr7AfNjPlsKWhOpyNCA9CaMLt
dMa/SX42wyPCNgJyTQS/aHdXDyCR6PaeDLZ7lppg2LGSUdJD2IMqamSiA3BfONN/
xs8t7Rz8wXJXgPSZqojr
=uf3i
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LM 1.2 - Issues with LM 1.2 Can not login


Hi ab,

Thanks for that. Can't see anything in relation to low memory the LM
only has 8 gig RAM. I logged a call with support, since then I found
that the RD box is down, well the sentinel service is not running. I can
see loads of entries saying failed to forward events
(SentinelLinkStoreAndForward) on the server0.0..log (LM) so I am
thinking it must be trying so often that it is unable to do anything
else.

So along with support, we think the following might be the best course
of action;

1) Stop LM (it is a VM and take the memory to 24gig)
2) Stop all the CM's
3) Stop all the event sources in ESM
4) Start the RD
5) Start the LM
6) Wait for cache to clear from LM to RD
7) Start the CM's, wait for cache to clear (approx 5 gig on each CM)
😎 Start Event Sources one by one in ESM
9) Hope it all works
10) Buy large amounts of beer

Sound like a plan ?

Thanks,

George


--
gfont96
------------------------------------------------------------------------
gfont96's Profile: http://forums.novell.com/member.php?userid=109878
View this thread: http://forums.novell.com/showthread.php?t=452035

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LM 1.2 - Issues with LM 1.2 Can not login

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mostly, sure. I am not sure how much success you'll have stopping event
sources after stopping CMs, so maybe flip those two in order, but
otherwise most of it could have the desired results.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPORysAAoJEF+XTK08PnB5FyAQAID5fdwmOjS4LJb3nFa+iUYZ
wXEG1ufH2zD3KjTXE3Y8wAmDm7mFLeebx5WQcQwhWdCCJ4r05ILYQGnUZ66tlR8b
iJpIm0eEMIYcgtqe+8+HfUE4OHepCgEDO2ibzB7F3vx8ohRZLggnW47himwnX9/D
p5z6Er1AmH4yRXDCx2Z5opXaPg5fErWGKz7ZCnDE2pCki5IGVzhqzPA8LVsn1DRe
Kn+sywdwppzhVhHjBvAUtO6Rf10UZUpWgQ2UEz8KCXsriytYh/Kz1S+eVdnhEmhr
OfQLkpncE5v7R37ngmOk15RgmE4OGxSA5RX8quJF8w1ULZCcin6npnQ87pldeSHx
2tNDDhTMel9eZnKppOaKlEl82rhjd0EbscfPnqdJ8IFax7CKl/gXfmUiX2L9PU4v
nA1XOowsd/E/Yx9V7VUJni8NfR3YfIAqea/D7sgbwle1z3aOFxTGIQVNKDZavSRT
O2m8QD2Zwh+qiHVvLOgoNVSddSlokr1BHsNxyyR0g1GNVRCpuB/yzIu0j9norrgP
DL98WUmCFE7lXLcQZBF6y86cfu1xSFuKv+buaSkR7rv/XPZP7cmlBwf2btlvlXvU
V2vpSM6GK5RVqlk3thbtCDkSC//NtV1Ww0/nKTkt+ArCxXnXDJjA6DWTazcsSq3Y
Z5lPk3B4e/9c7W1RHlzO
=pVvj
-----END PGP SIGNATURE-----
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.