Go Back   Phoenix Labs > Projects > PeerGuardian Linux
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
Thread Tools Display Modes

 
Old 08-28-2009, 11:01 AM   #1
xaeniac

Member
Join Date: Aug 2009
Posts: 4
Default moblock will not start Ubuntu 9.04

Moblock will not start. The error I get is
sudo blockcontrol start
* Starting IP block daemon moblock [fail]
Copy of Blockcontrol.conf

Code:
# blockcontrol.conf - configuration file for blockcontrol

# This file is sourced by a shell script. Any line which starts with a # (hash)
# is a comment and is ignored. If you set the same variable several times,
# then only the last line will be used.

# Refer to blockcontrol.defaults (/usr/lib/blockcontrol/blockcontrol.defaults)
# for the complete set of possible configuration variables with comments.

# Do a "blockcontrol restart" (sometimes even "reload" is enough) when you have
# edited this file.



WHITE_TCP_OUT="http https"
INIT="0"
WHITE_TCP_IN=""
xaeniac is offline   Reply With Quote

 
Old 08-29-2009, 08:11 AM   #2
jre

Senior Member
Join Date: Sep 2005
Posts: 588
Default Re: moblock will not start Ubuntu 9.04

Please check /var/log/blockcontrol.log.

Probably "blockcontrol show_config" and "dpkg -l moblock blockcontrol lsb-base" might help, too.
__________________
Code:
Please post your logfiles and output of commands wrapped in
[ CODE ] tags. You find them in the advanced editing mode: #
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.
jre is offline   Reply With Quote

 
Old 08-29-2009, 10:19 AM   #3
xaeniac

Member
Join Date: Aug 2009
Posts: 4
Default Re: moblock will not start Ubuntu 9.04

var/log/blockcontrol.log
Code:
2009-08-29 08:56:02 AM CDT Begin: blockcontrol restart
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ....
Building blocklist... .
Inserting iptables ...
Allowing inbound LAN traffic for 192.168.1.129 with subnetmask 255.255.255.0.
Allowing outbound LAN traffic for 192.168.1.129 with subnetmask 255.255.255.0.
Allowing forwarded LAN traffic for 192.168.1.129 with subnetmask 255.255.255.0.
Allowing outbound traffic to DNS server 192.168.1.1.
Allowing forwarded traffic to DNS server 192.168.1.1.
Allowing loopback traffic.
.
Starting moblock ....
Starting blockcontrol.wd ....
2009-08-29 08:56:02 AM CDT End: blockcontrol restart
2009-08-29 09:01:02 AM CDT Begin: blockcontrol restart
Stopping blockcontrol.wd.
Deleting iptables ...
.
Stopping moblock ... failed!
Problematic daemon status: 1
moblock is not running. ... failed!
2009-08-29 09:02:01 AM CDT Begin: blockcontrol restart
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ... failed!
Problematic daemon status: 1
moblock is not running. ... failed!
2009-08-29 09:09:53 AM CDT Begin: blockcontrol restart
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ...
blockcontrol show_config
Code:
bash: /var/log/blockcontrol.log: Permission denied
xaeniac@xaeniac-laptop:~$ blockcontrol show_config
blockcontrol current settings:
ACCEPT="1"
ACCEPT_MARK="20"
ALLOW_FW=""
ALLOW_IN="/etc/blockcontrol/allow.p2p"
ALLOW_OUT="/etc/blockcontrol/allow.p2p"
BLOCKLIST_FORMAT="p"
BLOCKLISTS_DIR="/var/spool/blockcontrol"
BLOCKLISTS_LIST="/etc/blockcontrol/blocklists.list"
CONTROL_CONF="/etc/blockcontrol/blockcontrol.conf"
CONTROL_LIB="/usr/lib/blockcontrol/blockcontrol.lib"
CONTROL_LOG="/var/log/blockcontrol.log"
CONTROL_NAME="blockcontrol"
CONTROL_SCRIPT="/usr/bin/blockcontrol"
CRON="1"
CRON_MAILTO="root"
CUSTOM_DAEMON_OPTS=""
DAEMON="/usr/bin/moblock"
DAEMON_LOG="/var/log/moblock.log"
DESC="IP block daemon"
E_BADARGS="2"
E_BLOCKLIST="9"
E_CONFIG="6"
E_IPTABLES="8"
E_NETWORK_DOWN="171"
E_NOTROOT="4"
E_XBIN="5"
E_XCD="66"
E_XEXTERNAL="170"
E_XFILE="7"
INIT="0"
IP_REMOVE=""
IPTABLES_ACTIVATION="1"
IPTABLES_CUSTOM_DIR="/etc/blockcontrol"
IPTABLES_SETTINGS="1"
IPTABLES_TARGET="NFQUEUE"
IPTABLES_TARGET_WHITELISTING="RETURN"
LOG_IPTABLES=""
LOG_SYSLOG="0"
LOG_TIMESTAMP="1"
LSB=""
MASTER_BLOCKLIST_DIR="/var/lib/blockcontrol"
MD5SUM_FILE="/var/spool/blockcontrol/MD5SUM"
NAME="moblock"
NFQUEUE_NUMBER="92"
NICE_LEVEL="5"
PATH="/usr/bin:/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin"
PIDFILE="/var/run/moblock.pid"
REJECT="1"
REJECT_FW="DROP"
REJECT_IN="DROP"
REJECT_MARK="10"
REJECT_OUT="REJECT"
STATFILE="/var/log/MoBlock.stats"
STDIFS=" "
TESTHOST="iblocklist.com"
VERBOSITY="1"
VERSION="1.6"
WD="1"
WD_NICE="19"
WD_PATHNAME="/usr/bin/blockcontrol.wd"
WD_PID="/var/run/blockcontrol.wd.pid"
WD_SLEEP="300"
WGET_OPTS="wget -q -t 5 -T 120 -w 5 --user-agent=blockcontrol/1.6"
WHITE_IP_FORWARD=""
WHITE_IP_IN=""
WHITE_IP_OUT=""
WHITE_LOCAL="1"
WHITE_TCP_FORWARD=""
WHITE_TCP_IN=""
WHITE_TCP_OUT="http https"
WHITE_UDP_FORWARD=""
WHITE_UDP_IN=""
WHITE_UDP_OUT=""

Using internal LSB init-functions.
Using start-stop-daemon.

The following blocklists are configured to be used:
http://list.iblocklist.com/?list=ijfqtofzixtwayqovmxn
http://list.iblocklist.com/?list=ecqbsykllnadihkdirsh
http://list.iblocklist.com/?list=jcjfaxgyyshvdbceroxf
http://list.iblocklist.com/?list=pfefqteoxlfzopecdtyw
http://list.iblocklist.com/?list=tbnuqfclfkemqivekikv
http://list.iblocklist.com/?list=ewqglwibdgjttwttrinl
http://list.iblocklist.com/?list=bt_proxy
http://list.iblocklist.com/?list=bt_dshield
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ 
xaeniac@xaeniac-laptop:~$ blockcontrol show_config
blockcontrol current settings:
ACCEPT="1"
ACCEPT_MARK="20"
ALLOW_FW=""
ALLOW_IN="/etc/blockcontrol/allow.p2p"
ALLOW_OUT="/etc/blockcontrol/allow.p2p"
BLOCKLIST_FORMAT="p"
BLOCKLISTS_DIR="/var/spool/blockcontrol"
BLOCKLISTS_LIST="/etc/blockcontrol/blocklists.list"
CONTROL_CONF="/etc/blockcontrol/blockcontrol.conf"
CONTROL_LIB="/usr/lib/blockcontrol/blockcontrol.lib"
CONTROL_LOG="/var/log/blockcontrol.log"
CONTROL_NAME="blockcontrol"
CONTROL_SCRIPT="/usr/bin/blockcontrol"
CRON="1"
CRON_MAILTO="root"
CUSTOM_DAEMON_OPTS=""
DAEMON="/usr/bin/moblock"
DAEMON_LOG="/var/log/moblock.log"
DESC="IP block daemon"
E_BADARGS="2"
E_BLOCKLIST="9"
E_CONFIG="6"
E_IPTABLES="8"
E_NETWORK_DOWN="171"
E_NOTROOT="4"
E_XBIN="5"
E_XCD="66"
E_XEXTERNAL="170"
E_XFILE="7"
INIT="0"
IP_REMOVE=""
IPTABLES_ACTIVATION="1"
IPTABLES_CUSTOM_DIR="/etc/blockcontrol"
IPTABLES_SETTINGS="1"
IPTABLES_TARGET="NFQUEUE"
IPTABLES_TARGET_WHITELISTING="RETURN"
LOG_IPTABLES=""
LOG_SYSLOG="0"
LOG_TIMESTAMP="1"
LSB=""
MASTER_BLOCKLIST_DIR="/var/lib/blockcontrol"
MD5SUM_FILE="/var/spool/blockcontrol/MD5SUM"
NAME="moblock"
NFQUEUE_NUMBER="92"
NICE_LEVEL="5"
PATH="/usr/bin:/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin"
PIDFILE="/var/run/moblock.pid"
REJECT="1"
REJECT_FW="DROP"
REJECT_IN="DROP"
REJECT_MARK="10"
REJECT_OUT="REJECT"
STATFILE="/var/log/MoBlock.stats"
STDIFS=" "
TESTHOST="iblocklist.com"
VERBOSITY="1"
VERSION="1.6"
WD="1"
WD_NICE="19"
WD_PATHNAME="/usr/bin/blockcontrol.wd"
WD_PID="/var/run/blockcontrol.wd.pid"
WD_SLEEP="300"
WGET_OPTS="wget -q -t 5 -T 120 -w 5 --user-agent=blockcontrol/1.6"
WHITE_IP_FORWARD=""
WHITE_IP_IN=""
WHITE_IP_OUT=""
WHITE_LOCAL="1"
WHITE_TCP_FORWARD=""
WHITE_TCP_IN=""
WHITE_TCP_OUT="http https"
WHITE_UDP_FORWARD=""
WHITE_UDP_IN=""
WHITE_UDP_OUT=""

Using internal LSB init-functions.
Using start-stop-daemon.

The following blocklists are configured to be used:
http://list.iblocklist.com/?list=ijfqtofzixtwayqovmxn
http://list.iblocklist.com/?list=ecqbsykllnadihkdirsh
http://list.iblocklist.com/?list=jcjfaxgyyshvdbceroxf
http://list.iblocklist.com/?list=pfefqteoxlfzopecdtyw
http://list.iblocklist.com/?list=tbnuqfclfkemqivekikv
http://list.iblocklist.com/?list=ewqglwibdgjttwttrinl
http://list.iblocklist.com/?list=bt_proxy
http://list.iblocklist.com/?list=bt_dshield
dpkg command
Code:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
pi  blockcontrol   1.6-1~jaunty   Manage IP blockers
ii  lsb-base       4.0-0ubuntu0.9 Linux Standard Base 4.0 init script function
ii  moblock        0.9~rc2-23~pre An IP blocker for Linux
xaeniac is offline   Reply With Quote

 
Old 08-30-2009, 11:58 AM   #4
jre

Senior Member
Join Date: Sep 2005
Posts: 588
Default Re: moblock will not start Ubuntu 9.04

moblock crashed after it was started successfully. No idea why. Please post /var/log/moblock.log. This is the main issue.

Besides that I have to fix the verification of the correct "stop" (status 1). But thatīs no big deal.
__________________
Code:
Please post your logfiles and output of commands wrapped in
[ CODE ] tags. You find them in the advanced editing mode: #
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.
jre is offline   Reply With Quote

 
Old 08-30-2009, 01:50 PM   #5
xaeniac

Member
Join Date: Aug 2009
Posts: 4
Default Re: moblock will not start Ubuntu 9.04

more /var/log/blockcontrol.log
Code:
2009-08-30 12:48:09 PM CDT Begin: blockcontrol stop
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ... failed!
2009-08-30 12:48:29 PM CDT End: blockcontrol stop
2009-08-30 12:48:38 PM CDT Begin: blockcontrol start
Problematic daemon status: 1
moblock is not running. ... failed!
xaeniac@xaeniac-laptop:~$ more /var/log/blockcontrol.log
2009-08-30 12:48:09 PM CDT Begin: blockcontrol stop
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ... failed!
2009-08-30 12:48:29 PM CDT End: blockcontrol stop
2009-08-30 12:48:38 PM CDT Begin: blockcontrol start
Problematic daemon status: 1
moblock is not running. ... failed!
xaeniac@xaeniac-laptop:~$ more /var/log/blockcontrol.log
2009-08-30 12:48:09 PM CDT Begin: blockcontrol stop
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ... failed!
2009-08-30 12:48:29 PM CDT End: blockcontrol stop
2009-08-30 12:48:38 PM CDT Begin: blockcontrol start
Problematic daemon status: 1
moblock is not running. ... failed!
xaeniac@xaeniac-laptop:~$ more /var/log/blockcontrol.log
2009-08-30 12:48:09 PM CDT Begin: blockcontrol stop
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ... failed!
2009-08-30 12:48:29 PM CDT End: blockcontrol stop
2009-08-30 12:48:38 PM CDT Begin: blockcontrol start
Problematic daemon status: 1
moblock is not running. ... failed!
xaeniac@xaeniac-laptop:~$ more /var/log/blockcontrol.log
2009-08-30 12:48:09 PM CDT Begin: blockcontrol stop
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ... failed!
2009-08-30 12:48:29 PM CDT End: blockcontrol stop
2009-08-30 12:48:38 PM CDT Begin: blockcontrol start
Problematic daemon status: 1
moblock is not running. ... failed!
xaeniac@xaeniac-laptop:~$ more /var/log/blockcontrol.log
2009-08-30 12:48:09 PM CDT Begin: blockcontrol stop
Stopping blockcontrol.wd.
Deleting iptables ...
iptables v1.4.1.1: Couldn't load target `blockcontrol_in':/lib/xtables/libipt_bl
ockcontrol_in.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_out':/lib/xtables/libipt_b
lockcontrol_out.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.1.1: Couldn't load target `blockcontrol_fw':/lib/xtables/libipt_bl
ockcontrol_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: 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
 failed!
Don't worry! There occured some errors during the deletion of the iptables ... (
warning).
rules. The most common reason for this is that they did not exist, because ... (
warning).
moblock was not running. ... (warning).
But if moblock was running there is some problem. Most probably you have ... (wa
rning).
installed another firewall application that did delete the iptables rules. ... (
warning).
A "blockcontrol restart" will then fix the situation. ... (warning).
Stopping moblock ... failed!
2009-08-30 12:48:29 PM CDT End: blockcontrol stop
2009-08-30 12:48:38 PM CDT Begin: blockcontrol start
Problematic daemon status: 1
moblock is not running. ... failed!
xaeniac is offline   Reply With Quote

 
Old 08-31-2009, 12:11 PM   #6
jre

Senior Member
Join Date: Sep 2005
Posts: 588
Default Re: moblock will not start Ubuntu 9.04

no no
This time I wanted moblock.log, not blockcontrol.log.
Do
Code:
sudo rm -f /var/log/moblock.log
sudo blockcontrol start
wait a few minutes and then post the moblock.log.



EDIT: Just released 1.6.7 which should at least fix a part of the problem. (Removing the pidfile of a crashed daemon on stop). But I still donīt know why the moblock daemon crashed in the first time. So I still need /var/log/moblock.log
__________________
Code:
Please post your logfiles and output of commands wrapped in
[ CODE ] tags. You find them in the advanced editing mode: #
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.

Last edited by jre : 08-31-2009 at 02:22 PM.
jre is offline   Reply With Quote

 
Old 09-03-2009, 03:34 AM   #7
xaeniac

Member
Join Date: Aug 2009
Posts: 4
Default Re: moblock will not start Ubuntu 9.04

Here is more /var/log/moblock.log'

Can it be OpenDNS?

Code:
more /var/log/moblock.log
Short guarding.p2p line <html>, skipping it...
Short guarding.p2p line 	<head>, skipping it...
Short guarding.p2p line 		<title>OpenDNS</title>, skipping it...
Short guarding.p2p line 	</head>, skipping it...
Short guarding.p2p line 	<body id="mainbody" onLoad="testforbanner();" st
yle="margin: 0px;">, skipping it...
Short guarding.p2p line 		<script language="JavaScript">, skipping
 it...
Short guarding.p2p line 			function testforbanner() {, skip
ping it...
Short guarding.p2p line 				var width;, skipping it.
..
Short guarding.p2p line 				var height;, skipping it
...
Short guarding.p2p line 				var x = 0;, skipping it.
..
Short guarding.p2p line 				var isbanner = false;, s
kipping it...
Short guarding.p2p line 				var bannersizes = new Ar
ray(16), skipping it...
Short guarding.p2p line 				bannersizes[0] = '300x25
0';, skipping it...
Short guarding.p2p line 				bannersizes[1] = '250x25
0';, skipping it...
Short guarding.p2p line 				bannersizes[2] = '240x40
0';, skipping it...
Short guarding.p2p line 				bannersizes[3] = '336x28
0';, skipping it...
Short guarding.p2p line 				bannersizes[4] = '180x15
0';, skipping it...
Short guarding.p2p line 				bannersizes[5] = '468x60
';, skipping it...
Short guarding.p2p line 				bannersizes[6] = '234x60
';, skipping it...
Short guarding.p2p line 				bannersizes[7] = '88x31'
;, skipping it...
Short guarding.p2p line 				bannersizes[8] = '120x90
';, skipping it...
Short guarding.p2p line 				bannersizes[9] = '120x60
';, skipping it...
Short guarding.p2p line 				bannersizes[10] = '120x2
40';, skipping it...
Short guarding.p2p line 				bannersizes[11] = '125x1
25';, skipping it...
Short guarding.p2p line 				bannersizes[12] = '728x9
0';, skipping it...
Short guarding.p2p line 				bannersizes[13] = '160x6
00';, skipping it...
Short guarding.p2p line 				bannersizes[14] = '120x6
00';, skipping it...
Short guarding.p2p line 				bannersizes[16] = '300x6
00';, skipping it...
Short guarding.p2p line 				bannersizes[17] = '300x1
25';, skipping it...
Short guarding.p2p line 				bannersizes[18] = '530x3
00';, skipping it...
Short guarding.p2p line 				bannersizes[19] = '190x2
00';, skipping it...
Short guarding.p2p line 				bannersizes[20] = '470x2
50';, skipping it...
Short guarding.p2p line 				if(typeof(window.innerHe
ight) == 'number') {, skipping it...
Short guarding.p2p line 					height = window.
innerHeight;, skipping it...
Short guarding.p2p line 					width = window.i
nnerWidth;, skipping it...
Short guarding.p2p line 				} else if(typeof(documen
t.body.offsetHeight) == 'number') {, skipping it...
Short guarding.p2p line 					height = documen
t.body.offsetHeight;, skipping it...
Short guarding.p2p line 					width = document
.body.offsetWidth;, skipping it...
Short guarding.p2p line 				};, skipping it...
Short guarding.p2p line 				for (x=0; x<bannersizes.
length; x++) {, skipping it...
Short guarding.p2p line 					if(bannersizes[x
] == width + 'x' + height) {, skipping it...
Short guarding.p2p line 						isbanner
 = true;, skipping it...
Short guarding.p2p line 					};, skipping it.
..
Short guarding.p2p line 				};, skipping it...
Short guarding.p2p line 				if(isbanner || width < 1
00 || height < 100) {, skipping it...
also sudo blockcontrol status
Code:
sudo blockcontrol status
Current IPv4 iptables rules (this may take a while):

Chain INPUT (policy ACCEPT 7 packets, 1542 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    6   624 blockcontrol_in  all  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW mark match !0x14 

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 blockcontrol_fw  all  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW mark match !0x14 

Chain OUTPUT (policy ACCEPT 19 packets, 6010 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    4  1234 blockcontrol_out  all  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW mark match !0x14 

Chain blockcontrol_fw (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       all  --  *      *       0.0.0.0/0            0.0.0.0/0           mark match 0xa 
    0     0 RETURN     all  --  *      *       0.0.0.0/0            192.168.1.1         
    0     0 RETURN     all  --  *      *       192.168.1.0/24       192.168.1.0/24      
    0     0 NFQUEUE    all  --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 92

Chain blockcontrol_in (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       all  --  *      *       0.0.0.0/0            0.0.0.0/0           mark match 0xa 
    0     0 RETURN     all  --  lo     *       0.0.0.0/0            0.0.0.0/0           
    0     0 RETURN     all  --  *      *       192.168.1.0/24       0.0.0.0/0           
    6   624 NFQUEUE    all  --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 92

Chain blockcontrol_out (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           mark match 0xa reject-with icmp-port-unreachable 
    0     0 RETURN     all  --  *      lo      0.0.0.0/0            0.0.0.0/0           
    0     0 RETURN     all  --  *      *       0.0.0.0/0            192.168.1.1         
    0     0 RETURN     all  --  *      *       0.0.0.0/0            192.168.1.0/24      
    2   131 RETURN     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:443 
    2  1103 RETURN     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:80 
    0     0 NFQUEUE    all  --  *      *       0.0.0.0/0            0.0.0.0/0           NFQUEUE num 92

Please check if the above printed iptables rules are correct!

moblock is not running. ... failed!
blockcontrol.wd is running..
PID: 4950    CMD: /bin/sh /usr/bin/blockcontrol.wd

Last edited by xaeniac : 09-03-2009 at 03:36 AM. Reason: addition
xaeniac is offline   Reply With Quote

 
Old 09-03-2009, 12:09 PM   #8
jre

Senior Member
Join Date: Sep 2005
Posts: 588
Default Re: moblock will not start Ubuntu 9.04

Quote:
Originally Posted by xaeniac View Post
Can it be OpenDNS?
Yes :-/ This is a known problem. I havenīt looked into it, but I got the same reports from 2 other people (this has nothing to do with any recent update, but is a permanent problem).

Only solution in the short run:
Donīt use OpenDNS + fix (remove) your broken downloads with "sudo blockcontrol force-update"

Sorry, I donīt run OpenDNS, but Iīm sure that itīs something wothy to be supported, so I will try to get on that soon ...
__________________
Code:
Please post your logfiles and output of commands wrapped in
[ CODE ] tags. You find them in the advanced editing mode: #
Maintainer of http://moblock-deb.sourceforge.net: MoBlock, mobloquer, blockcontrol and NFBlock Debian packages.
Author of blockcontrol, previously moblock-control.
jre is offline   Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 03:17 AM.


  

Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
© Phoenix Labs Staff