After I finally killed the hung process, I saw the following, which probably
is all the known bug, but I'll send it just in case:
net-responsibility-report[15216]: The following exception
(SQLite3::BusyException) is caused by a known bug. If you know how to fix
it, do tell! Otherwise, you can safely ignore it (I hope).
net-responsibility-report[15216]: /usr/lib/ruby/1.8/sqlite3/errors.rb:94:in
'check': Unable to close due to unfinalised statements
(SQLite3::BusyException)
net-responsibility-report[15216]: => from
/usr/lib/ruby/1.8/sqlite3/database.rb:154:in 'close'
net-responsibility-report[15216]: => from
/usr/local/bin/net-responsibility-report:114:in 'initialize'
net-responsibility-report[15216]: => from
/usr/local/bin/net-responsibility-report:137:in 'new'
net-responsibility-report[15216]: => from
/usr/local/bin/net-responsibility-report:137
net-responsibility-report[15216]: Time for this report: 22964.071385
/usr/lib/ruby/1.8/sqlite3/statement.rb:252:in `must_be_open!': cannot use a
closed statement (SQLite3::Exception)
from /usr/lib/ruby/1.8/sqlite3/statement.rb:77:in `close'
from /usr/lib/ruby/1.8/sqlite3/resultset.rb:170:in `close'
from /usr/share/net-responsibility/lib/modules/db.rb:330:in
`delete_log_entries'
from /usr/share/net-responsibility/lib/modules/db.rb:161:in
`rotate_log'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `each_slice'
from /usr/share/net-responsibility/lib/modules/db.rb:161:in `each'
from /usr/share/net-responsibility/lib/modules/db.rb:161:in
`each_slice'
from /usr/share/net-responsibility/lib/modules/db.rb:161:in
`rotate_log'
from /usr/share/net-responsibility/lib/modules/db.rb:158:in `each'
from /usr/share/net-responsibility/lib/modules/db.rb:158:in
`rotate_log'
from /usr/local/bin/net-responsibility-report:109:in `initialize'
from /usr/local/bin/net-responsibility-report:137:in `new'
from /usr/local/bin/net-responsibility-report:137
Thanks for your help.
Martin
On 16 March 2010 18:42, Roggan <email address hidden> wrote:
> Your right, that's the problem!
> Rotating log actually means clearing history.
>
> Try to rename /var/log/net-responsibility.log to
> /var/log/net-responsibility.log.bak or something so you can change back
> later. Then restart net-responsibility.
> See if the problem remains, in that case we have to look closer to it.
>
> --
> Log does not clear
> https://bugs.launchpad.net/bugs/538443
> You received this bug notification because you are a direct subscriber
> of the bug.
>
I think that has fixed it.
After I finally killed the hung process, I saw the following, which probably
is all the known bug, but I'll send it just in case:
net-responsibil ity-report[ 15216]: The following exception :BusyException) is caused by a known bug. If you know how to fix ity-report[ 15216]: /usr/lib/ ruby/1. 8/sqlite3/ errors. rb:94:in :BusyException) ity-report[ 15216]: => from ruby/1. 8/sqlite3/ database. rb:154: in 'close' ity-report[ 15216]: => from bin/net- responsibility- report: 114:in 'initialize' ity-report[ 15216]: => from bin/net- responsibility- report: 137:in 'new' ity-report[ 15216]: => from bin/net- responsibility- report: 137 ity-report[ 15216]: Time for this report: 22964.071385 ruby/1. 8/sqlite3/ statement. rb:252: in `must_be_open!': cannot use a :Exception) ruby/1. 8/sqlite3/ statement. rb:77:in `close' ruby/1. 8/sqlite3/ resultset. rb:170: in `close' net-responsibil ity/lib/ modules/ db.rb:330: in log_entries' net-responsibil ity/lib/ modules/ db.rb:161: in ruby/1. 8/rubygems/ custom_ require. rb:27:in `each_slice' net-responsibil ity/lib/ modules/ db.rb:161: in `each' net-responsibil ity/lib/ modules/ db.rb:161: in net-responsibil ity/lib/ modules/ db.rb:161: in net-responsibil ity/lib/ modules/ db.rb:158: in `each' net-responsibil ity/lib/ modules/ db.rb:158: in bin/net- responsibility- report: 109:in `initialize' bin/net- responsibility- report: 137:in `new' bin/net- responsibility- report: 137
(SQLite3:
it, do tell! Otherwise, you can safely ignore it (I hope).
net-responsibil
'check': Unable to close due to unfinalised statements
(SQLite3:
net-responsibil
/usr/lib/
net-responsibil
/usr/local/
net-responsibil
/usr/local/
net-responsibil
/usr/local/
net-responsibil
/usr/lib/
closed statement (SQLite3:
from /usr/lib/
from /usr/lib/
from /usr/share/
`delete_
from /usr/share/
`rotate_log'
from /usr/lib/
from /usr/share/
from /usr/share/
`each_slice'
from /usr/share/
`rotate_log'
from /usr/share/
from /usr/share/
`rotate_log'
from /usr/local/
from /usr/local/
from /usr/local/
Thanks for your help.
Martin
On 16 March 2010 18:42, Roggan <email address hidden> wrote:
> Your right, that's the problem! net-responsibil ity.log to net-responsibil ity.log. bak or something so you can change back /bugs.launchpad .net/bugs/ 538443
> Rotating log actually means clearing history.
>
> Try to rename /var/log/
> /var/log/
> later. Then restart net-responsibility.
> See if the problem remains, in that case we have to look closer to it.
>
> --
> Log does not clear
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>