Getting Data In

splunk group in linux

maede_yavari
Explorer

Hello,

I noticed that in versions upper 9.1, the user and group were changed to "splunkfwd"

I have updated the universal forwarder to the newer version (9.1), but the user and group did not change to "splunkfwd." Subsequently, we encountered several problems related to permissions, such as the Universal Forwarder lacking permission to read auditd logs. Therefore, it is necessary to modify the "log_group" parameter in the auditd.conf file.

Should I manually change it, or is there an alternative solution to resolve all permission problems?

Labels (1)
0 Karma

maede_yavari
Explorer

I have updated the universal forwarder with RPM and deb packages and following commands:

rpm -Uvh and dpkg -i

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Wait a second. You did both on the same host? rpm and deb?

0 Karma

PickleRick
SplunkTrust
SplunkTrust

How did you install and upgrade your forwarder? RPM? deb? tgz?

0 Karma

maede_yavari
Explorer

I have updated the universal forwarder with RPM and deb packages and following commands:

rpm -Uvh and dpkg -i

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!

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

55 Days to Go: Secure Your Seat at Splunk University in Denver

Your .conf26 Experience Starts Before Opening Keynote  If Denver is known for its mile-high elevation, Splunk ...

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...