Jump to content

raspberry pi pcmonitor status FAIL


Recommended Posts

Posted

Greetings...I have installed and configured the pcmonitor service and config file as per instructions and when I start the service all looks well but when I type in status command I get 

 
root@raspberrypi:~# /etc/init.d/pcmonitor status
[FAIL] pcmonitor is not running ... failed!
 
 
But when I type in restart command it look good
 
root@raspberrypi:~# /etc/init.d/pcmonitor restart
[ ok ] Restarting pcmonitor: pcmonitor.
 
I do not see the system listed obviously on my account.
 
Any help would be appreciated

 

Posted

I am a Linux noob...

I entered the text and it went to a prompt with no response.  I then changed my directory to cd var log and did a vi on syslog and there is a lot of data in there.  Do you want to see that here?

Posted

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

  • 3 weeks later...
Posted

Hey mhsears1!

 

What would that second place to fill in username/password be? I have the same problem you described, and I can't find another instance to fill in login data in the config file. Thanks!

 

E.

  • Staff
Posted

There is no "second place to fill in username/password".

In config.xml this is the only place where you need to put credentials :

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

 

Mark

  • 3 months later...
Posted

 

Greetings...I have installed and configured the pcmonitor service and config file as per instructions and when I start the service all looks well but when I type in status command I get 

 
root@raspberrypi:~# /etc/init.d/pcmonitor status
[FAIL] pcmonitor is not running ... failed!
 
 
But when I type in restart command it look good
 
root@raspberrypi:~# /etc/init.d/pcmonitor restart
[ ok ] Restarting pcmonitor: pcmonitor.
 
I do not see the system listed obviously on my account.
 
Any help would be appreciated
login as: pi
pi@192.168.2.214's password:
Linux raspi 3.12.19+ #682 PREEMPT Mon May 12 23:27:36 BST 2014 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jun  6 01:59:33 2014 from tfk1.fritz.box
pi@raspi ~ $ /etc/init.d/pulseway start
pi@raspi ~ $ /etc/init.d/pulseway status
[FAIL] pulseway is not running ... failed!
pi@raspi ~ $ /etc/init.d/pulseway status
[FAIL] pulseway is not running ... failed!
pi@raspi ~ $ /etc/init.d/pulseway start
pi@raspi ~ $ /etc/init.d/pulseway status
[FAIL] pulseway is not running ... failed!
pi@raspi ~ $ /etc/init.d/pulseway status
[FAIL] pulseway is not running ... failed!
pi@raspi ~ $ /etc/init.d/pulseway start
pi@raspi ~ $ /etc/init.d/pulseway status
[FAIL] pulseway is not running ... failed!
pi@raspi ~ $ pulseway
-bash: pulseway: Kommando nicht gefunden.
pi@raspi ~ $ /etc/init.d/pulseway stop
pi@raspi ~ $ /etc/init.d/pulseway status
[FAIL] pulseway is not running ... failed!
pi@raspi ~ $ /etc/init.d/pulseway start
pi@raspi ~ $ /etc/init.d/pulseway status
[FAIL] pulseway is not running ... failed!
pi@raspi ~ $

pi@raspi ~ $ pulseway start
-bash: pulseway: Kommando nicht gefunden.
pi@raspi ~ $ ^C
pi@raspi ~ $ /etc/init.d/pulseway start
pi@raspi ~ $
pi@raspi ~ $ cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xml
cp: reguläre Datei „/etc/pulseway/config.xml“ kann nicht angelegt werden: Keine                                                                              Berechtigung
pi@raspi ~ $ sudo cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xml
pi@raspi ~ $ sudo nano /etc/pulseway/config.xml
pi@raspi ~ $ sudo cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xml
pi@raspi ~ $ sudo nano /etc/pulseway/config.xml
pi@raspi ~ $ sudo nano /etc/pulseway/config.xml
pi@raspi ~ $ sudo nano /etc/pulseway/config.xml
pi@raspi ~ $ sudo nano /etc/pulseway/config.xml
pi@raspi ~ $ cat /var/log/syslog | grep pcmonitor

pi@raspi ~ $ cat /var/log/syslog | grep pulseway
Jun  6 02:01:52 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:06:22 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:17:45 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:28:17 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:45:26 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
pi@raspi ~ $ cat /var/log/syslog | grep pulseway
Jun  6 02:01:52 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:06:22 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:17:45 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:28:17 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:45:26 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
pi@raspi ~ $ cat /var/log/syslog | grep pulseway
Jun  6 02:01:52 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:06:22 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:17:45 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:28:17 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
Jun  6 02:45:26 raspi pulseway: Error acquiring unique lock. Another process may use the file. Code: 9, Bad file descriptor
pi@raspi ~ $ cat /var/log/syslog | grep pulseway

 

o/ i have too the aktion  here is a screendump from my aktiv putty  term

 

i dont have any servers here what the config asked, need i a server or why cant start this tools for my raspi ?

 

pls help me to run my raspi with pulseway for send status

mails from my robot ^^

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...