At start I had a problem with start-stop-daemon that doesn't exist on CentOS 7 by default, than I overcome that and still I noticed that mqtt was not working, in fact I think it freezes emoncms when I create a process that sends data to the mqtt server.
I also noticed errors in emonhub log that are coincident with the time I tried to use mqtt, even with the mqtt_input process not running, maybe it sent something, or maybe it was due to the freezing of emoncms...
File "/home/pi/emonhub/src/interfacers/EmonHubEmoncmsHTTPInterfacer.py", line 121, in _send_post
response = urllib2.urlopen(request, timeout=60)
File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 401, in open
response = self._open(req, data)
File "/usr/lib/python2.7/urllib2.py", line 419, in _open
'_open', req)
File "/usr/lib/python2.7/urllib2.py", line 379, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 1211, in http_open
return self.do_open(httplib.HTTPConnection, req)
File "/usr/lib/python2.7/urllib2.py", line 1184, in do_open
r = h.getresponse(buffering=True)
File "/usr/lib/python2.7/httplib.py", line 1034, in getresponse
response.begin()
File "/usr/lib/python2.7/httplib.py", line 407, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.7/httplib.py", line 365, in _read_status
line = self.fp.readline()
File "/usr/lib/python2.7/socket.py", line 447, in readline
data = self._sock.recv(self._rbufsize)
timeout: timed out
How can I debug this.
Off-topic: is it easy to add the schedule module to the emoncms 8.5 in EmonPI?
Trouble using mqtt_input
Submitted by CidiRome on Wed, 09/12/2015 - 22:29Hi.
I'm have problems with mqtt. I want to send data to emonHUB in EmonPI but I think I'm having problems with the init script:
At start I had a problem with start-stop-daemon that doesn't exist on CentOS 7 by default, than I overcome that and still I noticed that mqtt was not working, in fact I think it freezes emoncms when I create a process that sends data to the mqtt server.
I also noticed errors in emonhub log that are coincident with the time I tried to use mqtt, even with the mqtt_input process not running, maybe it sent something, or maybe it was due to the freezing of emoncms...
How can I debug this.
Off-topic: is it easy to add the schedule module to the emoncms 8.5 in EmonPI?