Archived community.zenoss.org | full text search
Skip navigation
1 2 3 4 Previous Next 143216 Views 55 Replies Latest reply: Sep 12, 2013 11:01 AM by loatswil RSS
jsauve Rank: White Belt 49 posts since
Dec 28, 2007
Currently Being Moderated

Nov 16, 2008 1:28 AM

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

Hello all,

Since upgrading to 2.3 (stack installer on openSUSE 10.3), almost all of my Windows servers are getting the following error:

Could not read the status of Windows services (NT_STATUS_ACCESS_DENIED). Check your username/password settings and verify network connectivity.

I was NOT getting this with 2.2.4, so it's not a question of credentials!

I checked the zenwin log and it's full of the same messages:

2008-11-15 23:34:33 INFO zen.zenwin: Scanning PLASTIPAK-SQL
2008-11-15 23:34:33 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-15 23:34:33 ERROR zen.zenwin: NT_STATUS_ACCESS_DENIED
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenWin/zenwin.py", line 90, 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-15 23:34:33 ERROR zen.zenwin: NT_STATUS_ACCESS_DENIED
Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenWin/zenwin.py", line 124, in inner
driver.next()
File "/usr/local/zenoss/zenoss/Products/ZenUtils/Driver.py", line 64, in result
raise ex
WMIFailure: NT_STATUS_ACCESS_DENIED


...over and over again.

Any suggestions would be appreciated.

Thanks!

Jacques
  • mwcotton Rank: Brown Belt 563 posts since
    Apr 23, 2008
    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?
  • imptech4 Rank: White Belt 19 posts since
    Jul 13, 2008
    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)
  • russuhte Rank: Green Belt 131 posts since
    Jun 28, 2007
    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
  • eblush Newbie 3 posts since
    Nov 17, 2008
    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?
  • imptech4 Rank: White Belt 19 posts since
    Jul 13, 2008
    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?
  • mrjohnbravo Rank: White Belt 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.
  • zigga Newbie 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
  • zigga Newbie 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
  • tseward Rank: Green Belt 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
  • sapofeo Rank: White Belt 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).
  • russuhte Rank: Green Belt 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...
  • jason Rank: Green Belt 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
1 2 3 4 Previous Next

More Like This

  • Retrieving data ...