Deployment Architecture

Apps not deploying correctly

lhollada
Engager

I'm setting up a new deployment server and a test client. When deploying apps to this client, I get these sorts of errors in the client log:

11-08-2011 11:08:16.404 -0600 WARN  DeployedApplication - Installing app: linux to location: /opt/splunkforwarder/etc/apps/linux
11-08-2011 11:08:16.407 -0600 ERROR IniFile - Cannot open ini file for parsing: No such file or directory
11-08-2011 11:08:16.407 -0600 ERROR ConfObjectManagerDB - Cannot initialize: /opt/splunkforwarder/etc/apps/linux/metadata/local.meta

The actual app files update, but I cannot figure out why it's having a problem with the metadata. Here's my serverclass.conf:

[global]
blacklist.0=*
restartSplunkd = True

[serverClass:AppsByMachineType]
machineTypes=windows-intel,linux-i686,linux-x86_64

[serverClass:AppsByMachineType:app:allservers]
machineTypes=windows-intel,linux-i686,linux-x86_64

[serverClass:AppsByMachineType:app:windows]
machineTypes=windows-intel

[serverClass:AppsByMachineType:app:linux]
machineTypes = linux-x86_64,linux-i686
restartSplunkd = True

Any ideas would be appreciated.

One additional note: it doesn't seem like the clients are acutally restarting Splunkd like they should be, but I'm not sure why.

0 Karma
1 Solution

lhollada
Engager

In case anyone is curious, the problem here was the lack of a metadata/local.meta file in the app directory on the deployment server. Once that was in place, the app was installed successfully to the client, which then restarted splunkd.

View solution in original post

lhollada
Engager

In case anyone is curious, the problem here was the lack of a metadata/local.meta file in the app directory on the deployment server. Once that was in place, the app was installed successfully to the client, which then restarted splunkd.

View solution in original post

OMohi
Path Finder

I am facing similar issue, how did you get the metadata/local.meta file in place in the app directory?

Please let us know.

Thanks

Obaid

0 Karma
Register for .conf21 Now! Go Vegas or Go Virtual!

How will you .conf21? You decide! Go in-person in Las Vegas, 10/18-10/21, or go online with .conf21 Virtual, 10/19-10/20.