I tested two ways,
mick@tom:~$ ps -ewo pid,args | grep ow
1652 grep ow
mick@tom:~$
I would expect to see owserver listed, and
mick@tom:~$ sudo /opt/owfs/bin/owfs -s localhost:4304 -m /var/1-wire/mnt
--allow_other
DEFAULT: owlib.c:LibStart(54) No valid 1-wire buses found
mick@tom:~$
Also when I have run owserver with debug previously it keeps running and
provides more output as I access the system. When I run it now it
produces the output I posted and terminates.
Thanks
Mick
On 05/07/12 16:23, Paul Alfille wrote:
Hmm -- The debug output that you posted seems to show that owserver is
running. How are you testing?
Paul
And the debug output would say if the port was unavailable, so that's
not the issue.
On Thu, Jul 5, 2012 at 5:10 AM, Mick Sulley <m...@sulley.info
<mailto:m...@sulley.info>> wrote:
I tried a few different ports with the same result. Is there any
way to test a port to see is it is open? If I run nmap I get
mick@tom:~$ nmap localhost
Starting Nmap 5.00 ( http://nmap.org ) at 2012-07-05 09:45 BST
Interesting ports on localhost (127.0.0.1):
Not shown: 992 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
111/tcp open rpcbind
139/tcp open netbios-ssn
445/tcp open microsoft-ds
901/tcp open samba-swat
2049/tcp open nfs
3306/tcp open mysql
Nmap done: 1 IP address (1 host up) scanned in 0.16 seconds
mick@tom:~$
but I must confess I am a little out of my depth here. Would 4304
just open when I run owserver or should it show in the list?
Thanks
Mick
On 05/07/12 02:02, Paul Alfille wrote:
Is the port available? Try a different one.
On Wed, Jul 4, 2012 at 5:25 PM, Mick Sulley <m...@sulley.info
<mailto:m...@sulley.info>> wrote:
More testing - I just installed owfs-2.8p13, which is running
fine on my Ubuntu server, but on the Debian server I still
get the same problem, owfs will run but owserver will not. I
am starting to think this may be something I have set up
incorrectly. Any ideas what it could be?
Thanks
Mick
On 04/07/12 21:03, Mick Sulley wrote:
I just downloaded and installed owfs-2.8p16. I tried
testing with a DS9490R USB adapter and it does the same
thing, owfs on its own runs OK but owserver does not. I ran
owserver with --debug and this is what it returned. Is
there anything else I can do to try to debug this?
mick@tom:/usr/local/src/owfs-2.8p16$
<mailto:mick@tom:/usr/local/src/owfs-2.8p16$> sudo
/opt/owfs/bin/owserver -p 4304 -u --debug
DEBUG MODE
libow version:
2.8p16
DEBUG: ow_daemon.c:(167) main thread id = 139670356117248
DEBUG: ow_avahi_link.c:(75) Avahi support: libavahi-client
loaded successfully
DEBUG: ow_avahi_link.c:(77) Avahi library function found:
avahi_client_errno
DEBUG: ow_avahi_link.c:(78) Avahi library function found:
avahi_client_free
DEBUG: ow_avahi_link.c:(79) Avahi library function found:
avahi_client_new
DEBUG: ow_avahi_link.c:(80) Avahi library function found:
avahi_client_get_domain_name
DEBUG: ow_avahi_link.c:(81) Avahi library function found:
avahi_entry_group_add_service
DEBUG: ow_avahi_link.c:(82) Avahi library function found:
avahi_entry_group_commit
DEBUG: ow_avahi_link.c:(83) Avahi library function found:
avahi_entry_group_is_empty
DEBUG: ow_avahi_link.c:(84) Avahi library function found:
avahi_entry_group_new
DEBUG: ow_avahi_link.c:(85) Avahi library function found:
avahi_entry_group_reset
DEBUG: ow_avahi_link.c:(87) Avahi library function found:
avahi_service_resolver_free
DEBUG: ow_avahi_link.c:(88) Avahi library function found:
avahi_service_resolver_new
DEBUG: ow_avahi_link.c:(89) Avahi library function found:
avahi_service_browser_free
DEBUG: ow_avahi_link.c:(90) Avahi library function found:
avahi_service_browser_new
DEBUG: ow_avahi_link.c:(102) Avahi support:
libavahi-common loaded successfully.
DEBUG: ow_avahi_link.c:(104) Avahi library function found:
avahi_simple_poll_free
DEBUG: ow_avahi_link.c:(105) Avahi library function found:
avahi_simple_poll_get
DEBUG: ow_avahi_link.c:(106) Avahi library function found:
avahi_simple_poll_loop
DEBUG: ow_avahi_link.c:(107) Avahi library function found:
avahi_simple_poll_new
DEBUG: ow_avahi_link.c:(108) Avahi library function found:
avahi_simple_poll_quit
DEBUG: ow_avahi_link.c:(109) Avahi library function found:
avahi_strerror
CALL: ow_parsename.c:(98) path=[]
DEBUG: owlib.c:(82) Globals temp limits 0C 100C (for
simulated adapters)
CONNECT: ow_usb_cycle.c:(68) Bus master found: 2:3
DEFAULT: ow_usb_msg.c:(295) Opened USB DS9490 bus master at 2:3.
CALL: ow_parsename.c:(98) path=[]
CALL: ow_parsename.c:(98) path=[/uncached/bus.0]
DEBUG: ow_dir.c:(65) path=/uncached/bus.0
CALL: ow_dir.c:(100) path=/uncached/bus.0
CALL: ow_parsename.c:(98) path=[/uncached/bus.0/interface]
DEBUG: ow_usb_cycle.c:(125) Callback on
/uncached/bus.0/interface
DEBUG: ow_parsename.c:(62) /uncached/bus.0/interface
DEBUG: ow_search.c:(32) Start of directory
path=/uncached/bus.0 device=00 00 00 00 00 00 00 00
DEBUG: ow_ds9490.c:(606) Index 0
DEBUG: ow_select.c:(66) Selecting a path (and device)
path=/uncached/bus.0 SN=00 00 00 00 00 00 00 00 last path=00
00 00 00 00 00 00 00
DEBUG: ow_select.c:(79) Continuing root branch
DEBUG: ow_ds9490.c:(494) DS9490 RESET. changed 15, flex: 1
DATA: ow_ds9490.c:(941) set flexible speed
DEBUG: ow_ds9490.c:(545) DS9490_Reset: OK
DEBUG: ow_ds9490.c:(682) Got 16 bytes from USB search
DEBUG: ow_ds9490.c:(710) gulp. Adding element 0:10 0D 54
A9 01 08 00 DC
DEBUG: ow_ds9490.c:(624) SN found: 10 0D 54 A9 01 08 00 DC
DEBUG: ow_search.c:(74) Device found: 10 0D 54 A9 01 08 00 DC
DEBUG: ow_cache.c:(561) Adding device location 10 0D 54 A9
01 08 00 DC bus=0
DEBUG: ow_cache.c:(650) Add to cache sn 10 0D 54 A9 01 08
00 DC pointer=0x7f0789d5057c index=0 size=4
DEBUG: ow_cache.c:(561) Adding device location 10 0D 54 A9
01 08 00 DC bus=0
DEBUG: ow_cache.c:(650) Add to cache sn 10 0D 54 A9 01 08
00 DC pointer=0x7f0789d5057c index=0 size=4
CALL: ow_parsename.c:(98)
path=[/uncached/bus.0/10.0D54A9010800]
DEBUG: ow_usb_cycle.c:(125) Callback on
/uncached/bus.0/10.0D54A9010800
DEBUG: ow_parsename.c:(62) /uncached/bus.0/10.0D54A9010800
DEBUG: ow_ds9490.c:(606) Index 1
DEBUG: ow_select.c:(66) Selecting a path (and device)
path=/uncached/bus.0 SN=00 00 00 00 00 00 00 00 last path=00
00 00 00 00 00 00 00
DEBUG: ow_select.c:(79) Continuing root branch
DEBUG: ow_ds9490.c:(494) DS9490 RESET. changed 0, flex: 1
DEBUG: ow_ds9490.c:(545) DS9490_Reset: OK
DEBUG: ow_ds9490.c:(682) Got 8 bytes from USB search
DEBUG: ow_ds9490.c:(710) gulp. Adding element 0:81 8C 7E
30 00 00 00 BA
DEBUG: ow_ds9490.c:(624) SN found: 81 8C 7E 30 00 00 00 BA
DEBUG: ow_search.c:(74) Device found: 81 8C 7E 30 00 00 00 BA
DEBUG: ow_cache.c:(561) Adding device location 81 8C 7E 30
00 00 00 BA bus=0
DEBUG: ow_cache.c:(650) Add to cache sn 81 8C 7E 30 00 00
00 BA pointer=0x7f0789d5057c index=0 size=4
DEBUG: ow_cache.c:(561) Adding device location 81 8C 7E 30
00 00 00 BA bus=0
DEBUG: ow_cache.c:(650) Add to cache sn 81 8C 7E 30 00 00
00 BA pointer=0x7f0789d5057c index=0 size=4
CALL: ow_parsename.c:(98)
path=[/uncached/bus.0/81.8C7E30000000]
DEBUG: ow_usb_cycle.c:(125) Callback on
/uncached/bus.0/81.8C7E30000000
DEBUG: ow_parsename.c:(62) /uncached/bus.0/81.8C7E30000000
DEBUG: ow_ds9490.c:(606) Index 2
DEBUG: ow_cache.c:(484) Adding directory for 00 00 00 00
00 00 00 00 elements=2
DEBUG: ow_cache.c:(650) Add to cache sn 00 00 00 00 00 00
00 00 pointer=0x7f0789d5058c index=0 size=16
CALL: ow_parsename.c:(98) path=[/uncached/bus.0/simultaneous]
DEBUG: ow_parsename.c:(380) TEST set simultaneous
DEBUG: ow_usb_cycle.c:(125) Callback on
/uncached/bus.0/simultaneous
DEBUG: ow_parsename.c:(62) /uncached/bus.0/simultaneous
CALL: ow_parsename.c:(98) path=[/uncached/bus.0/alarm]
DEBUG: ow_usb_cycle.c:(125) Callback on /uncached/bus.0/alarm
DEBUG: ow_parsename.c:(62) /uncached/bus.0/alarm
DEBUG: ow_dir.c:(195) ret=0
DEBUG: ow_usb_cycle.c:(155) Finished FS_dir
DEBUG: ow_parsename.c:(62) /uncached/bus.0
DEFAULT: ow_usb_cycle.c:(191) Set DS9490 2:3 unique id to 81
8C 7E 30 00 00 00 BA
mick@tom:/usr/local/src/owfs-2.8p16$
<mailto:mick@tom:/usr/local/src/owfs-2.8p16$>
On 04/07/12 15:39, Mick Sulley wrote:
No, with or without debug it does not run. I included the
debug output at the end of the mail, I cannot see anything
in there that looks like an error, but then my knowledge is
not that great.
Mick
On 04/07/12 12:47, Paul Alfille wrote:
Does it work with --debug? There was a backgrounding issue
in 2.8p15
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions
will include endpoint security, mobile security and the latest in
malware
threats.http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
<mailto:Owfs-developers@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions
will include endpoint security, mobile security and the
latest in malware
threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
<mailto:Owfs-developers@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
