[
https://issues.apache.org/jira/browse/CLOUDSTACK-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747368#comment-14747368
]
ASF GitHub Bot commented on CLOUDSTACK-8840:
--------------------------------------------
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/820#issuecomment-140719214
@wido No luck yet:
```
error: File not found:
/data/git/cs2/cloudstack/dist/rpmbuild/BUILDROOT/cloudstack-4.6.0-SNAPSHOT.el7.centos.x86_64/usr/sbin/cloudstack-usage-sysd
RPM build errors:
Binaries arch (1) not matching the package arch (2).
File not found:
/data/git/cs2/cloudstack/dist/rpmbuild/BUILDROOT/cloudstack-4.6.0-SNAPSHOT.el7.centos.x86_64/usr/sbin/cloudstack-usage-sysd
RPM Build Failed
```
> Update systemd profile for usage server
> ---------------------------------------
>
> Key: CLOUDSTACK-8840
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8840
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Usage
> Reporter: Wido den Hollander
> Assignee: Wido den Hollander
> Labels: systemd
> Fix For: 4.6.0
>
>
> Currently there is a systemd profile for the usage server, but it is not
> packaged properly and can be improved much.
> We should align this with the Agent systemd profile.
> In /usr/libexec/cloudstack there should be a wrapper which does the actual
> Java invoke and the wrapper is invoked by systemd.
> Output of the usage server should go to stdout as well so it is catched by
> journalctl.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
