Calin

If you got no response for cat /var/log/syslog | grep pcmonitor, it means you have no such errors. Can we get more details on your system : which os for raspberry , the output for uname -a , the config file you are using (remove sensitive data ) . Also make sure pcmonitor is running by issuing ps aux | grep pcmonitord

Hello, Can you check the logs with: cat /var/log/syslog | grep pcmonitor

Can you test to see if openssl is working ok : openssl s_client -connect wsn.pulseway.com:443

Hello, Do you guys connect to a dedicated PC Monitor Server ?

Hello, It will be fixed in the next native linux release

Are you launching as root ? Can you list us the content of /var/pcmonitor ?

The last output you included seems to point to some connection issues. When you said it died , did you mean crashed or was it just offline do to connection issues ?

Hello Stephen. Please give us more info about your machine . Result of uname -a and your config file (please remove sensitive information) would be useful.

Hello. Please give us more info about your machine . Result of uname -a and your config file (please remove sensitive information) would be useful.

I just asked your phone model to have a complete picture of your setup. Now let's divide this in 2 parts : 1. is your computer configured correctly for wake on lan. (a possible test solution is to send a magic packet from another computer or phone in the same lan . there are a lot of free apps available out there) 2. is the wake on wan port configured in pc monitor , and forwarded on the router (you can check the PC Monitor Manager and maybe install a sniffer like winshark to see if the packages arrive at the computer)

Hello, What mobile are you using to send the command. Is it in the same lan as the computer or over 3g ?

Hi, Can you post the result of the command uname -a. Also, please make sure that uname -c is set to unlimited , and send us the core file created in /var/pcmonitor. If that still doesn't work stop the abrtd daemon and try again

Hello, Please make sure you have the latest PC Monitor version installed.

Hello, Can you tell us if anything appears in the logs ? We log in the daemon facility, so if you have the default configuration cat /var/log/daemon.log | grep pcmonitor should let you see the logs.

We are working on it.

This features will be added in the next releases for the native agent. You can use the old (java based) one to monitor network interfaces for now.

You can try and delete HKEY_LOCAL_MACHINE\SOFTWARE\MMSOFT Design\PC Monitor\ComputerIdentifier value on one of the computers.

Yes, the features will be added in next releases

Please make sure you have the latest version. Download it again from site and remove and install the app again.

Supported Linux Distributions Debian based: Debian 6 or newer and Ubuntu 12.04 or newer RPM based: CentOS 6 or newer, Red Hat Enterprise Linux 6 or newer, Oracle Linux 6 or newer, Fedora 16 or newer Choosing the right package First step when installing is to choose the right package from http://www.pulseway.com/downloads. You should consider your Linux distribution (debian or rpm based) and if you have a 32 or 64 bit machine. To determine the latest use the Linux command: uname -m If the result of this command is something like i386,i586 or i686 then it's a 32bit machine if it's x86_64 then it's a 64bit machine. Installing Now , that you have downloaded the right install package you have to use one of 2 commands depending on the Linux distribution: dpkg -i <package name>.deb or rpm -ihv <package name>.rpm If all went well now you should have Pulseway installed on the machine. You should configuring the machine by creating a /etc/pulseway/config.xml file using the sample located at /etc/pulseway/config.xml.sample Example We will provide two examples , first will be a Debian 6 32 bit machine and the second a Fedora 17 64 bit machine 1. Debian 6 32 bit - package used http://www.pulseway.com/download/pulseway_x86.deb root@debian:~# uname -m i686 root@debian:~# wget http://www.pulseway.com/download/pulseway_x86.deb HTTP request sent, awaiting response... 200 OK Length: 747906 (730K) [application/octet-stream] Saving to: “pulseway_x86.deb” 100%[======================================>] 747,906 455K/s in 1.6s 2013-11-17 08:59:29 (455 KB/s) - “pulseway_x86.deb” saved [747906/747906] root@debian:~# dpkg -i pulseway_x86.deb Selecting previously deselected package pulseway. (Reading database ... 119503 files and directories currently installed.) Unpacking pulseway(from pulseway_x86.deb) ... Setting up pulseway(4.4) ... update-rc.d: using dependency based boot sequencing ****************************************************************** *** Beware, you must create the configuration file for Pulseway! *** We provide an example of complete configuration in *** /etc/pulseway directory (config.xml.sample). You can use it *** to create your own custom configuration and then *** start pulseway using command: /etc/init.d/pulseway start ***************************************************************** root@debian:~# 2. Fedora 17 64 - package used http://www.pulseway.com/download/pulseway_x64.rpm [root@fedora ~]# uname -m x86_64 [root@fedora ~]# wget http://www.pulseway.com/download/pulseway_x64.rpm HTTP request sent, awaiting response... 200 OK Length: 144460 (141K) [application/x-rpm] Saving to: `pulseway_x64.rpm' 100%[======================================>] 144,460 175K/s in 0.8s 2013-11-17 16:07:44 (175 KB/s) - `pulseway_x64.rpm' saved [144460/144460] [root@fedora ~]# rpm -ihv pulseway_x64.rpm ****************************************************************** *** Beware, you must create the configuration file for Pulseway! *** We provide an example of complete configuration in *** /etc/pulseway directory (config.xml.sample). You can use it *** to create your own custom configuration and then *** start pulseway using command: /etc/init.d/pulseway start ***************************************************************** [root@fedora ~]#

What device are you using ?

Also verify that the shutdown command is not hidden in the group policy.

Hello, The fact that wake up is working when you are on the home wifi proves that the Wake on LAN is working for that computer. Unfortunately , Wake on LAN works, as the name implies, on LAN . So, the solution is, you either have another device on that LAN (either the android phone when you issue the wake command or another computer with PC Monitor) or use Wake on WAN.

Hello, PCMonitor uses the ping command to determine latency times, but it only sends one package. If it displays a value of 24 that means that at some time the command ping <your address> returned a value of 24. But, the fact that you are getting a notification means that the threshold is constantly exceeded during x configured minutes. I am not sure why you are seeing this large gaps between PC Monitor and console. Could a firewall limit the number of requests per second maybe ? Are you running PCMonitor as root ? If not are there any limitations applied to that user ?

Is this issue happening since you created your account or just recently ? Did you changed your password (if yes from where).