I recently moved my OWFS setup to a new installation (on Funtoo,
should it matter), and have noticed that I do have the issue Markus
mentioned.

I haven't spent much time debugging quite yet.  Curiously, though,
while 'cat' doesn't work, other methods of reading such as 'head' or
opening the file in Python seem unaffected.

~Jacob


On Sun, 04 Jan 2015 10:59:08 +0100
Stefano Miccoli <mo...@icloud.com> wrote:

> It seems that your question is still unanswered, so I will try to
> help you, although I___m not able to replicate your setup (and I___m no
> expert of the internal workings of owfs).
> 
> From your message it seems that the problem is limited to owfs, and
> not in owserver, but let me double-check.
> 
> 1) Do you have an owserver running and owfs is quering owserver? 
> (You can check by inspecting owfs.conf and running ___sudo netstat
> -tlp___. If there is an owserver deamon running there should be a line
> like
> 
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address           Foreign Address
> State       PID/Program name tcp        0      0
> *:4304                  *:*                     LISTEN
> 31595/owserver  
> 
> 2) If you have an owserver running can you confirm that
> ___owread /10.FE771D020800/temperature___ gives you a sensible answer
> while ___cat /mnt/1wire/10.FE771D020800/temperature___ yields an error?
> 
> 
> If the problem is only in owfs a workaround would be using
> owdir/owread/owwrite in the shell, and one of the clients in
> module/ownet for other languages. 
> 
> Bye
> 
> Stefano
> 
> > On 30 Dec 2014, at 22:15, Markus Gaugusch <mar...@gaugusch.at
> > <mailto:mar...@gaugusch.at>> wrote:
> > 
> > Hi,
> > 
> > Symptom:
> > monitor:/mnt/1wire/10.FE771D020800 # cat temperature
> > cat: temperature: Message too long
> > 
> > I've updated my monitoring server from openSUSE 13.1 to 13.2, which
> > broke owfs. I had 2.9p5 before and also tried to update to 2.9p8,
> > but the problem stayed the same. Access using owdir, owget and
> > owwrite works fine. I've started owfs in debug mode, leading to the
> > following output (error at the bottom).
> > 
> >   DEBUG: ow_tcp_read.c:(63) attempt 24 bytes Time: 2.000000 seconds
> >   DEBUG: ow_tcp_read.c:(113) read: 24 - 0 = 24
> >   DEBUG: ow_tcp_read.c:(63) attempt 8 bytes Time: 2.000000 seconds
> >   DEBUG: ow_tcp_read.c:(113) read: 8 - 0 = 8
> >   DEBUG: ow_buslock.c:(54) pthread_mutex_lock 9A270CC begin
> >   DEBUG: ow_buslock.c:(54) pthread_mutex_lock 9A270CC done
> >   DEBUG: ow_buslock.c:(56) pthread_mutex_lock B779D9A0 begin
> >   DEBUG: ow_buslock.c:(56) pthread_mutex_lock B779D9A0 done
> >   DEBUG: ow_buslock.c:(56) pthread_mutex_unlock B779D9A0 begin
> >   DEBUG: ow_buslock.c:(56) pthread_mutex_unlock B779D9A0 done
> >   DEBUG: ow_buslock.c:(76) pthread_mutex_lock B779D9A0 begin
> >   DEBUG: ow_buslock.c:(76) pthread_mutex_lock B779D9A0 done
> >   DEBUG: ow_buslock.c:(79) pthread_mutex_unlock B779D9A0 begin
> >   DEBUG: ow_buslock.c:(79) pthread_mutex_unlock B779D9A0 done
> >   DEBUG: ow_buslock.c:(81) pthread_mutex_unlock 9A270CC begin
> >   DEBUG: ow_buslock.c:(81) pthread_mutex_unlock 9A270CC done
> >   DEBUG: ow_presence.c:(269) Presence of 10 FE 77 1D 02 08 00 3A
> > FOUND on bus 127.0.0.1
> >   DEBUG: ow_cache.c:(546) Adding device location 10 FE 77 1D 02 08
> > 00 3A bus=0
> >   DEBUG: ow_cache.c:(635) Add to cache sn 10 FE 77 1D 02 08 00 3A 
> > pointer=0xb779d914 index=0 size=4
> >   DEBUG: ow_cache.c:(667) pthread_mutex_lock B779D9A0 begin
> >   DEBUG: ow_cache.c:(667) pthread_mutex_lock B779D9A0 done
> >   DEBUG: ow_cache.c:(670) pthread_mutex_unlock B779D9A0 begin
> >   DEBUG: ow_cache.c:(670) pthread_mutex_unlock B779D9A0 done
> >   DEBUG: ow_cache.c:(336) pthread_mutex_lock B779D9A0 begin
> >   DEBUG: ow_cache.c:(336) pthread_mutex_lock B779D9A0 done
> >   DEBUG: ow_cache.c:(336) pthread_mutex_unlock B779D9A0 begin
> >   DEBUG: ow_cache.c:(336) pthread_mutex_unlock B779D9A0 done
> >   DEBUG: ow_read.c:(88) pthread_mutex_lock B779D9A0 begin
> >   DEBUG: ow_read.c:(88) pthread_mutex_lock B779D9A0 done
> >   DEBUG: ow_read.c:(95) pthread_mutex_unlock B779D9A0 begin
> >   DEBUG: ow_read.c:(95) pthread_mutex_unlock B779D9A0 done
> >   DEBUG: ow_read.c:(96) /10.FE771D020800/temperature return -90
> >   DEBUG: ow_parsename.c:(61) /10.FE771D020800/temperature
> >    unique: 140, error: -90 (Message too long), outsize: 16
> > unique: 141, opcode: RELEASE (18), nodeid: 41, insize: 64, pid: 0
> > release[0] flags: 0x8000
> >    CALL: owfs_callback.c:(135) RELEASE
> > path=/10.FE771D020800/temperature unique: 141, success, outsize: 16
> > 
> > 
> > 
> > It might be related to the new kernel, but I'm not sure ...
> > monitor:~ # uname -a
> > Linux monitor 3.16.7-7-default #1 SMP Wed Dec 17 18:00:44 UTC 2014
> > (762f27a) i686 i686 i386 GNU/Linux
> > 
> > 
> > Help! :-)
> > (and many thanks for owfs!)
> > 
> > kind regards,
> > Markus
> > 
> > ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming! The Go Parallel
> > Website, sponsored by Intel and developed in partnership with
> > Slashdot Media, is your hub for all things parallel software
> > development, from weekly thought leadership blogs to news, videos,
> > case studies, tutorials and more. Take a look and join the
> > conversation now. http://goparallel.sourceforge.net
> > <http://goparallel.sourceforge.net/>
> > _______________________________________________ Owfs-developers
> > mailing list Owfs-developers@lists.sourceforge.net
> > <mailto:Owfs-developers@lists.sourceforge.net>
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
> 

Attachment: pgpa3YJGa5baj.pgp
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to