Nick Maludy
Nick Maludy
Currently we generate this using an exec (bad practice) https://github.com/StackStorm/puppet-st2/blob/master/manifests/profile/web.pp#L42-L47
@armab Doesn't appear to be an issue in the Puppet module. In Puppet we use the `ini_setting` resource and edit individual pieces instead of templating the whole file (for now).
Removing from 3.3.0 until upstream changes in hubot have been fixed.
@lattisimo Your changes look good, we're just in a change freeze right now due to a pending 3.3.0 release. I'm going to target this for the 3.4.0 milestone, does that...
+1 We've been using Rocky Linux 8 and Rocky Linux 9 for our non-production workloads. This has been a perfect replacement and stepping stone for RHEL. Look forward to seeing...
@flurreN I haven't changed the `Log On` settings of the service. Does the default `SYSTEM` user not have access to the `Security` channel? Should i change the `Log On` setting...
@flurreN I have changed the service to login as local admin and no change. Still seeing the errors above and now that you mention the `Security` channel i'm not seeing...
@flurreN I confirmed that all folders and files in the path including `C:\opt\td-agent\worker0\windows_eventlog\storage.json` are all writable by `SYSTEM`.  I also confirmed that the `ruby` processes are indeed running as...