| View previous topic :: View next topic |
| Author |
Message |
galandilias
n00b
Joined: 03 Jul 2011
Posts: 51
|
 Posted: Tue Jun 03, 2014 4:45 pm Post subject: [SOLVED] Problem with running DenyHosts |
 |
|
I am unable to start DenyHosts on my machine - I am posting debug output from run script below, any ideas? I have no more clues... :/
| Code: |
/etc/init.d/denyhosts --debug start
* Caching service dependencies ...
Usage:
pip <command> [options]
no such option: --jre-home
Usage:
pip <command> [options]
no such option: --classpath [ ok ]
+ _conf_d=/etc/init.d/../conf.d
+ _c=denyhosts
+ '[' -n denyhosts -a denyhosts '!=' denyhosts ']'
+ unset _c
+ sourcex -e /etc/init.d/../conf.d/denyhosts.default
+ '[' -e = -e ']'
+ shift
+ '[' -e /etc/init.d/../conf.d/denyhosts.default ']'
+ return 1
+ sourcex -e /etc/init.d/../conf.d/denyhosts
+ '[' -e = -e ']'
+ shift
+ '[' -e /etc/init.d/../conf.d/denyhosts ']'
+ return 1
+ unset _conf_d
+ sourcex -e /etc/rc.conf
+ '[' -e = -e ']'
+ shift
+ '[' -e /etc/rc.conf ']'
+ . /etc/rc.conf
++ rc_shell=/sbin/sulogin
++ unicode=YES
++ rc_tty_number=12
+ '[' -n '' ']'
++ command -v cgroup_add_service
+ '[' cgroup_add_service = cgroup_add_service ']'
+ cgroup_add_service /sys/fs/cgroup/openrc
+ for d in '/sys/fs/cgroup/*'
+ '[' -f /sys/fs/cgroup/cpuacct/tasks ']'
+ echo 0
+ for d in '/sys/fs/cgroup/*'
+ '[' -f /sys/fs/cgroup/cpuset/tasks ']'
+ echo 0
+ for d in '/sys/fs/cgroup/*'
+ '[' -f /sys/fs/cgroup/openrc/tasks ']'
+ echo 0
+ openrc_cgroup=/sys/fs/cgroup/openrc
+ '[' -d /sys/fs/cgroup/openrc ']'
+ cgroup=/sys/fs/cgroup/openrc/denyhosts
+ mkdir -p /sys/fs/cgroup/openrc/denyhosts
+ '[' -f /sys/fs/cgroup/openrc/denyhosts/tasks ']'
+ echo 0
+ cgroup_add_service /sys/fs/cgroup/systemd/system
+ for d in '/sys/fs/cgroup/*'
+ '[' -f /sys/fs/cgroup/cpuacct/tasks ']'
+ echo 0
+ for d in '/sys/fs/cgroup/*'
+ '[' -f /sys/fs/cgroup/cpuset/tasks ']'
+ echo 0
+ for d in '/sys/fs/cgroup/*'
+ '[' -f /sys/fs/cgroup/openrc/tasks ']'
+ echo 0
+ openrc_cgroup=/sys/fs/cgroup/openrc
+ '[' -d /sys/fs/cgroup/openrc ']'
+ cgroup=/sys/fs/cgroup/openrc/denyhosts
+ mkdir -p /sys/fs/cgroup/openrc/denyhosts
+ '[' -f /sys/fs/cgroup/openrc/denyhosts/tasks ']'
+ echo 0
++ command -v cgroup_set_limits
+ '[' cgroup_set_limits = cgroup_set_limits ']'
+ cgroup_set_limits
+ local blkio=
+ '[' -n '' ']'
+ local cpu=
+ '[' -n '' ']'
+ local cpuacct=
+ '[' -n '' ']'
+ local cpuset=
+ '[' -n '' ']'
+ local devices=
+ '[' -n '' ']'
+ local memory=
+ '[' -n '' ']'
+ local net_prio=
+ '[' -n '' ']'
+ return 0
+ sourcex /etc/init.d/denyhosts
+ '[' /etc/init.d/denyhosts = -e ']'
+ . /etc/init.d/denyhosts
++ extra_stopped_commands=purge
+ unset _d
+ unset _f
+ '[' -n '' ']'
+ '[' -n start ']'
+ '[' start = depend ']'
+ for _cmd in describe start stop status '${extra_commands:-$opts}' '$extra_started_commands' '$extra_stopped_commands'
+ '[' describe = start ']'
+ for _cmd in describe start stop status '${extra_commands:-$opts}' '$extra_started_commands' '$extra_stopped_commands'
+ '[' start = start ']'
++ command -v start
+ '[' start = start ']'
+ yesno
+ '[' -z '' ']'
+ return 1
+ for _cmd in '$extra_stopped_commands'
+ '[' purge = start ']'
+ unset _cmd
+ case $1 in
+ verify_boot
+ '[' '!' -e /run/openrc/softlevel ']'
+ return 0
++ command -v start_pre
+ '[' '' = start_pre ']'
+ start
+ ebegin 'Starting DenyHosts daemon'
* Starting DenyHosts daemon ...
+ start-stop-daemon --start --exec /usr/bin/denyhosts.py --pidfile /var/run/denyhosts.pid -- --daemon -c /etc/denyhosts.conf
Usage:
pip <command> [options]
no such option: --daemon
* start-stop-daemon: failed to start `/usr/bin/denyhosts.py'
+ eend 1 [ !! ]
+ exit 1
* ERROR: denyhosts failed to start
|
Last edited by galandilias on Thu Jun 05, 2014 6:09 am; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21621
|
| Posted: Wed Jun 04, 2014 1:56 am Post subject: |
|
|
| It looks like you have set Pip as your Python interpreter, which is not a good idea since Pip is not a Python interpreter, but rather a Python script which is sad excuse for a package manager. I seem to recall seeing this problem within the last few months, where someone reported that all Python scripts were being handled by running pip. If I recall correctly, the problem was traced to having used pip in a way that caused it to overwrite /usr/bin/python (or possibly one of the related links) with a link to run Pip. Have you recently run pip as root? |
|
| Back to top |
|
|
galandilias
n00b
Joined: 03 Jul 2011
Posts: 51
|
| Posted: Wed Jun 04, 2014 8:52 am Post subject: |
|
|
Sure  thats exactly what I did what now? /usr/bin/python leads to python-wrapper which should be okay /usr/bin/python2 leads to python2.7 and /usr/bin/python3 leads to python3.3
calling:
| Code: | | /usr/bin/python --version |
results in:
which sould also be fine.
gives nothing except errors from /proc  |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21621
|
| Posted: Thu Jun 05, 2014 2:09 am Post subject: |
|
|
| First, never run Pip. Second, you need to repair the damage done by running Pip. Unfortunately, I do not recall the forum thread where this was reported. Normally, I would suggest using equery check to find the bad files, but that relies on a working Python. |
|
| Back to top |
|
|
galandilias
n00b
Joined: 03 Jul 2011
Posts: 51
|
|
| Back to top |
|
|
|
Portage & Programming
