1

Good day everyone,

Anyone else using SpiceWorks Network Monitor tool?

Not sure if this is the right place to post this (if not please direct me). I understand it is still under development (beta) and just wanted to share my observations so far. I’ve been using this at my jos (tech support) and I find it really helpful. It monitors our servers, sends alerts in case it has low disk space, high memory usage, and many other options.

The first thing I want to point out is the memory usage it takes to run the app. It consumes a LOT of it!
(about 1.5 of RAM)

spice.PNG
spice.PNG800×76 38.9 KB

I also had some trouble adding servers to my server list. I am unable to add a few servers and I keep getting an error sating username/password incorrect when in fact it is the correct one (same user/password for all servers). Or, I would get an error saying it couldn’t connect to the server.

Those are the two main factors that I believe needs some work done. Please feel free to respond with any comments or questions.

Thanks in advance!

Cheers!

@Spiceworks

3 Spice ups
2

This may seem like an idiot question but I will ask it. Are the servers that you can not add, part of your domain where the others are not ? So that you have to login using domain credentials like MICROSOFT\gatesbill and yourpassword ?

And to your other question I did notice the very high horse power requirements. Or maybe it scales ? Meaning if you have more, it will take more ? I have mine on an 4 core VM with 8 gig of ram. Added note, this VM also does my normal Spiceworks too.

3

Hi garyfarm, thanks for your reply.

My mistake for not specifying the type of network we’re in. There is no domain controller (unfortunately). And all the servers are on the same network that we’re in as well.

Your theory makes much sense. It could be that the more devices I monitor the more resources it needs. I will remove about half of the servers and see if there’s any difference.

Will keep updating as I work on this.

Thanks again.

@garyfarm

4

I was going to get you the below info yesterday but I got sidetracked. I also had to remove 2 or 3 servers that were not “as important” as other from monitoring because my VM was spiking during the day to near 100% Memory and pretty high on CPU too. In Spicework’s defense, this is still all “a work in progress” and I think the fine-tuning will come later as well as bug fixes and memory leaks and memory usage tuning along with a million other adjustments and maybe some “granular” fine tuning by the user. I’m sure the “Dashboard” a year from now will be unrecognizable to what it is now. Meaning it will have a ton more stuff. Thank you Spiceworks Network Monitor Team !

SpiceworksEventProcessor 2200 MB

SpiceworksAppServer.exe 871 MB

mxdomainmgr.exe 627 MB

spiceworks.exe 615 MB

sqlservr.exe 267 MB

spiceworks-httpd.exe 33 MB

5

Hi all,

We just posted RC2 to fix some memory leak issues that were leading to huge Event Processor memory utilization. Please uninstall RC1 and install RC2 to make sure it resolves your issue. You will see it potentially grow to 1.2GB, but I have yet to see it get bigger than that. We are continuing to monitor the issue (pun intended!)

As for the problems adding servers–are these same servers properly inventoried in Spiceworks Inventory (I see you are running that)? Or are they showing up as unknown devices? There’s a fair amount of documentation in Help at http://community.spiceworks.com/help/Resolving_Unknown_Devices to help you with fixing WMI issues.

Also, you can try running wmic at the command line of your Spiceworks server specifying the /node:“hostname” of your server to be monitored and the /user:username for the login name to use. Most common problems I run into are Firewall issues and the LocalAccountTokenFilterPolicy setting in the Windows registry.

Let us know if you install RC2 and continue to have problems! Thanks for trying the beta!

-David

6

The guy with the problem that started this thread did not say he was running spiceworks.exe. That was I that posted last what my install was using for memory and I was running both on the same VM instance.

7

Ah. Thanks for the clarification. I was skimming pretty fast there.

Hopefully CompWiz will use the help documentation to fix those WMI issues.

8

I will post this in a NEW message for SW RC2 but I wanted to post here also since this is where I first posted about the high memory usage on the SW RC1. Lot lower than what I posted above yesterday. The RC2 has the same servers in it and 3 or 4 more switches. CPU usage is rock bottom right now, but I won’t know how that goes until mid-day Monday.

SpiceworksEventProcessor 524 MB

SpiceworksAppServer.exe 594 MB

mxdomainmgr.exe 1200 MB This is a lot higher but I just restarted the VM and it is still polling.

spiceworks.exe 229 MB

sqlservr.exe 141 MB

spiceworks-httpd.exe 22 MB