Reporting

Job Management Dashboard not Functional 'str' object has no attribute 'os_startIndex'

dflodstrom
Builder

I am receiving the following error when attempting to view the job management dashboard from my clustered search heads:
[JobManager module] 'str' object has no attribute 'os_startIndex'
We have recently upgraded to Splunk version 6.2.3, this has been an issue since the upgrade. Any suggestions will help.

0 Karma

bohanlon_splunk
Splunk Employee
Splunk Employee
0 Karma

dflodstrom
Builder

The previous answer did not permanently fix my issue. Splunk support says upgrading to the latest version, 6.2.4, should fix this issue. I haven't tested this upgrade yet, I'll accept this answer when I confirm.

0 Karma

kikexclusive
Path Finder

This issue was not resolved neither in 6.3.0 Splunk Enterprise version... anyone knows how to fix it?

dflodstrom
Builder

I apologize for not circling back after I resolved this issue. I worked with support to fix this and they should have fixed this in later releases.

The issue was with this python script: lib/python2.7/site-packages/httplib2/init.py.org

I would provide the change to you but I'm not sure if the workaround we applied is 1. appropriate to share or 2. the correct way to resolve this long-term.

If you're able to update you can try that or reach out to support. I worked with Masaaki Yana on this case.

0 Karma

jonathan_cooper
Communicator

Hi Dave, long time no talk! (It's Cooper, your PS guy)

I'm on a current engagement with another customer on 6.3.3 and see this issue still. 😞

dflodstrom
Builder

Terrible. You've got mail.

0 Karma

dflodstrom
Builder

This issue was not resolved in version 6.2.4. It has been added to the list of known issues in that version. I'm testing 6.2.5 now which should fix this issue. Should.

0 Karma

dflodstrom
Builder

This is still an issue for us in version 6.2.5

0 Karma

dflodstrom
Builder

After upgrading to 6.2.3 this was only an issue on my search head cluster. All other Splunk instances displayed the dashboard without an issue. Adding the following to $SPLUNK_HOME/etc/system/local/limits.conf fixed it

[restapi]
jobscontentmaxcount = 100

The default value for this parameter in limits.conf is 0:

jobscontentmaxcount = <integer>
* Maximum length of a property in the contents dictionary of an entry from /jobs getter from REST API
* Value of 0 disables truncation
* Defaults to 0
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 ...