Xsan Admin[1444]: ERROR: Error reading san information: kOfflineError (0)

Andrew Allen's picture

I have a long and harrowing tale of constant Xsan problems. But I don't have the time to recite it here. 

I've got 3 MDCs that were on 10.9.1. Had lots of problems. Upgraded them last night to 10.9.2. Everything seemed ok. However, MDC3 has been churning out thousands of these errors: 

Mar  6 00:10:17 shareserver.local WindowServer[112]: _CGXHWCaptureWindowList: No capable active display found.
Mar  6 00:10:56 shareserver.local Xsan Admin[1444]: ERROR: Error reading san information: kOfflineError (0)
Mar  6 00:11:56 shareserver.local Xsan Admin[1444]: ERROR: Error reading san information: kOfflineError (0)
Mar  6 00:12:56 shareserver.local Xsan Admin[1444]: ERROR: Error reading san information: kOfflineError (0)
Mar  6 00:13:56 shareserver.local Xsan Admin[1444]: ERROR: Error reading san information: kOfflineError (0)
Mar  6 00:14:57 shareserver.local Xsan Admin[1444]: ERROR: Error reading san information: 

 

It repeats this over and over and over and over. It;s the host Machine for SAN3. SAN3 is visible and accessible no problems. This machine is also a SAN Share server using OS X Server to simply share our 3 SANS to specific windows machines on the network. 

The problem is now that all the windows machines can't access the SAN. THis doesn't seem like an Xsan problem, but more of an OS X server problem. However there are no errors from OS X server in the console but thousands of these, in the same format, with this random monitor error in the middle of it. 

The machine is an Xserve from 09 I believe. It's connected to a KVM at all times and I'm not sure why it would be giving this monitor error. 

 

Any thoughts? What does this error message mean. 

 

proton's picture

The error is harmless. It means that Xsan Admin GUI cannot access Xsan servers/clients, i.e. they are offline. Close all Xsan Admin windows and errors should be gone.

To solve this once and for all you must have your Xsan clients configured with static/reserved IP addresses. Additionally no virtual interfaces should be present on them, like for example Parallel virtual interfaces.

Andrew Allen's picture

Thanks for your reply. We resolved the Windows connectivity issue to the Shareserver. The problem is Apple's new SMB2 protocol, especially with older Windows machines. There's a few old EVS machines running WIndows XP that are used for encoding. The problem was that these old PCs have a setting on their Ethernet cards to turn off when the computer goes to sleep. Apple's SMB2 protocol doesn't function with this behavior well, so whenever the Windows machine would go to sleep, it would shut off it's ethernet card and it couldn't reconnect to the Apple ShareServer without a reboot. However, in the dialog box for the Ethernet card on the PCs, you can turn off this going to sleep feature. Once we did that, we haven't had any issue with the Windows machines not being able to access the ShareServer.

As for static IP addresses, to my knowledge all of the machines on the SAN are already configured with Static IP addresses. At least they should be; we have a spreadsheet with their dedicated IP addresses and whenever I've looked at the clients, I've confirmed that they are set to the proper static IP. However, I haven't specifically checked on EVERY machine to make sure this is the case. We might have an outlier that's set to DHCP--I know we found one set to DHCP a month ago and that was causing problems.