All Apps and Add-ons

Exception error when launching SplunkIt search test

alukens
Engager

I'm using SplunkIt to test performance of new indexer hardware. I setup SplunkIt and ran the indexing test without issues and was able to get splunkit-user working, but I am getting an exception error (below) when launching searchtest.py on the server side.

Other information:

  • CentOS 6.3
  • Python 2.7.5
  • Splunk 4.3.6
  • SplunkWeb listening on TCP/8000
  • iptables is open
  • Nothing is listening on 8080 or 8081 per netstat
  • Host is registered in DNS and can resolve adddresses

Suggestions on what may be wrong?

Thanks


[root@phelsplind001 splunkit-server]# /usr/local/bin/python2.7 bin/searchtest.py

Preparing logger

[2013-10-11 08:48:48,483] ServerMain: Preparing server and test driver object

[2013-10-11 08:48:48,483] TestDriver: Preparing Pyro test driver object

[2013-10-11 08:48:48,484] TestDriver: Preparing results logger with CSV output enabled

[2013-10-11 08:48:48,484] TestDriver: CSV fields: ['timestamp', 'unix_timestamp', 'test_name', 'test_class', 'host', 'thread', 'id', 'agent_run', 'client_run', 'elapsed', 'run_duration', 'username', 'event_count', 'result_count', 'time_to_first_event', 'time_to_search']

[2013-10-11 08:48:48,485] ServerMain: Starting pyro server thread

Traceback (most recent call last):

File "bin/searchtest.py", line 616, in

main()

File "bin/searchtest.py", line 526, in main

server_thread = PyroServerThread(test_objects={'test.driver' : testdriver}, host=properties['server_host'], nameserver_port=int(properties['server_port']), daemon_port=int(properties['server_secondary_port']))

File "/var/splunkit-server/lib/pyro_server.py", line 130, in init
self.server = PyroServer(host=host, nameserver_port=nameserver_port, daemon_port=daemon_port, server_type=server_type)

File "/var/splunkit-server/lib/pyro_server.py", line 58, in init
nameserver_uri, nameserver_daemon, broadcast_server = Pyro4.naming.startNS(host=host, port=nameserver_port, enableBroadcast=False)

File "/var/splunkit-server/lib/Pyro4/naming.py", line 251, in startNS
daemon=NameServerDaemon(host, port, unixsocket, nathost=nathost, natport=natport)

File "/var/splunkit-server/lib/Pyro4/naming.py", line 121, in init
super(NameServerDaemon, self).init(host, port, unixsocket, nathost=nathost, natport=natport)

File "/var/splunkit-server/lib/Pyro4/core.py", line 772, in init
self.transportServer.init(self, host, port, unixsocket)

File "/var/splunkit-server/lib/Pyro4/socketserver/threadpoolserver.py", line 77, in init
self.sock=socketutil.createSocket(bind=bind_location, reuseaddr=Pyro4.config.SOCK_REUSE, timeout=Pyro4.config.COMMTIMEOUT, noinherit=True)

File "/var/splunkit-server/lib/Pyro4/socketutil.py", line 217, in createSocket
sock.bind(bind)

File "/usr/local/lib/python2.7/socket.py", line 224, in meth
return getattr(self.sock,name)(*args)

socket.error: [Errno 99] Cannot assign requested address

Shutting down Pyro server

Exception AttributeError: "PyroServer instance has no attribute 'nameserver_daemon'" in <bound method PyroServer.
del_ of > ignored

Exception AttributeError: "'PyroServerThread' object has no attribute 'server'" in > ignored

Tags (1)

tameem
New Member

Sometimes using an ip address instead of hostname for server_host in pyro.properties will help. This occurs due to the limitations of the pyro library this framework is built on.

Thanks

0 Karma

alukens
Engager

It's very odd because the server can resolve it's own address in DNS, but using the IP address in pyro.properties in splunkit-server fixed it.

Thanks for your help.

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...