search

noahd1 / oink

Log parser to identify actions which significantly increase VM heap size
MIT License
1.18k stars 71 forks source link

invalid byte sequence #13

Open thepixelmonk opened 12 years ago

thepixelmonk commented 12 years ago

[root@vps-626-1 thirsty]# bundle exec oink log ---- MEMORY THRESHOLD ---- THRESHOLD: 75 MB /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

'

mhenrixon commented 12 years ago

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 12 years ago

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?

mhenrixon commented 12 years ago

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 9 years ago

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

softmonkeyjapan commented 8 years ago

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