[CentOS 7]

Thank you! it's now working but how do I get it to start at boot? I tried this command "systemctl enable pulseway.service" and here's another error message...

[jason@jarvis ~]$ sudo systemctl enable pulseway.service
pulseway.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig pulseway on
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).

[CentOS 7]

Remove and installed rpm package with -ivh options, then setup config.xml and here's the result:

[root@jarvis pulseway]# systemctl start pulseway.service
Job for pulseway.service failed. See 'systemctl status pulseway.service' and 'journalctl -xn' for details.
[root@jarvis pulseway]# journalctl -f
-- Logs begin at Fri 2015-01-23 00:45:26 MST. --
Jan 23 01:37:14 jarvis.{redacted}.com pulseway[5525]: [FAILED]
Jan 23 01:37:14 jarvis.{redacted}.com systemd[1]: pulseway.service: control process exited, code=exited status=1
Jan 23 01:37:14 jarvis.{redacted}.com systemd[1]: Failed to start LSB: start and stop pulsewayd.
Jan 23 01:37:14 jarvis.{redacted}.com systemd[1]: Unit pulseway.service entered failed state.
Jan 23 01:37:35 jarvis.{redacted}.com systemd[1]: Starting LSB: start and stop pulsewayd...
Jan 23 01:37:36 jarvis.{redacted}.com pulseway[5542]: Starting pulseway daemon: /bin/bash: /usr/sbin/pulsewayd: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
Jan 23 01:37:36 jarvis.{redacted}.com pulseway[5542]: [FAILED]
Jan 23 01:37:36 jarvis.{redacted}.com systemd[1]: pulseway.service: control process exited, code=exited status=1
Jan 23 01:37:36 jarvis.{redacted}.com systemd[1]: Failed to start LSB: start and stop pulsewayd.
Jan 23 01:37:36 jarvis.{redacted}.com systemd[1]: Unit pulseway.service entered failed state.

[CentOS 7]

This is what happened on CentOS 7... assuming it's not supported yet?

pulseway.service - LSB: start and stop pulsewayd
   Loaded: loaded (/etc/rc.d/init.d/pulseway)
   Active: failed (Result: exit-code) since Thu 2015-01-22 12:54:17 MST; 1min 9s ago
  Process: 4925 ExecStart=/etc/rc.d/init.d/pulseway start (code=exited, status=1/FAILURE)

Jan 22 12:54:17 (removed).com pulseway[4925]: Starting pulseway daemon: /bin/bash: /usr/sbin/pulsewayd: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
Jan 22 12:54:17 (removed).com pulseway[4925]: [FAILED]
Jan 22 12:54:17 (removed).com systemd[1]: pulseway.service: control process exited, code=exited status=1
Jan 22 12:54:17 (removed).com systemd[1]: Failed to start LSB: start and stop pulsewayd.
Jan 22 12:54:17 (removed).com systemd[1]: Unit pulseway.service entered failed state.