• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
pilight fails starting on boot
#1
I´m expiriencing some Trouble with a freshly installed pilight on a new Pi and SD-Card.

Only on bootup, pilight Fails to start:

Code:
● pilight.service - pilight
   Loaded: loaded (/etc/systemd/system/pilight.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Sat 2019-06-08 20:58:18 CEST; 44s ago
  Process: 385 ExecStart=/usr/local/sbin/pilight-daemon (code=exited, status=0/SUCCESS)
 Main PID: 454 (code=killed, signal=ABRT)
Jun 08 20:58:00 raspberrypi systemd[1]: Starting pilight...
Jun 08 20:58:02 raspberrypi systemd[1]: Started pilight.
Jun 08 20:58:18 raspberrypi pilight-daemon[385]: pilight-daemon: /home/pilight/source/daemon-dev/libs/pilight/core/json.c:1147: emit_string: Assertion `utf8_validate(str)' failed.
Jun 08 20:58:18 raspberrypi systemd[1]: pilight.service: Main process exited, code=killed, status=6/ABRT
Jun 08 20:58:18 raspberrypi systemd[1]: pilight.service: Unit entered failed state.
Jun 08 20:58:18 raspberrypi systemd[1]: pilight.service: Failed with result 'signal'.

If I start pilight manually after that, pilight starts with no Errors.

My Config:

Code:
{
 "devices": {
  "zeit": {
   "protocol": [ "datetime" ],
   "id": [{
    "longitude": 13.15,
    "latitude": 52.66
   }],
   "year": 2019,
   "month": 6,
   "day": 8,
   "hour": 19,
   "minute": 21,
   "second": 21,
   "weekday": 7,
   "dst": 1
  },
  "keller_ha": {
   "protocol": [ "elro_800_switch" ],
   "id": [{
    "systemcode": 23,
    "unitcode": 1
   }],
   "state": "off"
  },
  "helper": {
   "protocol": [ "generic_switch" ],
   "id": [{
    "id": 101
   }],
   "state": "off"
  },
  "label1": {
   "protocol": [ "generic_label" ],
   "id": [{
    "id": 100
   }],
   "label": "nein",
   "color": "black"
  },
  "label2": {
   "protocol": [ "generic_label" ],
   "id": [{
    "id": 100
   }],
   "label": "nein",
   "color": "black"
  },
  "sensor_keller": {
   "protocol": [ "tfa30" ],
   "id": [{
    "id": 60
   }],
   "temperature": 26.7,
   "humidity": 40.0
  },
  "sensor_draussen": {
   "protocol": [ "tfa30" ],
   "id": [{
    "id": 62
   }],
   "temperature": 27.0,
   "humidity": 40.0
  }
 },
 "rules": {
  "oktovent": {
   "rule": "IF helper.state == on AND OKTOVENT(sensor_draussen.temperature,sensor_draussen.humidity,sensor_keller.temperature,sensor_keller.humidity) THEN switch DEVICE keller_ha TO on ELSE switch DEVICE keller_ha TO off",
   "active": 1
  },
  "oktoventlabel": {
   "rule": "IF OKTOVENT(sensor_draussen.temperature,sensor_draussen.humidity,sensor_keller.temperature,sensor_keller.humidity) THEN label DEVICE label2 TO ja ELSE label DEVICE label2 TO nein",
   "active": 1
  },
  "zeitschaltuhr1": {
   "rule": "IF ((datetime.hour == 6) AND datetime.minute == 0 AND datetime.second == 0) THEN switch DEVICE helper TO on FOR '60 MINUTE'",
   "active": 1
  },
  "zeitschaltuhr2": {
   "rule": "IF ((datetime.hour == 9) AND datetime.minute == 0 AND datetime.second == 0) THEN switch DEVICE helper TO on FOR '30 MINUTE'",
   "active": 1
  },
  "zeitschaltuhr3": {
   "rule": "IF ((datetime.hour == 12) AND datetime.minute == 0 AND datetime.second == 0) THEN switch DEVICE helper TO on FOR '60 MINUTE'",
   "active": 1
  },
  "zeitschaltuhr4": {
   "rule": "IF ((datetime.hour == 15) AND datetime.minute == 0 AND datetime.second == 0) THEN switch DEVICE helper TO on FOR '30 MINUTE'",
   "active": 1
  },
  "zeitschaltuhr5": {
   "rule": "IF ((datetime.hour == 18) AND datetime.minute == 0 AND datetime.second == 0) THEN switch DEVICE helper TO on FOR '60 MINUTE'",
   "active": 1
  },
  "Oktolabel": {
   "rule": "IF helper.state == on THEN label DEVICE label1 TO ein ELSE label DEVICE label1 TO aus",
   "active": 1
  }
 },
 "gui": {
  "sensor_draussen": {
   "name": "Aussentemperatur",
   "group": [ "Keller" ],
   "media": [ "all" ]
  },
  "sensor_keller": {
   "name": "Kellertemperatur",
   "group": [ "Keller" ],
   "media": [ "all" ]
  },
  "label1": {
   "name": "Zeitschaltuhr",
   "group": [ "Keller" ],
   "media": [ "all" ]
  },
  "label2": {
   "name": "Lüften sinnvoll?",
   "group": [ "Keller" ],
   "media": [ "all" ]
  },
  "keller_ha": {
   "name": "Ventilator HA",
   "group": [ "Keller" ],
   "media": [ "all" ]
  }
 },
 "settings": {
  "log-level": 6,
  "pid-file": "/var/run/pilight.pid",
  "log-file": "/var/log/pilight.log",
  "standalone": 0,
  "webserver-enable": 1,
  "webserver-root": "/usr/local/share/pilight/webgui",
  "webserver-http-port": 5001,
  "webserver-https-port": 5002,
  "webserver-cache": 1,
  "whitelist": "",
  "gpio-platform": "raspberrypi3"
 },
 "hardware": {
  "433gpio": {
   "sender": 0,
   "receiver": 1
  }
 },
 "registry": {
  "webserver": {
   "ssl": {
    "certificate": {
     "location": "/etc/pilight/pilight.pem"
    }
   }
  },
  "pilight": {
   "version": {
    "current": "8.1.4"
   }
  }
 }
}

Any Ideas? Mayby Lua is not loaded while pilight is starting? Is there a way to suspend pilight a few seconds?
 
Reply
#2
pilight debug output or logs are the only places that can tell us why.
 
Reply
#3
Hm. does not work out for me.

On Startup, the Logfiles (tail -f /var/log/pilight.log) stay empty.
And if I start pilight-daemon -D, pilight is running with no Errors.

How can I monitor the first start at Startup, because the Error only then happens?

Or else, for testing, how can I delay pilight for a few seconds at Startup?
 
Reply
#4
Maybe add a delay in the init script?
 
Reply
#5
(06-09-2019, 12:24 PM)curlymo Wrote: Maybe add a delay in the init script?

Could  you please be a little more specific? Sorry for beeing a Copy/Paste User, but if I had Knowledge, where to do this best, I‘ve wouldnt have been asking?
 
Reply
#6
That's fine, but sometimes it's as easy as googling. "pilight start delay" pointed me to this post:
https://forum.pilight.org/showthread.php...0#pid20300
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
Tongue pilight 8.1.5-1-gc0a175e0 Chrashes fleisch 4 143 08-17-2019, 01:04 PM
Last Post: curlymo
  pilight for Raspbian Buster (raspberry pi 4) ? starob 29 1,579 07-15-2019, 08:45 PM
Last Post: curlymo
  pilight-receive Filteroption not working Alex 2 358 07-14-2019, 08:35 AM
Last Post: Alex
  pilight usb nano format conversion ettman8 2 249 07-14-2019, 08:32 AM
Last Post: curlymo
  pilight 8.1.4 crashes after some hours Ulrich.Arnold 47 2,039 06-29-2019, 08:58 PM
Last Post: curlymo
  Raspberry PI, gpio-ir-tx and pilight not starting lordslash 5 556 06-11-2019, 05:19 PM
Last Post: curlymo
  GPIO input -> starting a rule scootermacro 1 136 06-09-2019, 07:40 AM
Last Post: curlymo
  Google Assistant coupled to pilight hansrijn2 4 928 05-29-2019, 06:54 PM
Last Post: curlymo
  pilight-send does not stop (terminate) va13 3 474 05-15-2019, 06:06 PM
Last Post: curlymo
  oom_reaper: reaped process pilight-daemon va13 4 538 05-15-2019, 08:03 AM
Last Post: va13

Forum Jump:


Browsing: 1 Guest(s)