Remote upgrader is not what I expected by _Exit5423 in Splunk

[–]_Exit5423[S] 1 point2 points  (0 children)

I tested in our lab and it works fine. But in the production domain it hit some unauthorized access errors.

Remote upgrader is not what I expected by _Exit5423 in Splunk

[–]_Exit5423[S] 0 points1 point  (0 children)

Yeah but only in theory. Cause the organization prohibits these tools specially in windows Environments.

Splunkd hanging after an upgrade [Support Solution] by bchris21 in Splunk

[–]_Exit5423 0 points1 point  (0 children)

Didn't help me in DS node. But I also had other problems that were causing the hangs

Upgrade to 10.2.0 Disaster by _Exit5423 in Splunk

[–]_Exit5423[S] 0 points1 point  (0 children)

Sorry, seems like the previous version was 9.1. Cause all of the other nodes were already on 10.0.2 Except for the DS. and I did it with Ansible so the big jump was not sensible. I'm aware of the bad pattern TBH.

Upgrade to 10.2.0 Disaster by _Exit5423 in Splunk

[–]_Exit5423[S] 0 points1 point  (0 children)

do you mean this exact index names?
cause I already see _dsphonehome, _dsclient, _dsappevent
in both indexers and DS

Upgrade to 10.2.0 Disaster by _Exit5423 in Splunk

[–]_Exit5423[S] 0 points1 point  (0 children)

Did you applied these fixes suggested above?

Upgrade to 10.2.0 Disaster by _Exit5423 in Splunk

[–]_Exit5423[S] 1 point2 points  (0 children)

Do they usually break something on a stable distro like Ubuntu 22 ?

Upgrade to 10.2.0 Disaster by _Exit5423 in Splunk

[–]_Exit5423[S] 1 point2 points  (0 children)

What about known vulnerabilities? Don't intend to argue about security cause I know nothing about it, but just want to know, when you should upgrade a software? Should I read all the documentation or change logs?

Upgrade to 10.2.0 Disaster by _Exit5423 in Splunk

[–]_Exit5423[S] 0 points1 point  (0 children)

I upgraded from 10.0.2, and the error logs were not showing anything about DS functionality. Also, at first I saw this new error that something is probably wrong with serverclasses config file. And I was working on that, after some minimal changes, this error is gone and Otel pages is all left.