Jump to content

Mark

Staff
  • Posts

    157
  • Joined

  • Last visited

Posts posted by Mark

  1. Hi,

     

     

    Just tested now on CentOS 6 with :

     

    <Service Name="postfix" DisplayName="Postfix Service" IsDaemon="true" DaemonType="SYSVINIT" Path="" StartParameters="" CanBeStopped="true" Enabled="true"/>

     

    and works as expected.

     

    Please send an email to support@pulseway.com with your config file and output of the following:

     

    cat /proc/cpuinfo
    uname -a
    openssl -v
    ldd --version
     

    Regards,

    Mark

  2. 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

  3. 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.
  4. Is there supposed to be a PKGBUILD file in the tarball? I copied everything into the directories after untarring, but I'm getting a missing /lib/init/vars.sh error when trying to run the init file.

     

    Arch package contain precompiled binaries. You can install it via pacman -U pulseway_x64.pkg.tar.xz

     

    Mark

  5. Hi,

    Can you, please sent us (support@pulseway.com) your config file (after remove all sensitive informations). As well can you please send the output of: uname -a; cat /etc/issue; openssl -v .

    Thanks!

    Regards,

    Mark

  6. I want to echo what bbb was saying in that I too had the Linux agent stop working on October 13th. I received the same messages in the agent log (see below).

    Has a work-around for this issue been discovered or are the Pulseway devs working on a fix? I'd really like to get the agent running again.

    Thanks everyone.

    Hi,

    What distro (uname -a; cat /etc/issue; openssl version) are you using? Can you, please, PM your config file? (After removing your username and password)

    Thanks!

    Mark

  7. Thanks Chris, same problem:

    [root@b3 09:16:58] $ uname -a

    Linux b3 2.6.32-5-686 #1 SMP Tue May 13 16:33:32 UTC 2014 i686 GNU/Linux

    Oct 16 09:16:48 b3 pulseway: Configuration read successfully!

    Oct 16 09:16:55 b3 pulseway: Got exception signal: 4

    And a diff of config.xml with account details removed:

    diff -awB config.xml config.xml.sample

    9c10,11

    < <Account Username="myaccount" Password="hex" UseCustomServer="false" CustomServerAddress=""/>

    ---

    > <Account Username="" Password="" UseCustomServer="false" CustomServerAddress="" />

    >

    13c15,16

    < <ComputerInformation Name="b3new" Group="Default"/>

    ---

    > <ComputerInformation Name="" Group="Default" />

    >

    138d165

    < </config>

    139a167

    > </config>

    I then change all true to false:

    < <OnShutdown Priority="0" Enabled="false"/>

    ---

    > <OnShutdown Priority="0" Enabled="true" />

    < <SSLCertificateExpiration Days="15" Priority="0" Enabled="false"/>

    ---

    > <SSLCertificateExpiration Days="15" Priority="0" Enabled="true"/>

    < <WebSiteNotAvailable Minutes="1" Priority="0" Enabled="false"/>

    ---

    > <WebSiteNotAvailable Minutes="1" Priority="0" Enabled="true"/>>

    And same problem

    Oct 16 09:25:55 b3 pulseway: Configuration read successfully!

    Oct 16 09:26:02 b3 pulseway: Got exception signal: 4

    Can you give me an idea of what signal 4 means?

    Hi,

    Do you have any particular software that will change default core libs (glibc, gcc, kernel, OpenSSL) ?

    I'm asking this because I tested your config with a fresh distro install and works. I'm trying to isolate your issue.

    Mark

  8. 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

    Hi,

    This is your replay from other thread after I tested your configure file with a vanilla FC16 installation:

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

    So, what might cause the problem on my machine ? :("

    We don't what you have installed on your machine, we don't know how your machine is configured. All our release we test then against fresh VANILLA distributions. And your config file WORKS with a fresh install of FC16.

    Mark

  9. Hi,

     

    What is the version of Debian? (uname -a; cat /etc/debian_version; openssl version).

    Try to a

     rm -rf /usr/sbin/pulseway*

    get latest version from our website and give it a try.

    If still an issue send me more details about your distro along with config.xml (on PM) I'll try to set up an environment and try to replicate it.

     

    Regards,

    Mark

  10. 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.
  11. Unfortunately, it was only running for two hours...

     

    Oct  8 01:36:53  pulseway: curl_easy_perform() failed: Couldn't resolve host name

    Oct  8 01:36:53  pulseway: *** glibc detected *** /usr/sbin/pulsewayd: munmap_chunk(): invalid pointer: 0x00007f38d97fa740 ***

    Oct  8 01:36:53  pulseway: Got shutdown signal: 6

     

    Can you enable core dump on your machine? Will be great if we can analyse the crash.

     

    Mark.

  12. Hi Mark...

    No... I wasn't present, i have installed the package and Pulseway is now running..

    But please tell me, why this was'nt an issues before? - And how do i avoid this problem in the future..? - It's very unsettling, knowing that Pulseway stops working because of updates on your part...

     

    Libidn is part of default installation on all distributions (at least the ones that we test pulseway on). We'll do more investigation but libidn it's a dependence for pulseway package (like openssl, wget and ca-certificates).

     

    Mark

  13. Unfortunately, it was only running for two hours...

     

    Oct  8 01:36:53  pulseway: c

    Oct  8 01:36:53  pulseway: *** glibc detected *** /usr/sbin/pulsewayd: munmap_chunk(): invalid pointer: 0x00007f38d97fa740 ***

    Oct  8 01:36:53  pulseway: Got shutdown signal: 6

     

     

    Do you have any network issues? Looks like "curl_easy_perform() failed: Couldn't resolve host name" trigger the crash...and this point to a network issues.

     

    Mark

×
×
  • Create New...