invalid byte sequence #13

nbolt opened this Issue Oct 5, 2011 · 5 comments


None yet

5 participants

nbolt commented Oct 5, 2011

[root@vps-626-1 thirsty]# bundle exec oink log
/usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:20:in =~': invalid byte sequence in UTF-8 (ArgumentError) from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:20:inblock (2 levels) in print'
from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:16:in each_line' from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:16:inblock in print'
from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:15:in each' from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/reports/memory_usage_report.rb:15:inprint'
from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/lib/oink/cli.rb:68:in process' from /usr/lib/ruby/gems/1.9.1/gems/oink-0.9.3/bin/oink:4:in<top (required)>'
from /usr/lib/ruby/gems/1.9.1/bin/oink:19:in load' from /usr/lib/ruby/gems/1.9.1/bin/oink:19:in



I don't have a problem with ruby 1.9.3 but with 1.9.2 on ubuntu I can confirm this is a problem

noahd1 commented Jan 20, 2012

I'm guessing there's some characters in the log file that oink doesn't handle gracefully. Can you bisect the log file it's parsing to see if you can determine where it's choking?


The log file was completely hmm fudged up so I just emptied it and configured the logging according to recommendation and it's fine now.

pavelz commented Jun 23, 2015

i have russian characters in the log file, oink breaks in the same place


Experiencing the same problem using Ruby 2.2.1p85 and Ubuntu 14.04. Did someone found a workaround for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment