Hi @tbaublys_splunk,
So, there are two things happening here:
We removed 99% of the underlying AdvancedXML modules in Splunk 8.0. This means trying to make a custom module that inherits from one that no longer exists is going to fail. It sounds like search_activity still uses AdvancedXML, so in order for that app to work with 8.0 it would have to be ported.
When you have a python import exception in the appserver/splunkweb layer, CherryPy, the appserver/splunkweb, will not start. So, because 1 is failing on import, it breaks splunkweb.
I would highly recommend you run the Readiness App (https://splunkbase.splunk.com/app/4698/) on your system. It should have caught all of these upgrade blockers before you upgraded to 8.0.
I hope this helps!
Cory
... View more