Stenographer consistently fails to actually run

[charlesfair]

Upon installation of ROCK 2.0 prodution, with stenographer enabled, stenographer always fails:

[rockadmin@simplerockbuild ~]$ sudo systemctl enable stenographer.service
[sudo] password for rockadmin:
[rockadmin@simplerockbuild ~]$ systemctl start stenographer.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to manage system services or units.
Authenticating as: rockadmin
Password:
==== AUTHENTICATION COMPLETE ===
[rockadmin@simplerockbuild ~]$ sudo systemctl status stenographer.service
● stenographer.service - packet capture to disk
Loaded: loaded (/etc/systemd/system/stenographer.service; enabled; vendor preset: disabled)
Active: active (exited) since Thu 2017-03-09 13:07:08 UTC; 4min 26s ago
Main PID: 30510 (code=exited, status=0/SUCCESS)

Mar 09 13:07:08 simplerockbuild.simplerock.lan systemd[1]: Starting packet ca...
Mar 09 13:07:08 simplerockbuild.simplerock.lan systemd[1]: Started packet cap...
Hint: Some lines were ellipsized, use -l to show in full.
[rockadmin@simplerockbuild ~]$

[charlesfair]

From /var/log/messages

Mar 9 13:05:33 localhost ansible-copy: Invoked with src=/root/.ansible/tmp/ansible-tmp-1489064733.08-131035167464111/source directory_mode=None force=True remote_src=None unsafe_writes=None selevel=None seuser=None setype=None group=root content=NOT_LOGGING_PARAMETER dest=/etc/systemd/system/stenographer.service serole=None original_basename=stenographer.service delimiter=None mode=420 regexp=None owner=root follow=False validate=None backup=False
Mar 9 13:05:34 localhost ansible-command: Invoked with creates=/etc/stenographer/certs/client_key.pem executable=None _uses_shell=False _raw_params=/usr/bin/stenokeys.sh stenographer stenographer removes=None warn=True chdir=None
Mar 9 13:05:41 localhost ansible-systemd: Invoked with name=stenographer enabled=False daemon_reload=False state=stopped user=False masked=None

[peasead]

@charlesfair Can you run journalctl?

[charlesfair]

Thanks! Will run and update with results. So right now, no idea of the root cause...

[dcode]

This is being fixed in hotfix/2.0.2 with commit bf40964.

[dcode]

This was fixed in 2.0.2