Mark

Hi, There is anything in logs? (/var/logs/messages)? Regards, Mark

Hi Dennis, Can you, please, check if you have libidn installed? sudo apt-get install libidn11 Regards, Mark

Hi, Arch package will be available for the next Linux release (due in next few days). Regards, Mark

Hi, Thank you for your reply! We'll try to replicate the issue. (although 32 bits OS are very uncommon this days ) Future releases will add new functionality (all functionality from java client will be available in native client). Regards, Mark

Hi, If you installed the 32-bit version of Ubuntu, it won't recognize over 4GB of memory. You will need to install the 64-bit version of Ubuntu for the system to recognize more than 4GB of memory. You have three solutions: install a 64-bit kernel on your i386 installation install a 32-bit kernel with PAE activated reinstall a complete 64-bit system Regards, Mark https://help.ubuntu.com/community/32bit_and_64bit

Hi, Pulseway comming with a sample configuration file (/etc/pulseway/config.xml.sample). Please check http://forum.pulseway.com/topic/1219-sample-configxml/ You'll find there, under MonitoredServices tag, every parameter explained plus some examples: <MonitoredServices> <!--Name: Service name--> <!--DisplayName: Friendly Display Name--> <!--IsDaemon: 'true' or 'false'. 'true' if the monitored service is a daemon and 'false' if the monitored service is a process--> <!--DaemonType: System Management daemon type: NONE or SYSVINIT or UPSTART or SYSTEMD--> <!--Path: The 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'--> <!--Enabled: 'true' or 'false'--> <Service Name="cups" DisplayName="CUPS Service" IsDaemon="true" DaemonType="SYSVINIT" Path="" StartParameters="" CanBeStopped="true" Enabled="false"/> <Service Name="ssh" DisplayName="SSH Daemon" IsDaemon="true" DaemonType="UPSTART" Path="" StartParameters="" CanBeStopped="true" Enabled="false"/> <Service Name="SuSEfirewall2.service" DisplayName="SuSE Firewall Service" IsDaemon="true" DaemonType="SYSTEMD" 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"/> </MonitoredServices> Regards, Mark

Hi, Correct configuration for sshd service on Fedora is: <Service Name="sshd.service" DisplayName="SSH Daemon" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="true"/> Regards, Mark

Hi, Reading your logs, looks like there is an issue with your config file: sie 01 16:50:02 sonic pulseway[7568]: Configuration: expected element name Best Regards, Mark

Hi, Please send your log to support@pulseway.com. Thanks! Regards, Mark

Hi, I just install it on a fresh Fedora 20 and everything works as expected. Please check your log for any possible error or your config file. Regards, Mark [root@localhost ~]# uname -a Linux localhost.localdomain 3.11.10-301.fc20.x86_64 #1 SMP Thu Dec 5 14:01:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root@localhost ~]# cat /etc/issue Fedora release 20 (Heisenbug) Kernel \r on an \m (\l) [root@localhost ~]# [root@localhost ~]# rpm -ihv pulseway-4.4.3-1.x86_64.rpm Preparing... ################################# [100%] Stopping pulseway service done Updating / installing... 1:pulseway-4.4.3-1 ################################# [100%] [root@localhost ~]# systemctl start pulseway.service [root@localhost ~]# systemctl status pulseway.service pulseway.service - LSB: start and stop pulsewayd Loaded: loaded (/etc/rc.d/init.d/pulseway) Active: active (running) since Thu 2014-07-31 21:46:34 IST; 20s ago Process: 2289 ExecStop=/etc/rc.d/init.d/pulseway stop (code=exited, status=0/SUCCESS) Process: 2733 ExecStart=/etc/rc.d/init.d/pulseway start (code=exited, status=0/SUCCESS) CGroup: /system.slice/pulseway.service 2738 /usr/sbin/pulsewayd Jul 31 21:46:34 localhost.localdomain pulseway[2733]: Starting pulseway daemo... Jul 31 21:46:34 localhost.localdomain systemd[1]: Started LSB: start and stop... Hint: Some lines were ellipsized, use -l to show in full. [root@localhost ~]# ps auxww|grep '[p]ulsewayd' root 3295 0.2 0.5 360032 5224 ? Ssl 21:48 0:00 /usr/sbin/pulsewayd [root@localhost ~]#

Thanks! We'll investigate it! Regards, Mark

Last...system update? Mark

Hi, Thank you for let us know! Did you update your system recently? Is it possible to link this behaviour to any system update? (Glibc, Gcc, Openssl). What versions of glibc, gcc and openssl do you have installed? Many thanks! Mark

Hi, 'Name' can be modified editing 'Computer Information' section from config.xml (/etc/pulseway/config.xml): <!--Computer Information--> <!--Name: the name you want this computer to be listed as (Default: Linux computer name)--> <!--Group: the name of the group you want this computer to be listed in (Default: "Default")--> <ComputerInformation Name="" Group="" /> Regards, Mark

Hi, First step will be to check logs for any errors. Regards, Mark

Hi, Unfortunately SuSE 10 is not supported. Regards, Mark

Hi, Thanks! Armada 300 is quite old (370 and newest 375 replace it) but when time will allow us we'll look into this. Stay close and watch the newsletter. Mark

Hi, There are minimum requirements for native client: openssl 0.9.8j , kernel 2.6.32, glibc 2.9. Most of the armv5 systems are outdated: 2.6.16 kernel, glibc 2.5. Mark

Hi, "pcmonitord" is the name of the binary. "pcmonitor" is the name of service script. Starting the service with "pcmonitord start" it's in fact a hack. The install process should register "pcmonitor" as a service script. The PCMonitor package does not support Gentoo systems yet. This does not mean it is not running fine on Gentoo. (or Slackware, or Arch) Regards, Mark

Hi, Gentoo is not supported yet but we're working on this and soon we'll have packages for Gentoo, Slackware and Arch. Regards, Mark

Must be an issue with permisions. I've installed an vanilla CentOS 6.4 in vm, install pcmonitor and started with no issues. Regards, Mark

That's strange. Just to rule out any local issues: - Kill the web server on 443 - Make it listen on port 80 - Start the web server again - Check the logs and make sure there are no issues - Do a telnet localhost 80 to be sure that the port is open - Change pcmonitor to monitor port 80 - Check if port is correctly displayed as open. - Change pcmonitor to monitor website on localhost port 80 - Check if webpage response is 200 - If everything ok change the web server to port 443 and repeat these steps. Regards, Mark

Hi, According to your log looks like you have some local issues: servermgrd[70165]: Got error -9805 for SSLHandshake remote address is 127.0.0.1:44765 Server[39262]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9812) servermgrd[70165]: Exception in SessionController threadListen: Socket: Connect failed com.mobilepcmonitor.PCMonitorHelper[8566]: NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9812) PCMonitorHelper[8566]: --> port:443 on hostname:localhost is closed pcmonitor throw same kCFStreamErrorDomainSSL error like servermgrd(ServerAdmin) and Server processes. Port monitor corectly response back with "close" port status. Can you, please send us screenshots (from mobile device) with port monitor and web site monitor ? Regards, Mark

Hi, I replicate same env with apache running on 443 and port monitor and web monitor set up and I have no issues. Can you, please, try this: 1. close PCMonitor ('Hide' option from context menu) 2. open Terminal and type: sudo launchctl remove com.mobilepcmonitor.PCMonitorHelper 3. open Console and clear it 4. open PCMonitor agent. 6. copy and send Console output (check as well if any PCMonitor .crash file under Diagnosis and Usage Information) to support@pulseway.com. Thanks! Mark

Hi, Can you, please, try this: 1. close PCMonitor ('Hide' option from context menu) 2. open Terminal and type: sudo launchctl remove com.mobilepcmonitor.PCMonitorHelper 3. open Console and clear it 4. open PCMonitor agent. 6. copy and send Console output (check as well if any PCMonitor .crash file under Diagnosis and Usage Information) to support@pulseway.com. Thanks! Mark