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

[tor-bugs] Re: #1315 [Tor - Tor client]: Unable to get Tor to compile using OpenSSL 1.0.0-beta5 on Debian Lenny

To: undisclosed-recipients:;
Subject: [tor-bugs] Re: #1315 [Tor - Tor client]: Unable to get Tor to compile using OpenSSL 1.0.0-beta5 on Debian Lenny
From: "Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>
Date: Wed, 28 Jul 2010 18:53:06 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivered-to: tor-bugs-outgoing@xxxxxxxx
Delivered-to: tor-bugs@xxxxxxxxxxxxxx
Delivery-date: Wed, 28 Jul 2010 14:53:12 -0400
In-reply-to: <044.c8a4519cd52e97f0cc428c487023d9fd@xxxxxxxxxxxxxx>
References: <044.c8a4519cd52e97f0cc428c487023d9fd@xxxxxxxxxxxxxx>
Reply-to: tor-assistants@xxxxxxxxxxxxxx
Sender: owner-tor-bugs@xxxxxxxxxxxxxx

#1315: Unable to get Tor to compile using OpenSSL 1.0.0-beta5 on Debian Lenny
--------------------------------+-------------------------------------------
 Reporter:  narr                |         Type:  defect          
   Status:  new                 |     Priority:  minor           
Milestone:  Tor: 0.2.2.x-final  |    Component:  Tor - Tor client
  Version:  0.2.2.10-alpha      |   Resolution:  None            
 Keywords:                      |       Parent:                  
--------------------------------+-------------------------------------------

Old description:

> My high bandwidth exit node crashes every few days - network timeouts,
> unable to connect
> (for server config, see below). Using remote console, I can see a lot of
> output being
> printed; from my limited  Linux knowledge the following lines look most
> interesting:
>
> oom-killer: gfp_mask=0xd0, order=1
>  [<c013f177>] out_of_memory+0x25/0x13a
>  [<c0140655>] __alloc_pages+0x1f5/0x275
>  [<c015626e>] cache_alloc_refill+0x297/0x493
>  [<c015603a>] cache_alloc_refill+0x63/0x493
>  [<c0155fbe>] kmem_cache_alloc+0x3b/0x54
>  [<c0118d7a>] copy_process+0xa5/0x10ae
>  [<c0155fcd>] kmem_cache_alloc+0x4a/0x54
>  [<c028a288>] _spin_lock_irq+0x8/0x18
>  [<c01295bb>] alloc_pid+0x1fc/0x219
>  [<c0119fe8>] do_fork+0x91/0x17a
>  [<c01239a5>] sigprocmask+0xcc/0xd2
>  [<c0102c06>] sys_clone+0x28/0x2d
>  [<c0104883>] syscall_call+0x7/0xb
>
> Sometimes I also get:
>
> <c01506c2>] read_swap_cache_async+0x2f/0xac
>  [<c01461b2>] swapin_readahead+0x3a/0x58
>  [<c0148654>] __handle_mm_fault+0xa62/0xfa3
>  [<c015844e>] do_truncate+0x6b/0x75
>  [<c013ff4f>] __pagevec_free+0x14/0x1a
>  [<c0141f78>] release_pages+0x143/0x14b
>  [<c0111889>] do_page_fault+0x6af/0xb76
>  [<c0325c7c>] flush_window+0x4b/0x94
>  [<c014b7bc>] unmap_region+0xe1/0xf0
>  [<c0155c0d>] kmem_cache_free+0x44/0x7d
>  [<c011e9ea>] sys_gettimeofday+0x27/0x53
>  [<c01111da>] do_page_fault+0x0/0xb76
>  [<c0104a0f>] error_code+0x2b/0x30
>
> So, after reading the FAQ, I'm now trying to build Tor with OpenSSL
> 1.0.0-beta5 manually.
> These are the steps I performed:
>
> - I left the Debian OpenSSL package installed and used configure, make
> and make install to
> install OpenSSL1.0.0-beta5 to /usr/local/ssl
> - Using the guide at https://www.torproject.org/docs/debian.html.en , I
> got the source for
> Tor 0.2.2.10-alpha and tried to configure it:
>
>  ./configure --enable-openbsd-malloc --enable-static-openssl --with-
> openssl-dir=/usr/local/ssl
>
> Then, I used debuild -rfakeroot -uc -us and installed the package, but
> Tor still seems to be
> using OpenSSL 0.9.8:
>
>  [notice] Tor 0.2.2.10-alpha (git-e43253ba9e9430ea) opening log file.
>  [notice] OpenSSL OpenSSL 0.9.8g 19 Oct 2007 [90807f] looks like it's
> older than 0.9.8l,
>  but some vendors have backported 0.9.8l's renegotiation code to earlier
> versions.  #
>  I'll set SSL3_FLAGS just to be safe.
>
> Makefile:
>
>  OPENSSL = /usr/local/ssl/bin/openssl
>  TOR_OPENSSL_LIBS = /usr/local/ssl/lib/libssl.a
> /usr/local/ssl/lib/libcrypto.a
>
> Sebastian suggested to also compile libevent statically, but I'm not sure
> how: The
> option --with-libevent-dir wants me to specify a directory, whereas I
> only have
> libevent libraries directly inside /usr/lib.
> Also, is it on purpose that configure accepts both --with-openssl-
> dir=/usr/local/ssl
> and --with-openssl-dir=/usr/local/ssl/bin ?
>
> You can find me on IRC (nick "narr").
>
> ----
> Debian Lenny DomU with 2.6.18-6-xen-686 etch Kernel
> ~5MB/s bandwidth
>
> free -m (no tor running)
>              total       used       free     shared    buffers     cached
> Mem:          1640       1625         15          0         14       1200
> -/+ buffers/cache:        410       1229
> Swap:         1023          0       1023
>

> [Automatically added by flyspray2trac: Operating System: Other Linux]

New description:

 My high bandwidth exit node crashes every few days - network timeouts,
 unable to connect
 (for server config, see below). Using remote console, I can see a lot of
 output being
 printed; from my limited  Linux knowledge the following lines look most
 interesting:

 oom-killer: gfp_mask=0xd0, order=1
  [<c013f177>] out_of_memory+0x25/0x13a
  [<c0140655>] __alloc_pages+0x1f5/0x275
  [<c015626e>] cache_alloc_refill+0x297/0x493
  [<c015603a>] cache_alloc_refill+0x63/0x493
  [<c0155fbe>] kmem_cache_alloc+0x3b/0x54
  [<c0118d7a>] copy_process+0xa5/0x10ae
  [<c0155fcd>] kmem_cache_alloc+0x4a/0x54
  [<c028a288>] _spin_lock_irq+0x8/0x18
  [<c01295bb>] alloc_pid+0x1fc/0x219
  [<c0119fe8>] do_fork+0x91/0x17a
  [<c01239a5>] sigprocmask+0xcc/0xd2
  [<c0102c06>] sys_clone+0x28/0x2d
  [<c0104883>] syscall_call+0x7/0xb

 Sometimes I also get:

 <c01506c2>] read_swap_cache_async+0x2f/0xac
  [<c01461b2>] swapin_readahead+0x3a/0x58
  [<c0148654>] __handle_mm_fault+0xa62/0xfa3
  [<c015844e>] do_truncate+0x6b/0x75
  [<c013ff4f>] __pagevec_free+0x14/0x1a
  [<c0141f78>] release_pages+0x143/0x14b
  [<c0111889>] do_page_fault+0x6af/0xb76
  [<c0325c7c>] flush_window+0x4b/0x94
  [<c014b7bc>] unmap_region+0xe1/0xf0
  [<c0155c0d>] kmem_cache_free+0x44/0x7d
  [<c011e9ea>] sys_gettimeofday+0x27/0x53
  [<c01111da>] do_page_fault+0x0/0xb76
  [<c0104a0f>] error_code+0x2b/0x30

 So, after reading the FAQ, I'm now trying to build Tor with OpenSSL
 1.0.0-beta5 manually.
 These are the steps I performed:

 - I left the Debian OpenSSL package installed and used configure, make and
 make install to
 install OpenSSL1.0.0-beta5 to /usr/local/ssl
 - Using the guide at https://www.torproject.org/docs/debian.html.en , I
 got the source for
 Tor 0.2.2.10-alpha and tried to configure it:

  ./configure --enable-openbsd-malloc --enable-static-openssl --with-
 openssl-dir=/usr/local/ssl

 Then, I used debuild -rfakeroot -uc -us and installed the package, but Tor
 still seems to be
 using OpenSSL 0.9.8:

  [notice] Tor 0.2.2.10-alpha (git-e43253ba9e9430ea) opening log file.
  [notice] OpenSSL OpenSSL 0.9.8g 19 Oct 2007 [90807f] looks like it's
 older than 0.9.8l,
  but some vendors have backported 0.9.8l's renegotiation code to earlier
 versions.  #
  I'll set SSL3_FLAGS just to be safe.

 Makefile:

  OPENSSL = /usr/local/ssl/bin/openssl
  TOR_OPENSSL_LIBS = /usr/local/ssl/lib/libssl.a
 /usr/local/ssl/lib/libcrypto.a

 Sebastian suggested to also compile libevent statically, but I'm not sure
 how: The
 option --with-libevent-dir wants me to specify a directory, whereas I only
 have
 libevent libraries directly inside /usr/lib.
 Also, is it on purpose that configure accepts both --with-openssl-
 dir=/usr/local/ssl
 and --with-openssl-dir=/usr/local/ssl/bin ?

 You can find me on IRC (nick "narr").

 ----
 Debian Lenny DomU with 2.6.18-6-xen-686 etch Kernel
 ~5MB/s bandwidth

 free -m (no tor running)
              total       used       free     shared    buffers     cached
 Mem:          1640       1625         15          0         14       1200
 -/+ buffers/cache:        410       1229
 Swap:         1023          0       1023


 [Automatically added by flyspray2trac: Operating System: Other Linux]

--

Comment(by arma):

 Is this a bug better suited for debian's bugtracker? It isn't getting much
 attention here.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1315#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

Prev by Author: [tor-bugs] Re: #1346 [Tor - Tor client]: Reachability Testing passes, yet Relay is marked as down by authorities
Next by Author: [tor-bugs] Re: #1258 [Tor - Relay]: Tor allows non-ASCII chars in contact line
Previous by thread: [tor-bugs] Re: #1346 [Tor - Tor client]: Reachability Testing passes, yet Relay is marked as down by authorities
Next by thread: [tor-bugs] Re: #1258 [Tor - Relay]: Tor allows non-ASCII chars in contact line
Index(es):
- Author
- Thread