problems with a fresh G1.2 install

Message

emerge newbie · Post by **emerge newbie** » Wed Oct 23, 2002 9:27 am

I recently re-installed a fresh copy of Gentoo 1.2. The install went fine and my system was up and running. I sshd'd into the box from my Windows machine and started updating all the packages. I did an 'emerge -u world' after checking what was going to be installed and off it went. Half way through emerging all the new packages my windows machine reset (gah!). I then tried restarting the 'emerge -u world' on the machine locally and it seemed to finish fine. When I then tried to log into the box locally I kept getting all these weird error messages popping up:

configuration error - unknown item 'CONSOLE' (notify administrator)
configuration error - unknown item 'CREATE_HOME' (notify administrator)
configuration error - unknown item 'DIALUPS_CHECK_ENAB' (notify administrator)
configuration error - unknown item 'ENVIRON_FILE' (notify administrator)
configuration error - unknown item 'ENV_HZ' (notify administrator)
configuration error - unknown item 'ERASECHAR' (notify administrator)
configuration error - unknown item 'KILLCHAR' (notify administrator)
configuration error - unknown item 'LOG_OK_LOGINS' (notify administrator)
configuration error - unknown item 'MAIL_CHECK_ENAB' (notify administrator)
configuration error - unknown item 'mAIL_DIR' (notify administrator)
configuration error - unknown item 'NOLOGINS_FILE' (notify administrator)
configuration error - unknown item 'PORTTIME_CHECKS_ENAB' (notify administrator)
configuration error - unknown item 'QUOTAS_ENAB' (notify administrator)
configuration error - unknown item 'SU_NAME' (notify administrator)
configuration error - unknown item 'SU_WHEEL_ONLY' (notify administrator)
configuration error - unknown item 'SYSLOG_SG_ENAB' (notify administrator)
configuration error - unknown item 'SYSLOG_SU_ENAB' (notify administrator)

This happens with all users and only seems to be when I log in locally. If I ssh into my box I dont get the errors.

I did do a quick search around the forums and after that decided to trying reinstalling bash. But now when I try and re-emerge it I get the following message:

emerge bash
Calculating dependencies ...done!
>>> emerge sys-apps/bash-2.05a-r3 to /
Traceback (most recent call last):
File "/usr/bin/emerge", line 1355, in ?
mydepgraph.merge(mydepgraph.altlist())
File "/usr/bin/emerge", line 903, in merge
retval=portage.doebuild(y,"clean",myroot,edebug)
File "/usr/lib/python2.2/site-packages/portage.py", line 1072, in doebuild
return spawn("/usr/sbin/ebuild.sh "+mydo,debug,free=1)
File "/usr/lib/python2.2/site-packages/portage.py", line 798, in spawn
os.execve(mycommand,myargs,settings.environ())
OSError: [Errno 2] No such file or directory

Any help would be appreciated.

emerge newbie · Post by **emerge newbie** » Mon Oct 28, 2002 10:35 pm

Ok I just tried another fresh install of 1.2 and 2hours later I have exactly the same problem as I had in my old install. When I first finish the install root can login fine without any errors, but as soon as I 'emerge -u world' I get the same problem:

configuration error - unknown item 'CONSOLE' (notify administrator)
configuration error - unknown item 'CREATE_HOME' (notify administrator)
configuration error - unknown item 'DIALUPS_CHECK_ENAB' (notify administrator)
configuration error - unknown item 'ENVIRON_FILE' (notify administrator)
configuration error - unknown item 'ENV_HZ' (notify administrator)
configuration error - unknown item 'ERASECHAR' (notify administrator)
configuration error - unknown item 'KILLCHAR' (notify administrator)
configuration error - unknown item 'LOG_OK_LOGINS' (notify administrator)
configuration error - unknown item 'MAIL_CHECK_ENAB' (notify administrator)
configuration error - unknown item 'mAIL_DIR' (notify administrator)
configuration error - unknown item 'NOLOGINS_FILE' (notify administrator)
configuration error - unknown item 'PORTTIME_CHECKS_ENAB' (notify administrator)
configuration error - unknown item 'QUOTAS_ENAB' (notify administrator)
configuration error - unknown item 'SU_NAME' (notify administrator)
configuration error - unknown item 'SU_WHEEL_ONLY' (notify administrator)
configuration error - unknown item 'SYSLOG_SG_ENAB' (notify administrator)
configuration error - unknown item 'SYSLOG_SU_ENAB' (notify administrator)

I searched around the forums last time and the only problem I could find that was related was this one, but noone was able to help here either.

Surely someone must know what the problem could be? I could paste the contents of my /usr/portage/distfiles if need be.

Any help would be appreciated.

edit: this is the contents of my /usr/portage/distfile, surely one of these packages is responsible?

ExtUtils-MakeMaker-6.05.tar.gz
man-1.5k.tar.gz
Linux-PAM-0.75.tar.gz
man-pages-1.52.tar.bz2
Python-2.2.2.tgz
metalog-0.6.tar.gz
autoconf-2.13.tar.gz
miscfiles-1.3.tar.gz
autoconf-2.54.tar.bz2
modutils-2.4.19.tar.bz2
automake-1.4-p5.tar.gz
nano-1.0.9.tar.gz
automake-1.5.tar.gz
ncompress-4.2.4.tar.gz
automake-1.6.3.tar.gz
ncurses-5.2.tar.gz
bash-2.05a.tar.gz
net-tools-1.60.tar.bz2
bison-1.35.tar.gz
openssh-3.5p1.tar.gz
bzip2-1.0.2.tar.gz
openssl-0.9.6g.tar.gz
cracklib2_2.7.orig.tar.gz
pam-0.75-r10-gentoo.tbz2
db-3.2.9.tar.gz
pam_login-3.7.tar.bz2
debianutils_1.16.3.tar.gz
patches-2.4.19-gentoo-r10.tar.bz2
devfsd-v1.3.25.tar.gz
pcre-3.9.tar.bz2
diffutils-2.8.4.tar.gz
perl-5.6.1.tar.gz
e2fsprogs-1.29.tar.gz
procps-2.0.10.tar.bz2
expat-1.95.4.tar.gz
pwdb-0.61.tar.gz
file-3.39.tar.gz
readline-4.1.tar.gz
fileutils-4.1.11.tar.gz
reiserfsprogs-3.6.4.tar.gz
flex-2.5.22.tar.gz
rsync-2.5.5.tar.gz
gawk-3.1.1.tar.gz
sed-4.0.tar.gz
gcc-2.95.3.tar.gz
sh-utils-2.0.15.tar.gz
gettext-0.11.5.tar.gz
shadow-4.0.3.tar.gz
glib-1.2.10.tar.gz
ssmtp-2.38.14.tar.gz
glibc-2.2.5.tar.bz2
sysvinit-2.84.tar.gz
glibc-linuxthreads-2.2.5.tar.bz2
tar-1.13.25.tar.gz
groff-1.17.2.tar.gz
texinfo-4.2b.tar.gz
gzip-1.3.3.tar.gz
textutils-2.1.tar.gz
hdparm-5.2.tar.gz
util-linux-2.11r.patch.gz
iptables-1.2.7a.tar.bz2
util-linux-2.11w.tar.gz
less-378.tar.gz
vixie-cron-3.0.1.tar.bz2
libtool-1.4.1.tar.gz
wget-1.8.2.tar.gz
linux-2.4.19.tar.bz2
wget-new-percentage-cvs-20011209.tar.gz
make-3.80.tar.gz
which-2.14.tar.gz

emerge newbie · Post by **emerge newbie** » Tue Oct 29, 2002 5:56 am

Noone?

emerge newbie · Post by **emerge newbie** » Wed Oct 30, 2002 2:23 am

Can someone even maybe have a guess as to what the problem could be related to, or possibly suggest what I could try re-emerging? Or maybe somewhere I could ask to try and get the issue resolved.

Anyone, please!

Mnemia · Post by **Mnemia** » Wed Oct 30, 2002 2:54 am

I don't really know what is causing this, but since no one else seems to either I can make a guess. I think that that error is usually associated with pam-login or pam, so you could try reemerging those. It may be a messed up configuration file or something, since it seems like one of those isn't finding its settings.

Have you been using nano without the -w option to edit files? That can easily totally ruin the config files and cause all kinds of bizarre behavior.

emerge newbie · Post by **emerge newbie** » Wed Oct 30, 2002 3:38 am

Firstly; thanks a lot for the reply, this is sending me nuts.

No, I always use the '-w' option. The install was literally fresh, it was booted once and pretty much immediately I ran 'emerge -u world'. I thought it might be something to do with PAM so I rerean 'emerge pam' this mornign before coming to work but that didn't seem to solve the problem. I am wondering if there is anything that could go wrong by unmerging PAM altogether and then re-emerging it? Would unmerging it delete the config files etc?

Mnemia · Post by **Mnemia** » Wed Oct 30, 2002 4:32 am

I'm not sure that unmerging PAM would be a very wise move. It might render your system unable to boot, for instance. The only other thing I can think of is to do an emerge -e system to rebuild all the core system and replace the config files from scratch rather than copying your old ones over (if you're doing that). I don't really know what to do beyond that, so someone else will have to help if they can. I didn't find anything really relevant to your problem on Google or Google Groups either, though I could be searching for the wrong thing...all I saw was that those variables it is saying are unconfigured are needed by the login program. Did you reemerge pam-login in addition to just pam?

emerge newbie · Post by **emerge newbie** » Wed Oct 30, 2002 4:59 am

Yer, I did the whole PAM thing which included pam_login. This is really starting to get me down, I don't really have a lot of time to use the machine at home so another 2hours installing would be a pain!

What will '-e system' actually do? Here is the man explination of -e:

--emptytree (-e)
Virtually tweaks the tree of installed packages to
only contain glibc; this is great to use together
with --pretend. This allows developers to get a
complete overview of the complete dependency tree
of a package, and it enables complete trees to be
rebuilt using the latest libraries.

I'm not sure thats the option you meant?

Also; where are the package listings for those in the world and system groups?

Thanks again for the reply.

Mnemia · Post by **Mnemia** » Wed Oct 30, 2002 5:16 am

If you do an emerge -pe system or an emerge -pe world, you will see all the packages that are included in the system or world dependency tree. Dropping the -p option will rebuild everything in that tree. So if ya want to rebuild your entire installation, you can do an emerge -e world. That's how the Gentoo 1.2->1.4 upgrade worked, for instance. The system tree is a subset of the world tree, and doesn't take *too* long to build since most of the packages are small. Exceptions are in there like GCC which takes a fair amount of time.

As for your original problem, I don't really know what to tell you. I'm not sure why it would pop up in a clean install like that. I hope someone else has a better answer for you than rebuilding the thing again.

emerge newbie · Post by **emerge newbie** » Wed Oct 30, 2002 5:40 am

Thanks again for the reply. If no-one else has replied by tomorrow I may as well just run 'emerge -e system' and see what happens.

I'll get back to the thread when I have tried it (assuming again no-one else replies) and tell you what happens.

rac · Post by **rac** » Wed Oct 30, 2002 6:23 am

emerge newbie wrote:where are the package listings for those in the world and system groups?

/var/cache/edb/world
/etc/make.profile/packages

I looked into your original problem. chfn and chsh contain some of those strings, and /etc/login.defs might be a file to look at. I would also try reemerging shadow.

emerge newbie · Post by **emerge newbie** » Wed Oct 30, 2002 6:57 am

I had a look at /etc/login.defs, and this is the contents of it:

#MAIL_FILE .mail
#MD5_CRYPT_ENAB yes
#QMAIL_DIR Maildir
CHFN_AUTH yes
CHFN_RESTRICT rwh
CONSOLE /etc/securetty
#CREATE_HOME is a RedHat'ism and not supported
#by the stock shadow package.
#Generates warning message if set to 'yes'
CREATE_HOME no
DEFAULT_HOME yes
DIALUPS_CHECK_ENAB yes
ENVIRON_FILE /etc/environment
ENV_HZ HZ=100
ENV_PATH PATH=/bin:/usr/bin
ENV_SUPATH PATH=/sbin:/bin:/usr/sbin:/usr/bin
ERASECHAR 0177
FAILLOG_ENAB yes
FAIL_DELAY 3
FTMP_FILE /var/log/btmp
GID_MAX 60000
GID_MIN 100
HUSHLOGIN_FILE .hushlogin
KILLCHAR 025
LASTLOG_ENAB yes
LOGIN_RETRIES 5
LOGIN_TIMEOUT 60
LOG_OK_LOGINS no
LOG_UNKFAIL_ENAB no
MAIL_CHECK_ENAB yes
MAIL_DIR /var/spool/mail
MOTD_FILE /etc/motd
NOLOGINS_FILE /etc/nologin
OBSCURE_CHECKS_ENAB yes
PASS_ALWAYS_WARN yes
PASS_CHANGE_TRIES 5
PASS_MAX_DAYS 99999
PASS_MIN_DAYS 0
PASS_MIN_LEN 5
PASS_WARN_AGE 7
PORTTIME_CHECKS_ENAB yes
QUOTAS_ENAB yes
SU_NAME su
SU_WHEEL_ONLY no
SYSLOG_SG_ENAB yes
SYSLOG_SU_ENAB yes
TTYGROUP tty
TTYPERM 0600
UID_MAX 60000
UMASK 022

If someone has some time could they please check this against what they have? I will also try reemerging shadow when I get home (or could I use the -e option for just shadow prehaps?).

Thanks for the reply rac, and yours as well Mnemia.

Mnemia · Post by **Mnemia** » Wed Oct 30, 2002 7:43 am

I don't really know why, but that file is totally different from what I have in /etc/login.defs. Did you by any chance do something like install over a previous distro without reformatting? Or copy config files from somewhere else? I don't know why yours is different: both my 1.2 server that I haven't touched in like a month and my 1.4rc1 laptop have what I posted below.
Perhaps you need to update some config files in /etc after doing an update?
Here is what I have:

Code: Select all

#
# /etc/login.defs - Configuration control definitions for the login package.
#
# All items are optional - if not specified then the described action or
# option will be inhibited.
#
# Comment lines (lines beginning with "#") and blank lines are ignored.
#

#
# Delay in seconds before being allowed another attempt after a login failure
#
FAIL_DELAY		3

#
# Enable logging and display of /var/log/faillog login failure info.
#
FAILLOG_ENAB		yes

#
# Enable display of unknown usernames when login failures are recorded.
#
LOG_UNKFAIL_ENAB	no

#
# Enable logging and display of /var/log/lastlog login time info.
#
LASTLOG_ENAB		yes

#
# If defined, ":" delimited list of "message of the day" files to
# be displayed upon login.
#
MOTD_FILE	/etc/motd
#MOTD_FILE	/etc/motd:/usr/lib/news/news-motd

#
# If defined, file which maps tty line to TERM environment parameter.
# Each line of the file is in a format something like "vt100  tty01".
#
TTYTYPE_FILE	/etc/ttytype

#
# If defined, login failures will be logged here in a utmp format.
# last, when invoked as lastb, will read /var/log/btmp, so...
#
FTMP_FILE	/var/log/btmp

#
# If defined, file which inhibits all the usual chatter during the login
# sequence.  If a full pathname, then hushed mode will be enabled if the
# user's name or shell are found in the file.  If not a full pathname, then
# hushed mode will be enabled if the file exists in the user's home directory.
#
HUSHLOGIN_FILE	.hushlogin
#HUSHLOGIN_FILE	/etc/hushlogins

#
# The default PATH settings.
#
ENV_PATH                /usr/local/bin:/usr/bin:/bin

#
# The default PATH settings for root:
#
ENV_ROOTPATH            /sbin:/bin:/usr/sbin:/usr/bin

#
# The default PATH settings when su'ing to root:
#
ENV_SUPATH              /sbin:/bin:/usr/sbin:/usr/bin

#
# Terminal permissions
#
#	TTYGROUP	Login tty will be assigned this group ownership.
#	TTYPERM		Login tty will be set to this permission.
#
# If you have a "write" program which is "setgid" to a special group
# which owns the terminals, define TTYGROUP to the group number and
# TTYPERM to 0620.  Otherwise leave TTYGROUP commented out and assign
# TTYPERM to either 622 or 600.
#
TTYGROUP	tty
TTYPERM		0600

#
# Password aging controls:
#
#	PASS_MAX_DAYS	Maximum number of days a password may be used.
#	PASS_MIN_DAYS	Minimum number of days allowed between password changes.
#	PASS_MIN_LEN	Minimum acceptable password length.
#	PASS_WARN_AGE	Number of days warning given before a password expires.
#
PASS_MAX_DAYS	99999
PASS_MIN_DAYS	0
PASS_MIN_LEN	5
PASS_WARN_AGE	7

#
# Min/max values for automatic uid selection in useradd
#
UID_MIN			 1000
UID_MAX			60000

#
# Min/max values for automatic gid selection in groupadd
#
GID_MIN			  100
GID_MAX			60000

#
# Max number of login retries if password is bad
#
LOGIN_RETRIES        3

#
# Max time in seconds for login
#
LOGIN_TIMEOUT		60

#
# Require password before chfn/chsh can make any changes.
#
CHFN_AUTH		yes

#
# Which fields may be changed by regular users using chfn - use
# any combination of letters "frwh" (full name, room number, work
# phone, home phone).  If not defined, no changes are allowed.
# For backward compatibility, "yes" = "rwh" and "no" = "frwh".
#
CHFN_RESTRICT		rwh

rac · Post by **rac** » Wed Oct 30, 2002 7:51 am

When remerging shadow, don't use -e. Just "emerge shadow".

emerge newbie · Post by **emerge newbie** » Wed Oct 30, 2002 8:08 am

Mnemia wrote:I don't really know why, but that file is totally different from what I have in /etc/login.defs. Did you by any chance do something like install over a previous distro without reformatting? Or copy config files from somewhere else? I don't know why yours is different: both my 1.2 server that I haven't touched in like a month and my 1.4rc1 laptop have what I posted below.
Perhaps you need to update some config files in /etc after doing an update?
Here is what I have:

It was a completey fresh install, I had Gentoo 1.2 on it before that as well. The drivers were both stripped and repartitioned and formatted.

I tried re-emerging shadow but that didn't really help. Which package belongs to /etc/login.defs?

Does anyone have their login.defs from a 1.2 install?

Mnemia · Post by **Mnemia** » Wed Oct 30, 2002 8:17 am

I have the exact same file as the one I posted above on my 1.2 machine. And it was last written to on September 22, so it's been that way for quite some time. So - I can't explain why yours is different. It would seem that yours is trying to define variables that aren't supported by your version of login.

And I don't know how you determine what package that file belongs to: qpkg -f /etc/login.defs returns nothing. So I can't help ya there.

Maybe just try it with the file I posted if you don't find another more elegant solution?

rac · Post by **rac** » Wed Oct 30, 2002 8:17 am

emerge newbie wrote:Which package belongs to /etc/login.defs?

qpkg is your friend with questions like this. emerge gentoolkit if you haven't, and then "qpkg -f /etc/login.defs". Here it says pam-login. Remerge that and let it update /etc/login.defs and see what happens.

Mnemia · Post by **Mnemia** » Wed Oct 30, 2002 8:19 am

rac wrote:
emerge newbie wrote:Which package belongs to /etc/login.defs?
qpkg is your friend with questions like this. emerge gentoolkit if you haven't, and then "qpkg -f /etc/login.defs". Here it says pam-login. Remerge that and let it update /etc/login.defs and see what happens.

I thought that was right, but how come my qpkg doesn't say anything for some of the config files in /etc?
Also, I think he already tried reemerging pam-login. Is there any reason why it wouldn't have created a new config file like the one I have when he did that?

emerge newbie · Post by **emerge newbie** » Wed Oct 30, 2002 8:54 am

Ok I re-did pam-login as well and it didnt update the config file at all. I'm doing a 'emerge -e world' at the moment so we will see what that does.

Thanks for the qpkg advise, will come in handy in the not so distant future I'm sure!

rac · Post by **rac** » Wed Oct 30, 2002 8:56 am

emerge -e world here is like using a nuclear missile to kill an ant. How about

Code: Select all

# FORCE_LOGIN_DEFS=1 emerge pam-login

emerge newbie · Post by **emerge newbie** » Wed Oct 30, 2002 10:48 pm

rac wrote:

emerge -e world here is like using a nuclear missile to kill an ant. How about
Code: Select all
# FORCE_LOGIN_DEFS=1 emerge pam-login

I don't believe this!

Firstly I let the 'emerge -e system' go through because it had already started, and that didn't change the config file at all.. so then I tried the 'FORCE_LOGIN_DEFS=1 emerge pam-login' and that didn't change it either. The contents of that config file are now exactly the same as they were when I started. Why oh why won't they change?!

Maybe I should just try editting the contents to be the same as Mnemia's?

Sorry guys.

emerge newbie · Post by **emerge newbie** » Thu Oct 31, 2002 10:53 pm

Mnemia.. rac..?

Mnemia · Post by **Mnemia** » Thu Oct 31, 2002 11:03 pm

Hmm...I have no clue why it's not updating the file, because it sure should be. Did you copy it over from the hidden file that portage creates?
eg mv /etc/._cfg0000_login.defs /etc/login.defs?
If you did that and it's still the same or the ebuild didn't create the file /etc/._cfg0000_login.defs, then I would just backup your old one and then try pasting the one I posted into there.

clacour · Post by **clacour** » Thu Oct 31, 2002 11:58 pm

Part of the confusion about which package the /etc/login.defs comes from is that it is in BOTH shadow and pam_login. Which one you installed last would determine what qpkg thinks.

Of course, both versions don't look anything like what emerge newbie posted, they look much more like what Mnemia had.

One thing I'd try: manually rename /etc/login.defs to something else, and try re-emerging the shadow and pam_login packages. (Don't emerge them both at once. Emerge one, check the file (and rename that one, too, if it exists) and then emerge the other.)

The login.defs file you have looks like the standard one after it's been sorted and all the blank lines and comments removed.

The problem is, it has things that are not listed in the documentation as legitimate options, and that's exactly what it looks like the error message is.

The only problem with that theory (aside from the fact that it says nothing about where the thing came from) is that Red Hat uses "CREATE_HOME" in THEIR login.defs, and it works fine.

Just did a little research on that, and the two versions are definitely different. My Gentoo login say it is "login (pam_login) 3.7". The Red Hat doesn't respect the "--version" flag, and gives very cryptic help when you give it input it doesn't like.

A "qpkg -f $(which login)" gave an odd result:

sys-apps/pam-login
sys-apps/util-linux

Since you've already tried emerging pam-login to no avail, you might give util-linux a shot.

I wouldn't do anything drastic like "emerge -e world" (YeeOUCH!) again unless you find out your 1.2 ISO image is no good.

Speaking of which, where did you get it, and does it match the size and checksum on Gentoo's site?

If none of the above helps, post as much info as you can find on versions of the various programs, what packages they came from, etc.

In particular, I'd like to know what's different between a local login and an ssh login.

A "ps -ef" after a local login on my box shows:

login -- clacour
bash -

(I'm already late, or I'd look up what an ssh login looks like.)

emerge newbie · Post by **emerge newbie** » Sat Nov 02, 2002 5:09 am

I just want to thank all you guys that posted messages (Mnemia, rac, clacour) as my system is now up and running properly. I was really relieved when I logged in and didn't get the message anymore because I was dreding having to go back to some other crappy distro.

I'd like to be able to say exactly what fixed it so if anyone else had the same problem and searched on it they could fix it as well but I really don't know exactly what did fix it.

If I had to guess I think it would of been playing around with emerging pam-login and shadow and then moving the ._cfg0000_login.defs to login.defs until it worked.

Once again thanks guys, you have been very helpful! Long live Gentoo!