| View previous topic :: View next topic |
| Author |
Message |
Shaiko Voice
Joined: 15 Oct 2006 Posts: 3
|
Posted: Thu Feb 08, 2007 7:21 am Post subject: error flushing, broken pipe. I need some help. |
|
|
Suddenly when i woke up this morning, my bot didnt answer on some cmds, in the partyline it stands:
[12:10] Tcl error [stats]: error flushing "sock11": broken pipe
[12:20] Tcl error [stats]: error flushing "sock12": broken pipe
I`m really confused. I dont know what do do to.
Is it someone who can help me out here? |
|
| Back to top |
|
 |
Alchera Revered One

Joined: 11 Aug 2003 Posts: 3344 Location: Ballarat Victoria, Australia
|
Posted: Thu Feb 08, 2007 8:41 am Post subject: |
|
|
Something to do with that stats module by the looks of it.
Have you tried a simple .restart? _________________ Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM |
|
| Back to top |
|
 |
De Kus Revered One

Joined: 15 Dec 2002 Posts: 1361 Location: Germany
|
Posted: Fri Feb 09, 2007 8:41 pm Post subject: |
|
|
the error occurs when you use I/O commands on sockets which has recieved fatal signals (like broken pipe in that case, you would also get it when it was closed by peer). try to close them on the console like '.tcl close sock11; close sock12' or do what you got mentioned before. _________________ De Kus
StarZ|De_Kus, De_Kus or DeKus on IRC
Copyright © 2005-2009 by De Kus - published under The MIT License
Love hurts, love strengthens... |
|
| Back to top |
|
 |
|