I'm still unable to start or update moblock...I still get the following message:
E: /var/cache/apt/archives/moblock-nfq_0.8-39+gutsy_i386.deb: subprocess new pre-removal script returned error exit status 6
Help, please!
I'm still unable to start or update moblock...I still get the following message:
E: /var/cache/apt/archives/moblock-nfq_0.8-39+gutsy_i386.deb: subprocess new pre-removal script returned error exit status 6
Help, please!
Please post (if possible) the complete output of the moblock installation and your /var/log/moblock-control.log, please.
I guess you have the problem I first thought about in the previous cases: sometimes MoBlock simply fails to download the blocklists the first time which results in the exit code 6.
An "moblock-control update" should help then. Further I hope that you installed the new conf files when you were asked.
greets
jre
Please post your logfiles and output of commands wrapped in code tags:Co-author of PeerGuardian Linux (pgl). Maintainer of the pgl package repositories for Debian and Ubuntu.Code:[code]output[/code]
OK, I just fixed my problem.
What I did was purge Moblock-nfq from the computer, did the white listed the IP ports for internet, THEN finally fixed the white list IP's. It was blocking my router. To whitelist your router, go back to your moblock.conf file look for the WHITE_IP_OUT and copy your router IP address to allow communications with your router. Don't forget to do a moblock-control restart and reload.
Thx for the help guys, couldn't have done it without the forums =).
This is what I got when I tried to do the purge/reinstall suggested earlier:
After reading that, I checked the sources.list file, and it was still set to pull from the moblock feisty repositories (since I'd upgraded through Ubuntu as opposed to a fresh install). Changed the sources.list file, ran apt-get update and tried the purge/install again, still gave me the same error message. See below:Code:Do you want to continue? [Y/n/?] y Writing extended state information... Done Selecting previously deselected package moblock-nfq. (Reading database ... 212246 files and directories currently installed.) Preparing to replace moblock-nfq 0.8-32+feisty (using .../moblock-nfq_0.8-36+feisty_i386.deb) ... /usr/bin/moblock-control: line 92: [: too many arguments * Error 6: Check your VERBOSITY settings in /etc/moblock/moblock.conf. invoke-rc.d: initscript moblock-nfq, action "stop" failed. dpkg: warning - old pre-removal script returned error exit status 6 dpkg - trying script from the new package instead ... /usr/bin/moblock-control: line 92: [: too many arguments * Error 6: Check your VERBOSITY settings in /etc/moblock/moblock.conf. invoke-rc.d: initscript moblock-nfq, action "stop" failed. dpkg: error processing /var/cache/apt/archives/moblock-nfq_0.8-36+feisty_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 6 /usr/bin/moblock-control: line 92: [: too many arguments * Error 6: Check your VERBOSITY settings in /etc/moblock/moblock.conf. invoke-rc.d: initscript moblock-nfq, action "start" failed. dpkg: error while cleaning up: subprocess post-installation script returned error exit status 6 Errors were encountered while processing: /var/cache/apt/archives/moblock-nfq_0.8-36+feisty_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: dpkg: error processing moblock-nfq (--configure): Package is in a very bad inconsistent state - you should reinstall it before attempting configuration. Errors were encountered while processing: moblock-nfq Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Writing extended state information... Done Building tag database... Done
It gave the following message during both purges:Code:Do you want to continue? [Y/n/?] y Writing extended state information... Done Get:1 http://moblock-deb.sourceforge.net gutsy/main moblock-nfq 0.8-39+gutsy [43.6kB] Fetched 43.6kB in 1s (36.5kB/s) Selecting previously deselected package moblock-nfq. (Reading database ... 212246 files and directories currently installed.) Preparing to replace moblock-nfq 0.8-32+feisty (using .../moblock-nfq_0.8-39+gutsy_i386.deb) ... /usr/bin/moblock-control: line 92: [: too many arguments * Error 6: Check your VERBOSITY settings in /etc/moblock/moblock.conf. invoke-rc.d: initscript moblock-nfq, action "stop" failed. dpkg: warning - old pre-removal script returned error exit status 6 dpkg - trying script from the new package instead ... /usr/bin/moblock-control: line 92: [: too many arguments * Error 6: Check your VERBOSITY settings in /etc/moblock/moblock.conf. invoke-rc.d: initscript moblock-nfq, action "stop" failed. dpkg: error processing /var/cache/apt/archives/moblock-nfq_0.8-39+gutsy_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 6 /usr/bin/moblock-control: line 92: [: too many arguments * Error 6: Check your VERBOSITY settings in /etc/moblock/moblock.conf. invoke-rc.d: initscript moblock-nfq, action "start" failed. dpkg: error while cleaning up: subprocess post-installation script returned error exit status 6 Errors were encountered while processing: /var/cache/apt/archives/moblock-nfq_0.8-39+gutsy_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: dpkg: error processing moblock-nfq (--configure): Package is in a very bad inconsistent state - you should reinstall it before attempting configuration. Errors were encountered while processing: moblock-nfq Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Writing extended state information... Done Building tag database... Done
To be honest, I don't remember which option I chose when prompted regarding the conf files, since this has been ongoing for several weeks now. Any help that you could offer would be greatly appreciated.Code:dpkg: error processing moblock-nfq (--purge): Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. Errors were encountered while processing: moblock-nfq E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover:
Last edited by the_unexpected; December 23rd, 2007 at 02:26 AM. Reason: Typos.
Hi,
I'm having siilar problems as above. If i try and purge i get:
If i try to reinstall i get:Code:dpkg: error processing moblock-nfq (--purge): Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. Errors were encountered while processing: moblock-nfq E: Sub-process /usr/bin/dpkg returned an error code (1)
I'm unable to remove or reinstall through synaptic either. The problem also stops me from installing any other software. Everytime i try it seems that synaptic is trying to upgrade moblock which it has problems doing.Code:* MoBlock: /etc/moblock/moblock.conf not installed. invoke-rc.d: initscript moblock-nfq, action "stop" failed. dpkg: warning - old pre-removal script returned error exit status 6 dpkg - trying script from the new package instead ... * MoBlock: /etc/moblock/moblock.conf not installed. invoke-rc.d: initscript moblock-nfq, action "stop" failed. dpkg: error processing /var/cache/apt/archives/moblock-nfq_0.8-39+feisty_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 6 * MoBlock: /etc/moblock/moblock.conf not installed. invoke-rc.d: initscript moblock-nfq, action "start" failed. dpkg: error while cleaning up: subprocess post-installation script returned error exit status 6 Errors were encountered while processing: /var/cache/apt/archives/moblock-nfq_0.8-39+feisty_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
Any help would obviosuly be appreciated.
I just did a fresh Gutsy install and for some reason moblock is blocking everything. I have gotten http and https unblocked as it says in the how-to, but for some reason anything outside of that is being blocked. I can't get updates or use Synaptic at all while moblock is running.
How can I fix this? I never had this issue in Feisty and I never had it in Gutsy when I first started running it. It just seems to be an issue with this install.
Any help is greatly appreciated. I don't like running my box with no IP blocker.
OFFTOPIC:
I think that the owners of the Moblock project should talk to some forum admins and get a corner of their own such as one in the 3rd party sub-forums.
Then you should create something like 2 sub-sub-forums. One for dealing with problems that arises from upgrades. And another one for learning how to use the complicated functions inside the program.
It seems like the same kind of questions comes back again and again. The mixing of these 2 issues makes it difficult to read through 100 threads when searching for answers that have already been answered before.
That's my 2 cents.
I have the same problem, i just installed gutsy - fresh install and moblock is blocking everything. Incidentially i have another gutsy install on my laptop and moblock is working just fine, so... i copied /etc/moblock onto my fresh install of gutsy. But to no avail, it still is blocking everything - (except google searches, can't click on results though). To make matters even more confusing both machines tell me moblock is version 0.8.
OK, fixed my problem. Didnt' whitelist my router, only the http ports. i whitelisted my router in the next section and all is well
Last edited by empthollow; December 25th, 2007 at 05:47 AM.
if ignorance is bliss, where are all the happy people
Jeremy
@the_unexpected and darles: Your moblock.conf is broken (old version) or non existent. So manually install a new one from the current package:
Darles, replace gutsy with feisty in the second line of the above code. Of course you both have to insert your real {YOURLOGIN}.Code:mkdir /home/{YOURLOGIN}/moblock_0.8-39 dpkg -X /var/cache/apt/archives/moblock-nfq_0.8-39+gutsy_i386.deb /home/{YOURLOGIN}/moblock_0.8-39 sudo cp /home/{YOURLOGIN}/moblock_0.8-39/etc/moblock/moblock.conf /etc/moblock/moblock.conf
So whitelisting http and https works? Then you can simply whitelist other protocols or IPs. Check the log (tail -f /var/log/moblock.log) to see what is blocked.
If you have more severe problems: Please post "moblock-control status", I guess you have installed additional firewall software (this will cause problems). Further you need to be more concrete what is not working (which IPs are blocked (see logfile)? On which ports (which application wanted to contact them? or use "whireshark" to analyze the traffic).
Maybe a good idea but I guess people would still post here. So next to development I prefer to improve the HOWTO so that it is easier to point people there.
Please post your logfiles and output of commands wrapped in code tags:Co-author of PeerGuardian Linux (pgl). Maintainer of the pgl package repositories for Debian and Ubuntu.Code:[code]output[/code]
Bookmarks