2003-Oct-11

su didn't work:

su: Error in service module

passwd was just hanging. strace showed it couldn't create lock file. So I realized it was setuid "bin" (because the configure script saw that INSTALL was using BINOWN and BINGRP settings).

su still didn't work but passwd worked after that fix.

Then syslogd wasn't working. The -d switch reported:

Called logerr, msg: network logging disabled (syslog/udp service unknown).
logmsg: syslog.err<43>, flags 4, from puget, msg syslogd: network logging disabled (syslog/udp service unknown).

So even though network logging is disabled, it still didn't work locally when /etc/services was missing that field.

Once, I had logging working, su and sshd caused:

Oct 11 01:07:45 puget su[17064]: cannot open login definitions /etc/login.defs
[No such file or directory]

Once I created that file (with no settings), then PAM was used, but I next got:

Oct 11 01:12:53 puget su(pam_unix)[17089]: authentication failure; logname= uid=100 euid=2 tty=ttyp0 ruser=reed rhost=  user=root
Oct 11 01:12:54 puget su[17089]: pam_authenticate: Authentication failure
Oct 11 01:13:19 puget sshd[17092]: Failed password for reed from 192.168.0.2 port 61294 ssh2