Opened 12 years ago

Last modified 7 years ago

#397 closed defect (Fixed)

bandwidthrate unreadable ?

Reported by: zambetti Owned by:
Priority: Low Milestone: 0.1.2.x-final
Component: Core Tor/Tor Version: 0.1.2.7-alpha
Severity: Keywords:
Cc: zambetti Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hello,

I'm a new Tor user and I tried to set up server mode. However, I always get these warnings (they come 1 time / min, approx.)

févr. 24 14:29:34:078 [Warning] bandwidthrate unreadable or 0. Failing.
févr. 24 14:29:34:250 [Warning] router_rebuild_descriptor(): Couldn't allocate string for descriptor.

Does it means my server is KO ? I don't know if it's a problem in my configuration or a bug.

Thanks for your help

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Child Tickets

Change History (19)

comment:1 Changed 12 years ago by nickm

Well, if it's a problem with your configuration, there is still a bug: the error message in question is
pretty useless.

Can you attach a copy of your torrc file?

comment:2 Changed 12 years ago by zambetti

Thanks for your help. My torrc is below :

# This file was generated by Tor; if you edit it, comments will not be preserved
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor will ignore it

# The advertised (external) address we should use.
Address 82.66.212.76
# Limit the maximum token buffer size (also known as burst) to the given
# number of bytes.
BandwidthBurst 204800
# A token bucket limits the average incoming bandwidth on this node to the
# specified number of bytes per second.
BandwidthRate 102400
# Administrative contact information to advertise for this server.
ContactInfo kazorial at gmail dot com
# If set, Tor will accept connections from the same machine (localhost only)
# on this port, and allow those connections to control the Tor process using
# the Tor Control Protocol (described incontrol-spec.txt).
ControlPort 9051
# Serve directory information from this port, and act as a directory cache.
DirPort 9030
# Address/port ranges for which to accept or reject outgoing connections on
# behalf of Tor users.
ExitPolicy accept *:80,accept *:706,accept *:1863,accept *:5050,accept *:5190,accept *:5222,accept *:8300,accept *:8888,reject *:*
# Where to send logging messages. Format is minSeverity[-maxSeverity]
# (stderr|stdout|syslog|file FILENAME).
Log notice stdout
# Set the server nickname.
Nickname Astaroth
# Advertise this port to listen for connections from Tor clients and servers.
ORPort 9001

comment:3 Changed 12 years ago by knappo

I can second this bug motion. I had the same problem on my WinXP SP2 (german) testing with Vidalia 0.0.11 and TOR 0.1.2.7. I can not confirm it on other settings, just didn't test it...

There was also a entry at the or-mailing list where somebody had exactly the same bug. I got rid of this bug by doing the following steps:

  1. Setting the speedlimit in Vidalia to a 3-digit number (e.g. 101 or 075 or 001 or....).
  2. Shutting down tor and Vidalia.
  3. Restarting Vidalia (tor autostart)

The Messages vanished.

Some more details for my settings:
NO Exit
DirPort 80
ORPort 443
BwRate 101
BWMaxRate 110

Lets find this bug!

Knappo

comment:4 Changed 12 years ago by zambetti

I just tried this trick. In Vidalia I replaced BWR 100 (kB/s) by ... 100 and BWB 200 by 200, then stop and restart vidalia and tor and it's works fine : no more warnings ! I had a look to my torrc after that : it's exactly the same as previous.

(my server runs on XP SP2)

Thanks

comment:5 Changed 12 years ago by knappo

Glad I could help. BUT this is a bug (but I think a Vidalia thing???)

comment:6 Changed 12 years ago by knappo

It is NOT a Vidalia thing, i have installed 0.0.10 again and it is also happening... seems to happen only with 1.2.7-alpha so this is perhabs the version to blame...

comment:7 Changed 12 years ago by nickm

So far only people using vidalia have reported this bug, but I think it is a problem with Tor somewhere.

What I still need, though, is some idea of how to reproduce this bug. Can you give me step-by-step
instructions so that we can see these warning messages?

comment:8 Changed 12 years ago by zambetti

Here it is to ways for reproducing this bug. First one operates every time. Second one, operates sometimes
only but is interesting because quite different :

1st way :

  • Run Vidalia settings GUI
  • Click on "Server" button
  • Click on "Bandtwith limits" tab
  • Change bandwidth rate ("100" --> "20")
  • Stop and restart Vidalia + tor

Note : if you give "020" as new value, warnings don't appear

2nd way :

  • Run Vidalia settings GUI
  • Click on "Advanced" button
  • Activate "Run as a windows service"
  • Stop and restart Vidalia + tor

comment:9 Changed 12 years ago by nickm

Matt Edman (the vidalia guy) says that he managed to reproduce the bug only on Windows, and
only using Tor 0.1.2.7-alpha and earlier; apparently the svn code may be fixed.

Can somebody try this with Tor's logging turned on to level INFO, and read the messages (and
surrounding material) out of _Tor's_ log (not vidalia's copy of Tor's log)?

comment:10 Changed 12 years ago by nickm

edmanm to the rescue:

Feb 25 14:21:42.295 [warn] bandwidthrate unreadable or 0. Failing.
Feb 25 14:21:42.326 [warn] send_control1_event_impl(): Unable to format event for controller.
Feb 25 14:21:42.326 [err] router_dump_router_to_string(): We just generated a router descriptor we can't parse: [[router Unnamed 24.149.57.148 9001 0 0
platform Tor 0.1.2.7-alpha on Windows XP Service Pack 2 [workstation] {terminal services, single user}
published 2007-02-25 19:21:42
opt fingerprint 072A 30F3 A620 52D0 8441 8922 147D BBCC 408E 18AC
uptime 123
bandwidth 0 102400 0
onion-key


MIGJAoGBAN23wcawkkgwX5E7PESxSmWhUeQp39Zh58nHe6/q5VaK4UWEGDrnVhg4
i7pegIPIwOhAS0WA+ZGb9FDZ8nFMafkbU523gtO8DcfD5ItJx4bojySHsHS+mbW7
G/yEfrB/BLOBwOAyBwalo6f9GkD2N3isAmxNPNL30SG3HhukhJipAgMBAAE=


signing-key


MIGJAoGBAMVIlYjLedzOKFXDLjHrvOCIExIkXFqxl+G3lbeIB9p2e2HxQ9wMGmhH
XaHYT3Bz/kNwGSYbcAZM5RfG9eEH0TukjD7qKFz8/rvr270j1NLp6WwjnjMe6rCR
dRVoYby/SoLKet1eGMFIG3cdS0jxrypL9a9rP+Ek7f9FW7G0zR5dAgMBAAE=


opt write-history 2007-02-25 19:15:59 (900 s) 59392,0,0,0,0,0,0,0,0
opt read-history 2007-02-25 19:15:59 (900 s) 1776640,0,0,0,0,0,0,0,0
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:465
reject *:563
reject *:587
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*
router-signature


uq2r/T7LC0NO91mYZfn4cdAcVHdzTG5sjYQv6IXLUjWfM8XO+7I5MOYwn70wyi35
HyE+03O8B3mQItyAEDiGnCuoOtcWliAO8zuYBEQxUN4l4Qx2+/DWc2N8FaKCw5J9
nZBTNOvcOMgNU1GRvj8hBB8GceG8um/T4EIqDdu5Ta4=


]]
Feb 25 14:21:42.326 [warn] router_rebuild_descriptor(): Couldn't allocate string for descriptor.

comment:11 Changed 12 years ago by nickm

01:31 < edmanm> nickm: for another data point, i can make my win32 tor flip out

about "bandwidthrate unreadable or 0" without vidalia by
sending it:

01:31 < edmanm> setconf orport="9001" dirport="9030" nickname="Unnamed"

bandwidthrate="20480"

01:32 < nickm> win32 only?
01:32 < edmanm> tor 0.1.2.7-alpha on my mac doesn't seem to mind, at least.
01:32 < nickm> bizarre!
01:37 < edmanm> tor 0.1.2.7-alpha-dev doesn't seem to mind either, so, yay?
01:37 < nickm> does tor 0.1.2.7-alpha-dev mind on windows?
01:38 < edmanm> no.
01:39 < nickm> wow.

comment:12 Changed 12 years ago by nickm

Okay, we're a step closer; this bug seems to be caused by bug 400.

comment:13 Changed 12 years ago by nickm

Also note that Matt Edman describes a possible workaround in his writeup:

A side-effect of this problem is that Win32 users of Tor 0.1.2.8-beta are unable to start a
Tor server with Vidalia, unless they manually set a value for
MaxAdvertisedBandwidth to something greater than or equal to 10000 and less
than 2^32.

comment:14 Changed 12 years ago by nickm

Aha!

I think I fixed this in svn commit r9691, which will appear in 0.1.2.9-{rc/beta}.

comment:15 Changed 12 years ago by nickm

Could people try reproducing this bug with the beta-dev snapshot made by phobos at

http://interloper.org/tmp/tor-0.1.2.8/tor-0.1.2.8-beta-dev-win32.exe and .asc ? It's from r9691.

We'd really like to know whether we fixed this problem soon, so we can put out an -rc release.

comment:16 Changed 12 years ago by Crash

I recognized the same Bug some minutes ago, but the dev version from above fixed it well away. The torrc includes
the correct config again now. Thanks a lot!

comment:17 Changed 12 years ago by nickm

Great! I'll mark it fixed. Thanks for all your help.

comment:18 Changed 12 years ago by nickm

flyspray2trac: bug closed.
seems to be fixed by either something mysterious in 0.1.2.8-beta, or by r9691 patch.

comment:19 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.