Guys, God would punish me if I would play games here on you, after such a big help from you for a long time, till I managed Kannel working smoothly. The reason I open this thread was just curiosity on how multiple bearerboxes could be run having all its smpp connection in their respective conf files, being bind without problem. Maybe "SMSBOX not starting" topic was not appropriate because the reason was something else. But, be sure that I executed 4 instances of bearerbox having the same admin-port, and each kannel and access logs were separately written, so the traffic was splitted among SMPP connections, being written in the respective log files in the core group of each conf file. Anyone can have a try and can see that kannel will work properly regardless admin-port configuration. Only by accessing the web admin through localhost:13000 was showing the current SMSC connection was the first instance that grabbed that port.
Anyway I changed the configuration putting different ports. Thanks Elton 2009/4/20 Nikos Balkanas <nbalka...@gmail.com> > OK, > > Then please assign also different admin ports to each bearerbox on the same > server. Your configuration file, as it stands, is faulty and kannel can > react unpredictably. It is difficult to track problems and issues with > correct configuration files, let alone with faulty ones. When you ask for > help, please have the best configuration files, to your knowledge. I trust > you are not trying to play games on our time. > > BR, > Nikos > > ----- Original Message ----- > *From:* Elton Hoxha <elt...@gmail.com> > *To:* Alejandro Guerrieri <alejandro.guerri...@gmail.com> > *Cc:* Nikos Balkanas <nbalka...@gmail.com> ; users@kannel.org > *Sent:* Saturday, April 18, 2009 3:02 AM > *Subject:* Re: smsbox not starting > > I think there is a misunderstanding. I was refering to the port that > SMS-BOX is listening and we got confused with the admin-port. Of course all > my instances have different sms-box ports. I was just claiming that, having > the admin-port 13000 for all instances that bind successfully, it does not > affect the functionality of kannel. I can send sms-s though all the channels > and instances and receiving deliveries as well. > > That "address already in use" was refering to my old process of SMS-BOX > which I thought it was killed, and not admin-port. > > Of course, If I would like to manage/administer through > http://localhost:13000, it will give me the possibility to manage the > first instance that grabbed that port... > > Regards > Elton > > > On Sat, Apr 18, 2009 at 1:12 AM, Alejandro Guerrieri < > alejandro.guerri...@gmail.com> wrote: > >> Elton, it's not possible for more than one process to listen on the >> same address/port combination at the same time. >> >> Once a process attachs to a socket, it locks it until it releases. >> That's the "address already in use" error you get. It's just like >> trying to put two keys on the same lock at the same time... >> >> Think about it for a little while: you could then hijack any port on >> your box at your will, even those with services listening? >> >> Regards, >> >> Alejandro >> >> 2009/4/18 Nikos Balkanas <nbalka...@gmail.com>: >> > OK, then, please rewrite all C and sockets and start your own >> > college...Assuming of course that all bearerbox instances live on the >> same >> > server... >> > >> > ----- Original Message ----- >> > From: Elton Hoxha >> > To: Nikos Balkanas >> > Cc: users@kannel.org >> > Sent: Saturday, April 18, 2009 1:10 AM >> > Subject: Re: smsbox not starting >> > Its totally possible....all 4 conf files used by 4 bearerboxes have the >> same >> > admin-port 13000 and the routing of SMS through different SMPP >> connections >> > is done without problems. My problem consisted only at sms-box error >> message >> > that I couldnt understand but I suspect it was because one old smsbox >> > process was still alive not killed. >> > >> > 2009/4/17 Nikos Balkanas <nbalka...@gmail.com> >> >> >> >> Hi, >> >> >> >> That's not possible. It contradicts all socket theory. Besides, when >> you >> >> access through HTTP tcp 13000, which one of the boxes are you >> administering? >> >> Just assign different admin port to each one. You cannot disable it. >> >> >> >> Nikos >> >> >> >> ----- Original Message ----- >> >> From: Elton Hoxha >> >> To: users@kannel.org >> >> Sent: Friday, April 17, 2009 4:51 PM >> >> Subject: Re: smsbox not starting >> >> In theory it can be right what you said Milan, but practically I have >> >> started multiple bearerbox instances running on the admin-port 13000 >> without >> >> having problems for weeks :) >> >> >> >> On Fri, Apr 17, 2009 at 3:44 PM, Milan P. Stanic <m...@arvanta.net> >> wrote: >> >>> >> >>> On Fri, 2009-04-17 at 15:00, Elton Hoxha wrote: >> >>> > Actually I use 4 bearerbox instances separating my connections. I >> never >> >>> > had >> >>> > this type of error even using this configuration below. >> >>> >> >>> Interesting idea :). But it is useless (at least) and can lead to >> >>> problems. >> >>> >> >>> Actually, that can be cause of your problem. First instance of >> bearerbox >> >>> binds to port 13000 and other instances cannot bind and "bark" to log >> >>> files. >> >>> >> >>> > group = core >> >>> > admin-port = 13000 >> >>> > smsbox-port = 13010 >> >>> > sendsms-port = 13015 >> >>> > >> >>> > group = core >> >>> > admin-port = 13000 >> >>> > smsbox-port = 13020 >> >>> > sendsms-port = 13016 >> >>> > >> >>> > group = core >> >>> > admin-port = 13000 >> >>> > smsbox-port = 13030 >> >>> > sendsms-port = 13017 >> >>> > >> >>> > group = core >> >>> > admin-port = 13000 >> >>> > smsbox-port = 13040 >> >>> > sendsms-port = 13018 >> >>> > >> >>> > By the way, is logical the above? >> >>> >> >>> -- >> >>> Kind regards, Milan >> >>> >> >> >> > >> > >> > >
