topic Re: Splunk package error in Deployment Architecture

Splunk package error

automagication — Thu, 02 May 2024 14:01:32 GMT

Whenever I package the splunk app, I get execute permission error because I have 744 permission for conf files but splunk expects it to be 644.

With 644 permission I cannot package the app, is there any workaround for the same.

Below is the screenshot of the error.

Re: Splunk package error

richgalloway — Thu, 02 May 2024 15:06:50 GMT

I'm guessing you're packaging the app on a Windows machine. That will never work because Windows can't/won't set the file permissions correctly. When I used to package on Windows, I would transfer the .tgz file to a Linux system, explode it, change the permissions, then re-tar it and transfer back to the Windows machine for uploading.

Re: Splunk package error

automagication — Thu, 02 May 2024 15:17:42 GMT

No I use Linux ubuntu wsl on windows, I can set permissions correctly but the problem is with 644 permissions, I cant run slim package app-folder

Re: Splunk package error

automagication — Thu, 02 May 2024 15:23:35 GMT

I followed the permissions from the list
https://dev.splunk.com/enterprise/reference/appinspect/appinspectcheck/?_gl=1*fchjpf*_ga*MTA4MzA2OTgyNS4xNzA2MDE0Nzg4*_ga_GS7YF8S63Y*MTcxNDYzNDAxNy43Mi4xLjE3MTQ2MzYxMDAuNTcuMC4w*_ga_5EPM2P39FV*MTcxNDYzMzg3Ni4xMzAuMS4xNzE0NjM2MTM3LjAuMC43MzQxMzI1OTE.&_ga=2.202439633.1531808691.1714369489-1083069825.1706014788&_gac=1.15736132.1712044493.Cj0KCQjw2a6wBhCVARIsABPeH1t5zRXtGhlOnCnFrrO2uJB84ZoqzRxjfVT0wZruAQGQ9rWcd5insFMaAkIgEALw_wcB#Source-code-and-binaries-standards

Re: Splunk package error

automagication — Thu, 02 May 2024 15:24:38 GMT

Even untar and tar with different permissions, will not let me package because the permissions are 644, there is no execute permission

Re: Splunk package error

automagication — Thu, 02 May 2024 15:58:05 GMT

I don't think this is the issue, I am using linux

Re: Splunk package error

richgalloway — Thu, 02 May 2024 18:25:47 GMT

Ubuntu on Windows is still Windows. I had the same problem. You have to use a real Linux box.