Fedora client stopped working

[Bogdan]

Hi team,

 

Pulseway client from my Fedore machine stopped working this mordning out of the blue.

I made a clean install, but it didn't help.

 

I'm getting a strage message in /var/log/messages when I strat the clinet

 

systemd[1]: pulseway.service: main process exited, code=killed, status=4

 

...and the service status looks like this:

 

pulseway.service - LSB: start and stop pulsewayd
          Loaded: loaded (/etc/rc.d/init.d/pulseway)
          Active: active (exited) since Mon, 13 Oct 2014 16:33:34 +0300; 39min ago
        Main PID: 2984 (code=killed, signal=ILL)
          CGroup: name=systemd:/system/pulseway.service

 

Basically I did no change on my system. I just received a notification that my machine is offline and from that point the pulseway didn't want to start anymore.

 

Thanks,

Bogdan

[Mark]

Hi,

 

What version of Fedora are you using? (uname -a; cat /etc/issue; openssl version).

Can you see any errors/crash in logs? (journalctl -f)

 

Regards,

Mark

[Bogdan]

Mark,

I'm using FC16 - 3.1.0-7.fc16.i686.PAE #1 SMP Tue Nov 1 20:53:45 UTC 2011 i686 i686 i386 GNU/Linux

OpenSSL 1.0.0e-fips 6 Sep 2011

The only errrors/crashes from logs are these (in /var/log/messages):

 

When I start pulseway:

Oct 14 09:43:54 xxxxx pulseway: Configuration read successfully!
Oct 14 09:43:54 xxxxx pulseway[4672]: Starting pulseway daemon: [  OK  ]
Oct 14 09:43:56 xxxxx pulseway: Got exception signal: 4
Oct 14 09:43:56 xxxxx systemd[1]: pulseway.service: main process exited, code=killed, status=4

 

When I stop it:

Oct 14 09:55:48 xxxxx pulseway[4791]: Stopping pulseway daemon: [FAILED]
Oct 14 09:55:48 xxxxx systemd[1]: Unit pulseway.service entered failed state.

 

Thant's all I can find.

 

Thanks,

Bogdan

[Mark]

Hi,

 

Can you, please, download and install this version:

 

https://www.dropbox.com/s/s9nhiiglttznlyu/pulseway-4.5.4-2.i386.rpm?dl=0

 

Let us know if that fix your issue.

 

Regards,

Mark

[Bogdan]

It didn't change anything. I'm having the same issue

 

Thanks,

Bogdan

[Mark]

I'll get a vanilla FC16 and try to replicate your issue.

Can you, please PM you config.xml after you remove username/password.

 

Thanks!

Mark

[Bogdan]

Thanks Mark. I sent you the file.

Looking forward to hear news from you...

[Mark]

Works here using your config:

 

[root@localhost pulseway]# /etc/init.d/pulseway status

pulseway.service - LSB: start and stop pulsewayd

 Loaded: loaded (/etc/rc.d/init.d/pulseway)

 Active: active (running) since Tue, 14 Oct 2014 02:49:41 -0700; 7s ago

Process: 1126 ExecStop=/etc/rc.d/init.d/pulseway stop (code=exited, status=0/SUCCESS)

Process: 1146 ExecStart=/etc/rc.d/init.d/pulseway start (code=exited, status=0/SUCCESS)

 CGroup: name=systemd:/system/pulseway.service

  1152 /usr/sbin/pulsewayd

 

I'll use credential from config.xml that you send it to me and I'll start my FC16 test machine and let me know if you can see it online.

[Bogdan]

Yes, it works. I can see two new machines - one offline and one online.

 

So, what might cause the problem on my machine ?

[Mark]

So, your config against a vanilla FC16 works. Them must be something local then.

Have you installed recently any software that changed core libs? Or any system updates?

 

Mark

[Bogdan]

Nope. Nothing like this.

I agree with you, it works on FC16, as it worked on my machine for months...

I will dig deeper and let you know if I find something.

Anyway, any other suggestion is welcome from anyone...

 

Bogdan