[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Strange error

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Strange error
From: Marvin Preuss <xsteadfastx@xxxxxxxxx>
Date: Wed, 01 Feb 2006 19:16:13 +0100
Delivered-to: archiver@seul.org
Delivered-to: or-talk-outgoing@seul.org
Delivered-to: or-talk@seul.org
Delivery-date: Wed, 01 Feb 2006 13:16:26 -0500
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=BhHbjTocDVgtAo5BAzl6HuzfunqL/VCyZ6ktiw/EalHwveOFtdM9uXxrRkz9xo2ZNuAXUOgrYvVv88NPr3LKb9a7ducCb0V7iGEaOdMTzgkJXscEyRLK0F/Y8onB42tRx3qWCHCJmt5e2d701at15zM3qupVH2auG/NjDeCz9EA=
In-reply-to: <20060201172905.GC21764@asteria.noreply.org>
References: <43E0DEA7.50506@gmail.com> <20060201172905.GC21764@asteria.noreply.org>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (X11/20051201)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Palfrader wrote:

Hi Peter,
thank you for your fast question...i hope we can get this here working.

> Then go to /var/lib/tor (cd /var/lib/tor) and start gdb on the corefile
> (gdb /usr/sbin/tor core.<1234>) and type "bt" into gdb's prompt.  Send
> us that output please.

there is a core file for eachtime this happend already...but from
today...gdb gives me that:

(gdb) bt
#0  0x401e47c1 in kill () from /lib/libc.so.6
#1  0x40166771 in pthread_kill () from /lib/libpthread.so.0
#2  0x40166a7b in raise () from /lib/libpthread.so.0
#3  0x401e4554 in raise () from /lib/libc.so.6
#4  0x401e5a88 in abort () from /lib/libc.so.6
#5  0x0806d7cb in directory_initiate_command (address=0x82df438
"85.25.66.203", addr=1427718859, dir_port=61376,
    platform=0x823eac0 "Tor 0.1.0.16 on Linux i686", digest=0x114
<Address 0x114 out of bounds>, purpose=1 '\001',
    private_connection=1, resource=0x0, payload=0x0, payload_len=0) at
directory.c:297
#6  0x0806d3d5 in directory_initiate_command_router (router=0x4016cd00,
purpose=1 '\001', private_connection=0,
    resource=0x0, payload=0x0, payload_len=0) at directory.c:225
#7  0x080855ec in consider_testing_reachability () at router.c:407
#8  0x08078e96 in run_scheduled_events (now=1138532431) at main.c:706
#9  0x080791e4 in second_elapsed_callback (fd=-1, event=1, args=0x0) at
main.c:834
#10 0x401b5c79 in event_base_priority_init () from
/usr/lib/libevent-1.1a.so.1
#11 0x401b5f65 in event_base_loop () from /usr/lib/libevent-1.1a.so.1
#12 0x401b5dcb in event_loop () from /usr/lib/libevent-1.1a.so.1
#13 0x401b5cb0 in event_dispatch () from /usr/lib/libevent-1.1a.so.1
#14 0x0807967b in do_main_loop () at main.c:953
#15 0x0807a365 in tor_main (argc=0, argv=0x0) at main.c:1620
#16 0x0808df4b in main (argc=0, argv=0x0) at tor_main.c:19
#17 0x401d0e36 in __libc_start_main () from /lib/libc.so.6
#18 0x0804bf81 in _start () at ../sysdeps/i386/elf/start.S:102

i hope this helps...that its really from that time it failed. let me
know if you see something strange in it.

> Also let us know how your torrc looks like.

okidoki...here. i paste everything not just the server config.

## Configuration file for a typical Tor user
## Last updated 22 July 2005 for Tor 0.1.0.13.
## (May or may not work for older or newer versions of Tor.)
#
## See the man page, or http://tor.eff.org/tor-manual.html, for more
## options you can use in this file.
#
# On Unix, Tor will look for this file in someplace like "~/.tor/torrc" or
# "/etc/torrc"
#
# On Windows, Tor will look for the configuration file in someplace like
# "Application Data\tor\torrc" or "Application Data\<username>\tor\torrc"
#
# With the default Mac OS X installer, Tor will look in ~/.tor/torrc or
# /Library/Tor/torrc

## Replace this with "SocksPort 0" if you plan to run Tor only as a
## server, and not make any local application connections yourself.
SocksPort 0 # what port to open for local application connections
SocksBindAddress 127.0.0.1 # accept connections only from localhost
#SocksBindAddress 192.168.0.1:9100 # listen on a chosen IP/port too

## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests from SocksBindAddress.
#SocksPolicy accept 192.168.0.1/16
#SocksPolicy reject *

## Allow no-name routers (ones that the dirserver operators don't
## know anything about) in only these positions in your circuits.
## Other choices (not advised) are entry,exit,introduction.
AllowUnverifiedNodes middle,rendezvous

## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many log lines as
## you want.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send only debug and info messages to /var/log/tor/debug.log
#Log debug-info file /var/log/tor/debug.log
## Send ONLY debug messages to /var/log/tor/debug.log
#Log debug-debug file /var/log/tor/debug.log
## To use the system log instead of Tor's logfiles, uncomment these lines:
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr

## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line.
#RunAsDaemon 1

## Tor only trusts directories signed with one of these keys, and
## uses the given addresses to connect to the trusted directory
## servers. If no DirServer lines are specified, Tor uses the built-in
## defaults (moria1, moria2, tor26), so you can leave this alone unless
## you need to change it.
#DirServer 18.244.0.188:9031 FFCB 46DB 1339 DA84 674C 70D7 CB58 6434
C437 0441
#DirServer 18.244.0.114:80 719B E45D E224 B607 C537 07D0 E214 3E2D 423E 74CF
#DirServer 86.59.21.38:80 847B 1F85 0344 D787 6491 A548 92F9 0493 4E4E B85D

## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory /var/lib/tor

## The port on which Tor will listen for local connections from Tor
controller
## applications, as documented in control-spec.txt.  NB: this feature is
## currently experimental.
#ControlPort 9051

############### This section is just for location-hidden services ###

## Look in .../hidden_service/hostname for the address to tell people.
## HiddenServicePort x y:z says to redirect a port x request from the
## client to y:z.

#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80

#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22
#HiddenServiceNodes moria1,moria2
#HiddenServiceExcludeNodes bad,otherbad

################ This section is just for servers #####################

## NOTE: If you enable these, you should consider mailing your identity
## key fingerprint to the tor-ops, so we can add you to the list of
## servers that clients will trust. See
## http://tor.eff.org/doc/tor-doc.html#server for details.

## Required: A unique handle for this server
Nickname xsteadfastx

## The IP or fqdn for this server. Leave commented out and Tor will guess.
Address 85.25.66.203

## Contact info that will be published in the directory, so we can
## contact you if you need to upgrade or if something goes wrong.
## This is optional but recommended.
#ContactInfo xsteadfastx <xsteadfastx AT gmail dot com>
## You might also include your PGP or GPG fingerprint if you have one:
ContactInfo 1234D/8EC5DE83 xsteadfastx <xsteadfastx AT gmail dot com>

## Required: what port to advertise for tor connections
ORPort 9001
## If you want to listen on a port other than the one advertised
## in ORPort (e.g. to advertise 443 but bind to 9090), uncomment
## the line below. You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORBindAddress 0.0.0.0:9090

## Uncomment this to mirror the directory for others (please do)
DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised
## in DirPort (e.g. to advertise 80 but bind 9091), uncomment the line
## below. You'll need to do ipchains or other port forwarding yourself
## to make this work.
#DirBindAddress 0.0.0.0:9091

## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to *replace*
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you're *augmenting* (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## available in the man page or at http://tor.eff.org/documentation.html
##
## Look at http://tor.eff.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
ExitPolicy reject *:* # middleman only -- no exits allowed

BandwidthRate 30 KB
BandwidthBurst 100 KB

AccountingStart day 12:00
AccountingMax 500 MB

i hope you can help me with it...thank you already. maybe for a
workaround i could disable the dirport...but thats just my idea :)

Marvin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD4PrtChE8w47F3oMRAoWqAJ9fmRvvWRSc/GPpkUg6Z6zcDrliDwCdGExP
Pm7x532awwRN4B9LMEkhI5Q=
=95ld
-----END PGP SIGNATURE-----

Follow-Ups:
- Re: Strange error
  - From: Peter Palfrader

References:
- Strange error
  - From: Marvin Preuss
- Re: Strange error
  - From: Peter Palfrader

Prev by Author: Strange error
Next by Author: Re: Strange error
Previous by thread: Re: Strange error
Next by thread: Re: Strange error
Index(es):
- Author
- Thread