# Cannot read beyond the end of buffer on Opteron (and yes, pa

**URL:** <https://www.ruby-forum.com/t/cannot-read-beyond-the-end-of-buffer-on-opteron-and-yes-pa/85463>\
**Category:** Ruby\
**Created:** [February 13, 2007, 9:22pm UTC](https://www.ruby-forum.com/t/cannot-read-beyond-the-end-of-buffer-on-opteron-and-yes-pa/85463 "2007-02-13T21:22:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jake\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/4491bb/32.png) [@Jake\_C](https://www.ruby-forum.com/u/Jake_C)\
**Post date:** [February 13, 2007, 9:22pm UTC](https://www.ruby-forum.com/t/cannot-read-beyond-the-end-of-buffer-on-opteron-and-yes-pa/85463/1 "2007-02-13T21:22:49Z")

</div>

Hi guys.

I’m trying to get Ruby working properly on a Opteron (Ubuntu LTS server)  
system. It’s actually a Rails project, but I believe my problem to be  
specifically related to Ruby and not necessarily Rails.

When I run “rake migrate”, I get the following:

rake aborted!  
Buffer::EOF: cannot read beyond the end of buffer: SELECT  
a.attname, format\_type(a.atttypid, a.atttypmod), d.adsrc, a.attnotnull  
FROM pg\_attribute a LEFT JOIN pg\_attrdef d  
ON a.attrelid = d.adrelid AND a.attnum = d.adnum  
WHERE a.attrelid = ‘departments’::regclass  
AND a.attnum \> 0 AND NOT a.attisdropped  
ORDER BY a.attnum  
/usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active\_record/connection\_adapters/abstract\_adapter.rb:128:in  
`log' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active_record/connection_adapters/postgresql_adapter.rb:142:in `query’  
/usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active\_record/connection\_adapters/postgresql\_adapter.rb:528:in  
`column_definitions' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active_record/connection_adapters/postgresql_adapter.rb:223:in `columns’  
/usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active\_record/schema\_dumper.rb:68:in  
`table' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active_record/schema_dumper.rb:63:in `tables’  
/usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active\_record/schema\_dumper.rb:54:in  
`tables' /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active_record/schema_dumper.rb:23:in `dump’  
/usr/lib/ruby/gems/1.8/gems/activerecord-1.15.2/lib/active\_record/schema\_dumper.rb:17:in  
`dump' /usr/lib/ruby/gems/1.8/gems/rails-1.2.2/lib/tasks/databases.rake:24 /usr/lib/ruby/gems/1.8/gems/rails-1.2.2/lib/tasks/databases.rake:23 /usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute’  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:357:in `invoke’  
/usr/lib/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in `invoke’  
/usr/lib/ruby/gems/1.8/gems/rails-1.2.2/lib/tasks/databases.rake:5  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute’  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:357:in `invoke' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize’  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:364:in `invoke\_prerequisites’  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:999:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:363:in `invoke\_prerequisites’  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:356:in `invoke' /usr/lib/ruby/1.8/thread.rb:135:in `synchronize’  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `run’  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `run’  
/usr/lib/ruby/gems/1.8/gems/rake-0.7.1/bin/rake:7  
/usr/bin/rake:16

I did some research and found that this has been a known issue on 64bit  
systems, and found the patch here (  
[http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/180119](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/180119)). I  
then  
downloaded Ruby 1.8.5, verified that pack.c was already patched, and  
compiled. It compiled and installed just fine, but I still get the same  
error.

Can someone please tell me what I might be doing wrong?

Thanks!  
Jake

---

<div class="post-metadata">

**Author:** ![Jake\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/4491bb/32.png) [@Jake\_C](https://www.ruby-forum.com/u/Jake_C)\
**Post date:** [February 14, 2007, 4:04am UTC](https://www.ruby-forum.com/t/cannot-read-beyond-the-end-of-buffer-on-opteron-and-yes-pa/85463/2 "2007-02-14T04:04:29Z")

</div>

On 2/13/07, Jake C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> I’m trying to get Ruby working properly on a Opteron (Ubuntu LTS server)  
> system. It’s actually a Rails project, but I believe my problem to be  
> specifically related to Ruby and not necessarily Rails.

Responding to myself here…it was actually a problem with left over  
files  
from the 1.8.2 deb packages I had installed previously. Once i blew  
those  
completely away with dpkg --purge, I was good to go. Strange but true.

Thanks,  
Jake