Hi Jim,

I'm trying to piece out the issues from your report. Clearly there is an
error.

This initial owsever fail on boot may be a timing issue -- not everything
initialized yet. Also I'm not sure of the built-in configuration file for
owserver on boot in the pi package -- is it correct? Finally the boot
scripts may be misreporting the owserver status. it would be easy to test
by looking at a 'ps axf' listing.

You did a lot of test cases, let me see if I can understand them:

1. owfs (+ alias) works correctly

2. owserver + owfs (no alias) doubles sensor entries.
3. owserver + owhttp (no alias) doubles sensor entries.

4. owserver (?no alias) + owhttpd (+ alias) works correctly

etc...

One thing that occurs to me is that two copies of owserver might be
running? They shouldn't both be allowed to bind to the same port (4304) and
I'm surprised the i2c bus allows it so I may be off target.

It would also help if you can tell us the owfs version.


On Sun, Feb 24, 2013 at 3:34 PM, Jim Robertson <[email protected]>wrote:

> folks I know this is a lot but!
>
>
> 24 Feb 2013****
> Running a pie with the new 512 memory,  i2c=/dev/i2c-1****
> With only a monitor connected. ssh connected through a term session on a
> mac-mini.  I have run the pi with a keyboard and mouse same results.****
>
> Built the sh card on Debian wheezy - 2012-08-08-wheezy-armel-1.img ****
> Installed owfs with sudo apt-get owfs files where placed in  /usr/bin****
>
> using a RP12 sheepwalks i2c adapter which has a breadboard with 5****
> DS 18S20 temp sensors. ****
>
> Plan on having the pie run a solar panel system and some radiant****
> Heating 24-7****
>
> On boot I do get the msg:****
> [FAIL] Starting 1-wire TCP Server: owserver failed****
>
> running the test command: ****
>
> pi@raspberrypi /usr/bin $ sudo *owfs* --i2c=/dev/i2c-1:ALL -F -m
> /var/1-wire/mnt -a alias.txt --nozero --allow_other****
>
> *produces the results.*
>
> pi@raspberrypi /usr/bin $ *ls */var/1-wire/mnt****
> alarm  bus.1  mt_floor  mt_otside  mt_panel  mt_waterin  mt_waterout
> settings  simultaneous  statistics  structure  system  uncached****
>
> pi@raspberrypi /usr/bin $ *ls* /var/1-wire/mnt/*mt_panel*****
> address  alias  crc8  errata  family  id  locator  power  r_address  r_id
> r_locator  *temperature*  temphigh  templow  type****
>
> conclusion owfs alone runs alias files loaded in with subdirectorys and
> temperature files ****
>  ****
> Note: one entry per sensor with subdirectorys.****
>  ****
> Reboot  or sometimes sudo killall owfs****
> /////////////****
>
> Running the system****
> /usr/bin $ *sudo owserver *-p 4304 --nozero --i2c=/dev/i2c-1:ALL****
> /usr/bin $ *sudo owfs* -F -s localhost:4304 -m /var/1-wire/mnt
> --allow_other****
>
> pi@raspberrypi /usr/bin $ sudo *ls* /var/1-wire/mnt****
> 10.384A3B020800  10.5E503B020800  10.83373B020800  10.D6263B020800
> 10.F83A3B020800  alarm  *bus.1*     simultaneous  structure  uncached****
> 10.384A3B020800  10.5E503B020800  10.83373B020800  10.D6263B020800
> 10.F83A3B020800  *bus.0*  settings  statistics    system****
>
> pi@raspberrypi /usr/bin $ sudo *ls* /var/1-wire/mnt/10.384A3B020800****
> address  alias      crc8  errata  family  id  locator  power  r_address
> r_id  r_locator  temperature  *temphigh * templow  type****
>
> //****
>
> sudo owhttpd –p 3000 –s localhost:4304 –nozero ****
> runs fine and I can httpd and see both pages for the sensors.****
>
> If I run *owhttpd* with *–a alias.txt* I just see one page.****
>
> //////****
>
> pi@raspberrypi /usr/bin $ sudo *ls* /var/1-wire/mnt/10.384A3B020800****
> address  alias      crc8  errata  family  id  locator  power  r_address
> r_id  r_locator  *temperature*  temphigh  templow  type****
>
> note :****
> 1.    no –a alias command ****
> 2.    the double entry’s  and double bus 0 and 1 in /mnt but I still have
> the subdirectory with temps!****
>       it shure would be nice to be able to use –a alias names!****
> ////////////****
>
> pi@raspberrypi /usr/bin $ sudo killall owfs****
>
> pi@raspberrypi /usr/bin $ sudo *owfs *-F -s localhost:4304 -*a alias.txt*
> -m /var/1-wire/mnt --allow_other****
>
> pi@raspberrypi /usr/bin $ sudo *ls* /var/1-wire/mnt****
> alarm  bus.1        mt_floor   mt_otside  mt_panel    mt_waterin
> mt_waterout  simultaneous  structure  uncached****
> bus.0  mt_floor  mt_otside  mt_panel   mt_waterin  mt_waterout
> settings     statistics    system****
> pi@raspberrypi /usr/bin $ sudo *ls */var/1-wire/mnt/mt-panel****
> ls: cannot access /var/1-wire/mnt/mt-panel: *No such file or directory****
> *
>
> note:****
> still double entrys still two buses! ****
> when I use the: –a alias.txt I loose the subdirectory with the temperature
> file****
>
> sudo owhttpd –p 3000 –s localhost:4304 –a alias.txt –nozero ****
> runs fine but I *can not* see both pages for the sensors****
>
> so my 3 questions are:****
> 1. Why on boot up do I get   owserver TCP server fail ****
> 2. Why the double entrys in the /mnt directory anytime I use owserver?****
> 3. Why  running the owserver and then owfs with *–a alias.txt *causes
> /mnt/mt_panel but no subdirectory with temperature file ****
>  4. If double entrys in /mnt are normal why dose the –a alias.txt****
> file work alone with owfs but crates problems if I run owserver first?****
>
> sudo shutdown –h now shows tcp owserver being stoped
> so I suspect the startup error on tcp is not a problem?
>
> be nice I have only been in linux for about 3 weeks.****
>
>
>
> Jim****
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to