[vz-users] 1wirevz läuft nicht mehr nach Update

[Heiko Baumann]

Am 11.11.2014 um 05:32 schrieb Udo1:
> Am 10.11.2014 22:53, schrieb Heiko Baumann:
>> root at BauratPi:/dev# less /etc/rc.local
>> echo ds2482 0x1a > /sys/bus/i2c/devices/i2c-1/new_device
>>
>> # Part of S0/Impulse to Volkszaehler 'RaspberryPI deamon'
>> #echo 17 > /sys/class/gpio/export && echo "in" > 
>> /sys/class/gpio/gpio17/direction && echo "falling" > 
>> /sys/class/gpio/gpio17/edge 
> Dann fehlen aber hier Einträge:
>
> echo ds2482 0x18 > /sys/bus/i2c/devices/i2c-1/new_device
> echo ds2482 0x19 > /sys/bus/i2c/devices/i2c-1/new_device
> echo ds2482 0x1a > /sys/bus/i2c/devices/i2c-1/new_device
>
> Gruß
> Udo
>
Hallo Udo,
hab nochmal nachgeschaut, die Einträge sind in /etc/rc.local drin:
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
   printf "My IP address is %s\n" "$_IP"
fi

#killall vzlogger
#/usr/local/bin/vzlogger
#/usr/local/bin/vzlogger-c

owfs

# Part of DS2482 I2C 1-Wire Master to Volkszaehler 'RaspberryPI deamon'.

#Raspberry Rev1 alle 3 rauskommentiert
#echo ds2482 0x18 > /sys/bus/i2c/devices/i2c-0/new_device
#echo ds2482 0x19 > /sys/bus/i2c/devices/i2c-0/new_device
#echo ds2482 0x1a > /sys/bus/i2c/devices/i2c-0/new_device

# Raspberry Rev2
echo ds2482 0x18 > /sys/bus/i2c/devices/i2c-1/new_device
echo ds2482 0x19 > /sys/bus/i2c/devices/i2c-1/new_device
echo ds2482 0x1a > /sys/bus/i2c/devices/i2c-1/new_device

# Part of S0/Impulse to Volkszaehler 'RaspberryPI deamon'
#echo 17 > /sys/class/gpio/export && echo "in" > 
/sys/class/gpio/gpio17/direction && echo "falling" > 
/sys/class/gpio/gpio17/edge
#echo 18 > /sys/class/gpio/export && echo "in" > 
/sys/class/gpio/gpio18/direction && echo "falling" > 
/sys/class/gpio/gpio18/edge
#echo 22 > /sys/class/gpio/export && echo "in" > 
/sys/class/gpio/gpio22/direction && echo "falling" > 
/sys/class/gpio/gpio22/edge
#echo 23 > /sys/class/gpio/export && echo "in" > 
/sys/class/gpio/gpio23/direction && echo "falling" > 
/sys/class/gpio/gpio23/edge
#echo 24 > /sys/class/gpio/export && echo "in" > 
/sys/class/gpio/gpio24/direction && echo "falling" > 
/sys/class/gpio/gpio24/edge
#echo 27 > /sys/class/gpio/export && echo "in" > 
/sys/class/gpio/gpio27/direction && echo "falling" > 
/sys/class/gpio/gpio27/edge

echo 17 > /sys/class/gpio/export && echo "rising" > 
/sys/class/gpio/gpio17/edge
echo 18 > /sys/class/gpio/export && echo "rising" > 
/sys/class/gpio/gpio18/edge
echo 22 > /sys/class/gpio/export && echo "rising" > 
/sys/class/gpio/gpio22/edge
echo 23 > /sys/class/gpio/export && echo "rising" > 
/sys/class/gpio/gpio23/edge
echo 24 > /sys/class/gpio/export && echo "rising" > 
/sys/class/gpio/gpio24/edge
echo 27 > /sys/class/gpio/export && echo "rising" > 
/sys/class/gpio/gpio27/edge
exit 0

Das müsste doch auch passen.

Mein vz läuft ohne 1wirevz stabil, keine Probleme die letzten Tage - 
aber ohne Temperaturen ist die Sache natürlich nicht so toll...

Gerade nochmal probiert, gleiches Problem direkt nach starten von 
/etc/init.d/1wirevz start:

Nov 12 14:48:14 BauratPi 1wirevz: DS2482 I²C 1-Wire® Master to 
Volkszaehler deamon 1.5 (2) 5
Nov 12 14:48:14 BauratPi 1wirevz: VzServer: 127.0.0.1
Nov 12 14:48:14 BauratPi 1wirevz: VzPort: 80
Nov 12 14:48:14 BauratPi 1wirevz: VzPath: middleware.php
Nov 12 14:48:14 BauratPi 1wirevz: Metering interval: 60 sec
Nov 12 14:48:14 BauratPi 1wirevz: 28-0000045c6924 (Bus: 1) (VzUUID: 
267f2810-f2dc-11e2-8d7c-cb14f79472e0)
Nov 12 14:48:14 BauratPi 1wirevz: 28-000004c969de (Bus: 1) (VzUUID: 
c80251e0-f2db-11e2-8178-ef2453dba49c)
Nov 12 14:48:14 BauratPi 1wirevz: 28-000004c963b9 (Bus: 1) (VzUUID: 
112ddc60-f2dc-11e2-9294-971d5a648238)
Nov 12 14:48:14 BauratPi 1wirevz: 28-000004c913d5 (Bus: 1) (VzUUID: 
1fb4b660-f2dc-11e2-9685-936d7367e7ac)
Nov 12 14:48:14 BauratPi 1wirevz: 28-000004c96a87 (Bus: 1) (VzUUID: 
06e27ce0-f2dc-11e2-9196-1793d6d6626c)
Nov 12 14:48:14 BauratPi 1wirevz: 28-000004c9583f (Bus: 1) (VzUUID: 
1843ebf0-f2dc-11e2-b68a-0d188c147a46)
Nov 12 14:48:14 BauratPi 1wirevz: 28-0000045d7eb0 (Bus: 2) (VzUUID: 
37e34a40-f2dc-11e2-a9f5-617f327e9a54)
Nov 12 14:48:14 BauratPi 1wirevz: 28-000004a2845a (Bus: 2) (VzUUID: 
3e744e20-f2dc-11e2-ab3d-e5709e8f1bd3)
Nov 12 14:48:14 BauratPi 1wirevz: 28-000004f1c7c6 (Bus: 2) (VzUUID: 
614b6c60-f2dc-11e2-8b34-43269275292a)
Nov 12 14:48:14 BauratPi 1wirevz: 28-0000045c5c7e (Bus: 2) (VzUUID: 
53e45780-f2dc-11e2-bb40-e1626f6aa1bd)
Nov 12 14:48:14 BauratPi 1wirevz: 28-000004f2467e (Bus: 2) (VzUUID: 
e5cd78a0-33fc-11e3-92ab-25b39d4959eb)
Nov 12 14:48:14 BauratPi 1wirevz: 28-0000045d2497 (Bus: 2) (VzUUID: 
46f672b0-f2dc-11e2-8c00-43a2ff77fb28)
Nov 12 14:48:14 BauratPi 1wirevz: No such file or directory
Nov 12 14:48:14 BauratPi 1wirevz: No such file or directory
Nov 12 14:48:14 BauratPi console-kit-daemon[2920]: GLib-CRITICAL: Source 
ID 260 was not found when attempting to remove it

und sofort danach 1wirevz stop:
Nov 12 14:48:18 BauratPi 1wirevz: Daemon exiting

Also werden doch direkt beim Starten die Sensoren richtig erkannt und 
zugeordnet, oder sehe ich das falsch?
Aber danach gibts sofort die Probleme... komisch....

Idee: ich könnte ja mal die einzelnen Busse testen, dh. erst mal Bus 2 
abklemmen und dann sehen was passiert. Kann ich die "am lebenden System" 
abklemmen oder muss ich den pi vorher immer runterfahren?