Better handling HellaNZB dependencies
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| LottaNZB |
Fix Released
|
Wishlist
|
Severin H | ||
Bug Description
I added some server and LottaNZB failed to start.
~$ lottanzb
INFO Starting LottaNZB 0.2 using Python 2.5.2.
INFO HellaNZB output: hellanzb v0.13 (config = /home/vudu/
INFO Started HellaNZB daemon.
INFO Connected to the HellaNZB daemon.
WARNING Could not get an update from the HellaNZB daemon, is it (still) running?
WARNING Could not get an update from the HellaNZB daemon, is it (still) running?
(...)
WARNING Could not get an update from the HellaNZB daemon, is it (still) running?
INFO HellaNZB output: Unable to connect to XMLRPC server,
INFO HellaNZB output: error: Connection was refused by other side: 111: Connection refused.
INFO HellaNZB output: The hellanzb queue daemon @ http://
INFO HellaNZB daemon stopped.
but then I ran hellanzb:
$ hellanzb -c /home/vudu/
hellanzb v0.13 (config = /home/vudu/
Unable to use SSL for server: Secure UsenetServer
pyOpenSSL is not installed: No module named OpenSSL
I dunno how easy it is to implement (maybe reading HellaNZB's log) but it would be good if LottaNZB could warn about this kind of problems.
By the way, I see that it is possible to change the hellanzb_launcher on the .xml file but could it be added to the preferences window? I use "tsocks hellanzb" to socksify hellanzb :)
Related branches
- No reviews requested
| Severin H (severinh) wrote | #1 |
| Changed in lottanzb: | |
| assignee: | nobody → lottanzb |
| importance: | Undecided → Wishlist |
| milestone: | none → 0.2.1 |
| status: | New → In Progress |
| status: | In Progress → Confirmed |
| Changed in lottanzb: | |
| assignee: | lottanzb → lantash |
| status: | Confirmed → In Progress |
| VuDu (vudu-curse) wrote | #2 |
| Changed in lottanzb: | |
| status: | In Progress → Fix Committed |
| Changed in lottanzb: | |
| milestone: | 0.2.1 → 0.3 |
| Changed in lottanzb: | |
| status: | Fix Committed → Fix Released |
Hi VuDu,
thanks for sharing your ideas with us! The next major version of LottaNZB is going to ship with a new core, which _should_ be able to handle such HellaNZB problems and inform the user, but this is still work in progress.
I think it would be a good idea to check if the OpenSSL module can be imported when the user clicks on the SSL checkbox. If the module isn't available, a tiny confirm window should pop up, where the user is asked to install the required package or download without SSL encryption.
As for the hellanzb_launcher preference: This "hidden" option might indeed deserve a visual input box.