• 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 development installation -- failed / what is the secret?
#1
What is the secret to install the development version successfully?

Using a new SDcard with Raspian Jessie Light and had installed pilight v.7.0 stable and that was running well.

To install the dev version I first remove pilight with "apt-get remove pilight", rebooted and followed the instructions for installing, having
Code:
root@rpi4:/home/pi# cat /etc/apt/sources.list.d/pilight.list
deb http://apt.pilight.org/ stable main
deb http://apt.pilight.org/ nightly main
root@rpi4:/home/pi#
See below the resulting installation listing.

Can't see any error only the pilight doesn't start as can be seen with service pilight status

What's necessary for a successful installation?




Code:
pi@rpi4:~ $ sudo su
root@rpi4:/home/pi# wget -O - http://apt.pilight.org/pilight.key | apt-key add -
converted 'http://apt.pilight.org/pilight.key' (ANSI_X3.4-1968) -> 'http://apt.pilight.org/pilight.key' (UTF-8)
--2017-02-02 17:53:50--  http://apt.pilight.org/pilight.key
Resolving apt.pilight.org (apt.pilight.org)... 94.124.143.207
Connecting to apt.pilight.org (apt.pilight.org)|94.124.143.207|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3079 (3.0K) [application/pgp-keys]
Saving to: 'STDOUT'

-                                  100%[===============================================================>]   3.01K  --.-KB/s   in 0s    

2017-02-02 17:53:50 (29.1 MB/s) - written to stdout [3079/3079]

OK
root@rpi4:/home/pi# apt-get update        
Hit http://apt.pilight.org stable InRelease
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://apt.pilight.org nightly InRelease  
Hit http://archive.raspberrypi.org jessie InRelease
Hit http://apt.pilight.org stable/main armhf Packages
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages      
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages                  
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages                  
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages                      
Ign http://apt.pilight.org stable/main Translation-en                                  
Hit http://apt.pilight.org nightly/main armhf Packages                                  
Ign http://apt.pilight.org nightly/main Translation-en                                  
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en
Ign http://mirrordirector.raspbian.org jessie/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/non-free Translation-en
Ign http://mirrordirector.raspbian.org jessie/rpi Translation-en  
Hit http://archive.raspberrypi.org jessie/main armhf Packages    
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Ign http://archive.raspberrypi.org jessie/main Translation-en            
Ign http://archive.raspberrypi.org jessie/ui Translation-en              
Reading package lists... Done                                                                                                          
root@rpi4:/home/pi# apt-get install pilight
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following extra packages will be installed:
  pilight-webgui
Suggested packages:
  php5-cgi pilight-firmware
The following NEW packages will be installed:
  pilight pilight-webgui
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/6858 kB of archives.
After this operation, 118 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Can't set locale; make sure $LC_* and $LANG are correct!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LC_TIME = "de_DE.UTF-8",
        LC_MONETARY = "de_DE.UTF-8",
        LC_ADDRESS = "de_DE.UTF-8",
        LC_TELEPHONE = "de_DE.UTF-8",
        LC_NAME = "de_DE.UTF-8",
        LC_MEASUREMENT = "de_DE.UTF-8",
        LC_IDENTIFICATION = "de_DE.UTF-8",
        LC_NUMERIC = "de_DE.UTF-8",
        LC_PAPER = "de_DE.UTF-8",
        LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory
Selecting previously unselected package pilight-webgui.
(Reading database ... 31956 files and directories currently installed.)
Preparing to unpack .../pilight-webgui_7.4_armhf.deb ...
Unpacking pilight-webgui (7.4) ...
Selecting previously unselected package pilight.
Preparing to unpack .../pilight_7.0.172-g9249fd0_armhf.deb ...
Unpacking pilight (7.0.172-g9249fd0) ...
Setting up pilight-webgui (7.4) ...
Setting up pilight (7.0.172-g9249fd0) ...
Processing triggers for libc-bin (2.19-18+deb8u7) ...
root@rpi4:/home/pi# service pilight start
root@rpi4:/home/pi# service pilight status
● pilight.service - LSB: Starts pilight-daemon
   Loaded: loaded (/etc/init.d/pilight)
  Drop-In: /etc/systemd/system/pilight.service.d
           └─pilight.conf
   Active: active (exited) since Thu 2017-02-02 17:56:25 CET; 8s ago
  Process: 875 ExecStart=/etc/init.d/pilight start (code=exited, status=0/SUCCESS)

Feb 02 17:56:25 rpi4 pilight[875]: Starting : pilight failed!
Feb 02 17:56:25 rpi4 systemd[1]: Started LSB: Starts pilight-daemon.
root@rpi4:/home/pi#
 
Reply
#2
Ok, just totally reinstalled Jessie Light with all update/upgrades and installed the pilight dev on top of that again.

Again, same result!
Code:
root@rpi4:/home/pi# service pilight start
root@rpi4:/home/pi# service pilight status
● pilight.service - LSB: Starts pilight-daemon
   Loaded: loaded (/etc/init.d/pilight)
   Active: active (exited) since Thu 2017-02-02 23:35:12 CET; 6s ago
  Process: 981 ExecStart=/etc/init.d/pilight start (code=exited, status=0/SUCCESS)

Feb 02 23:35:12 rpi4 pilight[981]: Starting : pilight failed!
Feb 02 23:35:12 rpi4 systemd[1]: Started LSB: Starts pilight-daemon.

It's NOT possible to get the pilight dev version up and running! WHY?
 
Reply
#3
Which Kernel do you use ? Content of
Logging files in /var/log/pilight.err and .log ?

It also could be that the network is not fully up and running when pilight service starts up.
Gesendet von iPhone mit Tapatalk
 
Reply
#4
Thanks for the reply .. I can only answer part of it because I had to reinstall the stable version already.

I'm using Jessie light and platform is:
Code:
>>> platform.platform()
'Linux-4.4.34+-armv6l-with-debian-8.0'

No details for : Logging files in /var/log/pilight.err and .log ? Sorry.

Networking is up and running, the err is not only at bootup but also with manual call to "service pilight start".
Also the same networking with pilight 7.0 stable installation works well, see also other threads:
https://forum.pilight.org/Thread-Raspbia...6#pid19876

There are very interesting points about networking with Jessie compared with wheezy which was my solid installation over the last years. See the following discussion. Sorry it's German, but I'm sure the technical content is easy to understand .. also there are English discussions on the net also:
http://www.forum-raspberrypi.de/Thread-p...#pid264723

Would be great to find a dev installation to be able to support pilight dev with piSchedule as requested by users.
Thanks
 
Reply
#5
You need to pull up the forum links regarding run level for pilight an pischedule here on the forum. I submitted a Pull Request for it. Please check both files whether those modifications are integrated.
There is another issue for users who did not upgrade from wheezy to Jessie but use a blank Jessie framework as the startup scripts in use may be different.
I changed my up and down scripts.
3rd there is an issue with networking that I never fully investigated.
In etc/network/interfaces
Set iface eth0 to dhcp,
if you have wifi set allow-hot plug wlan0 and set iface to manual,
use wpa_supplicant for configuration and wpa_roam to configure your wifi using wpa-supplicant.conf
remove the iface line with default dhcp


Gesendet von iPhone mit Tapatalk
 
Reply
#6
If you refer with this
Quote:You need to pull up the forum links regarding run level for pilight an pischedule here on the forum. I submitted a Pull Request for it. Please check both files whether those modifications are integrated.
to the Runlevel setting. Yes I have Runlevel 3 4 5 for pilight and Runlevel 2 3 4 5 for piSchedule and that's OK for pilight stable!

And
Quote:I changed my up and down scripts.
Which, is there a listing of them?

With the network setting I'm not with you. Could you read the different infos about networking for Jessie? My current settings are doing well with stable, why not with the dev version?

--------------------
Add Note for the Runlevel

For the runlevel for piSchedule (which has to be started after pilight) I'm not sure to add the runlevel 2 makes a difference. Just tested pilight/piSchedule after I changed from without 2 to adding 2. Both situation do well, the ssdp is OK!

For pilight i have the beginning of /etc/init.d/pilight
Code:
#! /bin/sh
### BEGIN INIT INFO
# Provides:          pilight-daemon
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     3 4 5
# Default-Stop:      0 1 6
# Short-Description: Starts pilight-daemon
# Description:       Starts pilight-daemon
#
### END INIT INFO

... for /etc/init.d/piSchedule
Code:
#!/bin/bash
### BEGIN INIT INFO
# Provides:          piSchedule
# Required-Start:    $remote_fs $syslog $all
# Required-Stop:     $remote_fs $syslog
# Should-Start:      pilight
# Default-Start:     3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start|Stop service for piSchedule
# Description:       Start|Stop service for piSchedule
### END INIT INFO
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Bug: double free or corruption in pilight-send blackzombie 12 123 10-07-2019, 08:15 PM
Last Post: blackzombie
  pilight-control modify values coolinx 2 84 09-20-2019, 07:24 PM
Last Post: coolinx
  [Fixed] High CPU usage when pilight usb nano disconnects DieterK 1 136 08-13-2019, 05:43 PM
Last Post: curlymo
  pilight Nano USB interface curlymo 228 97,266 07-10-2019, 06:14 PM
Last Post: curlymo
  problems compiling pilight on Odroid C2 WitchDoctor 101 9,789 03-14-2019, 09:01 PM
Last Post: curlymo
  pilight 8 what chages for custom protocols? polo 11 2,924 02-15-2019, 06:22 PM
Last Post: polo
  Git active branches and development behrisch 9 600 01-21-2019, 09:09 PM
Last Post: behrisch
  pilight-debug shows nothing minhdomanh 3 544 10-18-2018, 07:01 AM
Last Post: felfert
  pilight-send and pilight-daemon DieterK 0 566 06-20-2018, 12:44 AM
Last Post: DieterK
  Lights not switched on or off by rules in pilight 8.1.0 rorie 22 2,503 06-12-2018, 03:56 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)