Re: [JDEV] msn transport
Hi Satish Reddy, Where r u from ?? Tx n Rgds r-a-v-i - Original Message - From: Satish Reddy To: [EMAIL PROTECTED] Sent: Thursday, March 28, 2002 10:59 AM Subject: [JDEV] msn transport Hello Every one i've msn tranport installed on my serser i've problems with msn transport. some times it cant send messges to the buddy specified it simply dumps back the same message to person who had sent it ! while receiving messages it works fine :) not able to figure out the problem ! tried re-installing the transport but all my efforts are in vein :( plz help me out in this issue. Best Regds Satish Reddy
RE: [JDEV] Jabberd in Startup on Linux
Thanks! It didn't get me there yet, but it gave me an indication on where the real problem seems to be. On startup I got this message: /opt/jabber-1.4.1/jabberd/jabberd: error while loading shared libraries: libpth.so.14: cannot open shared object file: No such file or directory So the problem wasn't in the scripts, something else is wrong... Strange though, I can manually start jabberd without any problems. Michel -Original message- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Namens Mike Sassak Verzonden: donderdag 28 maart 2002 1:04 Aan: [EMAIL PROTECTED] Onderwerp: Re: [JDEV] Jabberd in Startup on Linux The following 'old-fashioned way' won't get you the convenience of using 'chkconfig', 'service', etc. but it does work. Just add these two lines to the end of /etc/rc.d/rc.local: echo "Starting Jabber..." /path/to/jabberd & The above is quite optimistic - it doesn't check to see whether the server crashed - 'cos if it did jabber won't start until you delete the jabber.pid file. So I wouldn't do it this way on a production server, but it is a quick fix. HTH, -mike On Wed, 2002-03-27 at 05:44, Michel Oosterbeek wrote: > Hi All, > > I'm using Jabber 1.4.1 with Red Hat 7.2 and I have been trying to get > Jabberd to fire up on startup, but so far my attempts were unsuccessful. > Recently I read some messages of other people here, who were having the same > problem. Some scripts were offered, and I decided to give them a try, but > something strange is happening. So if the writer of these scrips is reading > this, please give me some advice? > ... > Now, on startup, I see the script is called: "Starting jabberd... [OK]", but > when I check it, there's nothing running at all. Though when I try to run > the script myself it works fine. So why won't it do that on startup? > > Thanks, > > Michel > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Jabberd in Startup on Linux
On Thu, Mar 28, 2002 at 10:49:46AM +0100, Michel Oosterbeek wrote:
> It didn't get me there yet, but it gave me an indication on where the real
> problem seems to be.
> On startup I got this message:
>
> /opt/jabber-1.4.1/jabberd/jabberd: error while loading shared libraries:
> libpth.so.14: cannot open shared object file: No such file or directory
locate libpth.so.14
(write down path)
export LD_LIBRARAY_PATH=$PTH_LIB_PATH.
i.e., on my obsd box the pth lib is in /usr/local/lib/pth/libpth*, so
i have to do
export LD_LIBRARY_PATH=/usr/local/lib/pth
Since youre on a linux box, you can also add the Path directly to
/etc/ld.so.conf (add it after the last line) and then just run
`ldconfig`
-mc
--
| Rico -mc- Gloeckner | <[EMAIL PROTECTED]> | {ICQ:99798577} |
| http://www.ukeer.de | mc (at) irc.tu-ilmenau.de | <[EMAIL PROTECTED]> |
| Jabber: [EMAIL PROTECTED] | :wq
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] icqv7 core dumps on external part ?
This is the result : Core was generated by `icqv7ext'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libsigc-1.0.so.0...done. Reading symbols from /lib/libpthread.so.0...done. Reading symbols from /lib/libresolv.so.2...done. Reading symbols from /usr/local/lib/libstdc++.so.3...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /usr/local/lib/libgcc_s.so.1...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. #0 0x40126e88 in chunk_alloc (ar_ptr=0x401bbd40, nb=16) at malloc.c:2875 2875malloc.c: No such file or directory. (gdb) bt #0 0x40126e88 in chunk_alloc (ar_ptr=0x401bbd40, nb=16) at malloc.c:2875 #1 0x401265ae in __libc_malloc (bytes=12) at malloc.c:2696 #2 0x80de950 in _ZNSt23__malloc_alloc_templateILi0EE8allocateEj (__n=12) at /usr/local/include/g++-v3/bits/stl_alloc.h:114 #3 0x806f6d1 in _ZN7bedrock3net6SocketC1ERNS0_13SocketWatcherERNS_10ThreadPoolEiiPNS0_5KarmaEPNS0_15ConnectionLimitE ( this=0x8153010, watcher=@0xb81c, pool=@0xb7c4, key=0, socketfd=-1, karma=0x0, conn_limit=0x0) at /usr/local/include/g++-v3/bits/stl_alloc.h:184 #4 0x806e655 in _ZN7bedrock3net13SocketWatcher19createConnectSocketEPNS0_19SocketEventListenerEPKcS5_iiPNS0_5KarmaE ( this=0xb81c, listener=0xb9f4, host=0x814fad4 "127.0.0.1", service=0x814fab4 "_jabber._tcp", defaultport=7000, thread_key=0, karma=0x0) at SocketWatcher.cpp:195 #5 0x80db48e in _ZN3jax16RouterConnectionINS_6PacketES1_E7connectERKSsS4_RN7bedrock3net7AddressE (this=0xb9f0, name=@0xb7a4, secret=@0xbac0, a=@0xb5d0) at /usr/local/include/g++-v3/bits/basic_string.h:396 #6 0x8059516 in _ZN8IcqTransC1ERKSsS1_S1_jb (this=0xb7a0, serviceid=@0xbad0, password=@0xbac0, hostname=@0xbab0, port=7000, outgoing_dir=true) at IcqTrans.cpp:67 #7 0x8069c17 in main (argc=1, argv=0xbb44) at main.cpp:113 Current language: auto; currently c David Waite wrote: > Wim Godden wrote: > > >Trying to run it like this : > >icqv7ext -n icqv7ext -s secretpass -h 127.0.0.1 -p 7000 -m > >sms.localnetwork.local > > > >I get : > >Starting component... > >Component ID : icqv7ext > >Secret : secretpass > >Jabberd IP : 127.0.0.1 > >Jabberd Port : 7000 > >Segmentation fault (core dumped) > > > > > >Any ideas ? > > > Sounds like it is core-dumping wihle trying to start the component :-) > > Perhaps you could post a backtrace from the core? (perhaps "gdb icqv7ext > -c core", then "bt".) Cores from threaded components are much nicer if > they are generated from something other than Linux; if you are using > Linux try to use the newest kernel possible (as they reworked a bit of > this logic within the 2.4 series) > > -David Waite > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev -- - FirstLink Networks - http://www.firstlinknetworks.com - De leukste moppen op je scherm en in je mailbox : http://www.moppen.be ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Jabberd in Startup on Linux
Can anybody give me the full steps from A-Z please !! Tx n Rgds r-a-v-i - Original Message - From: "Michel Oosterbeek" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 28, 2002 3:19 PM Subject: RE: [JDEV] Jabberd in Startup on Linux > Thanks! > > It didn't get me there yet, but it gave me an indication on where the real > problem seems to be. > On startup I got this message: > > /opt/jabber-1.4.1/jabberd/jabberd: error while loading shared libraries: > libpth.so.14: cannot open shared object file: No such file or directory > > So the problem wasn't in the scripts, something else is wrong... Strange > though, I can manually start jabberd without any problems. > > Michel > > > > > -Original message- > Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Namens Mike > Sassak > Verzonden: donderdag 28 maart 2002 1:04 > Aan: [EMAIL PROTECTED] > Onderwerp: Re: [JDEV] Jabberd in Startup on Linux > > > The following 'old-fashioned way' won't get you the convenience of using > 'chkconfig', 'service', etc. but it does work. > > Just add these two lines to the end of /etc/rc.d/rc.local: > > echo "Starting Jabber..." > /path/to/jabberd & > > The above is quite optimistic - it doesn't check to see whether the > server crashed - 'cos if it did jabber won't start until you delete the > jabber.pid file. So I wouldn't do it this way on a production server, > but it is a quick fix. > > HTH, > -mike > > On Wed, 2002-03-27 at 05:44, Michel Oosterbeek wrote: > > Hi All, > > > > I'm using Jabber 1.4.1 with Red Hat 7.2 and I have been trying to get > > Jabberd to fire up on startup, but so far my attempts were unsuccessful. > > Recently I read some messages of other people here, who were having the > same > > problem. Some scripts were offered, and I decided to give them a try, but > > something strange is happening. So if the writer of these scrips is > reading > > this, please give me some advice? > > ... > > Now, on startup, I see the script is called: "Starting jabberd... [OK]", > but > > when I check it, there's nothing running at all. Though when I try to run > > the script myself it works fine. So why won't it do that on startup? > > > > Thanks, > > > > Michel > > > > ___ > > jdev mailing list > > [EMAIL PROTECTED] > > http://mailman.jabber.org/listinfo/jdev > > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Jabberd in Startup on Linux
On Wed, Mar 27, 2002 at 07:03:56PM -0500, Mike Sassak wrote:
> The following 'old-fashioned way' won't get you the convenience of using
> 'chkconfig', 'service', etc. but it does work.
>
> Just add these two lines to the end of /etc/rc.d/rc.local:
Old-fashioned and deprecated, you Slackware fan you! :-)
A good thing when init-scripts behave like that is to check output and logs.
Secondly, I don't know about RH, but all other dists I've used have a
skeleton init-script to be copied and modified for creating new
init-scripts.
It should take arguments "start", "stop" an "restart" as a minimum. You
should exit with correct codes to tell the daemon script if start really was
OK or not.
That's the way to do it.
For using the script at http://www.bluecows.com/scripts/jabberd.start make
sure your Jabber server actualy is in "/opt". According to Linux standards
anything not distribution related should end up in "/usr/local", I think
"/opt" is an invention of Sun?
Hehe, standards are nice only if used. ;-)
I'm including a small init-script. It does not use the nice color stuff that
RH and other RH-based dists use, but it works fine on my Debian and
Slackware.
/P
---
#!/bin/bash
#
# jabberWill start, stop and restart Jabber daemon at will.
#
# Written by Peter Gebauer <[EMAIL PROTECTED]>.
# Modified for the Jabber mailing list <[EMAIL PROTECTED]>.
#
# This should be changed to wherever your stuff is:
INSTALLED=/usr/local
# This should be changed to wherever your Jabber dist is:
JABBERDIR=$INSTALLED/src/jabber
# This should be changed to where your Jabber daemon PID-file is:
PIDFILE=$JABBERDIR/jabber.pid
# This should be changed to where your Jabber daemon binary is:
JABBERD=$JABBERDIR/jabberd/jabberd
DAEMON=jabberd
NAME=jabber
DESC="Jabber daemon"
THIS=/etc/init.d/$NAME
if [ ! -x $JABBERBIN ]; then
echo "Could not find executable $JABBERBIN!"
echo "You need to configure $THIS with correct paths."
exit 4
fi
case "$1" in
start)
echo -n "Starting $DESC: "
if [ -e "$PIDFILE" ]; then
PIDNUM=`cat $PIDFILE`
fi
if [ -n "$PIDNUM" ] && [ -n "$DAEMON" ]; then
ISRUNNING=`ps -A | grep $PIDNUM | grep $DAEMON`
fi
if [ -n "$ISRUNNING" ]; then
echo "already running! (PID: $PIDNUM)"
exit 101
fi
nohup $JABBERD >/dev/null 2>&1 &
if [ "$?" -ne 0 ]; then
echo "failed to start!"
exit 102
fi
echo "OK."
;;
stop)
echo -n "Stopping $DESC: "
if [ -e "$PIDFILE" ]; then
PIDNUM=`cat $PIDFILE`
fi
if [ -n "$PIDNUM" ]; then
kill -TERM $PIDNUM > /dev/null 2>&1
KILLRESULT=$?
fi
if [ -z "$PIDNUM" ] || [ "$KILLRESULT" -ne 0 ]; then
echo -n "Killing all processes named $DAEMON: "
killall -TERM $DAEMON > /dev/null 2>&1
if [ "$?" -ne 0 ]; then
rm -f $PIDFILE
echo "failed! (perhaps it was not running?)"
exit 201
fi
fi
rm -f $PIDFILE
echo "OK."
;;
restart)
echo "Restart requested: "
$THIS stop
sleep 1
$THIS start
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart}" >&2
exit 1
;;
esac
exit 0
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
RE: [JDEV] Jabberd in Startup on Linux
> Since youre on a linux box, you can also add the Path directly to
> /etc/ld.so.conf (add it after the last line) and then just run
> `ldconfig`
I already tried that, but unfortunately it doesn't seem to help. It still
keeps telling me it can't find libpth.so.14 (or sometimes 13), while both
files are in the dir I mentioned in /etc/ld.so.conf
Michel.
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Namens Rico
-mc- Gloeckner
Verzonden: donderdag 28 maart 2002 11:01
Aan: [EMAIL PROTECTED]
Onderwerp: Re: [JDEV] Jabberd in Startup on Linux
On Thu, Mar 28, 2002 at 10:49:46AM +0100, Michel Oosterbeek wrote:
> It didn't get me there yet, but it gave me an indication on where the real
> problem seems to be.
> On startup I got this message:
>
> /opt/jabber-1.4.1/jabberd/jabberd: error while loading shared libraries:
> libpth.so.14: cannot open shared object file: No such file or directory
locate libpth.so.14
(write down path)
export LD_LIBRARAY_PATH=$PTH_LIB_PATH.
i.e., on my obsd box the pth lib is in /usr/local/lib/pth/libpth*, so
i have to do
export LD_LIBRARY_PATH=/usr/local/lib/pth
Since youre on a linux box, you can also add the Path directly to
/etc/ld.so.conf (add it after the last line) and then just run
`ldconfig`
-mc
--
| Rico -mc- Gloeckner | <[EMAIL PROTECTED]> | {ICQ:99798577} |
| http://www.ukeer.de | mc (at) irc.tu-ilmenau.de | <[EMAIL PROTECTED]> |
| Jabber: [EMAIL PROTECTED] | :wq
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
[JDEV] Re: [JDEV] webjab
J just wanted to connect to webjab surfing to www.webjab.com and when I try to connect to the jabber.org server with my username and password I receive the message "can't connect to the server" and when I try to connect a second time (action/sign in), I have the message "logging in" but nothing happens ??? When I run the same client installed on my computer I have the same pb ??? Thanks a lot. mevely > If it was connecting to jabber.org we probably accidentally disabled the > flash support ports when moving stuff around. Just let me know what you > need. > > --temas > > > On Wed, 2002-03-27 at 06:42, Niklas Gustavsson wrote: > > Hi > > > > My guess, is that webjab can not connect to the server because it uses the > > old Flash hack to connect, not the new method. We have not developed webjab > > in the last couple of months due to lots and lots of other work that has to > > be done :-) > > > > If you want to, you can find all the source code for webjab at sf.net > > (http://sourceforge.net/projects/jsjabber) and hack away yourself :-) > > > > /niklas > > > > > > - Original Message - > > From: <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, March 27, 2002 12:51 PM > > Subject: [JDEV] webjab > > > > > > > Hi, > > > I tried to run the webjab from webjab.com but I have the message "can't > > connect to the server" in the browser's window. > > > Does anybody know what happens ? > > > > > > And I tried to download the archieve but I have the same problem. Can > > anyone help ? > > > > > > Thanks in advance > > > mevely > > > > > > Faites un voeu et puis Voila ! www.voila.fr > > > Avec Voila Mail, consultez vos e-mails sur votre mobile Wap. > > > ___ > > > jdev mailing list > > > [EMAIL PROTECTED] > > > http://mailman.jabber.org/listinfo/jdev > > > > > > ___ > > jdev mailing list > > [EMAIL PROTECTED] > > http://mailman.jabber.org/listinfo/jdev > > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > Faites un voeu et puis Voila ! www.voila.fr Avec Voila Mail, consultez vos e-mails sur votre mobile Wap. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] icqv7 core dumps on external part ?
Without looking at the code, I can say there is a 99% chance this means that there has been memory corruption. Several things could have caused this corruption (array write out of bounds, double free, etc.) There is a good chance it could be gcc 3.0.1 - there are a ton of changes which happened to their C++ implementation between 2.95.3 and 3.0.x. There have also been a lot of improvements since 3.0, so if you can upgrade to 3.0.4, I would recommend it. The STL implementation within versions of gcc before 3.0.x were thread-unsafe, especially for std:string (they were interally reference-counted, but the reference modification was not atomic, nor was the reference comparison) -David Waite Wim Godden wrote: This is the result :Core was generated by `icqv7ext'.Program terminated with signal 11, Segmentation fault.Reading symbols from /usr/local/lib/libsigc-1.0.so.0...done.Reading symbols from /lib/libpthread.so.0...done.Reading symbols from /lib/libresolv.so.2...done.Reading symbols from /usr/local/lib/libstdc++.so.3...done.Reading symbols from /lib/libm.so.6...done.Reading symbols from /usr/local/lib/libgcc_s.so.1...done.Reading symbols from /lib/libc.so.6...done.Reading symbols from /lib/ld-linux.so.2...done.#0 0x40126e88 in chunk_alloc (ar_ptr=0x401bbd40, nb=16) at malloc.c:28752875malloc.c: No such file or directory.(gdb) bt#0 0x40126e88 in chunk_alloc (ar_ptr=0x401bbd40, nb=16) at malloc.c:2875#1 0x401265ae in __libc_malloc (bytes=12) at malloc.c:2696#2 0x80de950 in _ZNSt23__malloc_alloc_templateILi0EE8allocateEj (__n=12) at/usr/local/include/g++-v3/bits/stl_alloc.h:114#3 0x8 06f6d1 in_ZN7bedrock3net6SocketC1ERNS0_13SocketWatcherERNS_10ThreadPoolEiiPNS0_5KarmaEPNS0_15ConnectionLimitE(this=0x8153010, watcher=@0xb81c, pool=@0xb7c4, key=0,socketfd=-1, karma=0x0, conn_limit=0x0)at /usr/local/include/g++-v3/bits/stl_alloc.h:184#4 0x806e655 in_ZN7bedrock3net13SocketWatcher19createConnectSocketEPNS0_19SocketEventListenerEPKcS5_iiPNS0_5KarmaE(this=0xb81c, listener=0xb9f4, host=0x814fad4 "127.0.0.1",service=0x814fab4 "_jabber._tcp", defaultport=7000,thread_key=0, karma=0x0) at SocketWatcher.cpp:195#5 0x80db48e in_ZN3jax16RouterConnectionINS_6PacketES1_E7connectERKSsS4_RN7bedrock3net7AddressE(this=0xb9f0,name=@0xb7a4, secret=@0xbac0, a=@0xb5d0) at/usr/local/include/g++-v3/bits/basic_string.h:396#6 0x8059516 in _ZN8IcqTransC1ERKSsS1_S1_jb (this=0xb7a0,serviceid=@0xbad0, password=@0xbac0, hostname=@0xbab0,port= 7000, outgoing_dir=true) at IcqTrans.cpp:67#7 0x8069c17 in main (argc=1, argv=0xbb44) at main.cpp:113Current language: auto; currently cDavid Waite wrote: Wim Godden wrote: Trying to run it like this :icqv7ext -n icqv7ext -s secretpass -h 127.0.0.1 -p 7000 -msms.localnetwork.localI get :Starting component... Component ID : icqv7ext Secret : secretpass Jabberd IP : 127.0.0.1 Jabberd Port : 7000Segmentation fault (core dumped)Any ideas ? Sounds like it is core-dumping wihle trying to start the component :-)Perhaps you could post a backtrace from the core? (perhaps "gdb icqv7ext-c core", then "bt".) Cores from threaded components are much nicer ifthey are generated from something other than Linux; if you are usingLinux try to use the newest kernel possible (as they reworked a bit ofthis logic within the 2.4 series)-David Waite___jdev mailing list[EMAIL PROTECTED]http://mailman.jabber.org/listinfo/jdev ---FirstLink Networks - http://www.firstlinknetworks.com-De leukste moppen op je scherm en in je mailbox : http://www.moppen.be ___jdev mailing list[EMAIL PROTECTED]http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] icqv7 core dumps on external part ?
Sadly, I'm already using 3.0.4... I had to upgrade to 3.0.4 because my previous gcc wouldn't work... So I guess I'm stuck ? David Waite wrote: Without looking at the code, I can say there is a 99% chance this means that there has been memory corruption. Several things could have caused this corruption (array write out of bounds, double free, etc.) There is a good chance it could be gcc 3.0.1 - there are a ton of changes which happened to their C++ implementation between 2.95.3 and 3.0.x. There have also been a lot of improvements since 3.0, so if you can upgrade to 3.0.4, I would recommend it. The STL implementation within versions of gcc before 3.0.x were thread-unsafe, especially for std:string (they were interally reference-counted, but the reference modification was not atomic, nor was the reference comparison) -David Waite Wim Godden wrote: This is the result : Core was generated by `icqv7ext'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/libsigc-1.0.so.0...done. Reading symbols from /lib/libpthread.so.0...done. Reading symbols from /lib/libresolv.so.2...done. Reading symbols from /usr/local/lib/libstdc++.so.3...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /usr/local/lib/libgcc_s.so.1...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. #0 0x40126e88 in chunk_alloc (ar_ptr=0x401bbd40, nb=16) at malloc.c:2875 2875 malloc.c: No such file or directory. (gdb) bt #0 0x40126e88 in chunk_alloc (ar_ptr=0x401bbd40, nb=16) at malloc.c:2875 #1 0x401265ae in __libc_malloc (bytes=12) at malloc.c:2696 #2 0x80de950 in _ZNSt23__malloc_alloc_templateILi0EE8allocateEj (__n=12) at /usr/local/include/g++-v3/bits/stl_alloc.h:114 #3 0x8 06f6d1 in _ZN7bedrock3net6SocketC1ERNS0_13SocketWatcherERNS_10ThreadPoolEiiPNS0_5KarmaEPNS0_15ConnectionLimitE ( this=0x8153010, watcher=@0xb81c, pool=@0xb7c4, key=0, socketfd=-1, karma=0x0, conn_limit=0x0) at /usr/local/include/g++-v3/bits/stl_alloc.h:184 #4 0x806e655 in _ZN7bedrock3net13SocketWatcher19createConnectSocketEPNS0_19SocketEventListenerEPKcS5_iiPNS0_5KarmaE ( this=0xb81c, listener=0xb9f4, host=0x814fad4 "127.0.0.1", service=0x814fab4 "_jabber._tcp", defaultport=7000, thread_key=0, karma=0x0) at SocketWatcher.cpp:195 #5 0x80db48e in _ZN3jax16RouterConnectionINS_6PacketES1_E7connectERKSsS4_RN7bedrock3net7AddressE (this=0xb9f0, name=@0xb7a4, secret=@0xbac0, a=@0xb5d0) at /usr/local/include/g++-v3/bits/basic_string.h:396 #6 0x8059516 in _ZN8IcqTransC1ERKSsS1_S1_jb (this=0xb7a0, serviceid=@0xbad0, password=@0xbac0, hostname=@0xbab0, port= 7000, outgoing_dir=true) at IcqTrans.cpp:67 #7 0x8069c17 in main (argc=1, argv=0xbb44) at main.cpp:113 Current language: auto; currently c David Waite wrote: Wim Godden wrote: Trying to run it like this : icqv7ext -n icqv7ext -s secretpass -h 127.0.0.1 -p 7000 -m sms.localnetwork.local I get : Starting component... Component ID : icqv7ext Secret : secretpass Jabberd IP : 127.0.0.1 Jabberd Port : 7000 Segmentation fault (core dumped) Any ideas ? Sounds like it is core-dumping wihle trying to start the component :-) Perhaps you could post a backtrace from the core? (perhaps "gdb icqv7ext -c core", then "bt".) Cores from threaded components are much nicer if they are generated from something other than Linux; if you are using Linux try to use the newest kernel possible (as they reworked a bit of this logic within the 2.4 series) -David Waite ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev -- - FirstLink Networks - http://www.firstlinknetworks.com - De leukste moppen op je scherm en in je mailbox : http://www.moppen.be ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev -- - FirstLink Networks - http://www.firstlinknetworks.com - De leukste moppen op je scherm en in je mailbox : http://www.moppen.be
Re: [JDEV] icqv7 core dumps on external part ?
Most of the past GCC issues have been threading-related; so if this happens predictably it is probably an issue in the code of the external component (or the JECL libraries it is based on). I guess I can put it on my long TODO list :-) The only memory debugging tool I know of for *nix which would work for debugging this sort of setup is dmalloc. -David Waite Wim Godden wrote: > Sadly, I'm already using 3.0.4... I had to upgrade to 3.0.4 because my > previous gcc wouldn't work... > > So I guess I'm stuck ? > > > David Waite wrote: > >> Without looking at the code, I can say there is a 99% chance this >> means that there has been memory corruption. Several things could >> have caused this corruption (array write out of bounds, double free, >> etc.) There is a good chance it could be gcc 3.0.1 - there are a ton >> of changes which happened to their C++ implementation between 2.95.3 >> and 3.0.x. There have also been a lot of improvements since 3.0, so >> if you can upgrade to 3.0.4, I would recommend it. The STL >> implementation within versions of gcc before 3.0.x were >> thread-unsafe, especially for std:string (they were interally >> reference-counted, but the reference modification was not atomic, nor >> was the reference comparison) >> >> -David Waite >> >> Wim Godden wrote: >> >>>This is the result : >>> >>>Core was generated by `icqv7ext'. >>>Program terminated with signal 11, Segmentation fault. >>>Reading symbols from /usr/local/lib/libsigc-1.0.so.0...done. >>>Reading symbols from /lib/libpthread.so.0...done. >>>Reading symbols from /lib/libresolv.so.2...done. >>>Reading symbols from /usr/local/lib/libstdc++.so.3...done. >>>Reading symbols from /lib/libm.so.6...done. >>>Reading symbols from /usr/local/lib/libgcc_s.so.1...done. >>>Reading symbols from /lib/libc.so.6...done. >>>Reading symbols from /lib/ld-linux.so.2...done. >>>#0 0x40126e88 in chunk_alloc (ar_ptr=0x401bbd40, nb=16) at malloc.c:2875 >>>2875malloc.c: No such file or directory. >>>(gdb) bt >>>#0 0x40126e88 in chunk_alloc (ar_ptr=0x401bbd40, nb=16) at malloc.c:2875 >>>#1 0x401265ae in __libc_malloc (bytes=12) at malloc.c:2696 >>>#2 0x80de950 in _ZNSt23__malloc_alloc_templateILi0EE8allocateEj (__n=12) at >>>/usr/local/include/g++-v3/bits/stl_alloc.h:114 >>>#3 0x8 >>>06f6d1 in >>>_ZN7bedrock3net6SocketC1ERNS0_13SocketWatcherERNS_10ThreadPoolEiiPNS0_5KarmaEPNS0_15ConnectionLimitE >>>( >>>this=0x8153010, watcher=@0xb81c, pool=@0xb7c4, key=0, >>>socketfd=-1, karma=0x0, conn_limit=0x0) >>>at /usr/local/include/g++-v3/bits/stl_alloc.h:184 >>>#4 0x806e655 in >>>_ZN7bedrock3net13SocketWatcher19createConnectSocketEPNS0_19SocketEventListenerEPKcS5_iiPNS0_5KarmaE >>>( >>>this=0xb81c, listener=0xb9f4, host=0x814fad4 "127.0.0.1", >>>service=0x814fab4 "_jabber._tcp", defaultport=7000, >>>thread_key=0, karma=0x0) at SocketWatcher.cpp:195 >>>#5 0x80db48e in >>>_ZN3jax16RouterConnectionINS_6PacketES1_E7connectERKSsS4_RN7bedrock3net7AddressE >>>(this=0xb9f0, >>>name=@0xb7a4, secret=@0xbac0, a=@0xb5d0) at >>>/usr/local/include/g++-v3/bits/basic_string.h:396 >>>#6 0x8059516 in _ZN8IcqTransC1ERKSsS1_S1_jb (this=0xb7a0, >>>serviceid=@0xbad0, password=@0xbac0, hostname=@0xbab0, >>>port= >>>7000, outgoing_dir=true) at IcqTrans.cpp:67 >>>#7 0x8069c17 in main (argc=1, argv=0xbb44) at main.cpp:113 >>>Current language: auto; currently c >>> >>> >>>David Waite wrote: >>> Wim Godden wrote: >Trying to run it like this : >icqv7ext -n icqv7ext -s secretpass -h 127.0.0.1 -p 7000 -m >sms.localnetwork.local > >I get : >Starting component... > Component ID : icqv7ext > Secret : secretpass > Jabberd IP : 127.0.0.1 > Jabberd Port : 7000 >Segmentation fault (core dumped) > > >Any ideas ? > Sounds like it is core-dumping wihle trying to start the component :-) Perhaps you could post a backtrace from the core? (perhaps "gdb icqv7ext -c core", then "bt".) Cores from threaded components are much nicer if they are generated from something other than Linux; if you are using Linux try to use the newest kernel possible (as they reworked a bit of this logic within the 2.4 series) -David Waite ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev >>> >>>-- >>>- >>>FirstLink Networks - http://www.firstlinknetworks.com >>>- >>>De leukste moppen op je scherm en in je mailbox : http://www.moppen.be >>> >>> >>>___ >>>jdev mailing list >>>[EMAIL PROTECTED] >>>http://mailman.jabber.org/listinfo/jdev >>> >> >> > > -- > - > FirstLink Networks - http://www.firstlinknetworks.com > - > De leukste moppen op je scherm en in je mailbox : http://www.moppen.be > > > _
[JDEV] Jabber advocacy
>What we need is a group of people to step up and say >I am interested in = >Jabber advocacy. That's the first step I am interested in Jabber advocacy:-) It's been up before but I don't think it got further than this:( Peter, you're up for it aren't you? /Rikard _ Hitta snörapporter... från 500 olika skidorter i Europa på http://se.snow.yahoo.com ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] A Jabber 'client deamon'
Hello, I'll try to explain my idea, but feel free to ask questions if anything is unclear! I was thinking about some sort of 'client deamon' for Jabber. The situation I'm confronted with is the following: I have a website running MyPHPNuke (a Content Management System - visitors can enter news, which I then review and eventually post on the page - in some ways similar to Slashdot). Every time someone enters a new news item, I would like to be notified of this. Jabber seems like a good way to do this. However, there is a problem. Every time I want to send a message, a connection to Jabber should be open. I can do this with Perl, but I still need to sleep() some time, because I'm waiting for the Jabber server to respond. When the connection is open, I can send my message. After this, the connection is closed, and the page can finish loading. Schematic view: 1. User submits new story 2. Server starts new process to handle this request 3. Server process opens connection to Jabber server 4. Server process sends message 5. Server process closes connection to Jabber server 6. Server process returns page to user Can you see the problem? Steps 3 and 5 should be avoidable. My suggestion is: At boot time, some sort of 'client deamon' is started, and it logs in to the Jabber server. When I want a PHP script to send a message to me, it only does a small call to some application, that then connects to the daemon to send it. Maybe there this should work in two ways: I can send a message to 'the machine', to execute some task. I'm sorry if all this sounds confusing, but I don't know how to explain it otherwise. Greetings, Jan Fabry -- Vlaamse Scholierenkoepel vzw Paleizenstraat 90 1030 Brussel 02-215 32 29 02-215 41 78 (fax) [EMAIL PROTECTED] Bezoek onze website: http://www.vsknet.be *** ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: Re: [JDEV] Dynamic Creation of Users in Jabber Server
I am not too sure what level of complexity you are looking to go for, but JabminRPC (https://www.jabberstudio.org/projects/view.php?id=10) could be used to do this very thing. Of course it's not java, but as long as your client speaks JabberRPC(Jabber flavoured XMLRPC) its not a problem at all to interface to add/remove/change users stuff without directly manipulating the user.xml file (We let jabberd handle all of that). Plus there are other nifty features and of course we are working on more. So check it out. See if that can help. Nick On Wed, 27 Mar 2002 09:14:52 +0600, raditha dissanayake <[EMAIL PROTECTED]> wrote: hi, as far as i know there isn't an exposed api that you can use for administration at the moment. If you want to add and remove users the easiest way would be for you to make/remove/edit entries in the spool directory. I also recommend that you check out the jabberbeans which will help you in creating any sort of client with java. r-a-v-i wrote: > Thanks for the immediate response Raditha ! > Ur guess was exactly correct. I am trying to administer Jabber Server via a > Java Client !! Wherein, I am able to connect to the server using the > existing JIDs, > but, am unable to create a new ID remotely. Infact, I am looking for the > following kinda if thing : > > java CreateUser > > Pls guide me what should I do ?? > > Lots of thanks in advance... > > Tx n Rgds > > r-a-v-i > - Original Message - > From: "raditha dissanayake" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, March 26, 2002 7:04 PM > Subject: Re: [JDEV] Dynamic Creation of Users in Jabber Server > > > >>Hi ravi, >>can you tell us if you are trying to administor a jabber server via a >>remote client or are you refering to an existing java client? >> >>ps: please remove the stationaer from your reply some of us will not be >>able to read your mail otherwise. >> >> >>r-a-v-i wrote: >> >> >>>href="file://C:\Program Files\Common Files\Microsoft >>> > Shared\Stationery\"> > >>>Hi All, >>> >>> >>> >>> Can anybody tell me how to configure Users in Jabber Server >>>dynamically using a java client ?? >>> >>> >>> >>>Lots of thanks in advance ... >>> >>> >>> >>>Tx n Rgds >>> >>> >>> >>>r-a-v-i >>> >>> >> >> >>-- >>Raditha Dissanayake >>[EMAIL PROTECTED] >>http://www.mediasolv.com/?rd >> >> >> >> >>___ >>jdev mailing list >>[EMAIL PROTECTED] >>http://mailman.jabber.org/listinfo/jdev >> > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > -- Raditha Dissanayake [EMAIL PROTECTED] http://www.mediasolv.com/?rd ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] A Jabber 'client deamon'
On Tue, Mar 26, 2002 at 05:18:33PM +0100, Jan Fabry wrote: | I'll try to explain my idea, but feel free to ask questions if anything | is unclear! | | I was thinking about some sort of 'client deamon' for Jabber. The | situation I'm confronted with is the following: ... | Schematic view: | 1. User submits new story | 2. Server starts new process to handle this request | 3. Server process opens connection to Jabber server | 4. Server process sends message | 5. Server process closes connection to Jabber server | 6. Server process returns page to user | | Can you see the problem? Steps 3 and 5 should be avoidable. Yeah, you want to pool the connection from one use to the next. You want a persistant connection. I think that persistant CGI could solve it for you. It depends on how easy it is to make phpNuke work as pcgi. | My suggestion is: | | At boot time, some sort of 'client deamon' is started, and it logs in to | the Jabber server. When I want a PHP script to send a message to me, it | only does a small call to some application, that then connects to the | daemon to send it. | | Maybe there this should work in two ways: I can send a message to 'the | machine', to execute some task. | | I'm sorry if all this sounds confusing, but I don't know how to explain | it otherwise. This makes perfect sense and is what I would do in that situation. Just to make things easy on yourself, pick a nice middleware such as XML-RPC or CORBA to communicate between the CGI script and the jabber client daemon. -D -- One man gives freely, yet gains even more; another withholds unduly, but comes to poverty. Proverbs 11:24 ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
