Deployment Architecture

How to fix Linux proxy issue?

willec09
New Member

I am currently running on Red Hat Enterprise Linux. I have already set up the proxy by using the following commands:

export http_proxy=http://XXX.XXX.XXX.XXX:XXX
export https_proxy=http://XXX.XXX.XXX.XXX:XXX

I have also added those addresses to the /etc/sysconfig/splunk file.

I am now able to do a wget of apps.splunk.com, but when I try to access them through Splunk web, I get the following error:

The splunkd daemon cannot be reached by splunkweb. Check that there are no blocked network ports or that splunkd is still running.

After following the link, I receive the error below:

2015-04-28 16:52:32,269 ERROR [55400102397fd289b3a210] decorators:420 - Splunkd daemon is not responding: ('Error connecting to /services/apps/remote/entries: The read operation timed out',)
Traceback (most recent call last):
  File "/opt/splunk/lib/python2.7/site-packages/splunk/appserver/mrsparkle/lib/decorators.py", line 406, in handle_exceptions
    return fn(self, *a, **kw)
  File "/opt/splunk/lib/python2.7/site-packages/splunk/appserver/mrsparkle/controllers/admin.py", line 3190, in splunkbase_browser
    apps, total_results = self._getRemoteEntries(**kwargs)
  File "/opt/splunk/lib/python2.7/site-packages/splunk/appserver/mrsparkle/controllers/admin.py", line 3148, in _getRemoteEntries
    entities = en.getEntities(url, **kwargs)
  File "/opt/splunk/lib/python2.7/site-packages/splunk/entity.py", line 129, in getEntities
    atomFeed = _getEntitiesAtomFeed(entityPath, namespace, owner, search, count, offset, sort_key, sort_dir, sessionKey, uri, hostPath, **kwargs)
  File "/opt/splunk/lib/python2.7/site-packages/splunk/entity.py", line 222, in _getEntitiesAtomFeed
    serverResponse, serverContent = rest.simpleRequest(uri, getargs=kwargs, sessionKey=sessionKey, raiseAllErrors=True)
  File "/opt/splunk/lib/python2.7/site-packages/splunk/rest/__init__.py", line 478, in simpleRequest
    raise splunk.SplunkdConnectionException, 'Error connecting to %s: %s' % (path, str(e))
SplunkdConnectionException: Splunkd daemon is not responding: ('Error connecting to /services/apps/remote/entries: The read operation timed out',)
2015-04-28 16:52:32,268 ERROR [55400102397fd289b3a210] __init__:477 - Socket error communicating with splunkd (error=The read operation timed out), path = /services/apps/remote/entries
Tags (3)
0 Karma

pmdba
Builder

It's hard to say for sure, but my best guess based on what you've shared is that something is now being routed to the proxy that shouldn't be - such as a call to localhost or some such that the proxy doesn't know how to handle, so the connection times out.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...

Build and Launch AI Agents from Your Splunk Workflows

  Register We’ve all been there: juggling alerts, runbooks, and endless manual searches. What if you could ...

Splunk Cloud Application Management in Terraform

Register   On Tuesday, August 4 at 11AM PDT / 2PM EDT, we’re diving into how you can bring Infrastructure as ...