[Debian start produces "Got exception signal: 4"]

Mark, I understand what you're saying, but since the problem occurred on other systems as well and almost at the same moment in time, after a new version was installed, for me this sort for coincidence is too much

I don't totally exclude the possibility to have an issue with my system, but I will keep follow the thread anyway

 

Cheers

Bogdan

[Debian start produces "Got exception signal: 4"]

Looking forward to hear news from developers...

 

Thank you,

Bogdan

[Debian start produces "Got exception signal: 4"]

I have the same problem on Fedora (FC16 x86)

Another thread on this topic is opened here: http://forum.pulseway.com/topic/1277-fedora-client-stopped-working/

The problem started to occur on 13th Oct too....so the similarities between this issue and mine make me believe that the problem is no related to my machine, but to pulseway.

Did you release any update on 12th-13th of October ?

 

Cheers

Bogdan

[Fedora client stopped working]

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

[Fedora client stopped working]

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

 

So, what might cause the problem on my machine ?

[Fedora client stopped working]

Thanks Mark. I sent you the file.

Looking forward to hear news from you...

[Fedora client stopped working]

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

 

Thanks,

Bogdan

[Fedora client stopped working]

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

[Fedora client stopped working]

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