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

[tor-bugs] #7267 [Tor]: src/or/channel.c:1315 channel_closed: Assertion chan->state == CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state == CHANNEL_STATE_ERROR failed;

To: undisclosed-recipients:;
Subject: [tor-bugs] #7267 [Tor]: src/or/channel.c:1315 channel_closed: Assertion chan->state == CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state == CHANNEL_STATE_ERROR failed;
From: "Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>
Date: Wed, 31 Oct 2012 12:57:21 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Wed, 31 Oct 2012 08:57:39 -0400
List-archive: <http://lists.torproject.org/pipermail/tor-bugs>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: Tor bug tracker status mails" <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
Reply-to: tor-assistants@xxxxxxxxxxxxxx
Sender: tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx

#7267: src/or/channel.c:1315 channel_closed: Assertion chan->state ==
CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state
== CHANNEL_STATE_ERROR failed;
-----------------------+----------------------------------------------------
 Reporter:  asn        |          Owner:                    
     Type:  defect     |         Status:  new               
 Priority:  major      |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor        |        Version:  Tor: 0.2.4.4-alpha
 Keywords:  tor-relay  |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------
 aagbsn reported the following bug:

 {{{
 "torrc" 191L, 8688C written
 tor24@DC03R05DS10:~$ tor -f torrc
 Oct 27 15:32:59.306 [notice] Tor v0.2.4.5-alpha (git-17a6aa56cefe9d83)
 running on Linux with Libevent 2.0.16-stable and OpenSSL 0.9.8o.
 Oct 27 15:32:59.307 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/downlo
 ad#warning
 Oct 27 15:32:59.307 [notice] This version is not a stable Tor release.
 Expect more bugs than usual.
 Oct 27 15:32:59.307 [notice] Read configuration file "/home/tor24/torrc".
 Oct 27 15:32:59.307 [notice] Your ContactInfo config option is not set.
 Please consider setting it, so we can contact you if your serve
 r is misconfigured or something else goes wrong.
 Oct 27 15:32:59.307 [notice] Opening OR listener on 0.0.0.0:2424
 Oct 27 15:32:59.307 [notice] Opening Directory listener on 0.0.0.0:9024
 Oct 27 15:32:59.000 [notice] Configured to measure directory request
 statistics, but no GeoIP database found. Please specify a GeoIP da
 tabase using the GeoIPFile option.
 Oct 27 15:32:59.000 [notice] Your OpenSSL version seems to be 0.9.8o. We
 recommend 1.0.0 or later.
 Oct 27 15:32:59.000 [notice] Your Tor server's identity key fingerprint is
 'lna24 E02894BC4F3B8E74CC0182866BC74F044D1C75A9'
 Oct 27 15:33:00.000 [notice] We now have enough directory information to
 build circuits.
 Oct 27 15:33:00.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network.
 Oct 27 15:33:01.000 [notice] Self-testing indicates your ORPort is
 reachable from the outside. Excellent. Publishing server descriptor.
 Oct 27 15:33:02.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop.
 Oct 27 15:33:02.000 [notice] We weren't able to find support for all of
 the TLS ciphersuites that we wanted to advertise. This won't hu
 rt security, but it might make your Tor (if run as a client) more easy for
 censors to block.
 Oct 27 15:33:02.000 [notice] To correct this, use a more recent OpenSSL,
 built without disabling any secure ciphers or features.
 Oct 27 15:33:02.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
 Oct 27 15:33:06.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Oct 27 15:33:06.000 [notice] Bootstrapped 100%: Done.
 Oct 27 15:34:05.000 [notice] Self-testing indicates your DirPort is
 reachable from the outside. Excellent.
 Oct 27 15:36:07.000 [notice] Performing bandwidth self-test...done.
 Oct 27 21:33:01.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with
 138 circuits open. I've sent 4.34 GB and received 4.07 GB.
 Oct 28 03:33:01.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with
 260 circuits open. I've sent 9.07 GB and received 8.49 GB.
 Oct 28 09:33:01.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with
 406 circuits open. I've sent 17.43 GB and received 16.27 GB.
 Oct 28 15:33:01.000 [notice] Heartbeat: Tor's uptime is 1 day 0:00 hours,
 with 949 circuits open. I've sent 32.61 GB and received 30.51 GB.
 Oct 28 21:33:01.000 [notice] Heartbeat: Tor's uptime is 1 day 6:00 hours,
 with 1293 circuits open. I've sent 81.66 GB and received 77.32 GB.
 Oct 29 03:33:01.000 [notice] Heartbeat: Tor's uptime is 1 day 12:00 hours,
 with 3153 circuits open. I've sent 137.15 GB and received 129.72 GB.
 Oct 29 09:33:01.000 [notice] Heartbeat: Tor's uptime is 1 day 18:00 hours,
 with 4141 circuits open. I've sent 223.18 GB and received 209.59 GB.
 Oct 29 11:01:44.000 [warn] Tried to establish rendezvous on non-OR or non-
 edge circuit.
 Oct 29 15:33:01.000 [notice] Heartbeat: Tor's uptime is 2 days 0:00 hours,
 with 13439 circuits open. I've sent 365.67 GB and received 339.01 GB.
 Oct 29 16:24:15.000 [warn] Your computer is too slow to handle this many
 circuit creation requests! Please consider using the
 MaxAdvertisedBandwidth config option or choosing a more restricted exit
 policy.
 Oct 29 19:53:18.000 [warn] Tried to establish rendezvous on non-OR or non-
 edge circuit.
 Oct 29 19:53:40.000 [warn] Tried to establish rendezvous on non-OR or non-
 edge circuit.
 Oct 29 21:33:01.000 [notice] Heartbeat: Tor's uptime is 2 days 6:00 hours,
 with 6755 circuits open. I've sent 544.70 GB and received 502.54 GB.
 Oct 30 03:33:01.000 [notice] Heartbeat: Tor's uptime is 2 days 12:00
 hours, with 7723 circuits open. I've sent 653.13 GB and received 598.68
 GB.
 Oct 30 09:02:42.000 [notice] Received reload signal (hup). Reloading
 config and resetting internal state.
 Oct 30 09:02:42.000 [notice] Read configuration file "/home/tor24/torrc".
 Oct 30 09:02:42.000 [notice] Your ContactInfo config option is not set.
 Please consider setting it, so we can contact you if your server is
 misconfigured or something else goes wrong.
 Oct 30 09:02:42.000 [notice] Configured hibernation. This interval begins
 at 2012-10-30 00:00:00 and ends at 2012-10-31 00:00:00. We have no prior
 estimate for bandwidth, so we will start out awake and hibernate when we
 exhaust our quota.
 Oct 30 09:02:42.000 [notice] Configured to measure directory request
 statistics, but no GeoIP database found. Please specify a GeoIP database
 using the GeoIPFile option.
 Oct 30 09:02:43.000 [notice] Not advertising DirPort (Reason:
 AccountingMax enabled)
 Oct 30 09:33:01.000 [notice] Heartbeat: Tor's uptime is 2 days 18:00
 hours, with 4635 circuits open. I've sent 733.72 GB and received 668.67
 GB.
 Oct 30 12:29:02.000 [warn] Your computer is too slow to handle this many
 circuit creation requests! Please consider using the
 MaxAdvertisedBandwidth config option or choosing a more restricted exit
 policy. [32 similar message(s) suppressed in last 60 seconds]
 Oct 30 15:33:01.000 [notice] Heartbeat: Tor's uptime is 3 days 0:00 hours,
 with 6767 circuits open. I've sent 794.36 GB and received 726.46 GB.
 Oct 30 19:28:50.000 [warn] Tried to establish rendezvous on non-OR or non-
 edge circuit.
 Oct 30 20:35:13.000 [notice] Bandwidth soft limit reached; commencing
 hibernation. No new connections will be accepted
 Oct 30 20:36:51.000 [notice] Going dormant. Blowing away remaining
 connections.
 Oct 30 20:36:51.000 [err] channel_closed(): Bug: src/or/channel.c:1315:
 channel_closed: Assertion chan->state == CHANNEL_STATE_CLOSING ||
 chan->state == CHANNEL_STATE_CLOSED || chan->state == CHANNEL_STATE_ERROR
 failed; aborting.
 src/or/channel.c:1315 channel_closed: Assertion chan->state ==
 CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED ||
 chan->state == CHANNEL_STATE_ERROR failed; aborting.
 Aborted
 $ tor --version
 Tor version 0.2.4.5-alpha (git-17a6aa56cefe9d83).
 }}}

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7267>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Follow-Ups:
- Re: [tor-bugs] #7267 [Tor]: src/or/channel.c:1315 channel_closed: Assertion chan->state == CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state == CHANNEL_STATE_ERROR failed;
  - From: Tor Bug Tracker & Wiki
- Re: [tor-bugs] #7267 [Tor]: src/or/channel.c:1315 channel_closed: Assertion chan->state == CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state == CHANNEL_STATE_ERROR failed;
  - From: Tor Bug Tracker & Wiki

Prev by Author: Re: [tor-bugs] #4246 [Website]: Create a JS-based clock-check page to diagnose HS problems
Next by Author: Re: [tor-bugs] #7164 [Tor]: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1
Previous by thread: Re: [tor-bugs] #4246 [Website]: Create a JS-based clock-check page to diagnose HS problems
Next by thread: Re: [tor-bugs] #7267 [Tor]: src/or/channel.c:1315 channel_closed: Assertion chan->state == CHANNEL_STATE_CLOSING || chan->state == CHANNEL_STATE_CLOSED || chan->state == CHANNEL_STATE_ERROR failed;
Index(es):
- Author
- Thread