Jump to content

ChrystalSolutions

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by ChrystalSolutions

  1. I have some questions about functionality on Linux. If these things can be done, and I missed something, please share.  If these things aren't possible, then they should be considered as feature requests.

    • Scheduled Maintenance: Linux servers have scheduled maintenance as well.  We need a way set a maintenance window on Linux servers.  I considered writing a script to modify the maintenance settings in config.xml, and schedule it in crontab for the beginning and end of maintenance window.  However, if the server were to not come back during the maintenance window, then a notification will not be sent, so this is a flaw.
    • Rules: It would be helpful to be able to write/assign scripts (possibly from the Pulseway script library, or just local on the machine) to run when certain events happen.
    • File Content Monitors: It would be very helpful to be able to create a plugin for Pulseway that monitors the contents of one or more specific files, then they could be displayed in the Pulseway app, along with it's values.  For example, we could script the power values from a UPS, and then display the voltage, battery remaining, status, etc.
    • Remote configuration:   We should be able to set the configuration options from the GUI on a Windows machine, at least for the functionality that's supported on Linux.
  2. I must say that after almost years, it is disappointing that this is still the case.  While I use Pulseway on Android on mobile, when I am on my desktop or laptop, I use the Pulseway Windows 10 app.  I understand that Windows Mobile is pretty much dead, but it's sad that Pulseway has neglected the Windows 10 app. 

  3. 30 minutes ago, windracer said:

    Having the same problem on a fresh install of Raspbian Strech Lite on my Raspberry Pi:

    
    Sep  7 22:21:21 pidp8 pulseway[11554]: /usr/sbin/pulsewayd: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

    Is there a way to fix this other than downgrading libssl?
     

     

    This is exactly what I'm working with.  I deployed a Pi on a client site and I want to monitor it.

    On ‎9‎/‎4‎/‎2017 at 7:22 AM, Chris said:

    Hi,

    I have installed the Debian GNU/Linux 9.0 (stratch) on one of mine VM's and the issue was with libssl1.0.1.

    As soon as I installed libssl0.9.8 the Pulseway service was started without any errors.

    wget http://snapshot.debian.org/archive/debian/20110406T213352Z/pool/main/o/openssl098/libssl0.9.8_0.9.8o-7_amd64.deb

    Please check this article.

     

    Thank you for this Chris.  Do you know where we can get the ARMHF version of this package in version 0.9.8?
    I searched on the page https://www.debian.org/distrib/packages  and came up empty.

    I also tried:  sudo apt-get install libssl0.9.8 but the response was:

    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Package libssl0.9.8 is not available, but is referred to by another package.
    This may mean that the package is missing, has been obsoleted, or
    is only available from another source
    E: Package 'libssl0.9.8' has no installation candidate
    

    It would be really great if Pulseway would accept the latest version of openSSL.  Is that possible?

  4. Hi I know this is an old post, but maybe this suggestion would be helpful.

    You find out what ports that database uses, and then set Pulseway to monitor those ports.  Chances are, if the application hangs, then it won't respond on those network ports.

    Hope that is helpful.

    -Dan

  5. Hi Martin & Kavaa,  I would suggest you create a Event Log rule in Pulseway to look for failed scheduled tasks.  When a task runs or doesn't run, Windows puts something in a system event log.  In Pulseway, create a rule in Notification > Event Logs.

    The log you are looking for is Microsoft Windows Task Scheduler\Operational.  In Pulseway, scroll way down the list of available logs.  It's a bit further down.

    This will pick up anything that fails to run because of an error (such as locked files, missing files, bad path, locked user accounts, etc).  If you are using scripts for your batch jobs, I also recommend adding something to the scripts that creates a custom entry in the Windows Application log as to the status of the script itself.  Then you can create another rule in Pulseway to look for those custom log entries.

  6. For Windows machines, I have found that the wake up command needs a few things to work.  First, the system being woken up must be connected via a wired network connection.  WOL usually doesn't work over a WLAN connection.  (This may be possible, but none of my system support WOL over WLAN)   Second, there must be another system on the same network to send the WOL packet.  So either my monitoring device (tablet or phone) must be on the same network, or there must be another system monitored by Pulseway on the same network.  So for example, if I have two monitored systems on the same network, and one is  asleep, I can send a wake up command from my phone over cellular data from outside that network.  If there is only one monitored system on a network, and my phone is not connected to the same network, I cannot wake it up.

    There are just what I've figured out on my own, but hopefully this will be helpful to you.

     

  7. Another suggestion would be to setup a scheduled task in Windows to run that batch file.  Then you could trigger that batch file to run it when you want to.  This method has the added bonus of being able to specifiy the user context that the batch file runs under.

×
×
  • Create New...