firestrife Posted January 22, 2015 Posted January 22, 2015 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.
firestrife Posted January 23, 2015 Author Posted January 23, 2015 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.
Staff Mark Posted January 23, 2015 Staff Posted January 23, 2015 Be sure that you don't mix 32bit with 64bit packages. If you have 32bit machine install pulseway_x86.rpm. If you have 64bit machine then pulseway_x64.rpm is what you need. Mark Update: I just reproduced your issue: Jan 23 09:58:49 localhost.localdomain pulseway[3869]: Starting pulseway daemon: /bin/bash: /usr/sbin/pulsewayd: /lib/ld-linux.so.2: bad ELF interpreter: No ...directory Jan 23 09:58:49 localhost.localdomain pulseway[3869]: [FAILED] Jan 23 09:58:49 localhost.localdomain systemd[1]: pulseway.service: control process exited, code=exited status=1 Jan 23 09:58:49 localhost.localdomain systemd[1]: Failed to start LSB: start and stop pulsewayd. Jan 23 09:58:49 localhost.localdomain systemd[1]: Unit pulseway.service entered failed state. On my 64bit machine I had installed the 32 bit rpm pulse way package. Again, be sure that you get the right package for your system.
firestrife Posted January 23, 2015 Author Posted January 23, 2015 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, ...).
Staff Mark Posted January 23, 2015 Staff Posted January 23, 2015 You don't need to enable it via systemd. It's using SysV and will automatically start on boot. root@localhost ~]# chkconfig --list iprdump 0:off 1:off 2:on 3:on 4:on 5:on 6:off iprinit 0:off 1:off 2:on 3:on 4:on 5:on 6:off iprupdate 0:off 1:off 2:on 3:on 4:on 5:on 6:off netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off network 0:off 1:off 2:on 3:on 4:on 5:on 6:off pulseway 0:off 1:off 2:off 3:on 4:off 5:on 6:off Mark
Mohammadreza Posted September 8, 2015 Posted September 8, 2015 hi can help me please? [root@digi ~]# rpm -ivh http://www.pulseway.com/download/pulseway_x64.rpmRetrieving http://www.pulseway.com/download/pulseway_x64.rpmPreparing... ################################# [100%]Stopping pulseway servicedoneUpdating / installing... 1:pulseway-4.7.5-1 ################################# [100%]service pulseway does not support chkconfigservice pulseway does not support chkconfigservice pulseway does not support chkconfig[root@digi ~]# cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xmlcp: overwrite ‘/etc/pulseway/config.xml’? y i have config file from old system and replace it here after installation /etc/pulseway/config.xml[root@digi ~]# /etc/init.d/pulseway startStarting pulseway (via systemctl): [ OK ] not start [root@digi ~]# sudo systemctl enable pulseway.service not workpulseway.service is not a native service, redirecting to /sbin/chkconfig.Executing /sbin/chkconfig pulseway onservice pulseway does not support chkconfig[root@digi ~]# chkconfig --listNote: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration. If you want to list systemd services use 'systemctl list-unit-files'. To see services enabled on particular target use 'systemctl list-dependencies [target]'.netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:offnetwork 0:off 1:off 2:on 3:on 4:on 5:on 6:off[root@digi ~]#
Staff Chris Posted September 8, 2015 Staff Posted September 8, 2015 Hi,Can you PM me your config.xml file (remove your account details first). Also do you have any error in the syslog?Chris
Staff Chris Posted September 24, 2015 Staff Posted September 24, 2015 Hi,Can you download the RPM one more time as we've released an update and the problem may have been resolved.Chris
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now