linecontrol-development Mailing List for LineControl (Page 4)
Brought to you by:
sfuchs
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(11) |
Feb
|
Mar
(10) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
(3) |
| 2003 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2004 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
(1) |
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
(4) |
Nov
(1) |
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Joao C. <jp...@rn...> - 2001-10-07 23:46:49
|
Dump of my /var/log/daemon.log : Oct 7 20:37:54 lfsPentiumRouter linesrv[1996]: LineControl ML Server 2.1.4 started. Oct 7 20:38:05 lfsPentiumRouter linesrv[1996]: 192.168.1.8:1102 registered Oct 7 20:42:05 lfsPentiumRouter linesrv[1996]: cleanup(): cought signal 11 (...) Oct 7 20:42:15 lfsPentiumRouter linesrv[1996]: 1 lines are still active. Close them manually! Oct 7 20:42:15 lfsPentiumRouter linesrv[1996]: SEGFAULT, please report to sf...@gm... Oct 7 20:42:15 lfsPentiumRouter linesrv[1996]: Value of segf_indicator: 16 Oct 7 20:43:36 lfsPentiumRouter linesrv[2104]: LineControl ML Server 2.1.4 started. Oct 7 20:43:43 lfsPentiumRouter linesrv[2104]: 192.168.1.8:1104 registered Oct 7 20:43:49 lfsPentiumRouter linesrv[2104]: 192.168.1.8:1104 online Oct 7 20:44:19 lfsPentiumRouter linesrv[2104]: 192.168.1.8:1104 online (...) Oct 7 20:44:58 lfsPentiumRouter linesrv[2104]: cleanup(): cought signal 11 Oct 7 20:45:08 lfsPentiumRouter linesrv[2104]: 1 lines are still active. Close them manually! Oct 7 20:45:08 lfsPentiumRouter linesrv[2104]: SEGFAULT, please report to sf...@gm... Oct 7 20:45:08 lfsPentiumRouter linesrv[2104]: Value of segf_indicator: 16 Those 2 lines above where 192.168.1.8 gets online twice are related to that bug report I issued earlier. As we can see, there is no offline() called by the client in the middle. Each of those calls would call isdn-up twice and isdn-off once I don't see much info here but... About the segfault, this seems the problem introduceb by my change to get multiple ISP, as that "safety code" I cuted would mask whatever is the problem here by forcing the lines to close... I'm back to plain vannilla linesrv 2.1.0 for now, as it seems the more stable about this segfault Somehow I get the feeling that if the newer version have some work around this problem, it has been away from the real cause of it and it will get away eventually only in the new 3.x version... So maybe lets not bother too much about this! Greetings to you all and next weekend maybe I'll send you some more goodies :) «»«»«»«» Joao Clemente «» jp...@rn... «»«»«»«» Well... it's not really a leak, is it? The memory will be returned when the user reboots ... «»«»«»«» ( Maybe a known OS philosophy? ) «»«»«»«» |
|
From: Joao C. <jp...@rn...> - 2001-10-07 22:10:15
|
Hello. I said some days ago that my WLC would fail as soon as I started it , with some error of acess violation or something.. It's happening the same with the new linesrv version, so it must not be a problem with linesrv but with the changes from the former versions of WLC. One curious thing : This fails in my Win2k box (as a super user) , and as I have some more win boxes, I decided to try out and i found that It runs perfect in Win95 boxes! So I tryed again in my win2k box , this time as Administrator (MS version of root?) and... it WORKED! I dunno if this brings some light to the problem but ...here goes... |
|
From: Joao C. <jp...@rn...> - 2001-10-07 22:05:09
|
Hello. I've once said that I was unable to use one of the newer linesrv versions, because the line would connect and then disconnect after a couple of seconds... I have this behaviour in the last (2.1.4) version. My client connects , the line is up for some seconds, and then disconnects. I've made my isdn-up and isdn-down line write something in a log when they are called... And see what strange behaviour I get : --------------------------- dialed ippp0 at Sun Oct 7 21:00:29 WEST 2001 dialed ippp0 at Sun Oct 7 21:00:31 WEST 2001 Issued hangup at Sun Oct 7 21:00:40 WEST 2001 ( I added the ISP name to get some more info, but are the same logs ) dialed ippp0 (Iol) at Sun Oct 7 21:09:40 WEST 2001 dialed ippp0 (Iol) at Sun Oct 7 21:09:43 WEST 2001 Issued hangup at Sun Oct 7 21:09:49 WEST 2001 ------------------------------- Why the strange thing this issues 2 isdn-up calls? And why does the hangup is called next? I think this somekind of timeout related, but timeout of what? I have my config timeouts for 15 secs, so these are not it... I've reversed my network back to linesrv 2.1.0 , that is still stable for me... Can this behaviour be introduced by some missing option in my config file ? (I'm using the same in 2.1.4 as in 2.1.0) |