35360 – After upgrading to openssh 3.7.1_p2-r1, /etc/init.d/sshd start will not start

Bug 35360 - After upgrading to openssh 3.7.1_p2-r1, /etc/init.d/sshd start will not start

Summary: After upgrading to openssh 3.7.1_p2-r1, /etc/init.d/sshd start will not start

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Server (show other bugs)
Hardware:	All Linux

Importance:	High major
Assignee:	Daniel Ahlberg (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-12-08 10:23 UTC by Ooblick
Modified:	2003-12-08 10:53 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ooblick 2003-12-08 10:23:47 UTC

This morning I did an "emerge -uv world" which upgraded my (previously working
correctly) installation of openssh to version 3.7.1_p2-r1. Now, when I run the
script "/etc/init.d/sshd start" I get this error message:

"Missing privilege separation directory: /var/empty                        [ !! ]"

sshd does not start


Reproducible: Always
Steps to Reproduce:
1. emerge -uv world -> installs openssh 3.7.1_p2-r1
2. Ran etc-updated. One file displayed /etc/ssh/sshd_config
3. Selected the option to overwrite old configuration with new configuration
4. restart sshd with "/etc/init.d/sshd restart"


Actual Results:  
"Missing privilege separation directory: /var/empty                        [ !! ]"

sshd does not start

Expected Results:  
sshd should have started without error

There were no relevant logs in /var/log/messages

Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.20-gentoo-r9)
=================================================================
System uname: 2.4.20-gentoo-r9 i686 AMD Athlon(tm) XP 2200+
Gentoo Base System version 1.4.3.10
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -mcpu=athlon-xp -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=athlon-xp -mcpu=athlon-xp -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="sandbox ccache autoaddcvs"
GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 oss apm avi crypt encode libg++ libwww mad mikmod mpeg ncurses nls
pdflib quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline
aalib svga tcltk gpm tcpd pam ssl perl python esd imlib oggvorbis motif opengl
mozilla cdr cups foomaticdb ppds usb java mmx sse jpeg png tiff gif 3dnow X gtk2
gtk gnome alsa sdl -kde -qt -arts"

Comment 1 SpanKY gentoo-dev

2003-12-08 10:40:12 UTC

do you have a /var/empty ?

Comment 2 Ooblick 2003-12-08 10:51:27 UTC

I've just tried the following actions:

1. Delete /etc/ssh/sshd_config
2. emerge openssh
3. /etc/init.d/sshd start

This time it started up correctly. Hmmmm. Odd.

I've had a look and I do now have an /var/empty.

Is this directory only created if /etc/ssh/sshd_config is absent? If so, this needs fixing.

Otherwise this bug can be closed.

Comment 3 SpanKY gentoo-dev

2003-12-08 10:53:37 UTC

no, /etc is unrelated to /var/empty

i fixed a keepdir bug with /var/empty perhaps this was related