Could not read the status of Windows services...since 2.3

mwcotton

563 posts since
Apr 23, 2008

Currently Being Moderated

1. Nov 16, 2008 6:55 PM (in response to jsauve)

RE: Could not read the status of Windows services...since 2.3

Well did you check the nt login and password?

Can you query the windows system using the login and password using the command line tools?

Report Abuse
Like (0)

imptech4

19 posts since
Jul 13, 2008

Currently Being Moderated

2. Nov 16, 2008 8:05 PM (in response to mwcotton)

RE: Could not read the status of Windows services...since 2.3

Confirmed behavior in the upgrade I've just done from 2.2.4 to 2.3.0. Still investigating what exactly broke.. (Ubuntu stack deb package)

Report Abuse
Like (0)

jsauve

49 posts since
Dec 28, 2007

Currently Being Moderated

3. Nov 16, 2008 9:09 PM (in response to imptech4)

RE: Could not read the status of Windows services...since 2.3

Well....why EXACTLY would all the credentials of my Windows servers change after the upgrade ???

The user accounts have not changed.

"mwcotton" wrote:

Well did you check the nt login and password?

Can you query the windows system using the login and password using the command line tools?

Report Abuse
Like (0)

russuhte

131 posts since
Jun 28, 2007

Currently Being Moderated

4. Nov 17, 2008 11:59 AM (in response to jsauve)

RE: Could not read the status of Windows services...since 2.3

I have yet to take the plunge from 2.2.3 to 2.3, but I suspect that maybe something in the migration sequence has corrupted the zwinuser and/or the zwinpassword. Have you tried to re-enter that data for just one server and see if it makes a difference??

-Russ

Report Abuse
Like (0)

eblush

3 posts since
Nov 17, 2008

Currently Being Moderated

5. Nov 17, 2008 3:41 PM (in response to russuhte)

RE: Could not read the status of Windows services...since 2.3

just to further the conversation, in testing zenoss 2.3 with the vmware application on Windows today i found that I received this error for all my windows boxes as well. I made sure to set the correct username and password beforehand. i tried this once before on an ubuntu 8.04 server with zenoss 2.2.3 and did not receive and of these. any ideas?

Report Abuse
Like (0)

jsauve

49 posts since
Dec 28, 2007

Currently Being Moderated

6. Nov 18, 2008 7:07 PM (in response to eblush)

RE: Could not read the status of Windows services...since 2.3

Tried that; didn't work.

"russuhte" wrote:

I have yet to take the plunge from 2.2.3 to 2.3, but I suspect that maybe something in the migration sequence has corrupted the zwinuser and/or the zwinpassword. Have you tried to re-enter that data for just one server and see if it makes a difference??

-Russ

Report Abuse
Like (0)

imptech4

19 posts since
Jul 13, 2008

Currently Being Moderated

7. Nov 23, 2008 7:20 PM (in response to jsauve)

RE: Could not read the status of Windows services...since 2.3

Any more news on a possible fix for this?

Why would the data be pulled correctly at 2.2.4 and fail at 2.3 with the same username/pass sequence?

Report Abuse
Like (0)

mrjohnbravo

13 posts since
Nov 24, 2008

Currently Being Moderated

8. Nov 24, 2008 5:15 PM (in response to imptech4)

Another user same issue

I am seeing the same issue as stated above.

Is there a bug listing for it yet?

No changes in username and passwords on client side. Only change was zenoss 2.2.4 to 2.3

Mr John Bravo

Ps. I am getting the same traceback as well.

Report Abuse
Like (0)

zigga

5 posts since
Oct 22, 2008

Currently Being Moderated

9. Nov 28, 2008 6:38 AM (in response to mrjohnbravo)

Exact same problem

I just upgraded from 2.2.4 to 2.3 yesterday and i'm getting the exact same problem.

Could somebody from zenoss dev please look into this, i'm considering rolling back to 2.24 if this is not resolved soon.

Log from zenwin -

WMIFailure: NT_STATUS_CONNECTION_REFUSED
2008-11-28 11:38:37 ERROR zen.zenwin: NT_STATUS_CONNECTION_REFUSED
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenWin/zenwin.py", line 127, in inner
driver.next()
File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result
raise ex
WMIFailure: NT_STATUS_CONNECTION_REFUSED
2008-11-28 11:38:37 WARNING zen.zenwin: Closing watcher of ARUK-BHX-S005
2008-11-28 11:38:38 ERROR p.w.Query: NT_STATUS_ACCESS_DENIED
Traceback (most recent call last):
File "/usr/local/zenoss/python/lib/pysamba/wbem/Query.py", line 167, in inner
yield deferred(ctx); driver.next()
File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result
raise ex
WMIFailure: NT_STATUS_ACCESS_DENIED
2008-11-28 11:38:38 ERROR zen.Watcher: NT_STATUS_ACCESS_DENIED
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenWin/Watcher.py", line 39, in inner
driver.next()
File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result
raise ex
WMIFailure: NT_STATUS_ACCESS_DENIED
2008-11-28 11:38:38 ERROR zen.zenwin: NT_STATUS_ACCESS_DENIED
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenWin/zenwin.py", line 127, in inner
driver.next()
File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result
raise ex
WMIFailure: NT_STATUS_ACCESS_DENIED
2008-11-28 11:38:38 WARNING zen.zenwin: Closing watcher of lhrapp134.alpha-group.com
2008-11-28 11:38:38 ERROR watchdog: Child died: Killed with signal 11

Report Abuse
Like (0)

zigga

5 posts since
Oct 22, 2008

Currently Being Moderated

10. Nov 28, 2008 6:50 AM (in response to zigga)

Exact same problem

What I do find odd is if I manually run

zenwin run -d -v10 'servername'

it updates the wmi correctly for that device and the change is seen in zenoss

Report Abuse
Like (0)

tseward

233 posts since
May 5, 2007

Currently Being Moderated

11. Dec 1, 2008 2:56 PM (in response to zigga)

RE: Exact same problem

The command should be zenwin run --debug -v 10 -d device.name

Report Abuse
Like (0)

sapofeo

31 posts since
Feb 16, 2008

Currently Being Moderated

12. Dec 2, 2008 8:43 AM (in response to tseward)

RE: Exact same problem

I'm receiving this error as well. The failures occur for Windows Services and Windows Event Log (the WMI based monitors). Occassionally, a reboot of the effected servers clears the error but never for very long. It does not effect every server I'm monitoring but generally a dozen or so will fail all at the same time. This rules out bad credentials (as most servers still work) or a misconfiguration on the server side (since multiple servers fail simultaneously).

Report Abuse
Like (0)

russuhte

131 posts since
Jun 28, 2007

Currently Being Moderated

13. Dec 2, 2008 11:35 AM (in response to sapofeo)

RE: Exact same problem

I'm not running 2.3 yet, but has anyone experiencing this problem had an opportunity to catch it via wireshark or tcpdump?? I think it may be helpful to look at the protocol data...

Report Abuse
Like (0)

jason

184 posts since
Feb 7, 2007

Currently Being Moderated

14. Dec 4, 2008 9:58 AM (in response to russuhte)

RE: Exact same problem

A few questions for those of you experiencing this problem:

1. Does this problem always occur with the same servers or does it seem to affect all your windows servers?

2. Do the servers affected by this consistently show this error or is it intermittent?

3. What versions of Windows have you seen this error with?

4. Can you run wmic from the command line against a server that is giving this error? The output is long, no need to post it, I'm just interested to hear if it successfully connects. A typical wmic command looks something like:

$ wmic -U <user>%<password> //<server> "select * from Win32_ComputerSystem"

Sapofeo - I know you already answered a couple of these questions. I'm interested to hear if others are seeing the same pattern as you. Could you try wmic from command line as well?

Thanks
-jason

Report Abuse
Like (0)

Nov 16, 2008 1:28 AM

Actions

More Like This