Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pimatic frequent crash : how to debug? #443

Closed
Yves911 opened this issue Dec 31, 2014 · 37 comments

Comments

@Yves911
Copy link
Contributor

commented Dec 31, 2014

my pimatic installation crash very often since about 1 week.

My setup is the following :

  • pimatic running on a raspberry pi (model B)
  • pimatic is connected to an arduino with homeduino
  • the raspberry pi filesystem is on an external disk (to avoid SD corruption things)
  • node.js version is v0.10.24

To enable debugging i have the following params into the pimatic config:

"settings": {
    "debug": true,
    "logLevel": "debug"

Unfortunately i have random crashes, for examples

20:49:34.207 [pimatic-homeduino] received: [ 688, 1970, 4264, 10088 ] 020102010201010202010201020101020201010202010102010201020201020101020201010202010201020102010201020102010201020102010201010202010102010201020201020102010102010202010102020101020201020102010201020103
20:49:34.251 [pimatic-homeduino] generic:  { id: 1111, type: 2, positive: true, value: 378528 }
20:49:42.920 [pimatic-homeduino] data: "RF receive 552 2105 4265 8452 0 0 0 0 0101020101010101020201010102010101010202010101020101010201010102010201010101010102010303"
20:49:42.961 [pimatic-homeduino] received: [ 552, 2105, 4265, 8452 ] 0101020101010101020201010102010101010202010101020101010201010102010201010101010102010303
20:49:43.005 [pimatic-homeduino] weather3:  { id: 131, channel: 2, temperature: -0.2, humidity: 84 }
20:49:43.085 [pimatic-homeduino] data: "ERR checksum_error"
20:49:43.137 [pimatic-homeduino] got checksum_error while reading dht sensor, retrying: 0 of 5
20:49:43.378 [pimatic-homeduino] data: "RF receive 520 2139 4299 8452 0 0 0 0 0101020101010101020201010102010101010202010101020101010201010102010201010101010102010303"
20:49:43.420 [pimatic-homeduino] received: [ 520, 2139, 4299, 8452 ] 0101020101010101020201010102010101010202010101020101010201010102010201010101010102010303
20:49:43.462 [pimatic-homeduino] weather3:  { id: 131, channel: 2, temperature: -0.2, humidity: 84 }
20:49:45.692 [pimatic-homeduino] data: "ACK 19.1 55.3"
20:49:51.066 [pimatic-homeduino] data: "RF receive 688 4264 1971 10088 0 0 0 0 010201020102020101020102010202010102020101020201020102010102010202010102020101020102010201020102010201020102010201020102020101020201020102010102010201020201020101020201010202010102010201020201020103"
20:49:51.109 [pimatic-homeduino] received: [ 688, 1971, 4264, 10088 ] 020102010201010202010201020101020201010202010102010201020201020101020201010202010201020102010201020102010201020102010201010202010102010201020201020102010102010202010102020101020201020102010102010203
20:49:51.153 [pimatic-homeduino] generic:  { id: 1111, type: 2, positive: true, value: 378531 }
20:49:54.753 [pimatic-homeduino] data: "ACK 19.1 55.3"
20:50:04.556 [pimatic-mobile-frontend] rendering theme: graphite/water
coffee-cache: compiling coffee-script file "themes/graphite/water.coffee"...Done
coffee-cache: compiling coffee-script file "themes/graphite/base.coffee"...Done
20:50:05.805 [pimatic-homeduino] data: "PING"
20:50:10.134 [pimatic-mobile-frontend] rendering theme finished
20:50:10.307 [pimatic-homeduino] data: "RF receive 688 4264 1969 10092 0 0 0 0 010201020102020101020102010202010102020101020201020102010102010202010102020101020102010201020102010201020102010201020102020101020201020102010102010201020201020101020201010202010102010202010201020103"
20:50:10.335 [pimatic-homeduino] received: [ 688, 1969, 4264, 10092 ] 020102010201010202010201020101020201010202010102010201020201020101020201010202010201020102010201020102010201020102010201010202010102010201020201020102010102010202010102020101020201020101020102010203
20:50:10.399 [pimatic-homeduino] generic:  { id: 1111, type: 2, positive: true, value: 378535 }
20:50:12.032 [pimatic-homeduino] data: "RF receive 532 1914 3924 7800 0 0 0 0 0101020201020102010101010101010102020201010201020102010102010101020201010101010102010303"
20:50:12.089 [pimatic-homeduino] received: [ 532, 1914, 3924, 7800 ] 0101020201020102010101010101010102020201010201020102010102010101020201010101010102010303
20:50:12.147 [pimatic-homeduino] weather3:  { id: 212, channel: 1, temperature: 11.5, humidity: 50 }
20:50:12.473 [pimatic-homeduino] data: "RF receive 489 1958 3970 7812 0 0 0 0 0101020201020102010101010101010102020201010201020102010102010101020201010101010102010303"
20:50:12.507 [pimatic-homeduino] received: [ 489, 1958, 3970, 7812 ] 0101020201020102010101010101010102020201010201020102010102010101020201010101010102010303
20:50:12.539 [pimatic-homeduino] weather3:  { id: 212, channel: 1, temperature: 11.5, humidity: 50 }
20:50:24.759 [pimatic-homeduino] data: "ACK 19.1 55.2"
20:50:25.255 [pimatic-homeduino] data: "RF receive 687 4266 1970 10084 0 0 0 0 010201020102020101020102010202010102020101020201020102010102010202010102020101020102010201020102010201020102010201020102020101020201020102010102010201020201020101020201010202010102020101020201010203"
20:50:25.309 [pimatic-homeduino] received: [ 687, 1970, 4266, 10084 ] 020102010201010202010201020101020201010202010102010201020201020101020201010202010201020102010201020102010201020102010201010202010102010201020201020102010102010202010102020101020201010202010102020103
20:50:25.361 [pimatic-homeduino] generic:  { id: 1111, type: 2, positive: true, value: 378538 }
Segmentation fault

How can i make pimatic more verbose or how can i track where the issue is coming from?

@ako82

This comment has been minimized.

Copy link

commented Dec 31, 2014

I had pimatic running flawlessly and then installed my first DHT11. Then the crashes began. After booting pimatic started and worked for a while and then crashed without any special reason. And that frequently.
Also restarting pimatic then caused a complete reboot of the pi. Also stopping and restarting pimatic manually for the first time after a reboot caused a reboot.
Now I have disabled the DHT plugin and pimatic is working again as it should.
So there seem to be issues with the plugin.

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Dec 31, 2014

@ako82 thanks for the tip i will disable with DHT22 device and see if it helps, i will report results here

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Dec 31, 2014

Just to be sure did you disabled pimatic-dhtxx plugin (because my DHT22 is connected to the arduino and so far was working like a charm)

@ako82

This comment has been minimized.

Copy link

commented Jan 1, 2015

I disabled the plugin.
I had also tried all Hardware variations before. 3,3v + 5v mixed with 4700 and 10000 Ohm.

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 1, 2015

@ako82, sorry i wasn't clear enough where your DHT was connected to : raspberry or arduino?

@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 1, 2015

Segmentation fault means that the node.js process crash while executing some native code (not js).

@Yves911 What plugins do you have in use?

I never had to debug a segmentation fault in node, but node-segfault-handler looks like a nice tool. Do the following:

cd pimatic-app/node_modules/pimatic
npm install segfault-handler

And add these two lines after the first line in pimatic.js:

var SegfaultHandler = require('segfault-handler');
SegfaultHandler.registerHandler();

and restart it. Hopefully the next crash then outputs something useful.

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 1, 2015

Thanks!

Here is the full list of plugins that i am using

11:23:56.467 [pimatic] info: loading plugin: "pimatic-links" (0.8.5)
11:23:56.720 [pimatic] info: loading plugin: "pimatic-homeduino" (0.8.31)
11:23:57.783 [pimatic] info: loading plugin: "pimatic-mail" (0.8.2)
11:23:59.695 [pimatic] info: loading plugin: "pimatic-log-reader" (0.8.2)
11:23:59.905 [pimatic] info: loading plugin: "pimatic-cron" (0.8.3)
11:24:00.489 [pimatic] info: loading plugin: "pimatic-mobile-frontend" (0.8.31)
11:24:03.739 [pimatic] info: loading plugin: "pimatic-shell-execute" (0.8.1)
11:24:03.934 [pimatic] info: loading plugin: "pimatic-filebrowser" (0.8.0)
11:24:03.989 [pimatic] warn: package.json of "pimatic-filebrowser" has no "configSchema" property. Could not validate config.
11:24:04.012 [pimatic] info: loading plugin: "pimatic-pushbullet" (0.8.4)
11:24:07.264 [pimatic] info: loading plugin: "pimatic-sysinfo" (0.8.10)
11:24:07.750 [pimatic] info: loading plugin: "pimatic-weather" (0.8.8)
11:24:12.479 [pimatic] info: loading plugin: "pimatic-ping" (0.8.3)

I will give a try to segfault-handler and let you know the result...

And here the result :

11:28:27.118 [pimatic-homeduino] received: [ 689, 1969, 4264, 10088 ] 020102010201010202010201020101020201010202010102010201020201020101020201010202010201020102010201020102010201020102010201010202010102010201020102020102010102020101020201010201020201020101020201010203
11:28:27.161 [pimatic-homeduino] generic:  { id: 1111, type: 2, positive: true, value: 386405 }
11:28:31.254 [pimatic-homeduino] data: "RF receive 638 1866 3786 7638 0 0 0 0 0101010202020201020101010201010101010202020201020102010201010101020201020101020202010303"
11:28:31.296 [pimatic-homeduino] received: [ 638, 1866, 3786, 7638 ] 0101010202020201020101010201010101010202020201020102010201010101020201020101020202010303
11:28:31.339 [pimatic-homeduino] weather3:  { id: 122, channel: 3, temperature: 16.7, humidity: 52 }
11:28:31.728 [pimatic-homeduino] data: "RF receive 590 1923 3830 7660 0 0 0 0 0101010202020201020101010201010101010202020201020102010201010101020201020101020202010303"
11:28:31.781 [pimatic-homeduino] received: [ 590, 1923, 3830, 7660 ] 0101010202020201020101010201010101010202020201020102010201010101020201020101020202010303
11:28:31.826 [pimatic-homeduino] weather3:  { id: 122, channel: 3, temperature: 16.7, humidity: 52 }
11:28:42.937 [pimatic-homeduino] data: "ACK 17.3 45.7"
PID 23049 received SIGSEGV for address: 0x77017300

Not really useful isn't it?

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 1, 2015

My guess (but no evidence here) is that pimatic-homeduino is causing the trouble. This trouble wasn't there 1 or 2 weeks ago. So could i install a previous version of pimatic-homeduino and check if problem still exists? It should be possible to isolate the issue.
So how can i install an old version of pimatic-homeduino?
ok should be something like : npm install pimatic-homeduino@0.8.27
With this version of pimatic-homeduino i have the same (bad) result:

11:50:55.733 [pimatic-homeduino] data: "RF receive 588 1925 3833 7658 0 0 0 0 0101010202020201020101010201010201010202020201020102010201010101020201020101010201020303"
11:50:55.757 [pimatic-homeduino] received: [ 588, 1925, 3833, 7658 ] 0101010202020201020101010201010201010202020201020102010201010101020201020101010201020303
11:50:55.783 [pimatic-homeduino] weather3:  { id: 122, channel: 3, temperature: 16.9, humidity: 52 }
PID 23547 received SIGSEGV for address: 0x0

I don't think that the problem is linked to the DB (because i also get the error with a new empty DB)

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 1, 2015

the crash seems to be linked to this rule:

if its20 and [$homeduino-temperature.temperature < $dummy-heating.temperatureSetpoint] 
then 
log \"Allumage Chaudière {date()}, température $homeduino-temperature.temperature° -> $dummy-heating.temperatureSetpoint° pour $heattime minutes\" 
and 
switch chaudiere off 
and
switch chaudiere on after 10 seconds for $heattime minutes 
and 
pushbullet title:\"Allumage chaudière {date()}\" message:\"Température du salon $homeduino-temperature.temperature°C, température de consigne $dummy-heating.temperatureSetpoint°C, temps de chauffe $heattime minutes\"

I have replaced recently my buttons based config to a dummy-heating heating one and it seems to be the root cause.. why exactly i don't know...

No problem with this rule (not using the dummy-heating)

if its20 and [$homeduino-temperature.temperature < $manualtemp] 
then 
log \"Allumage Chaudière {date()}, température $homeduino-temperature.temperature° -> $manualtemp° pour $heattime minutes\" 
and 
switch chaudiere on for $heattime minutes 
and 
pushbullet title:\"Allumage Chaudière {date()}, température $homeduino-temperature.temperature° -> $manualtemp° pour $heattime minutes\"
@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 1, 2015

Hm strange, can't imagine that it has something to do with the rule / dummy device. If I look at your plugin list I would guess that it is the homeduino plugin or more precisely the node-serialport module.

Which version of node-serialport is installed?

cd pimatic-app/node_modules/pimatic-homeduino
npm list

I was running with serialport v1.4.9 and had no problems and now updated to 1.4.10 and will test.

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 1, 2015

yes it's very strange also to me, but it seems to be the case.
about npm list this is what i have:

pimatic-homeduino@0.8.31 /root/pimatic-git/node_modules/pimatic-homeduino
├─┬ homeduino@0.0.25
│ ├── bluebird@2.2.2
│ ├── otaat-repl@1.0.2
│ ├── rfcontroljs@0.0.20
│ └─┬ serialport@1.4.10
│   ├── async@0.9.0
│   ├── bindings@1.2.1
│   ├── nan@1.3.0
│   ├─┬ node-pre-gyp@0.5.19
│   │ ├─┬ mkdirp@0.5.0
│   │ │ └── minimist@0.0.8
│   │ ├─┬ nopt@2.2.1
│   │ │ └── abbrev@1.0.5
│   │ ├─┬ npmlog@0.0.6
│   │ │ └── ansi@0.2.1
│   │ ├─┬ rc@0.4.0
│   │ │ ├── deep-extend@0.2.10
│   │ │ ├── ini@1.1.0
│   │ │ ├── minimist@0.0.10
│   │ │ └── strip-json-comments@0.1.3
│   │ ├─┬ request@2.36.0
│   │ │ ├── aws-sign2@0.5.0
│   │ │ ├── forever-agent@0.5.2
│   │ │ ├─┬ form-data@0.1.2
│   │ │ │ ├── async@0.2.10
│   │ │ │ └─┬ combined-stream@0.0.4
│   │ │ │   └── delayed-stream@0.0.5
│   │ │ ├─┬ hawk@1.0.0
│   │ │ │ ├── boom@0.4.2
│   │ │ │ ├── cryptiles@0.2.2
│   │ │ │ ├── hoek@0.9.1
│   │ │ │ └── sntp@0.2.4
│   │ │ ├─┬ http-signature@0.10.0
│   │ │ │ ├── asn1@0.1.11
│   │ │ │ ├── assert-plus@0.1.2
│   │ │ │ └── ctype@0.5.2
│   │ │ ├── json-stringify-safe@5.0.0
│   │ │ ├── mime@1.2.11
│   │ │ ├── node-uuid@1.4.1
│   │ │ ├── oauth-sign@0.3.0
│   │ │ ├── qs@0.6.6
│   │ │ ├─┬ tough-cookie@0.12.1
│   │ │ │ └── punycode@1.2.4
│   │ │ └── tunnel-agent@0.4.0
│   │ ├── rimraf@2.2.8
│   │ ├── semver@2.3.0
│   │ ├─┬ tar@0.1.19
│   │ │ ├── block-stream@0.0.7
│   │ │ ├─┬ fstream@0.1.25
│   │ │ │ ├── graceful-fs@2.0.3
│   │ │ │ └── mkdirp@0.3.5
│   │ │ └── inherits@2.0.1
│   │ └─┬ tar-pack@2.0.0
│   │   ├── debug@0.7.4
│   │   ├─┬ fstream@0.1.25
│   │   │ ├── graceful-fs@2.0.3
│   │   │ ├── inherits@2.0.1
│   │   │ └── mkdirp@0.3.5
│   │   ├─┬ fstream-ignore@0.0.7
│   │   │ ├── inherits@2.0.1
│   │   │ └─┬ minimatch@0.2.14
│   │   │   ├── lru-cache@2.5.0
│   │   │   └── sigmund@1.0.0
│   │   ├── graceful-fs@1.2.3
│   │   ├── once@1.1.1
│   │   ├─┬ readable-stream@1.0.27-1
│   │   │ ├── core-util-is@1.0.1
│   │   │ ├── inherits@2.0.1
│   │   │ ├── isarray@0.0.1
│   │   │ └── string_decoder@0.10.25-1
│   │   └── uid-number@0.0.3
│   ├─┬ optimist@0.6.1
│   │ ├── minimist@0.0.10
│   │ └── wordwrap@0.0.2
│   └── sf@0.1.7
└── UNMET DEPENDENCY pimatic 0.8.*

npm ERR! missing: pimatic@0.8.*, required by pimatic-homeduino@0.8.31
npm ERR! not ok code 0
@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 2, 2015

I don't have any crashes now, root of the trouble is unclear and seems to be linked to rules and dummy-heating.
For now we can close this issue (and if someone encounter same issue reopen)

@Yves911 Yves911 closed this Jan 2, 2015
@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 3, 2015

Unfortunately I still had some crashes...
Since yesterday evening no crash anymore (i have downgraded the pimatic frontend to 0.8.27)
Could crash be linked to pimatic-mobile-frontend? I have noticed that crashes happen mostly during pimatic startup or when accessing or playing with the web UI...

@Yves911 Yves911 reopened this Jan 3, 2015
@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 4, 2015

I may have something interesting here,right before crash i have the following:

TypeError: Cannot read property 'length' of undefined
    at Function.Buffer.concat (buffer.js:491:20)
    at afterRead (/root/pimatic-git/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/serialport.js:323:36)
    at /root/pimatic-git/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/serialport.js:342:9
    at Object.wrapper [as oncomplete] (fs.js:454:17)

All modules are up to date

@Icesory

This comment has been minimized.

Copy link
Contributor

commented Jan 4, 2015

Which arduino do you use?

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 4, 2015

Which arduino do you use?

arduino nano 3 clone with an atmega328

@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

I've added some debug flags and outputs to the node-serialport module, maybe this gives us a more verbose stack trace. I really don't think it is gui related. I think that there is some buffer that gets full / a overflow if there is too much serial port communication and pimatic is bussy with something else.

Please do the following to install node-seriaport mit debug outputs:

cd pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules
rm -rf serialport
npm install sweetpi/node-serialport

You should now get a SERIALPORT: _read for every read from serial port and hopefully a stack trash when the Segmentation fault happens.

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

thanks, this is what i get now

SERIALPORT: _read
PID 13464 received SIGSEGV for address: 0x0

and

SERIALPORT: _read
SERIALPORT: _read
SERIALPORT: _read
12:16:02.086 [pimatic-homeduino] data: "RF receive 941 342 8936 0 0 0 0 0 01101001010110101010011010010110101010100110101012"
12:16:02.111 [pimatic-homeduino] received: [ 342, 941, 8936 ] 10010110101001010101100101101001010101011001010102
12:16:02.136 [pimatic-homeduino] switch5:  { id: 408991, unit: 0, all: true, state: true }
SERIALPORT: _read
SERIALPORT: _read
PID 13520 received SIGSEGV for address: 0x0

last one

SERIALPORT: _read
12:19:58.725 [pimatic-homeduino] data: "PING"
SERIALPORT: _read
SERIALPORT: _read
12:19:58.835 [pimatic-homeduino] data: "ready"
SERIALPORT: _read
12:19:58.873 [pimatic-homeduino] Connected to homeduino device.
SERIALPORT: _read
12:19:58.952 [pimatic-homeduino] data: "ACK"
SERIALPORT: _read
12:19:58.989 [pimatic-homeduino] Receiving on pin 0
SERIALPORT: _read
12:19:59.033 [pimatic-homeduino] data: "ACK 17.3 49.1"
SERIALPORT: _read
SERIALPORT: _read
12:19:59.148 [pimatic-homeduino] data: "ACK"
SERIALPORT: _read
SERIALPORT: _read
12:19:59.196 [pimatic-homeduino] data: "ACK"
SERIALPORT: _read
SERIALPORT: _read
12:19:59.243 [pimatic-homeduino] data: "ACK"
SERIALPORT: _read
SERIALPORT: _read
SERIALPORT: _read
SERIALPORT: _read
SERIALPORT: _read
SERIALPORT: _read
SERIALPORT: _read
SERIALPORT: _read
12:20:10.109 [pimatic-homeduino] data: "RF receive 687 4265 1970 10084 0 0 0 0 010201020102020101020102010202010102020101020201020102010102010202010102020101020102010201020102010201020102010201020102020102010102020101020201020101020102010201020102010201020102010202010201010203"
12:20:10.184 [pimatic-homeduino] received: [ 687, 1970, 4265, 10084 ] 020102010201010202010201020101020201010202010102010201020201020101020201010202010201020102010201020102010201020102010201010201020201010202010102010202010201020102010201020102010201020101020102020103
12:20:10.250 [pimatic-homeduino] generic:  { id: 1111, type: 2, positive: true, value: 438278 }
SERIALPORT: _read
SERIALPORT: _read
PID 13740 received SIGSEGV for address: 0xec
@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

Is there a stacktrace-xxx-xxx.log file in the pimatic directory? (https://github.com/ddopson/node-segfault-handler/blob/master/src/segfault-handler.cpp#L35)

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

Yes, but the info is not more detailled

stacktrace-1420456815-13740.log:
PID 13740 received SIGSEGV for address: 0xec

My impression is that when i get this kind of errors if try to restart again pimatic most of the time it will fail with the same error.
If i restart the pi, then most of the time it will start without error.
The arduino is connected to a hub so i don't know if it get reset when i restart the pi.

@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

So: http://stackoverflow.com/questions/24700150/on-raspberry-pi-backtrace-returns-0-frames

I updated sweetpi/node-serialport with the right compilation flags. So could you rerun:

cd pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules
rm -rf serialport
npm install sweetpi/node-serialport

and test again?

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

So after

rm -rf serialport/

root@raspberrypi:~/pimatic-git/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules# npm install sweetpi/node-serialport
npm http GET https://registry.npmjs.org/nan
npm http GET https://registry.npmjs.org/node-pre-gyp
npm http GET https://registry.npmjs.org/bindings/1.2.1
npm http GET https://registry.npmjs.org/async/0.9.0
npm http GET https://registry.npmjs.org/sf/0.1.7
npm http GET https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/node-pre-gyp
npm http 304 https://registry.npmjs.org/nan
npm http 304 https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/bindings/1.2.1
npm http 304 https://registry.npmjs.org/async/0.9.0
npm http 304 https://registry.npmjs.org/sf/0.1.7
npm http GET https://registry.npmjs.org/wordwrap
npm http GET https://registry.npmjs.org/minimist
npm http 304 https://registry.npmjs.org/wordwrap
npm http 304 https://registry.npmjs.org/minimist

> serialport@1.4.10 install /root/pimatic-git/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport
> node-pre-gyp build --debug

make: Entering directory '/root/pimatic-git/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build'
  CXX(target) Debug/obj.target/serialport/src/serialport.o
  CXX(target) Debug/obj.target/serialport/src/serialport_unix.o
  CXX(target) Debug/obj.target/serialport/src/serialport_poller.o
  SOLINK_MODULE(target) Debug/obj.target/serialport.node
  SOLINK_MODULE(target) Debug/obj.target/serialport.node: Finished
  COPY Debug/serialport.node
  COPY /root/pimatic-git/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build/serialport/v1.4.10/Debug/node-v11-linux-arm/serialport.node
  TOUCH Debug/obj.target/action_after_build.stamp
make: Leaving directory '/root/pimatic-git/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build'
serialport@1.4.10 serialport
├── bindings@1.2.1
├── sf@0.1.7
├── async@0.9.0
├── nan@1.3.0
├── optimist@0.6.1 (wordwrap@0.0.2, minimist@0.0.10)
└── node-pre-gyp@0.5.31

Same result :

14:22:46.275 [pimatic] [ReferenceError: err is not defined]
SERIALPORT: _read
PID 7049 received SIGSEGV for address: 0x0

more stacktrace-1420464166-7049.log

PID 7049 received SIGSEGV for address: 0x0

PS : the 14:22:46.275 [pimatic] [ReferenceError: err is not defined] message is due to pimatic-weather (too many tentative to get result from msn wether api)

@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

Ok let's do it the hard way, please use gdb:

cd pimatic-app
sudo gdb node

you should now have a gdb shell open: Type:

run node_modules/pimatic/pimatic.js

After it crashed type:

backtrace
@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

Okay, here is the result:
SERIALPORT: _read

Program received signal SIGSEGV, Segmentation fault.
0x007316b8 in ?? ()
(gdb) backtrace

#0  0x007316b8 in ?? ()
#1  0x0052f1dc in uv__io_poll (loop=0x6ea788, timeout=0) at ../deps/uv/src/unix/linux-core.c:263
#2  0x005240a4 in uv_run (loop=0x6ea788, mode=<optimized out>) at ../deps/uv/src/unix/core.c:317
#3  0x003f8404 in node::Start(int, char**) ()
#4  0xb6d0082c in __libc_start_main () from /lib/arm-linux-gnueabihf/libc.so.6
#5  0x0016adfc in _start ()
@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

Damn almost there. But the important line is the one with the question-signs....

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

:-)

@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

So one more reinstall of node-serialport from my repo and it should expose the error :)

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

I am trying to reproduce the crash now, but as usual in this situation : you can't :-)

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

Ok here is the result:

Program received signal SIGSEGV, Segmentation fault.
0xffffff6a in ?? ()
(gdb) backtrace
#0  0xffffff6a in ?? ()
#1  0x0000f2a6 in ?? ()
#2  0x0000f2a6 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Program received signal SIGSEGV, Segmentation fault.
0x3e2a1704 in ?? ()
(gdb) backtrace
#0  0x3e2a1704 in ?? ()
#1  0x0052f1dc in uv__io_poll (loop=0x6ea788, timeout=676) at ../deps/uv/src/unix/linux-core.c:263
#2  0x005240a4 in uv_run (loop=0x6ea788, mode=<optimized out>) at ../deps/uv/src/unix/core.c:317
#3  0x003f8404 in node::Start(int, char**) ()
#4  0xb6d0082c in __libc_start_main () from /lib/arm-linux-gnueabihf/libc.so.6
#5  0x0016adfc in _start ()
@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

ok I think its not the serialport module. I produced an segfault in the serialport module and I get the function name and line number...

But the only two left with native modules are ping and sysinfo. Can you disable the two and test if it still segaults?

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

With ping and sysinfo disabled (just added DISABLE into plugin name)...

21:02:07.895 2015-01-05 Monday
21:02:15.918 [pimatic] Starting pimatic version 0.8.33
21:02:20.793 [pimatic] loading plugin: "pimatic-links" (0.8.5)
21:02:20.962 [pimatic] loading plugin: "pimatic-homeduino" (0.8.31)
21:02:22.067 [pimatic] loading plugin: "pimatic-mail" (0.8.2)
21:02:24.185 [pimatic] loading plugin: "pimatic-log-reader" (0.8.2)
21:02:24.377 [pimatic] loading plugin: "pimatic-cron" (0.8.3)
21:02:24.897 [pimatic] loading plugin: "pimatic-mobile-frontend" (0.8.32)
21:02:28.052 [pimatic] loading plugin: "pimatic-shell-execute" (0.8.1)
21:02:28.187 [pimatic] loading plugin: "pimatic-filebrowser" (0.8.0)
21:02:28.238 [pimatic] package.json of "pimatic-filebrowser" has no "configSchema" property. Could not validate config.
21:02:28.261 [pimatic] loading plugin: "pimatic-pushbullet" (0.8.4)
21:02:31.315 [pimatic] Installing: "sysinfoDISABLE"
21:02:38.277 [pimatic, npm] http GET https://registry.npmjs.org/pimatic-sysinfoDISABLE
21:02:39.537 [pimatic, npm] http 404 https://registry.npmjs.org/pimatic-sysinfoDISABLE
21:02:39.703 [pimatic, npm] ERR! 404 'pimatic-sysinfoDISABLE' is not in the npm registry.
21:02:39.773 [pimatic, npm] ERR! 404 You should bug the author to publish it
21:02:39.835 [pimatic, npm] ERR! 404 
21:02:39.893 [pimatic, npm] ERR! 404 Note that you can also install from a
21:02:39.940 [pimatic, npm] ERR! 404 tarball, folder, or http url, or git url.
21:02:39.991 [pimatic, npm] ERR! System Linux 3.12.35+
21:02:40.048 [pimatic, npm] ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "pimatic-sysinfoDISABLE"
21:02:40.101 [pimatic, npm] ERR! cwd /root/pimatic-git
21:02:40.148 [pimatic, npm] ERR! node -v v0.10.24
21:02:40.217 [pimatic, npm] ERR! npm -v 1.3.21
21:02:40.252 [pimatic, npm] ERR! code E404
21:02:40.284 [pimatic, npm] ERR! 
21:02:40.306 [pimatic, npm] ERR! Additional logging details can be found in:
21:02:40.335 [pimatic, npm] ERR!     /root/pimatic-git/npm-debug.log
21:02:40.357 [pimatic, npm] ERR! not ok code 0
21:02:40.445 [pimatic] Error running "npm install pimatic-sysinfoDISABLE"
21:02:41.080 [pimatic] Error: Error running "npm install pimatic-sysinfoDISABLE"
21:02:41.080 [pimatic]>    at ChildProcess.<anonymous> (/root/pimatic-git/plugins.coffee:219:24)
21:02:41.080 [pimatic]>    at ChildProcess.EventEmitter.emit (events.js:98:17)
21:02:41.080 [pimatic]>    at maybeClose (child_process.js:735:16)
21:02:41.080 [pimatic]>    at Socket.<anonymous> (child_process.js:948:11)
21:02:41.080 [pimatic]>    at Socket.EventEmitter.emit (events.js:95:17)
21:02:41.080 [pimatic]>    at Pipe.close (net.js:466:12)
21:02:41.118 [pimatic] loading plugin: "pimatic-weather" (0.8.8)
21:02:45.461 [pimatic] Installing: "pingDISABLE"
21:02:51.030 [pimatic, npm] http GET https://registry.npmjs.org/pimatic-pingDISABLE
21:02:52.300 [pimatic, npm] http 404 https://registry.npmjs.org/pimatic-pingDISABLE
21:02:52.453 [pimatic, npm] ERR! 404 'pimatic-pingDISABLE' is not in the npm registry.
21:02:52.535 [pimatic, npm] ERR! 404 You should bug the author to publish it
21:02:52.595 [pimatic, npm] ERR! 404 
21:02:52.637 [pimatic, npm] ERR! 404 Note that you can also install from a
21:02:52.691 [pimatic, npm] ERR! 404 tarball, folder, or http url, or git url.
21:02:52.722 [pimatic, npm] ERR! System Linux 3.12.35+
21:02:52.769 [pimatic, npm] ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "pimatic-pingDISABLE"
21:02:52.820 [pimatic, npm] ERR! cwd /root/pimatic-git
21:02:52.862 [pimatic, npm] ERR! node -v v0.10.24
21:02:52.906 [pimatic, npm] ERR! npm -v 1.3.21
21:02:52.937 [pimatic, npm] ERR! code E404
21:02:53.004 [pimatic, npm] ERR! 
21:02:53.031 [pimatic, npm] ERR! Additional logging details can be found in:
21:02:53.052 [pimatic, npm] ERR!     /root/pimatic-git/npm-debug.log
21:02:53.075 [pimatic, npm] ERR! not ok code 0
21:02:53.117 [pimatic] Error running "npm install pimatic-pingDISABLE"
21:02:53.156 [pimatic] Error: Error running "npm install pimatic-pingDISABLE"
21:02:53.156 [pimatic]>    at ChildProcess.<anonymous> (/root/pimatic-git/plugins.coffee:219:24)
21:02:53.156 [pimatic]>    at ChildProcess.EventEmitter.emit (events.js:98:17)
21:02:53.156 [pimatic]>    at maybeClose (child_process.js:735:16)
21:02:53.156 [pimatic]>    at Socket.<anonymous> (child_process.js:948:11)
21:02:53.156 [pimatic]>    at Socket.EventEmitter.emit (events.js:95:17)
21:02:53.156 [pimatic]>    at Pipe.close (net.js:466:12)
SERIALPORT: open
21:02:53.933 [pimatic-cron] the time is: Mon Jan 05 2015 21:02:53 GMT+0100 (CET)
21:02:54.141 [pimatic-pushbullet] apikey= XXXXXXXXXXXXXXXXXXXXXXXX
SERIALPORT: _read
SERIALPORT: _read
21:02:54.762 [pimatic] new device "Pin Switch"...
21:02:55.064 [pimatic] new device "Uptime"...
21:02:55.312 [pimatic] new device "Secu"...
21:02:55.423 [pimatic] new device "homeduino-button-chau"...
21:02:55.509 [pimatic] new device "Volume"...
21:02:55.606 [pimatic] new device "Détecteur de mouvements"...
21:02:55.711 [pimatic] new device "Compteur gaz"...
21:02:55.811 [pimatic] new device "Compteur élec"...
21:02:55.898 [pimatic] new device "Salon"...
21:02:56.056 [pimatic] new device "Chaudière"...
21:02:56.143 [pimatic] new device "Salon (P1)"...
21:02:56.229 [pimatic] new device "Prise 2"...
21:02:56.314 [pimatic] new device "Escalier (P3)"...
21:02:56.401 [pimatic] new device "Prise 4"...
21:02:56.493 [pimatic] new device "Mobile (S3)"...
21:02:56.581 [pimatic] new device "Jardin (S2)"...
21:02:56.666 [pimatic] new device "Garage (S1)"...
21:02:56.967 [pimatic] new device "Longpont A"...
21:02:57.074 [pimatic] new device "Longpont P"...
21:02:57.108 [pimatic] no plugin found for device "syssensor" of class "SystemSensor"!
21:02:57.199 [pimatic] new device "Evénement"...
21:02:57.287 [pimatic] new device "Iphone"...
21:02:57.370 [pimatic] new device "every5"...
21:02:57.452 [pimatic] new device "Haut-parleur"...
21:02:57.666 [pimatic] new device "Motion"...
21:02:57.890 [pimatic] new device "Notifications par mail"...
21:02:58.067 [pimatic] new device "VideoRecord"...
21:02:58.264 [pimatic] new device "Mode"...
21:02:58.490 [pimatic] new device "Mode thermostat"...
21:02:58.619 [pimatic] new device "Choix consigne"...
21:02:58.718 [pimatic] new device "Consigne"...
21:02:58.800 [pimatic] new device "Thermostat auto"...
21:02:58.880 [pimatic] new device "Prises salon"...
21:02:58.909 [pimatic] no plugin found for device "pingx230" of class "PingPresence"!
21:02:59.005 [pimatic] new device "20m/24h"...
21:02:59.105 [pimatic] new device "5m/24h"...
21:02:59.133 [pimatic] no plugin found for device "asus" of class "PingPresence"!
21:02:59.157 [pimatic] no plugin found for device "netgear" of class "PingPresence"!
21:02:59.181 [pimatic] no plugin found for device "nexus" of class "PingPresence"!
21:02:59.206 [pimatic] no plugin found for device "alcatel" of class "PingPresence"!
21:02:59.230 [pimatic] no plugin found for device "ping3gs" of class "PingPresence"!
21:03:16.856 [pimatic] rule allumagechaudiere19: set $manualtemp to 19
21:03:17.414 [pimatic-homeduino] Couldn't connect (operation timed out after 20000 ms), retrying...
SERIALPORT: open
21:03:17.986 [pimatic-mobile-frontend] packing static assets
21:03:20.417 [pimatic-mobile-frontend] packing static assets finished
21:03:20.458 [pimatic-mobile-frontend] rendering html
21:03:35.219 [pimatic-mobile-frontend] rendering html finished
21:03:35.407 [pimatic] listening for https-request on port 8443...
21:03:35.525 [pimatic] rule chauffage-stop-check: lowered Secu
21:03:35.628 [pimatic] Could not get attribute value of Longpont A.status: err is not defined
21:03:35.968 [pimatic] ReferenceError: err is not defined
21:03:35.968 [pimatic]>    at /root/pimatic-git/weather.coffee:67:26
21:03:35.968 [pimatic]>    at tryCatch1 (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/util.js:43:21)
21:03:35.968 [pimatic]>    at Promise$_callHandler [as _callHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:627:13)
21:03:35.968 [pimatic]>    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:641:18)
21:03:35.968 [pimatic]>    at Promise$_settlePromiseAt [as _settlePromiseAt] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:800:14)
21:03:35.968 [pimatic]>    at Promise$_settlePromises [as _settlePromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:934:14)
21:03:35.968 [pimatic]>    at Promise$_rejectPromises [as _rejectPromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:927:10)
21:03:35.968 [pimatic]>    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:75:12)
21:03:35.968 [pimatic]>    at Async$consumeFunctionBuffer (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:38:14)
21:03:35.968 [pimatic]>    at process._tickCallback (node.js:415:13)
21:03:36.010 [pimatic] Could not get attribute value of Longpont A.windspeed: err is not defined
21:03:36.039 [pimatic] ReferenceError: err is not defined
21:03:36.039 [pimatic]>    at /root/pimatic-git/weather.coffee:67:26
21:03:36.039 [pimatic]>    at tryCatch1 (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/util.js:43:21)
21:03:36.039 [pimatic]>    at Promise$_callHandler [as _callHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:627:13)
21:03:36.039 [pimatic]>    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:641:18)
21:03:36.039 [pimatic]>    at Promise$_settlePromiseAt [as _settlePromiseAt] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:800:14)
21:03:36.039 [pimatic]>    at Promise$_settlePromises [as _settlePromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:934:14)
21:03:36.039 [pimatic]>    at Promise$_rejectPromises [as _rejectPromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:927:10)
21:03:36.039 [pimatic]>    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:75:12)
21:03:36.039 [pimatic]>    at Async$consumeFunctionBuffer (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:38:14)
21:03:36.039 [pimatic]>    at process._tickCallback (node.js:415:13)
21:03:36.077 [pimatic] Could not get attribute value of Longpont A.temperature: err is not defined
21:03:36.105 [pimatic] ReferenceError: err is not defined
21:03:36.105 [pimatic]>    at /root/pimatic-git/weather.coffee:67:26
21:03:36.105 [pimatic]>    at tryCatch1 (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/util.js:43:21)
21:03:36.105 [pimatic]>    at Promise$_callHandler [as _callHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:627:13)
21:03:36.105 [pimatic]>    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:641:18)
21:03:36.105 [pimatic]>    at Promise$_settlePromiseAt [as _settlePromiseAt] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:800:14)
21:03:36.105 [pimatic]>    at Promise$_settlePromises [as _settlePromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:934:14)
21:03:36.105 [pimatic]>    at Promise$_rejectPromises [as _rejectPromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:927:10)
21:03:36.105 [pimatic]>    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:75:12)
21:03:36.105 [pimatic]>    at Async$consumeFunctionBuffer (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:38:14)
21:03:36.105 [pimatic]>    at process._tickCallback (node.js:415:13)
21:03:36.144 [pimatic] Could not get attribute value of Longpont A.humidity: err is not defined
21:03:36.174 [pimatic] ReferenceError: err is not defined
21:03:36.174 [pimatic]>    at /root/pimatic-git/weather.coffee:67:26
21:03:36.174 [pimatic]>    at tryCatch1 (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/util.js:43:21)
21:03:36.174 [pimatic]>    at Promise$_callHandler [as _callHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:627:13)
21:03:36.174 [pimatic]>    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:641:18)
21:03:36.174 [pimatic]>    at Promise$_settlePromiseAt [as _settlePromiseAt] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:800:14)
21:03:36.174 [pimatic]>    at Promise$_settlePromises [as _settlePromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:934:14)
21:03:36.174 [pimatic]>    at Promise$_rejectPromises [as _rejectPromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:927:10)
21:03:36.174 [pimatic]>    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:75:12)
21:03:36.174 [pimatic]>    at Async$consumeFunctionBuffer (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:38:14)
21:03:36.174 [pimatic]>    at process._tickCallback (node.js:415:13)
21:03:36.215 [pimatic] Could not get attribute value of Longpont P.forecast: err is not defined
21:03:36.277 [pimatic] ReferenceError: err is not defined
21:03:36.277 [pimatic]>    at /root/pimatic-git/weather.coffee:120:26
21:03:36.277 [pimatic]>    at tryCatch1 (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/util.js:43:21)
21:03:36.277 [pimatic]>    at Promise$_callHandler [as _callHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:627:13)
21:03:36.277 [pimatic]>    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:641:18)
21:03:36.277 [pimatic]>    at Promise$_settlePromiseAt [as _settlePromiseAt] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:800:14)
21:03:36.277 [pimatic]>    at Promise$_settlePromises [as _settlePromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:934:14)
21:03:36.277 [pimatic]>    at Promise$_rejectPromises [as _rejectPromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:927:10)
21:03:36.277 [pimatic]>    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:75:12)
21:03:36.277 [pimatic]>    at Async$consumeFunctionBuffer (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:38:14)
21:03:36.277 [pimatic]>    at process._tickCallback (node.js:415:13)
21:03:36.318 [pimatic] Could not get attribute value of Longpont P.low: err is not defined
21:03:36.348 [pimatic] ReferenceError: err is not defined
21:03:36.348 [pimatic]>    at /root/pimatic-git/weather.coffee:120:26
21:03:36.348 [pimatic]>    at tryCatch1 (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/util.js:43:21)
21:03:36.348 [pimatic]>    at Promise$_callHandler [as _callHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:627:13)
21:03:36.348 [pimatic]>    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:641:18)
21:03:36.348 [pimatic]>    at Promise$_settlePromiseAt [as _settlePromiseAt] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:800:14)
21:03:36.348 [pimatic]>    at Promise$_settlePromises [as _settlePromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:934:14)
21:03:36.348 [pimatic]>    at Promise$_rejectPromises [as _rejectPromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:927:10)
21:03:36.348 [pimatic]>    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:75:12)
21:03:36.348 [pimatic]>    at Async$consumeFunctionBuffer (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:38:14)
21:03:36.348 [pimatic]>    at process._tickCallback (node.js:415:13)
21:03:36.388 [pimatic] Could not get attribute value of Longpont P.high: err is not defined
21:03:36.415 [pimatic] ReferenceError: err is not defined
21:03:36.415 [pimatic]>    at /root/pimatic-git/weather.coffee:120:26
21:03:36.415 [pimatic]>    at tryCatch1 (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/util.js:43:21)
21:03:36.415 [pimatic]>    at Promise$_callHandler [as _callHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:627:13)
21:03:36.415 [pimatic]>    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:641:18)
21:03:36.415 [pimatic]>    at Promise$_settlePromiseAt [as _settlePromiseAt] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:800:14)
21:03:36.415 [pimatic]>    at Promise$_settlePromises [as _settlePromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:934:14)
21:03:36.415 [pimatic]>    at Promise$_rejectPromises [as _rejectPromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:927:10)
21:03:36.415 [pimatic]>    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:75:12)
21:03:36.415 [pimatic]>    at Async$consumeFunctionBuffer (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:38:14)
21:03:36.415 [pimatic]>    at process._tickCallback (node.js:415:13)
21:03:36.457 [pimatic] Could not get attribute value of Longpont P.precipitation: err is not defined
21:03:36.482 [pimatic] ReferenceError: err is not defined
21:03:36.482 [pimatic]>    at /root/pimatic-git/weather.coffee:120:26
21:03:36.482 [pimatic]>    at tryCatch1 (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/util.js:43:21)
21:03:36.482 [pimatic]>    at Promise$_callHandler [as _callHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:627:13)
21:03:36.482 [pimatic]>    at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:641:18)
21:03:36.482 [pimatic]>    at Promise$_settlePromiseAt [as _settlePromiseAt] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:800:14)
21:03:36.482 [pimatic]>    at Promise$_settlePromises [as _settlePromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:934:14)
21:03:36.482 [pimatic]>    at Promise$_rejectPromises [as _rejectPromises] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:927:10)
21:03:36.482 [pimatic]>    at Async$_consumeFunctionBuffer [as _consumeFunctionBuffer] (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:75:12)
21:03:36.482 [pimatic]>    at Async$consumeFunctionBuffer (/root/pimatic-git/node_modules/pimatic/node_modules/bluebird/js/main/async.js:38:14)
21:03:36.482 [pimatic]>    at process._tickCallback (node.js:415:13)
21:03:36.523 [pimatic] Could not update variable weather.status: err is not defined
21:03:36.560 [pimatic] [ReferenceError: err is not defined]
21:03:36.704 [pimatic] Could not update variable weather.windspeed: err is not defined
21:03:36.734 [pimatic] [ReferenceError: err is not defined]
21:03:36.764 [pimatic] Could not update variable weather.temperature: err is not defined
21:03:36.797 [pimatic] [ReferenceError: err is not defined]
21:03:36.821 [pimatic] Could not update variable weather.humidity: err is not defined
21:03:36.849 [pimatic] [ReferenceError: err is not defined]
21:03:36.880 [pimatic] Could not update variable forecast.forecast: err is not defined
21:03:36.909 [pimatic] [ReferenceError: err is not defined]
21:03:36.937 [pimatic] Could not update variable forecast.low: err is not defined
21:03:36.964 [pimatic] [ReferenceError: err is not defined]
21:03:36.991 [pimatic] Could not update variable forecast.high: err is not defined
21:03:37.021 [pimatic] [ReferenceError: err is not defined]
21:03:37.048 [pimatic] Could not update variable forecast.precipitation: err is not defined
21:03:37.077 [pimatic] [ReferenceError: err is not defined]
SERIALPORT: _read
21:03:37.183 [pimatic-homeduino] data: "RF receive 630 1885 3785 7674 0 PING"
SERIALPORT: _read
SERIALPORT: _read
21:03:37.248 [pimatic-homeduino] data: "ready"
SERIALPORT: _read
21:03:37.286 [pimatic-homeduino] Connected to homeduino device.
SERIALPORT: _read
21:03:37.404 [pimatic-homeduino] data: "ACK"
SERIALPORT: _read
21:03:37.447 [pimatic-homeduino] Receiving on pin 0
SERIALPORT: _read
21:03:37.498 [pimatic-homeduino] data: "ACK 19.1 48.3"
SERIALPORT: _read
SERIALPORT: _read
21:03:37.576 [pimatic-homeduino] data: "ACK"
SERIALPORT: _read
SERIALPORT: _read
21:03:37.627 [pimatic-homeduino] data: "ACK"
SERIALPORT: _read
SERIALPORT: _read
21:03:37.678 [pimatic-homeduino] data: "ACK"
SERIALPORT: _read
SERIALPORT: _read
PID 5887 received SIGSEGV for address: 0xddbe09ae

Still crash...

@Icesory

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

21:02:31.315 [pimatic] Installing: "sysinfoDISABLE"
There is a failure in your config

and what is this?
21:03:37.498 [pimatic-homeduino] data: "ACK 19.1 48.3"

@sweetpi

This comment has been minimized.

Copy link
Contributor

commented Jan 5, 2015

21:02:31.315 [pimatic] Installing: "sysinfoDISABLE"
There is a failure in your config

Its just to disable the plugin..

I've no idea at the moment, how to track the issue down.

@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 5, 2015

I will try to narrow the problem, its too vague for now

@sweetpi sweetpi added the in progress label Jan 6, 2015
@Yves911

This comment has been minimized.

Copy link
Contributor Author

commented Jan 9, 2015

I am closing this issue:

  • pimatic is stable when running
  • pimatic start with no problem if raspberry has been rebooted
    so the issue is not solved, but for me it's manageable like this...
    If someone encounter the same issue he can reopen this issue.
@KlausFeld

This comment has been minimized.

Copy link

commented Apr 8, 2015

Hi, I still have the Problems with the homeduino plugin and the arduino nano. My log tells this:

Disconnect completed
11:12:23.513 [pimatic-homeduino] warn: Couldn't connect (Serialport not open.), retrying...
11:12:23.521 [pimatic-homeduino] warn: Couldn't connect (Serialport not open.), retrying...

What can I check?

@Icesory

This comment has been minimized.

Copy link
Contributor

commented Apr 8, 2015

For this stuff please use the http://forum.pimatic.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.