Re: [PATCH] http client timeouts part1 (v2)
Hi, Alexander. Patch looks good. I try to test it next week, but conceptually I am +1. (by the way, in conn_pool_get ifdef not needed IMHO). Alexander Malysh wrote: second version of this patch (fixed double free bug). Alexander Malysh wrote: Hi, attached you can find path that fixes a problem with dead connections in http client connection pool. It's only a first part of fixes that we need (we still need to kill inactive connection after timeout expired). How it works is simple: 1) before putting connection into connection pool register dummy callback 2) if dummy callback called (we will receive error poll event) check if connection still ok and if not destroy it 3) before return connection from pool, unregister dummy callback Comments/votes please! -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv
Kannel to Kannel link with HTTP SMSC
Hi, I'm trying to build a fake test environment for my application, using Kannel to Kannel link as per smsc_http.c comments define: * KANNEL->KANNEL linking: (UDH not supported in MO messages) * * * FOR CLIENT/END-POINT KANNEL: * * group = smsc * smsc = http * system-type = kannel * port = NNN * smsc-username = XXX * smsc-password = YYY * send-url = "server.host:PORT" * * * FOR SERVER/RELAY KANNEL: * * group = smsbox * sendsms-port = PORT * ... * * group = sms-service * keyword = ... * url = "client.host:NNN/sms?user=XXX&pass=YYY&from=%p&to=%P&text=%a" * max-messages = 0 * * group = send-sms * username = XXX * password = YYY This doesn't work. There's no send-sms group defined anywhere. Is this a bug, comment problem or my blindness? What am I trying to do is to make one instance act like an SMSC, forwarding any MO messages to my fake message panel application via regular HTTP POST, and forward any MT messages to a proper client (matching with destination number) Kannel instance. This is what I am able to understand from those comments. Any clues? Enjoy, -- Enver ALTIN |http://skyblue.gen.tr/ Software developer @ Parkyeri | http://www.parkyeri.com/ signature.asc Description: This is a digitally signed message part
Re: [PATCH] daemonize & change user fixes
Hi,
Kalle, do you still have objections for this patch or is it ok to commit as
is?
Kalle Marjola wrote:
> On Tue, 2004-11-02 at 02:48, Alexander Malysh wrote:
>> Hi,
>>
>> attached patch fixes daemonize mode (make sure stdin/stdout/sdterr are
>> opened and do chdir("/")) and change user code (set supplementary group
>> id's and don't destroy passwd struct).
>>
> +1 for all except that '/' -thing:
> -
> /* XXX chdir breaks restart of boxes when
> started w/o a full path to binary */
> -/* chdir("/"); */
> +chdir("/");
> -
> Seems like there was reason not to do it. I do not say that
> this isn't right thing to do, but then if parachute is used,
> then Kannel should make sure that the path is full, not
> relative - can it like test, in daemon mode, that it can find
> itself before starting up?
>
>> This patch should go into 1.4.0 stable.
>
> Yes except notes above.
>
--
Thanks,
Alex
Some feature requests
Hello ! I've been fighting a lot lately with smsc routing and several production services, and i think it would be very nice - to have an option to enable or disable an smsc in a config like: smsc-enable = true | false Resulting that some connections may not be active unless specified with out the need to change files. - Another nice thing would be to have a way to start and stop smsc connections with out the need to restart the whole kannel, having that would allow us to have a live production system and safely start and stop other connections. Ok, those two are things that would be very useful for me, but there's another that before making a suggestion I would like to know what you think or if some one if already working on it. - When using http admin to restart kannel, happens sometimes that smsbox doesn't make it to reconnect successfully to the bearerbox, it currently works by waiting a few seconds to give time to the bearer to start, but is that really correct? it doesn't always works well as it happens on my system, my system would require more time, that is, by hand. I've thought of possible solutions, but they doesn't seem so correct either. I'll show them 2 u as a brainstorm: + Make smsbox try to connect several times until it makes a connection or a time out or something similar occurs. + Make smsbox do a sort of port scan to the bearer port until its open and connect to it. + Have a concertation box, that is, a box that receives all commands to bearer and/or smsbox and administers order of things and monitors how things are going to prevent errors from happening. + Let bearerbox to start explicitly the smsbox by executing it only when it is ready. Ok there's my participation as brainstorm, some ideas ?? == Oscar OM MANI PEME HUM
Testing, please disregard.
I think I'm having a problem sending messages here. Please disregard. -- Enver
Test message
This is a test -- Nick Clarey, System Architect| "Sometimes when you fill a vacuum, Trigenix | it still sucks." - Rob Pike p +44-1223-478900 fx +44-1223-478901 |
Re: [PATCH] daemonize & change user fixes
On Thu, 2004-11-04 at 00:25, Alexander Malysh wrote: > Hi, > > Kalle, do you still have objections for this patch or is it ok to commit as > is? > Feel free; just comment it to docs that directory is changes and it should be noted as 'compatibility breaker' ... :] -- &Kalle Marjola ::: Development ::: Helsinki ::: Enpocket
Re: Some feature requests
Oscar, At least on 1.3.2, you can start and stop individual smsc links using the "start-smsc" and "stop-smsc" commands from the HTTP interface. I find it quite useful for dealing with "queued and never sent" messages: just bring the troubled link down and up again using something like: http://kannelhost:adminport/cgi-bin/stop-smsc?password=foobar&smsc=mysmsc and afterwards http://kannelhost:adminport/cgi-bin/start-smsc?password=foobar&smsc=mysmsc Hope it helps, On Thu, 04 Nov 2004 12:31:26 -0600, Oscar Medina Duarte <[EMAIL PROTECTED]> wrote: > Hello ! > > I've been fighting a lot lately with smsc routing and several production > services, and i think it would be very nice > > - Another nice thing would be to have a way to start and stop smsc > connections with out the need to restart the whole kannel, having that > would allow us to have a live production system and safely start and > stop other connections. > > > Ok there's my participation as brainstorm, some ideas ?? > > == Oscar > OM MANI PEME HUM > > -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/
System error 24: Too many open files
Hi, I'm having a problem with DLR handling on Solaris with Kannel/CVS connecting to an EMI SMSC: 2004-11-05 18:58:57 [1503] [9] DEBUG: Parsing URL `http:///dlr.php?status=8': 2004-11-05 18:58:57 [1503] [9] DEBUG: Scheme: http:// 2004-11-05 18:58:57 [1503] [9] DEBUG: Host: 2004-11-05 18:58:57 [1503] [9] DEBUG: Port: 80 2004-11-05 18:58:57 [1503] [9] DEBUG: Username: (null) 2004-11-05 18:58:57 [1503] [9] DEBUG: Password: (null) 2004-11-05 18:58:57 [1503] [9] DEBUG: Path: dlr.php 2004-11-05 18:58:57 [1503] [9] DEBUG: Query: status=8 2004-11-05 18:58:57 [1503] [9] DEBUG: Fragment: (null) 2004-11-05 18:58:57 [1503] [9] ERROR: Couldn't create new socket. 2004-11-05 18:58:57 [1503] [9] ERROR: System error 24: Too many open files 2004-11-05 18:58:57 [1503] [9] ERROR: error connecting to server `' at port `80' I think it's reaching the per process fd limit. I tried increasing it to 4096 and even more. Seemed to work, but didn't help at all. Sooner or later, I hit this problem. What's going on? Is Kannel leaking file descriptors, or is it really too many outgoing DLR's blocking it? PS: Connection to SMSC is _very_ fast. PS2: I never encountered this problem with Linux. Thanks, -- Enver ALTIN |http://skyblue.gen.tr/ Software developer @ Parkyeri | http://www.parkyeri.com/ signature.asc Description: This is a digitally signed message part
Re: [PATCH] daemonize & change user fixes
Kalle Marjola wrote: > On Thu, 2004-11-04 at 00:25, Alexander Malysh wrote: >> Hi, >> >> Kalle, do you still have objections for this patch or is it ok to commit >> as is? >> > Feel free; just comment it to docs that directory is changes > and it should be noted as 'compatibility breaker' ... :] fine, attached userguide patch commited to cvs... -- Thanks, AlexIndex: doc/userguide/userguide.xml === RCS file: /home/cvs/gateway/doc/userguide/userguide.xml,v retrieving revision 1.288 diff -a -u -p -r1.288 userguide.xml --- doc/userguide/userguide.xml 28 Oct 2004 16:32:14 - 1.288 +++ doc/userguide/userguide.xml 5 Nov 2004 19:11:51 - @@ -1640,7 +1640,10 @@ white-list = "http://localhost/whitelist -d - Start process in as daemon (detached from a current shell session). + Start process as daemon (detached from a current shell session). + Note: Process will change CWD (Current working directory) to /, + therefore you should ensure that all paths to binary/config/config-includes are + absolute instead of relative. --daemonize
Re: [PATCH] daemonize & change user fixes
Alexander Malysh wrote:
> Hi,
>
> attached patch fixes daemonize mode (make sure stdin/stdout/sdterr are
> opened and do chdir("/")) and change user code (set supplementary group
> id's and don't destroy passwd struct).
>
> This patch should go into 1.4.0 stable.
>
patch commited to cvs.
--
Thanks,
Alex
