Results 1 to 9 of 9

Thread: Moblock and removing.

  1. #1
    Join Date
    Sep 2007
    Beans
    12

    Moblock and removing.

    Hello i installed Moblock but now every time i try to use any aptitude function it runs moblock and i get a

    Code:
    tail -f /var/log/moblock-control.log
    Stopping MoBlock                                                         [fail]
    2008-05-30 02:15:03 JST End: moblock-control stop
    2008-05-30 11:44:06 JST Begin: moblock-control start
     * Error 7: Missing file /etc/moblock/guarding.p2p.
     * Check the BLOCKLIST settings in /etc/moblock/moblock.conf.
     * Also check /etc/default/moblock.
    2008-05-30 11:48:32 JST Begin: moblock-control reload
    Building blocklist *  Error 9: There are no blocklists! Aborting.
    2008-05-30 11:48:32 JST Begin: moblock-control update
     * Error 171: No connection to www.bluetack.co.uk. Aborting!
    at the end of the aptitude process.

    Due to this error i cant even uninstall moblock.

    Does anyone have any idea on how i can uninstall moblock ?

  2. #2
    Join Date
    Mar 2008
    Location
    City of Pines
    Beans
    3,585

    Re: Moblock and removing.

    Try relating to this Moblock Uninstall Error thread.
    Steady movement is more important than speed, much of the time. So long as there is a regular progression of Stimuli to get your mental hooks into, there is room for lateral movement. Once this begins, its rate is a matter of discretion.

  3. #3
    Join Date
    Sep 2007
    Beans
    12

    Re: Moblock and removing.

    Ive had a look at that, but none of that seems to help me.

    It seems to happen because when i do moblock-control stop. it fails. And i dont have a clue why it fails :\

  4. #4
    Join Date
    Mar 2008
    Location
    City of Pines
    Beans
    3,585

    Re: Moblock and removing.

    Quote Originally Posted by schnoodles View Post
    Ive had a look at that, but none of that seems to help me.

    It seems to happen because when i do moblock-control stop. it fails. And i dont have a clue why it fails :\
    Did you try using sudo?

    Code:

    Code:
    sudo moblock-control stop
    Steady movement is more important than speed, much of the time. So long as there is a regular progression of Stimuli to get your mental hooks into, there is room for lateral movement. Once this begins, its rate is a matter of discretion.

  5. #5
    Join Date
    Sep 2007
    Beans
    12

    Re: Moblock and removing.

    Yes i did try and use sudo. that is why i find it so wierd that it fails.

  6. #6
    Join Date
    Sep 2007
    Beans
    12

    Re: Moblock and removing.

    Code:
    2008-05-30 21:37:38 JST Begin: moblock-control stop
    Deleting iptablesiptables v1.3.8: Couldn't load target `moblock_in':/lib/iptables/libipt_moblock_in.so: cannot open shared object file: No such file or directory
    
    Try `iptables -h' or 'iptables --help' for more information.
    iptables v1.3.8: Couldn't load target `moblock_out':/lib/iptables/libipt_moblock_out.so: cannot open shared object file: No such file or directory
    
    Try `iptables -h' or 'iptables --help' for more information.
    iptables v1.3.8: Couldn't load target `moblock_fw':/lib/iptables/libipt_moblock_fw.so: cannot open shared object file: No such file or directory
    
    Try `iptables -h' or 'iptables --help' for more information.
    iptables: No chain/target/match by that name
    iptables: Bad rule (does a matching rule exist in that chain?)
    iptables: No chain/target/match by that name
    iptables: No chain/target/match by that name
    iptables: No chain/target/match by that name
    iptables: No chain/target/match by that name
    iptables: No chain/target/match by that name
    iptables: No chain/target/match by that name
     * Some iptables rules could not be deleted. The most common reason for this is
     * that they did not exist. If MoBlock was not running this is the correct
     * behaviour. But if MoBlock was running there is some problem. Make sure that
     * MoBlock inserts its iptables rules correctly and that other software, e.g.
     * firewall applications, don't delete them. Make sure that MoBlock is started
     * after other firewall applications.
    Stopping MoBlock                                                        [fail]
    2008-05-30 21:37:38 JST End: moblock-control stop
    That seems to happen when i say stop. I dont seem to be able to find the moblock_*.so files and i cant seem to find them :\

  7. #7
    Join Date
    Jan 2007
    Beans
    772

    Re: Moblock and removing.

    Quote Originally Posted by schnoodles View Post
    I dont seem to be able to find the moblock_*.so files and i cant seem to find them :\
    This jsut relates to the iptables rules, but aren't any files.

    Indeed not very informative why it fails to stop.

    What do you get on moblock-control status and what on start (console output and logfile)?
    Which version do you use (dpkg --list moblock)?

    Try as a quick fix for aptitude (but you still won't have a working moblock):
    Code:
    sudo touch /etc/moblock/guarding.p2p
    This creates an empty blocklist file.
    Please post your logfiles and output of commands wrapped in code tags:
    Code:
    [code]output[/code]
    Co-author of PeerGuardian Linux (pgl). Maintainer of the pgl package repositories for Debian and Ubuntu.

  8. #8
    Join Date
    Sep 2007
    Beans
    12

    Re: Moblock and removing.

    Hey here are my results i get back

    josh@schnootop:~/workspace$ sudo moblock-control status
    [sudo] password for josh:
    Current iptables rules (this may take awhile):

    Chain INPUT (policy ACCEPT 25676 packets, 25M bytes)
    pkts bytes target prot opt in out source destination

    Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
    pkts bytes target prot opt in out source destination

    Chain OUTPUT (policy ACCEPT 23938 packets, 2754K bytes)
    pkts bytes target prot opt in out source destination

    Please check if the above printed iptables rules are correct!

    * moblock is not running.
    2008-05-31 15:28:34 JST Begin: moblock-control start
    * Error 7: Missing file /etc/moblock/guarding.p2p.
    * Check the BLOCKLIST settings in /etc/moblock/moblock.conf.
    * Also check /etc/default/moblock.
    Although, touching that .p2p file seemed to make it all work pretty nicely. Lets me delete the whole of moblock and also start and stop it. Looked like that was my only problem not having that file.

    Thankyou jre

  9. #9
    Join Date
    Jan 2007
    Beans
    772

    Re: Moblock and removing.

    Quote Originally Posted by schnoodles View Post
    Looked like that was my only problem not having that file.
    I still fear that there was some bug because the stop failed. For now I changed moblock-control to do only really necessary tests for valid variables when it stops. This way we avoid an refusal to stop if moblock is misconfigured.

    Glad I could help anyway
    jre
    Please post your logfiles and output of commands wrapped in code tags:
    Code:
    [code]output[/code]
    Co-author of PeerGuardian Linux (pgl). Maintainer of the pgl package repositories for Debian and Ubuntu.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •