Shazzam probe stopped working

[edavis1]

Hello folks. Our Shazzam probe has stopped working and I cannot figure out why. Everytime the Shazzam probe runs it reports "No results found from probe", whether I run a quick discovery or test it against a server. This was working previously and I don't know of any changes in our environment that would affect the behavior. I can successfully ping and telnet to the servers from the midserver, but when I execute a discovery or test of the Shazzam probe I always get no results. Can anybody help by providing some possible reasons for this? I am stuck. Thanks, in advance.

The following log entries are from a test of the Shazzam probe.

11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 Worker starting: Shazzam source: 10.27.48.78
11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 DEBUG: probe()
11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 DEBUG: source: 10.27.48.78
11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 DEBUG: rangeXML: null
11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 Shazzam will scan 1 IP addresses
11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 DEBUG: Chunk size: 1
11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 DEBUG: processChunk()
11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 DEBUG: Queuing Shazzam
11/04/13 10:26:37 (777) Probe: Shazzam:10.27.48.78 Sending to queue: Shazzam,,10.27.48.78
11/04/13 10:26:37 (793) Probe: Shazzam:10.27.48.78 Document: <?xml version="1.0" encoding="UTF-8"?><results active="0" alive="0" probe_time="0" total="1"><result/><parameters><parameter name="queue" value="output"/><parameter name="from_sys_id" value=""/><parameter name="state" value="ready"/><parameter name="sys_created_on" value="2013-11-04 16:26:24"/><parameter name="debug" value="true"/><parameter name="scanner_log" value="true"/><parameter name="HTTP_waitForResponseMS" value="5000"/><parameter name="probe" value="eb95df760ab301550015543188996362"/><parameter name="regulator_period_ms" value="1"/><parameter name="report_inactive" value="true"/><parameter name="ecc_queue" value="f104091e6f34d90022a309c54b3ee450"/><parameter name="shazzam_chunk_size" value="50"/><parameter name="table_name" value="ecc_queue"/><parameter name="name" value=""/><parameter name="agent_correlator" value=""/><parameter name="GenericTCP_waitForConnectMS" value="1000"/><parameter name="topic" value="Shazzam"/><parameter name="error" value=""/><parameter name="probe_name" value="Shazzam"/><parameter name="sys_id" value="f104091e6f34d90022a309c54b3ee450"/><parameter name="from_host" value=""/><parameter name="agent" value="mid.server.snmainmidserver"/><parameter name="processed" value=""/><parameter name="source" value="10.27.48.78"/><parameter name="response_to" value=""/><parameter name="sequence" value="14223efc34d0000001"/><parameter name="regulator_max_packets" value="3"/><parameter name="report_dead" value="true"/></parameters></results>
11/04/13 10:26:37 (793) Probe: Shazzam:10.27.48.78 Enqueuing: D:\ServiceNow Discovery\MidServer\mid.2013-04-19-2025.windows.x86-32\agent\work\monitors\ECCSender\output\ecc_queue.f104091e6f34d90022a309c54b3ee450.xml
11/04/13 10:26:37 (793) Probe: Shazzam:10.27.48.78 Worker completed: Shazzam source: 10.27.48.78 time: 0:00:00.000
11/04/13 10:26:37 (918) ECCSender.1 Sending ecc_queue.f104091e6f34d90022a309c54b3ee450.xml

[prdelong]

Have you checked the MID server files and directories? Is anything missing? Are the MID server and Instance on the same version? I'd try restarting the service and see if anything is popping up in the MID server logs.

[edavis1]

Thanks for the suggestions. There was an issue with the versions at first. However I just did a fresh install of the correct version and the issue is still happening. I can put an SSHCommand on the ECC Queue and get results from a particular unix server. However when I try to run the Shazzam probe on the same unix server I get "No results returned" (and I am using the IP address, not the name). It's like I can connect to the server on port 22, but I can't scan it. No one here can think of any changes to our environment that would have changed since it was working.

[prdelong]

Hmm not much else I can think of. I'd check the MID server logs to see if anything is popping up error wise for missing files or JARs. It looks like you're not seeing any errors when Discovery launches the Shazzam probe. If you don't notice anything else in the MID logs, I'd try again from a different server -- or maybe your laptop -- and see if it's the same behavior. If it is, grab the MID logs and open a HI incident.