Bug#359335: marked as done (ssh/openssh-server dependency problems prevent installation)
Your message dated Mon, 27 Mar 2006 19:23:58 -0500
with message-id <20060328002358.GA24162@andromeda>
and subject line Bug#359335: ssh/openssh-server dependency problems prevent installation--maybe local goof
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ssh
Version: 1:4.2p1-7
Severity: normal
Since this renders the package uninstallable, and may have broken my
previously working sshd, this may warrant higher severity. However, I
don't see other reports of this, so it may be some local peculiarity.
On the last dist-upgrade I get this:
Setting up openssh-client (4.2p1-7) ...
Setting up openssh-server (4.2p1-7) ...
Restarting OpenBSD Secure Shell server: sshdinvoke-rc.d: initscript ssh, action "restart" failed.
dpkg: error processing openssh-server (--configure):
subprocess post-installation script returned error exit status 1
# at the end
dpkg: dependency problems prevent configuration of ssh:
ssh depends on openssh-server; however:
Package openssh-server is not configured yet.
dpkg: error processing ssh (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
openssh-server
ssh
E: Sub-process /usr/bin/dpkg returned an error code (1)
I tried again, but got the same errors.
I though perhaps removing ssh would help, but lam-runtime depends on
it.
This was intended to be a report against the source package; I'm not
sure if things worked out that way.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (40, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages ssh depends on:
ii openssh-client 1:4.2p1-7 Secure shell client, an rlogin/rsh
pn openssh-server <none> (no description available)
ssh recommends no packages.
-- debconf information:
ssh/insecure_rshd:
ssh/privsep_ask: true
ssh/user_environment_tell:
* ssh/forward_warning:
ssh/insecure_telnetd:
ssh/new_config: true
* ssh/use_old_init_script: true
* ssh/SUID_client: true
ssh/disable_cr_auth: false
* ssh/privsep_tell:
ssh/ssh2_keys_merged:
* ssh/protocol2_only: true
ssh/encrypted_host_key_but_no_keygen:
* ssh/run_sshd: true
--- End Message ---
--- Begin Message ---
On Mon, Mar 27, 2006 at 04:20:24PM -0800, Ross Boylan wrote:
> On Mon, 2006-03-27 at 18:57 -0500, Justin Pryzby wrote:
> > On Mon, Mar 27, 2006 at 03:12:59PM -0800, Ross Boylan wrote:
> > > init.d/ssh includes these lines
> > >
> > > restart)
> > > check_config
> > > echo -n "Restarting OpenBSD Secure Shell server: sshd"
> > > start-stop-daemon --stop --quiet --oknodo --retry 30
> > > --pidfile /var/run/sshd.pid
> > >
> > > We made some changes to get a 2nd sshd running, and may have edited this
> > > by mistake. The argument to --pidfile should be /var/run/sshd/sshd.pid.
> > >
> > > With that change, things seem to work.
> > >
> > > So, if the original file is like that, I think it should be fixed.
> > >
> > > If it's not, sorry about the noise. OK to close.
> > /var/run/sshd.pid is what the original conffile has, and my upgrade
> > worked. Can this be closed, or is there still a bug?
>
> My init.d/ssh file has most commands using /var/run/ssh/sshd.pid for the
> pid file, except that restart was using /var/run/sshd.pid. I assumed
> the local change had been to lines after restart, but maybe it was to
> the others.
> start)
> check_for_no_start
> check_privsep_dir
> echo -n "Starting OpenBSD Secure Shell server: sshd"
> start-stop-daemon --start --quiet --pidfile /var/run/sshd/sshd.pid
> --exec /usr/sbin/sshd -- $SSHD_OPTS
> echo "."
> ;;
> stop)
> echo -n "Stopping OpenBSD Secure Shell server: sshd"
> start-stop-daemon --stop --quiet --oknodo
> --pidfile /var/run/sshd/sshd.pid
> echo "."
> ;;
>
> reload|force-reload)
> check_for_no_start
> check_config
> echo -n "Reloading OpenBSD Secure Shell server's configuration"
> start-stop-daemon --stop --signal 1 --quiet --oknodo
> --pidfile /var/run/sshd/sshd.pid --exec /usr/sbin/sshd
> echo "."
> ;;
>
> restart)
> check_config
> echo -n "Restarting OpenBSD Secure Shell server: sshd"
> start-stop-daemon --stop --quiet --oknodo --retry 30
> --pidfile /var/run/sshd/sshd.pid
> check_for_no_start
> check_privsep_dir
> start-stop-daemon --start --quiet --pidfile /var/run/sshd/sshd.pid
> --exec /usr/sbin/sshd -- $SSHD_OPTS
>
> So, I'd say that if all the pid file paths are consistent in the
> original, this is our locally introduced goof, and it's OK to close.
All references in the prisine conffile /etc/init.d/ssh are to
/var/run/sshd.pid.
--- End Message ---
Reply to: