Jump to content

Aaron Trujillo

Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by Aaron Trujillo

  1. We recently noticed a problem with our Pulseway notifications, on one of our Linux servers that is running Cassandra.  The Cassandra service had been put into the following state:  Active: active (excited), unfortunately we never received notification about the excited state.  I did some testing and when I manually stop the service, it shows Active: inactive (dead), I do get notifications.  I am at a lose as to why I get notifications when inactive (dead) but not when it is Active (excited).

    This is the current configuration:

    <Service Name="cassandra" DisplayName="cassandra" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="true" />

    If I change DaemonType to any other setting:  NONE, SYSVINIT, or UPSTART, the service will not be recognized at all by Pulseway.  So I am fairly confident that SYSTEMD is the correct parameter here.  What is the correct way to set this up, so that I get notifications when its dead and/or excited?

    Thank you for your help.

  2. Today i got a notification that read as the following: 

    Quote

    Hi Pulseway,

    The free space on the non-system disk drive D: on the computer 'GP1-PROD-FSVR01' in group 'Default' is below 20.0% (106.38 GB free of 999.99 GB)

    Regards,
    Pulseway Production

    I am not sure how this was set up in our configuration.  Is this an standard out of the box notification that is there regardless of set up or has it been set up to monitor disk space by someone on our end?  If so can you tell me how that is so?

    Thanks.

  3. Bottom line... can i change the computer identifier to something new?

    I am using a copy of a VM.vhdx to create a new secondary VM.  However, the computer identifier is the same on both after setting them up.  What do I need to do to create a new computer identifier?  Deleting and reinstalling Pulseway is not enough, it still shows up with the same one.  I assume somewhere deep in the registry I need to delete some things to stop this from happening.  

    Thanks

  4. So I copied a VM hard drive from one server to the next (lets say it was HDDx1), I just need to make a redundant VM (lets say it is HDDx2).  I have done this successfully many times but never on VMs that are monitored by Pulseway.  After I set up HDDx2, I did a system prep and reinstalled windows on it, gave it a new IP and name (I also renamed the copied VM HDD as well).  Everything seems fine, except for Pulseway.  It continues to send notifications that HDDx1 public IP has switched to HDDx2's IP and vice versa... What information can you provide to help me with this?  I have tried uninstalling and reinstall Pulseway but it continues.  I am not sure if I am fully uninstalling Pulseway though... any help would be appreciated.

  5. Can I get some step-by-step instruction for getting notification emails?  I have my email set in the account overview and the email notification tab checked... but i do not get any notifications by email...

    Thanks

  6. UPDATE

    When Kamailio is manually stopped (service kamailio stop) Pulseway will send a notification to me and the status shows:

    ‚óŹ kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server
       Loaded: loaded (/lib/systemd/system/kamailio.service; enabled)
       Active: inactive (dead) since Thu 2016-11-17 10:48:43 MST; 5s ago

    But when i kill one of the child process (kill -9 15489) Pulseway does not send notification and the status shows:

    ‚óŹ kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server
       Loaded: loaded (/lib/systemd/system/kamailio.service; enabled)
       Active: failed (Result: exit-code) since Thu 2016-11-17 10:45:01 MST; 3s ago

    Apparently what is happening is one of the child processes is being killed and this sends a message to kill all the processes and this obviously stops or kamailio service from working correctly...

    So why am I not getting notification when it is in a failed state?  Is there a way to fix it so that i do?

  7. Quote

    root@FOO:~# service kamailio status
    ‚óŹ kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server
       Loaded: loaded (/lib/systemd/system/kamailio.service; enabled)
       Active: active (running) since Thu 2016-11-17 06:24:17 MST; 1h 43min ago
      Process: 33393 ExecStart=/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY -u $USER -g $GROUP (code=exited, status=0/SUCCESS)
     Main PID: 33398 (kamailio)

     

    My Kamailio has gone down twice in the last two weeks and i have not been getting notifications through Pulseway.  Above is the Kamailio service in a running state and below is my configuration set up, for that service to be monitored.  

    Quote

      <!--Monitored Services-->
      <MonitoredServices>
        <!--Service
          - Name: service name
          - DisplayName: friendly name used for display
          - IsDaemon: 'true' if the monitored service is a daemon and 'false' if the monitored service is a process
          - DaemonType: system management daemon type: NONE, SYSVINIT, UPSTART or SYSTEMD
          - Path: path of the monitored service (this is used when the monitored service is a process)
          - StartParameters: parameters used to start the monitored service (this is used when the monitored service is a process)
          - CanBeStopped: 'true' or 'false'-->
        <Service Name="cups" DisplayName="CUPS Service" IsDaemon="true" DaemonType="SYSVINIT" Path="" StartParameters="" CanBeStopped="true" Enabled="false" />
        <Service Name="ntpd" DisplayName="NTPD Process" IsDaemon="false" DaemonType="NONE" Path="/usr/sbin/ntpd" StartParameters="-p /var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf" CanBeStopped="true" Enabled="false" />
        <Service Name="ssh" DisplayName="SSH/Jenkins" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="true" />
        <Service Name="SuSEfirewall2.service" DisplayName="SuSE Firewall Service" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="false" />
        <Service Name="kamailio" DisplayName="Kamailio (OpenSER)" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="true" />
        <Service Name="keepalived" DisplayName="keepalived" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="true" />
        <Service Name="nodejs" DisplayName="nodejs" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="true" />
      </MonitoredServices>

    Any guidance in fixing this problem would be greatly appreciated.

  8. After installing some new software (not related to Pulseway) a reboot was required.  As it happens, the server went down and no notifications were sent out.  Looking at the Pulseway manager it looked like it was monitoring the server, however i got NO notifications about the downed server.  When i ran a service pulseway restart... i quickly got a notification that the server was on-line.  That seemed to resolve the problem.

    My question is why does Pulseway not automatically do a restart when the machine is rebooted?  Is this something i need to do every time a server is rebooted?  I use Jenkins when i need to run mass jobs on our servers.  Should i create a job that restarts the Pulseway service daily to avoid this from happening again?  The only downfall with that is i don't want daily notifications that the server us up and running like it would send with the restart.

    Any thoughts would be greatly appreciated.

  9. When a specific service goes down, i am getting the appropriate notifications; however, when it comes back on-line i am not getting any notifications.  I would like to know when the server goes down but also when it comes back up... any ideas?

  10. I hope that this will be a simple question to resolve.  I need to enable repeat notifications that are sent to my phone.  If i miss a  notification and i may never know it is there if i dont get follow up notifications.  How do i set this up to allow repeat notifications that are sent to my phone app?

  11. I am setting up the Ping Notification feature and need some insight into how it works.  

    My understanding is that it pings the selected device every 5 seconds.  Is this a consistent 5 seconds for as long as i have the device added to the ping feature?  I don't know that i need it to ping every 5 seconds (can this be changed)

    300ms for 1 minute, i dont understand this... how often is it checking the device?

    Any help would be appreciated,

    Thanks.

  12. I am new to SNMP and I'm having a little trouble getting set up.  I understand that SNMP works by trapping signals sent from the Agent and they are sent to the Master.  I don't see any 'trapping" in the Pulseway set up.  I have successfully discovered a test device and have been able to pull up the MIB/OID list.  This list however makes very little sense to me as it doesn't explain what I am trying to monitor.  

    Could somebody give me some depth in this subject.  What is Pulseway monitoring exactly? How do i determine what the OID is?  Is there any trapping actually going on?  Any info would be greatly appreciated!!!

    Thanks,

    Aaron

  13. I have MegaRaid controller cards in several of my servers.  On my Windows servers I can use an app called MegaRaid Manager that logs errors and other info to the application event log that Pulseway monitors for me wonderfully.  However, on my Linux servers the app different, it is called StorCLI.  I can get plenty of information from this and even have a log generated but I don't know how to get Pulseway configured to monitor it.  

    Any help would be appreciated,

    Thanks,

    Aaron

  14. That is my thought also.  Let me give some context to the situation.  (I came into this with most of it already set up) So there are 7 user accounts, the first one is pulseway.agent.  The other 6 user accounts are associated with this pulseway.agent (we have to select pulseway.agent, then our account, then we can edit our systems to manage) I wonder if, because we are associated with pulseway.agent (who is monitoring all systems) we are getting all notifications regardless of what our account is monitoring?

  15. We have 55 machines that are being monitored by pulseway for various things.  Of the 55 I am only responsible for about 36 of them.  In my system tray it only shows the 36 I'm managing, however I still get notifications for the other servers and another member of our team that is managing the other half still gets notifications when my machines go down.  How can we make it so that we are not getting notifications for each others servers?

    Thanks,

    Aaron Trujillo

  16. On 9/7/2015 at 4:03 AM, Martin Stevnhoved said:

    Hi.

    My response was a bit short, because I wrote from the phone :-)

    But is it possible to get notifications when a managed schedule task fails?

    Best Regards,
    Martin Stevnhoved

    Is there an answer to this question????

  17. 2 hours ago, Mark said:

    Hi Aaron,inal and type:

    
    systemctl status haproxy
    systemctl status keepalived
    systemctl status nodejs

     

     

     

    It looks like all it needed was a simple reboot to get the service recognized in the manager.  I am now able to start and stop services from the manager but when I stop a service  I am NOT getting notifications.  All other notifications work  properly...

    Any other advice?

  18. root@GP1-STG1-APPLB1:~# systemctl status haproxy
    ‚óŹ haproxy.service - HAProxy Load Balancer
       Loaded: loaded (/lib/systemd/system/haproxy.service; enabled)
       Active: active (running) since Fri 2016-07-01 08:17:54 MDT; 8min ago
         Docs: man:haproxy(1)
               file:/usr/share/doc/haproxy/configuration.txt.gz
      Process: 893 ExecStartPre=/usr/sbin/haproxy -f ${CONFIG} -c -q $EXTRAOPTS (code=exited, status=0/SUCCESS)
     Main PID: 901 (haproxy-systemd)
       CGroup: /system.slice/haproxy.service
               ‚Ēú‚ĒÄ901 /usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid
               ‚Ēú‚ĒÄ904 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -Ds
               ‚ĒĒ‚ĒÄ905 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -Ds
    
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11)
    Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11)
    root@GP1-STG1-APPLB1:~# systemclt status nodejs
    -bash: systemclt: command not found
    root@GP1-STG1-APPLB1:~# systemctl status nodejs
    ‚óŹ nodejs.service - Total.Care NodeJs App
       Loaded: loaded (/etc/systemd/system/nodejs.service; enabled)
       Active: active (running) since Fri 2016-07-01 08:17:52 MDT; 9min ago
     Main PID: 568 (node)
       CGroup: /system.slice/nodejs.service
               ‚ĒĒ‚ĒÄ568 /usr/bin/node /home/totalcare/app.js
    
    Jul 01 08:17:56 GP1-STG1-APPLB1 node[568]: Example app listening on port 3000!
    ‚óŹ keepalived.service - LSB: Starts keepalived
       Loaded: loaded (/etc/init.d/keepalived)
       Active: active (running) since Fri 2016-07-01 08:17:54 MDT; 8min ago
      Process: 579 ExecStart=/etc/init.d/keepalived start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/keepalived.service
               ‚Ēú‚ĒÄ887 /usr/sbin/keepalived
               ‚Ēú‚ĒÄ888 /usr/sbin/keepalived
               ‚ĒĒ‚ĒÄ889 /usr/sbin/keepalived
    
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_healthcheckers[888]: Opening file '/etc/keepalived/keepalived.conf'.
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: Configuration is using : 63098 Bytes
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_healthcheckers[888]: Configuration is using : 6229 Bytes
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: Using LinkWatch kernel netlink reflector...
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_healthcheckers[888]: Using LinkWatch kernel netlink reflector...
    Jul 01 08:17:54 GP1-STG1-APPLB1 keepalived[579]: Starting keepalived: keepalived.
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: VRRP_Script(chk_haproxy) succeeded
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: VRRP_Instance(VI_1) Transition to MASTER STATE
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: VRRP_Instance(VI_1) Received higher prio advert
    Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: VRRP_Instance(VI_1) Entering BACKUP STATE

     

  19. How can I tell if the service is being monitored on a Linux server without actually killing the service and getting the notification?  On a windows machine it clearly states in the system pulseway manger via the monitored services tab...  There is no such tab on my Linux system pulseway manger.  I have configured my conf file for pusleway to monitor the selected services.

    Capture.PNG

    config.PNG

  20. Hi Paul, thanks for your response.

    I am having trouble installing my config file.  I am using the following code.

    "\\GP1-LAB-FSVR01\Software\Pulseway Agent\Windows\Pulseway_x64.msi" ALLUSERS=1 /qn username=???????? password=????????? group=Default server=????????
    shortcut /a:c /f:"c:\users\me\desktop\myshortcut.lnk" /t:"c:\Program Files\Pulseway\PCMonitorManager.exe"
    "C:\Program Files\Pulseway\PCMonitorManager.exe" /config="\\GP1-LAB-FSVR01\Software\Pulseway Agent\Windows\Configuration\NoPassword.pcmcfg"
    EXIT 0

    What am i doing wrong?  

  21. I want to send a batch file command through jenkins that will alter the config files for all the windows machines (i do this easily on my Linux machines).  Reading through the documents here i see instructions for importing config files but that is it.  Am i supposed to create my own config file and import it into my pulseway file?  If so how do i go about this, I am having trouble understanding where to go from here.

    Thanks,

    Aaron

×
×
  • Create New...