Hi all,

I have been running the Nov 22 2.1beta1 for a month or so.

Just now, I received a rather alarming message from the sysop of a private tracker who said that my IP number has been generating a huge amount of traffic on the server. After further investigation, this is what he determined:

Code: Select all

from xxx.xxx.xxx.xxx:
2006 Dec 31 19:45 (start of log) to 2007 Jan 5 00:50- 9558 announce/scrape calls (one rougly every 2-3 seconds)
 
from xxx.xxx.xxx.xxx:
2007 Jan 5 07:47:45 to 2007 Jan 27 13:10:43 (now)- 41105 announce/scrape calls (~same freq. as above)

It's your CLIENT. Someway your client's announce interval is set to ~1-2 seconds overriding our normal 30 min announce interval, flooding the tracker with announce/scrape requests. I'm taking immediate action & will implement some sort of anti-flood routine in our announce.php.
Please fix the client´s configuration ASAP.

In case this is a bug in the beta, I have uninstalled it and I am in the process of reinstalling the v2.0.3 rpm. (I am hoping the same bug doesn't exist in the earlier release.)

Anyone have any idea what was going on here? This nearly got me banned from the tracker.

If you need additional details, please let me know.

PS I am listed under two different IPs in the tracker's logs because I switched ISPs on 5 January.

I'm not quite sure if we changed something after 2.1beta1 but I strongly suggest you keep away from that version since it has some known bugs. If it's possible, try the latest SVN version and see if this is happening again so we can fix it for the upcoming version 2.1 which should be out the next weekend.

I just picked up this weekend's tarball. Alas it doesn't contain a "configure" script. Has something changed or am I missing something?

Code: Select all

[colin@ariel ktorrent-27-01-07]$ ls -1
admin
apps
AUTHORS
ChangeLog
configure.in.bot
configure.in.in
COPYING
COPYING-DOCS
Doxyfile
estimation-scripts
INSTALL
ktorrent.kdevelop
libktorrent
Makefile.am
Makefile.cvs
NEWS
plugins
README
scripts
templates
TODO
utests


You have to execute "make -f Makefile.cvs" first.

OK, I got it compiled and installed it in /usr/local

Unfortunately it crashes when I try to launch it:

Code: Select all

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208203568 (LWP 13309)]
[KCrash handler]
#6  0x00000000 in ?? ()
#7  0x00458d78 in kt::PluginManager::loadPluginList ()
   from /usr/local/lib/libktorrent-2.1dev.so
#8  0x0807cb29 in KTorrentCore::loadPlugins ()
#9  0x08067106 in KTorrent::KTorrent ()
#10 0x08084711 in KTorrentApp::newInstance ()
#11 0x0677b8cf in KUniqueApplication::processDelayed ()
   from /usr/lib/libkdecore.so.4
#12 0x067a89b8 in KUniqueApplication::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#13 0x0808410f in KTorrentApp::qt_invoke ()
#14 0x05f30bea in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x062bcace in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x05f4f3b7 in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x05f57ff3 in QSingleShotTimer::event ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x05ec7e6b in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x05ec92e9 in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x067deca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#21 0x05ebbc72 in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x05e701df in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x05ee13f0 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x05ee12a6 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x05ec797f in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x08062eb6 in main ()

You kept the old installation?

You should remove your previous installation and install KTorrent in your $KDEDIR otherwise bad things could happen.

So, probably something like ./configure --prefix=$KDEDIR

ahhh, ok. I was hoping I could keep the rpm installed in the default /usr path and run the beta from /usr/local, as I do with some other apps (to make it easy to switch between the two) but that appears not to be possible.

Because of the huge bandwidth problems caused by the beta (on a given day last month my client was generating 40% of the site's traffic), the private tracker I use has banned all versions of ktorrent later than v2.0.3. So, if I want to continue to use that tracker (which I do), I am forced to revert to 2.0.3.

If the next release proves stable, it will be added to the site's whitelist.

So, for the time being, I will be unable to help you test the betas, which I really regret. I realize that beta software is experimental and can lead to crashes, data loss, etc., and I accept this. At the same time, network issues like this, which we end users have little insight into and no control over, are really disastrous. I sincerely hope that the devs identify the code that was causing scrape.php to be called every 2-3 seconds and take steps to prevent such problems from arising again.

Via yum I installed v2.1 and asked the sysop of the private tracker to add it to the whitelist. He is adopting a wait-and-see attitude. If there are no negative reports over the next few weeks, it will be added.

His whitelist is based on the "peer_id" and he asked me to obtain it for this this release.

Thanks.

Peer ID is : -KT2100-

Followed by some random stuff.