pigpiod does not repsond to python test app about pigpio HOT 10 CLOSED

It's as if the daemon isn't running. That is the most likely explanation. I've just tried the same with Python 3.4 and have opened a socket manually and via the pigpio Python module.

N.B. I'm using a new version of the Python module which instantiates a class for each Pi (so more than one Pi can be controlled from one Python script).

joan@soft /ram $ sudo pigpiod
joan@soft /ram $ pigs t
740687050
joan@soft /ram $ pigs t
743243930
joan@soft /ram $ python3.4
Python 3.4.1rc1 (default, May 5 2014, 20:18:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.

import pigpio
local = pigpio.pi()
local.get_current_tick()
796894514
local.get_current_tick()
798635451
local.get_hardware_revision()
2
import socket
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.connect(('localhost', 8888))
s
<socket.socket fd=5, family=AddressFamily.AF_INET, type=SocketType.SOCK_STREAM, proto=0, laddr=('127.0.0.1', 37841), raddr=('127.0.0.1', 8888)>

joan@soft /ram $ pigs t
914567397
joan@soft /ram $

I suggest you use pigs to confirm the daemon is running.

from pigpio.

Here is my system setup: Ubuntu 12.04, Python 3.2, latest pigpio from github installed

I checked the process via ps

ps aux
[...]
root      9565 18.3  1.2  13552  5764 ?        SLsl 12:21   0:00 pigpiod
[...]

Result using pigs (after a long waiting time)

$ pigs t
connect failed

Using your code snippet

>>> import pigpio
>>> p = pigpio.pi()
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Can't connect to pigpio on localhost(8888)

Did you start the pigpio daemon? E.g. sudo pigpiod

Did you specify the correct Pi host/port in the environment
variables PIGPIO_ADDR/PIGPIO_PORT?
E.g. export PIGPIO_ADDR=soft, export PIGPIO_PORT=8888

Did you specify the correct Pi host/port in the
pigpio.pi() function? E.g. pigpio.pi('soft', 8888))
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>>> import socket
>>> s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
>>> s.connect(('localhost', 8888))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
socket.error: [Errno 110] Connection timed out

It looks like the daemon is running but not responding whatsoever...strange

from pigpio.

Ubuntu?

So you are running the pigpio Python module on a PC and connecting to the pigpio daemon running on a Pi?

You need to specify the name or IP address of the Pi running the daemon. Either as an argument to pigpio.start() (or pigpio.pi() if using the latest, 16, version of the library) or by setting the PIGPIO_ADDR environment variable.

export PIGPIO_ADDR=soft

from pigpio.

Sorry for the mistake and confusion: the pigpiod daemon and the python program are both executed on the RPi (running Raspbian). I am working within an ssh session from an Ubuntu 12.04 machine.

from pigpio.

Is the current situation that pigpiod is running but is not responsive?

Does pigs work? It uses the same socket interface as the Python module.

pigs t # show current tick
pigs pigpv # show library version
pigs hwver # show Pi's hardware revision

Does

cat /dev/pigerr&

spit out any error messages?

Use

sudo killall -USR2 pigpiod
sudo killall -USR2 pigpiod
sudo killall -USR2 pigpiod
sudo killall -USR2 pigpiod
sudo killall -USR2 pigpiod

to bump the internal debug level.

sudo killall -USR1 pigpiod
sudo killall -USR1 pigpiod
sudo killall -USR1 pigpiod
sudo killall -USR1 pigpiod
sudo killall -USR1 pigpiod
sudo killall -USR1 pigpiod

to reverse the process.

Do

./x_pigs
./x_pipe

work?

from pigpio.

Hi Joan,
sorry for my late response: I had to set up and configure my RPi from scratch after a gpio-unrelated system crash. The good news: after re-installing everything, I did clone the current repo, did a make, make install, started the pigpiod daemon and voila: the daemon is running and responding. Unfortunately I have no idea why it didn't work before I had to re-install everything.

Thanks a lot for your support and immediate responses. I am looking forward to finally implement my little servo project. If I somehow find out why this all happened, I let you know.

Cheers,
Jonas

from pigpio.

Hi Jonas,

In that case I'll close this as an issue. If the problem reappears we can start a new issue.

Regards,

from pigpio.

Hi, so I know this issue is closed, but I wanted to comment incase other encounter it.

I was struggling with this quite a bit and only solved it after working with another program and realizing I couldn't ping localhost. It turns out when I had followed a guide to setting up an automatic wlan network (this is the culprit: http://weworkweplay.com/play/automatically-connect-a-raspberry-pi-to-a-wifi-network/), I had turned off the loopback network. So pigpiod would still run and listen on a port just fine, but the scripts could never open a socket and reach it. I believe this is why Jonas's issue was resolved by a reinstall.

In any case, to others who encounter this: make sure that there's a "LOOPBACK" network appearing when you type "ifconfig." If not, check that there's a line "auto lo" in your /etc/network/interfaces file. Here's an article that helped me: https://scottlinux.com/2012/06/09/cant-ping-localhost-in-linux/

from pigpio.

Thanks for that information. It's something I wasn't aware of and I'll try to bear it in mind if I come across the same problem again.

from pigpio.

@lucentbeam Thanks for your post, I followed the same wifi tutorial and had the same problem. Your post saved me from having to settle on RPi.GPIO pwm, thanks!

from pigpio.