1

I’ve seen in the forums issues with the Network Monitor after upgrading in place but it has also been reported that an earlier version was supposed to address that problem.

I’ve recently upgraded to 1.3.136 and am now getting the blasted “Can’t connect to event service.” message…

Prior fixes look to be uninstall and re-install but this makes any upgrades undesirable.

1 Spice up
2

Hi,

Where you seeing that error message on the previous version as well? or did it start once you upgraded?

3

It started only after the upgrade. I am not certain which version I was at prior to the upgrade.

4

How often do you see that error message? Do the windows event logs show anything? What is the OS on the server you have the Network Monitor installed?

We have a few people reporting this and our devs are looking in to this. Hence the questions!

5

I am seeing it whenever I launch the Network Monitor and log in. It launches, displays devices configured and after a period of time trying to poll those devices it gives me that message, seems to time-out or something.

Running on a virtual Server 2012 R2 and I am not seeing anything in the Windows Event Logs during the time that it is launched and when the message appears.

6

How many devices are you monitoring? Also, do you see data stop coming in before you notice the event processor crashes? If you see the data stop, can you check how much RAM the event processor is running?

7

It is a relatively small environment. 6 servers, a firewall and a switch.

I am not able to get any data since the upgrade so since then I have not seen anything and have not gone through a process of uninstall/re-install since we have been going back and forth with this.

The Spiceworks Monitor Notifier looks to be sitting at less than 10 MB RAM for the last 5 min. though IE which only has that page open is around 225 MB. This is after restarting the SpiceworksEventProcessor service, which I had not done prior, and funny enough am getting data for two of my servers and the firewall.

8

Have you seen the error message pop up since you restarted that process?

9

No, the error message has not popped back up but I am still only seeing data for 2 servers and 1 firewall, out of the 8 devices that I have it set to watch.

10

Let me know if it pops up again. If it does, see if you can grab the memory usage at that time. Our devs are still working on this though!

11

What exact process are looking for the mem usage from?

12

We are looking at the SpiceworksEventProcessor. Our devs think it may be running out of memory and crashing…for some reason.

13

After restarting the server it is all coming up and reporting data once again for all of the devices. I can try and keep an eye on the processes and RAM usage and report back over the next bit what I am seeing.

14

RAM usage for the SpiceworksEventProcessor is sitting at ~250 MB RAM

15

Has it error-ed out at all since the restart?

16

Not as of this morning, I’ll keep an eye on it.

17

I should note, the RAM usage for the Spiceworks Event Processor is up from yesterday, although slightly, it is sitting at ~290 MB.

18

At some point during the night it crashed again, there is no information re: the amount of RAM it is/was using at the time, service is stopped.