Cannot install Net Responsibility on 64-bit Lucid Lynx

[nebcanuck]

I have run the scripts from source in order to create a 64-bit .deb, however the installer comes up stating "Wrong Architecture: x86_64".

The same message is present when trying to install the 32-bit version, but that's expected as I am running the 64-bit edition of Ubuntu.

[Rohn Clipperton (arrsea)]

I'm not sure whether NR has been tested on Lucid yet, so thanks for the report and we'll see what we can do.

Did you try the 64-bit .deb on the NR download page? I can't guarantee that'd work, but it might be worth a try. (http://www.netresponsibility.com/download.php).

Thanks for reporting,

Rohn Clipton

[nebcanuck (nebcanuck)]

The download worked, actually. Thanks.

Is that the alpha version? I was running Net Responsibility Alpha on a 32-bit installation before, and it had stopped sending reports after the first one.

[nebcanuck (nebcanuck)]

The 64-bit version of Net Responsibility does not seem to be running on my computer after having installed it. The configuration program works, but the program itself never seems to be running.

Again, running 64-bit edition of Lucid Lynx, with all packages up-to-date.

[Roggan (roggan87)]

Hi!
The 64-bit version on the website is not the latest 2.0 alpha version. The right thing to do would be to create a new 64-bit package from source, but I. not sure why it's not working.

Did the 32-bit version work for you, except for the automatic reports? That bug is reported, and worked on.
Thanks for your patience!

[nebcanuck (nebcanuck)]

The 32-bit version seemed to be running fine back when I was on a 32-bit installation. Naturally, it won't install on the 64-bit version of Ubuntu.

I will keep on working to install it from source, and see if I can find the problem.

[Martin (cyderia8530)]

I have just built a 2.0a .deb file from source on 64-bit Karmic. I run into the same problem as nebcanuck. It seems to be a 64 bit problem rather than a specifically Lucid problem. I've no idea at the moment what the problem is.

[Martin (cyderia8530)]

Okay, this is how I got 2.0a to work on 64-bit Karmic. I built the .deb at the command line as per instructions and then tried to install it from the command line using dpkg. This was my terminal output:

appleseed@appleseed-E:~/net-responsibility-2.0a/linux-2.6-x86_64$ sudo dpkg -i netresponsibility-2.0a-linux-2.6-x86_64.deb
dpkg: error processing netresponsibility-2.0a-linux-2.6-x86_64.deb (--install):
 package architecture (x86_64) does not match system (amd64)
Errors were encountered while processing:
 netresponsibility-2.0a-linux-2.6-x86_64.deb

It didn't like the X86_64 architecture it wanted amd64. To fix this I edited the "make_deb.sh" shell script. I added the option "-a amd64" option to the epm command line. I then ran the "make_deb.sh" shell script again and created a new .deb file. This new .deb file installed just fine, no warnings about X86_64 being the wrong architecture. Net Responsibility now works just fine on my 64-bit installation with manual reporting. No automatic reports just yet, but that's a known bug.

[nebcanuck (nebcanuck)]

Installed for me, too. When I attempt to generate a report using sudo net-responsibility-report however, I get this output:

net-responsibility-report[3068]: Generating report
net-responsibility-report[3068]: 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[3068]: /usr/lib/ruby/1.8/sqlite3/errors.rb:62:in 'check': unable to close due to unfinalised statements (SQLite3::BusyException)
net-responsibility-report[3068]: => from /usr/lib/ruby/1.8/sqlite3/database.rb:121:in 'close'
net-responsibility-report[3068]: => from /usr/local/bin/net-responsibility-report:103:in 'initialize'
net-responsibility-report[3068]: => from /usr/local/bin/net-responsibility-report:119:in 'new'
net-responsibility-report[3068]: => from /usr/local/bin/net-responsibility-report:119
/usr/lib/ruby/1.8/sqlite3/errors.rb:62:in `check': database is locked (SQLite3::BusyException)
 from /usr/lib/ruby/1.8/sqlite3/resultset.rb:56:in `check'
 from /usr/lib/ruby/1.8/sqlite3/resultset.rb:48:in `commence'
 from /usr/lib/ruby/1.8/sqlite3/resultset.rb:38:in `initialize'
 from /usr/lib/ruby/1.8/sqlite3/statement.rb:135:in `new'
 from /usr/lib/ruby/1.8/sqlite3/statement.rb:135:in `execute'
 from /usr/lib/ruby/1.8/sqlite3/database.rb:245:in `query'
 from /usr/share/net-responsibility/lib/modules/db.rb:196:in `get_paths'
 from /usr/share/net-responsibility/lib/report.rb:57:in `url_report'
 from /usr/share/net-responsibility/lib/report.rb:55:in `each'
 from /usr/share/net-responsibility/lib/report.rb:55:in `url_report'
 from /usr/share/net-responsibility/lib/report.rb:46:in `each'
 from /usr/share/net-responsibility/lib/report.rb:46:in `url_report'
 from /usr/share/net-responsibility/lib/report.rb:92:in `full_report'
 from /usr/local/bin/net-responsibility-report:88:in `initialize'
 from /usr/local/bin/net-responsibility-report:119:in `new'
 from /usr/local/bin/net-responsibility-report:119

It seems to be a database lock? Is this a known bug?

[Roggan (roggan87)]

Glad you got it to work!

Unfortunately the database lock is a known bug.
Usually you can run the command again successfully after this happens.

This is something we're working on, but it's really annoying!

[nebcanuck (nebcanuck)]

Okay, thanks!

As it is, that patch fixed the install for the source, so I guess this bug is fixed!

[Rohn Clipperton (arrsea)]

So this bug is fixed? Great! I guess I'll mark it as fixed!