All Apps and Add-ons

Splunk App and Add-on for ServiceNow: Why does the accounts setup page display error "Unexpected error "" from python handler: "HTTP 500 Internal Server Error -- In handler 'snow_account'"?

Contributor

We have Splunk Enterprise on-prem with a search head cluster behind F5 load balancer. I followed the steps to install the Splunk Add-on for ServiceNow and Splunk App for ServiceNow on Search heads using the deployer and also installed the add-on on the Heavy Forwarder.

http://docs.splunk.com/Documentation/ServiceNow/4.0.3/Install/Installon-prem

After the installation ran the remote target command to connect your search head and forwarder and was successful as well.

But when following steps to do the setup ( http://docs.splunk.com/Documentation/ServiceNow/4.0.3/Install/Setuptheapp ), I get an error on the setup page directly without even displaying any fields to enter the information on the Search Head .

Unexpected error occurs. In handler 'splunk_app_servicenow_accounts': Unexpected error "" from python handler: "HTTP 500 Internal Server Error -- In handler 'snow_account': External handler failed with code '1' and output: ''. See splunkd.log for stderr output.". See splunkd.log for more details.

Stack Trace from Splunkd.logs

02-17-2017 00:25:55.516 -0800 ERROR AdminManagerExternal - Stack trace from python handler:\nTraceback (most recent call last):\n  File "/opt/splunk/lib/python2
.7/site-packages/splunk/admin.py", line 129, in init\n    hand.execute(info)\n  File "/opt/splunk/lib/python2.7/site-packages/splunk/admin.py", line 590, in exe
cute\n    if self.requestedAction == ACTION_LIST:     self.handleList(confInfo)\n  File "/opt/splunk/etc/apps/splunk_app_servicenow/bin/snow_accounts_handler.py
", line 51, in handleList\n    account = account_manager.list()[0]\n  File "/opt/splunk/etc/apps/splunk_app_servicenow/bin/snow_account_manager.py", line 64, in
 list\n    return [self.get_by_name("snow_account")]\n  File "/opt/splunk/etc/apps/splunk_app_servicenow/bin/snow_account_manager.py", line 54, in get_by_name\n
    accounts = snow_account_collection.list()\n  File "/opt/splunk/etc/apps/splunk_app_servicenow/bin/splunklib/client.py", line 1459, in list\n    return list(
self.iter(count=count, **kwargs))\n  File "/opt/splunk/etc/apps/splunk_app_servicenow/bin/splunklib/client.py", line 1418, in iter\n    response = self.get(coun
t=pagesize or count, offset=offset, **kwargs)\n  File "/opt/splunk/etc/apps/splunk_app_servicenow/bin/splunklib/client.py", line 1648, in get\n    return super(
Collection, self).get(name, owner, app, sharing, **query)\n  File "/opt/splunk/etc/apps/splunk_app_servicenow/bin/splunklib/client.py", line 746, in get\n    **
query)\n  File "/opt/splunk/etc/apps/splunk_app_servicenow/bin/splunklib/binding.py", line 287, in wrapper\n    return request_fun(self, *args, **kwargs)\n  Fil
e "/opt/splunk/etc/apps/splunk_app_servicenow/bin/splunklib/binding.py", line 69, in new_f\n    val = f(*args, **kwargs)\n  File "/opt/splunk/etc/apps/splunk_ap
p_servicenow/bin/splunklib/binding.py", line 665, in get\n    response = self.http.get(path, self._auth_headers, **query)\n  File "/opt/splunk/etc/apps/splunk_a
pp_servicenow/bin/splunklib/binding.py", line 1160, in get\n    return self.request(url, { 'method': "GET", 'headers': headers })\n  File "/opt/splunk/etc/apps/
splunk_app_servicenow/bin/splunklib/binding.py", line 1221, in request\n    raise HTTPError(response)\nHTTPError: HTTP 500 Internal Server Error -- \n In handle
r 'snow_account': External handler failed with code '1' and output: ''.  See splunkd.log for stderr output.\n


02-17-2017 00:25:55.516 -0800 ERROR AdminManagerExternal - Unexpected error "" from python handler: "HTTP 500 Internal Serv
er Error -- \n In handler 'snow_account': External handler failed with code '1' and output: ''.  See splunkd.log for stderr output.".  See splunkd.log for more
details.

I haven't been able to figure out the issue here . Any help would be highly appreciated.

Thanks
alt text

1 Solution

Contributor

Fixed it. The issue was the Heavy Forwarder where the add-on is deployed was down. Restarted it and was able to run the setup successfully.

Thanks

View solution in original post

0 Karma

Contributor

Fixed it. The issue was the Heavy Forwarder where the add-on is deployed was down. Restarted it and was able to run the setup successfully.

Thanks

View solution in original post

0 Karma