The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Homeseer log question



I assume you are running build 24??  I have had the same problem since
upgrading to build 24 but I am unsure if it's the build or ultraview as I
installed them at the same time.

The Homeseer message board suggests it is a known problem and the simple
solution is to turn logging off until the next build of Homeseer.

Hope this helps
Pedro

-----Original Message-----
From: James, Daniel [mailto:daniel.james@xxxxxxx]
Sent: 31 January 2002 09:48
To: UKHA (E-mail)
Subject: [ukha_d] Homeseer log question

Hi all

I have just noticed that my homeseer log is filling up with this:

31/01/2002 09:49:09~!~Info~!~Web Server Error: 24035 Socket would block on
this operation
31/01/2002 09:49:09~!~Info~!~Error sending on TCP 2
Does anyone have any ideas what its about?

Thanks

Daniel


***********************************************************
This message is confidential and intended for the exclusive
use of the addressee(s) only and remains the property of
Exchange FS Group plc. You should not disclose its contents
to any other person. If you are not the intended recipient
please notify the sender named above immediately.

Registered Office: Munro House, Portsmouth Road, Cobham,
Surrey, KT11 1TE. Registered in England No. 2596452
***********************************************************



For more information: http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.