1

SW6 keeps reporting that a server is off line when its not. Any ideas?

7 Spice ups
2

I noticed this myself last night when SW told me that an entire bank of devices connected to one switch said it went offline. I know this is not true because that switch is my demarc point and if it was offline I would not have been able to get the message. Long story short you’re not the only one with the problem, I have been looking around SW to see if I can find anything but have come up empty handed also.

3

Can you ping the server that is showing offline from the spiceworks server without packet loss?

4

It pings fine.

5

There has been a couple discussions about this.

Does a new scan of the device change it’s status.

The info your looking at is current of the last scan that happened.

Here is a link on fixing inconsistency’s in SW

http://community.spiceworks.com/how_to/show/420

6

here is an example of this topic already posted http://community.spiceworks.com/topic/234256-some-vm-server-has-been-offline-for-longer-than-x-minutes

I know there were some from Beta 3 but it sounded like they were resolved.

1 Spice up
7

Just wanted to chime in that since installing the beta last night I see exactly the same thing. I can ping the devices fine from Spiceworks.

I have also tried removing the devices and rescanning as well as running a rescan without removing the device and same issue. This is happening on virtually all my inventory. When I remove the device and rescan it picks up all the data on the device, but just reports it as offline.

8

I have the same situation. I am running the latest Beta and it shows only certain servers offline but yet if I rescan them it does not change the status.

9

Just to clarify, there are no minor updates to a beta are there? In other words, there would not be a second version of Beta IV? Installing a fresh Beta IV after uninstalling Beta III AND NMAP fixed the offline problem for me.

10

I have the same issue with two devices

11

fwiw rescanning made no difference.

For one device, when I go to Tools - Ping - it pings just fine. But the other one it shows that it’s trying to ping the name “remote” which, technically, is the name of the VPN device. But we don’t have a DNS entry for it on our internal network - and when I edit the device I don’t see that name anywhere. The correct IP is associated with the device, and pinging that works just fine.

12

for the VPN device I used a SQLite editor and discovered the server_name was listed as “remote” instead of an IP address. I changed it, and now it at least pings. But even after kicking off another scan, it still shows “offline”.

13

One thing I can add with my situation is that this seems to affect devices on the local network, 192.168.1.xxx. Anything on a remote section of our network accessible by vpn at 192.168.30.xxx shows up fine. weird…

14

Are you guys still seeing issues with Spiceworks reporting devices online/offline status incorrectly with the RC build ?

15

James B (Spiceworks) wrote:

Are you guys still seeing issues with Spiceworks reporting devices online/offline status incorrectly with the RC build ?

James I responded on Friday to the other thread you sent out about this in RC 1 on friday.

http://community.spiceworks.com/topic/239118-online-offline-reporting-in-6-0-rc1

But when I go there today, my reply isn’t even there?

16

yes still having an issue with 1 server but i think its the windows firewall causing the issue.

17

James B (Spiceworks) wrote:

Are you guys still seeing issues with Spiceworks reporting devices online/offline status incorrectly with the RC build ?

I got false alerts immediately after upgrading. Some physical, some Hyper-V VMs. It was a couple hours after updating to RC. What’s weird to me is how the offline alerts show in the timeline. There’s an entry for “is offline” and one for “was offline”, but “was offline” is crossed out, signifying that’s no longer an issue? Wouldn’t the “is offline” be crossed out so you don’t look at it thinking it’s still ongoing?

Spiceworks_-Dashboard-_Mozilla_Firefox_2012-07-02_14-01-29.png

18

Thats what im getting

19

Thanks for reporting this guys. I have to ask the obvious question, does pinging the device come back with any lost packets? Also, are the devices reporting offline on a DHCP lease that may have expired, giving the device a new IP address?

One thing to keep in mind is that Spiceworks only updates IP addresses for devices after a network scan runs. If it has changed since the last network scan (Health Checks don’t pick this up) then Spiceworks will still look for it at the old IP.

20

I actually rolled back to ver 5 because of the problems with my devices. I had no lost packets when pinging however. A lot of the devices reporting offline were static ip’s as well.