Memory leak with Command line monitoring type

	Forums Register Login My Profile Inbox Address Book My Subscription My Forums Member List Search FAQ Ticket List Log Out

Memory leak with Command line monitoring type

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [Networking & Security] >> GFI Network Server Monitor >> Memory leak with Command line monitoring type

Page: [1]

Message

<< Older Topic Newer Topic >>

Memory leak with Command line monitoring type - 10.Oct.2005 6:22:00 AM

aboros

Posts: 2
Joined: 9.Oct.2005
Status: offline

Hi,

Week ago we installed NSM. Version: 6.0 Build: 20050721. Trial License.

Next to several standard "monitors" we added 2 custom:

1) Performance object: Processor, % processor time, _Total >10
All other options are inherited

2) Command line: C:\WINDOWS\system32\find.exe,
Params: "ERR:" \\server\d$\logs\*.log
Does not contain: ERR:
Frequency: every 1 minute
Threshold: 1
All other options are inherited

Memory usage drasticaly dropped in this one week.
I must make a notice that before we installed NSM this server NEVER had memory issues!

As you can see on MRTG graph memory drops after NSM install (green->real memory, blue->virtual memory)

Any idea?

Post #: 1

RE: Memory leak with Command line monitoring type - 18.Oct.2005 9:23:00 PM

Patrizia

Posts: 8474
Joined: 18.Aug.2003
From: Malta
Status: offline

Hi,

We are checking out this issue.

(in reply to aboros)

Post #: 2

RE: Memory leak with Command line monitoring type - 19.Oct.2005 3:22:00 AM

Calin Ghibu

Posts: 1194
Joined: 15.Dec.2002
Status: offline

Hi,

Tests here revealed a rise in memory but only a certain amount, after which memory did not rise anymore. So the memory leak was not confirmed.

You can know if the leak is specific to NSM by monitoring specifically the private bytes and virtual bytes of the NSM services, which are NSMEngine6.exe and NSMAttendant6.exe.

Best regards,
Calin

(in reply to aboros)

Post #: 3

RE: Memory leak with Command line monitoring type - 20.Oct.2005 1:50:00 AM

mstefa

Posts: 8
Joined: 26.Dec.2004
Status: offline

Hi, I also have the same issue.
As suggested I'm monitoring private bytes for service NSMEngine6.exe. Every time the command line check is executed, the graph shows a rise in memory of about 512KByte.
Disabling the check the graph is almost flat.
The check runs 3 psservice to monitor services on an old WinNT / MSExchange 5.5.
Thank you

(in reply to aboros)

Post #: 4

RE: Memory leak with Command line monitoring type - 20.Oct.2005 2:12:00 AM

Calin Ghibu

Posts: 1194
Joined: 15.Dec.2002
Status: offline

Hi Stefa,

Can you please post the buildnumber and also the setup you have there? (what OS is NSM installed on, number of checks using the command line file etc)

Best regards,
Calin

(in reply to aboros)

Post #: 5

RE: Memory leak with Command line monitoring type - 20.Oct.2005 9:38:00 PM

mstefa

Posts: 8
Joined: 26.Dec.2004
Status: offline

We have NSM ver6.0, build 20050721, the OS is Win2000 Pro SP4, the pc is a P4 2.7GHz with 512MB Ram and the total checks configured are about 90.

The only command line checks are the two tested yesterday (now disabled). Few weeks ago we tried other 3 command line checks to test some applications on a unix box but we had to disable them for the same problem.

Thank you

(in reply to aboros)

Post #: 6

RE: Memory leak with Command line monitoring type - 20.Oct.2005 10:00:00 PM

aboros

Posts: 2
Joined: 9.Oct.2005
Status: offline

Stefa,

I fully agree with you. We decided to uninstall the product because after 16h NSMEngine6.exe consumes about 250MB "private bytes" and it keep going...
Hope GFI can fix this problem because at this moment product is unreliable and not worth 450Euro [Frown]

(together with all other problems we saw in this message board).
When this happen we will (maybe) evaluate the product again.

Good luck!

(in reply to aboros)

Post #: 7

RE: Memory leak with Command line monitoring type - 21.Oct.2005 1:15:00 AM

Calin Ghibu

Posts: 1194
Joined: 15.Dec.2002
Status: offline

Hi Stefa,

There is an issue regarding ssh checks causing the NSM Engine service to leak memory.
Can you please retry to use comand line actions for non ssh checks ? Please disable the ssh checks, restart the NSM Engine service, set the command line to be run by non ssh checks, and see if the memory leak exists.

Thanks and regards,
Calin

(in reply to aboros)

Post #: 8

RE: Memory leak with Command line monitoring type - 21.Oct.2005 2:18:00 AM

mstefa

Posts: 8
Joined: 26.Dec.2004
Status: offline

Hi,
ssh checks were disabled when I did the tests last day; we disabled them weeks ago as soon as we dicovered the memory leak.
Moreover, the checks we did for the unix box were normal command line checks.
At the moment, with all command line checks disabled, there is no memory leaks. As soon as I enable one of the 2 c.l. checks, it starts consuming about 200KB at every execution og a c.l. check (~2MB at hte first execution).
I tried also rebooting the pc.

(in reply to aboros)

Post #: 9

RE: Memory leak with Command line monitoring type - 21.Oct.2005 3:12:00 AM

Calin Ghibu

Posts: 1194
Joined: 15.Dec.2002
Status: offline

Hi,

Can you please state what executable are you running?

Best regards,
Calin

[ October 21, 2005, 09:29 AM: Message edited by: Calin Ghibu ]

(in reply to aboros)

Post #: 10

RE: Memory leak with Command line monitoring type - 21.Oct.2005 4:10:00 AM

mstefa

Posts: 8
Joined: 26.Dec.2004
Status: offline

In these last checks we run the psexec.exe from Sysinternals.
The batch has 4 line like this:

c:\psservice \\servername query MSExchangeDS

The batch we made for unix uses the rsh.exe:

c:\winnt\system32\rsh.exe 1.2.3.4 -l usr /cals/bin/user/test.sh

(in reply to aboros)

Post #: 11

RE: Memory leak with Command line monitoring type - 21.Oct.2005 7:02:00 AM

mstefa

Posts: 8
Joined: 26.Dec.2004
Status: offline

>In these last checks we run the psexec.exe from Sysinternals

Sorry, obviously it is psservice.exe

Regards

(in reply to aboros)

Post #: 12