Hi!
i feel i have to reply to this!
i am running owfs mounted filesystem 24/7 for over 1 year now. its running on 3
different devices
sheevaplug,linux pc and now seagate dockstar.
i have for this time total stability, i have never seen any outage all sensors
are there.
i have 7 sensors, different model and different company.
(temp,humid,pressure,light,power switches ...)
so i think its your system, kernel, distro or maybe the owfs version.
i am using 2.8 and 2.7 and on ARM and x86 all works fine.
cheers,
Zoff.
Molnar Domokos wrote:
> Hi Eloy,
>
> I do not use aliases, all files are accessed directly.
>
> Cheers,
> Doma
>
> On 09/10/2010 01:13 PM, Eloy Paris wrote:
>> Hi Doma, list,
>>
>> On 09/10/2010 05:02 AM, Molnar Domokos wrote:
>>
>>> Hi,
>>>
>>> I have just read the thread *owfs-mounted directory fails first time
>>> after inactivity period
>>> <http://sourceforge.net/mailarchive/message.php?msg_name=4C7825D1.2070809%40chapus.net>
>>> *and may have something related to it.
>> I also have additional information related to this -- I am now polling
>> the sensors every five minutes so the TCP connection from owfs to
>> owserver is not timing out, as described in the above thread, and things
>> are pretty stable. Before finishing my implementation, though, I played
>> with the alias feature:
>>
>> http://owfs.org/index.php?page=aliases
>>
>> and that *was* causing the same stability problems described in the
>> above thread, but in a different way, i.e. I sniffed traffic on the wire
>> and the TCP connection was not dying, if I remember correctly, but still
>> my sensors would disappear from the owfs-mounted directory every now and
>> then.
>>
>> I didn't troubleshoot any further, and just stopped using OWFS aliases
>> (handled the 1-wire address to sensible sensor name matter in the script
>> that polls sensor data), and this made the instability problem go away.
>>
>> So, a shot in the dark -- are you using OWFS aliases? Based on a quick
>> look at your log entries below it doesn't seem like it but I thought I'd
>> ask just in case and also take this as a chance to document my
>> experience with the alias feature since I had not done that yet.
>>
>> Cheers,
>>
>> Eloy Paris.-
>>
>>> I have been running owfs lights out to control my HVAC at home for about
>>> 3 years, I have switches and temp sensors on it, and it works in "real
>>> time" so I had to resolve the stability issue with programming around.
>>>
>>> My HVAC controller reads the temperature of the furnace in a loop as it
>>> needs to act fast on temperature changes by switching on/off the gas
>>> burner and water pumps and magnetic valves. As a result I have a fair
>>> bit of experience with the stability of owfs.
>>>
>>> It is not very stable so I my controller does the following:
>>> Level1: The code catches the read/write exception of owfs provided files
>>> and retries max. 10 times, if does not succeed then
>>> Level2: Kills owfs with -9, umounts /mnt/1wire and restarts owfs
>>> If Level2 error happens it logs the event.
>>>
>>> Level1 error happens about every other day, while Level2 happens less
>>> frequently but it really is random.
>>>
>>> Here is the log for Level2 events from 1st of August this year. As you
>>> can see sometimes it goes on for 10, even 20 days w/o Level2 errors,
>>> then it just happens. Nothing changes in the usage pattern of the
>>> network or the controller, all sensors are continuously read, and all
>>> PIOs are written.
>>>
>>> The exceptions are mostly "No such file or directory" but sometimes
>>> "Software caused connection abort" happens too.
>>>
>>> It runs on a CentOs 5.4., with owfs 2.7p39, with zero caching as I need
>>> the new values every time.
>>>
>>>
>>> LOGITEM BEGIN @Mon Aug 2 22:14:07 2010
>>> Logging reason: Owfs restart logging
>>> Active state: Off
>>> Exception message: #<Errno::ECONNABORTED: Software caused connection
>>> abort - /mnt/1wire/10.869724010800/temperature>
>>> State history : (Off)->(Off)->(Off)->(Off)->(Off)
>>> LOGITEM END
>>>
>>> LOGITEM BEGIN @Sat Aug 7 18:58:15 2010
>>> Logging reason: Owfs restart logging
>>> Active state: Off
>>> Exception message: #<Errno::ENOENT: No such file or directory -
>>> /mnt/1wire/10.869724010800/temperature>
>>> State history : (Off)->(Off)->(Off)->(Off)->(Off)
>>> LOGITEM END
>>>
>>> LOGITEM BEGIN @Sun Aug 8 16:47:18 2010
>>> Logging reason: Owfs restart logging
>>> Active state: Off
>>> Exception message: #<Errno::ENOENT: No such file or directory -
>>> /mnt/1wire/10.869724010800/temperature>
>>> State history : (Off)->(Off)->(Off)->(Off)->(Off)
>>> LOGITEM END
>>>
>>> LOGITEM BEGIN @Sat Aug 14 20:20:50 2010
>>> Logging reason: Owfs restart logging
>>> Active state: Off
>>> Exception message: #<Errno::ENOENT: No such file or directory -
>>> /mnt/1wire/10.869724010800/temperature>
>>> State history : (Off)->(Off)->(Off)->(Off)->(Off)
>>> LOGITEM END
>>>
>>> LOGITEM BEGIN @Sun Aug 15 07:24:49 2010
>>> Logging reason: Owfs restart logging
>>> Active state: Off
>>> Exception message: #<Errno::ENOENT: No such file or directory -
>>> /mnt/1wire/10.869724010800/temperature>
>>> State history : (Off)->(Off)->(Off)->(Off)->(Off)
>>> LOGITEM END
>>>
>>> LOGITEM BEGIN @Wed Aug 18 09:19:22 2010
>>> Logging reason: Owfs restart logging
>>> Active state: Off
>>> Exception message: #<Errno::ENOENT: No such file or directory -
>>> /mnt/1wire/05.1AED31000000/PIO>
>>> State history : (Off)->(Off)->(Off)->(Off)->(Off)
>>> LOGITEM END
>>>
>>> LOGITEM BEGIN @Mon Sep 6 19:35:40 2010
>>> Logging reason: Owfs restart logging
>>> Active state: Off
>>> Exception message: #<Errno::ENOENT: No such file or directory -
>>> /mnt/1wire/05.200232000000/PIO>
>>> State history : (Off)->(Off)->(Off)->(Off)->(Off)
>>> LOGITEM END
>>>
>>> LOGITEM BEGIN @Thu Sep 9 13:47:47 2010
>>> Logging reason: Owfs restart logging
>>> Active state: Off
>>> Exception message: #<Errno::ENOENT: No such file or directory -
>>> /mnt/1wire/10.24E323010800/temperature>
>>> State history : (Off)->(Off)->(Off)->(Off)->(Off)
>>> LOGITEM END
>>>
>>> Cheers,
>>> Doma
>>>
>> ------------------------------------------------------------------------------
>> Automate Storage Tiering Simply
>> Optimize IT performance and efficiency through flexible, powerful,
>> automated storage tiering capabilities. View this brief to learn how
>> you can reduce costs and improve performance.
>> http://p.sf.net/sfu/dell-sfdev2dev
>> _______________________________________________
>> Owfs-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>
>
> ------------------------------------------------------------------------------
> Automate Storage Tiering Simply
> Optimize IT performance and efficiency through flexible, powerful,
> automated storage tiering capabilities. View this brief to learn how
> you can reduce costs and improve performance.
> http://p.sf.net/sfu/dell-sfdev2dev
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful,
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance.
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers