Very Computer

Hello

I upgraded my mac68k and my macppc to NetBSD-1.4. Since I did it, both
are crash city!

On the macppc, it does not boot anymore. I crashes just after the OF
loader messages. I thought it could be a problem with the kernel,
therefore I booted with the floppy, mounted my hard disk, and started to
recompile the kernel.

I can't do it! I get errors during compilation or link time. It's the
first time I see a NetBSD kernel haveing problem to compile.

On the mac68k, I installed in multiuser mode with tar -xvzp --unlink.
I have lots of daemonds crashing (ypserv, portmap, xntpd) with no
reason. I think it might be because I should not have unpacked in
multiuser mode

But I have more serious problems: perl does not work any more (It dumps
core), and the package does not compile.  Netatalk crashes too... I
don't understand what is going on: the generic kernel is supposed to
have 1.3.x backward compability, is'nt it?

Other problems (even more serious): my NAT does not work for one of my
machines (not translated outside), and the worst one: ftpd refuses any
login!

220 gizmo FTP server (Version: 7.1.0) ready.
Name (gizmo:manu): manu
331 Password required for manu.
Password:
421 Service not available, remote server has closed connection.
ftp: Login failed.

I'm thninking about reverting to 1.3.3...

--
Emmanuel Dreyfus.  
Pas de processeur Intel, pas de logiciels Microsoft:
Des programmes sains dans un ordinateur sain.

Sure, it should'nt happen. What kind or problem are these ? random
core dumps ?

Quote:

> On the mac68k, I installed in multiuser mode with tar -xvzp --unlink.
> I have lots of daemonds crashing (ypserv, portmap, xntpd) with no
> reason. I think it might be because I should not have unpacked in
> multiuser mode

No, shouldn't be a problem. I've done it several times.
How do they crash ? core dump ?

Quote:

> But I have more serious problems: perl does not work any more (It dumps
> core), and the package does not compile.  Netatalk crashes too... I
> don't understand what is going on: the generic kernel is supposed to
> have 1.3.x backward compability, is'nt it?

It should. But this can be related to the same problem you're seeing.

Quote:

> Other problems (even more serious): my NAT does not work for one of my
> machines (not translated outside), and the worst one: ftpd refuses any
> login!

> 220 gizmo FTP server (Version: 7.1.0) ready.
> Name (gizmo:manu): manu
> 331 Password required for manu.
> Password:
> 421 Service not available, remote server has closed connection.
> ftp: Login failed.

Is there something in the logs ?

--

--

[kernel does not compile]

Quote:> Sure, it should'nt happen. What kind or problem are these ? random
> core dumps ?

No, syntax and linking errors. I unpacked the whole sources again, and
it now compiles without any problem. The only difference is that the
first time I overwrote the NetBSD-1.3.3 /usr/src/sys directory, and on
the second time I did erase it before unpacking syssrc.tgz.

[daemons crashing]

Quote:> No, shouldn't be a problem. I've done it several times.
> How do they crash ? core dump ?

Yes, massive core dumping! This issue is now also OK. I had to unpack
base.tgz again (it's the same base.tgz file!)
The only problem that still existed was ftpd and perl crashing. I fixed
the perl problem by recompiling it. Ftpd still crashes.

Quote:> > 220 gizmo FTP server (Version: 7.1.0) ready.
> > Name (gizmo:manu): manu
> > 331 Password required for manu.
> > Password:
> > 421 Service not available, remote server has closed connection.
> > ftp: Login failed.

> Is there something in the logs ?

in /var/mail/authlog

May 13 10:57:38 gizmo ftpd[10274]: FTP LOGIN FAILED FROM 157.159.10.10,
manu^?

Nothing else.
--
Emmanuel Dreyfus

It returns a status: 0 or 1.
In csh or tcsh, the command would be:
ftpd -C manu
echo $status

--

--

You have mail.
gizmo: {1} /usr/libexec/ftpd -C manu
gizmo: {2} echo $status
0

What does that mean?
--
Emmanuel Dreyfus

Ok this is because there where some old files left, which were used instead
of the new one.

Quote:

> [daemons crashing]
> > No, shouldn't be a problem. I've done it several times.
> > How do they crash ? core dump ?

> Yes, massive core dumping! This issue is now also OK. I had to unpack
> base.tgz again (it's the same base.tgz file!)
> The only problem that still existed was ftpd and perl crashing. I fixed
> the perl problem by recompiling it. Ftpd still crashes.

Well, I can't see a reason for this.

Quote:> > Is there something in the logs ?

> in /var/mail/authlog

> May 13 10:57:38 gizmo ftpd[10274]: FTP LOGIN FAILED FROM 157.159.10.10,
> manu^?

> Nothing else.

Ok, sounds like ftpd just refused the login.
Did you check all the ftpd config file, /etc/shells, /etc/ftpusers,
/etc/ftpchroot, /etc/ftpd.conf, ...
Did you try a 'ftpd -C manu' and checked the status ?

--

--

ftpd -C manu returns nothing at all

           checkportcmd  all
           display       none
           maxtimeout    all    7200   # 2 hours
           modify        all
           modify        guest  off
           notify        none
           timeout       all    900    # 15 minutes
           umask         all    027
           umask         guest  0707

#       $NetBSD: ftpusers,v 1.4 1997/09/08 02:51:58 mikel Exp $
#
# list of users denied (or allowed) ftp access
# read by ftpd(8).
root    deny
altroot deny
toor    deny
uucp    deny
scroc   deny
leto    deny
hx      deny
tatoo   deny
newsmail        deny
ftpmail deny
anonymous       allow
*       allow
--
Emmanuel Dreyfus

"read the doc" !
This means that user "manu" is allowed to ftp in. The problem is somewhere
else.

There is something else wrong in your setup - 1.4 ftp works for me.
Check permissions on directories and files, maybe that's it.

--

--

All -rw-r--r--
Maybe a library related problem? I have lots of library related problems
since I upgraded...
--
Emmanuel Dreyfus

Anyway, I cannot get ftpd outputing log messages anywhere. I added a
 ftp.*                  /var/log/messages
to /etc/syslogd.conf and sent a kill -1 to syslogd, and I still get no
informations from ftp when a login fail.

--
Emmanuel Dreyfus

Maybe. What does 'ldd /usr/libexec/ftpd' says ?
Mine says:
antioche:/home/ftp/etc>ldd /usr/libexec/ftpd
/usr/libexec/ftpd:
    -lcrypt.0 => /usr/lib/libcrypt.so.0.0 (0x40023000)
    -lskey.0 => /usr/lib/libskey.so.0.0 (0x40029000)
    -lc.12 => /usr/lib/libc.so.12.40 (0x4002e000)

--

--

Are you sure ftpd is started at all ?
Try to kill inetd and restart it with '-d'.

--

--

The client does ask me for my login and password. I assume that the
server must be asking him that. I am wrong?

Quote:> Try to kill inetd and restart it with '-d'.

ADD : ftp proto=tcp, wait.max=0.40, user.group=root.(null) builtin=0
server=/usr
/libexec/ftpd
registered /usr/libexec/ftpd on 6

(...)

someone wants ftp
accept, ctrl 5
6230 execl /usr/libexec/ftpd    <<seems to work.
6230 reaped, status 0xb         <<this is when ftpd reject my login

And, the client messages:
220 gizmo FTP server (Version: 7.1.0) ready.
Name (gizmo:manu): manu
331 Password required for manu.
Password:
421 Service not available, remote server has closed connection.
ftp: Login failed.
ftp: No control connection for command.
ftp>

--
Emmanuel Dreyfus

Nearly the same at mine:

/usr/libexec/ftpd:
        -lcrypt.0 => /usr/lib/libcrypt.so.0.0 (0x4026000)
        -lskey.0 => /usr/lib/libskey.so.0.0 (0x402c000)
        -lc.12 => /usr/lib/libc.so.12.40 (0x4032000)

--
Emmanuel Dreyfus

No, you're rigth,

You said you  didn't get anything in /var/log/message, although you had
ftp.* redirected to it.
Could you start ftpd with -lld flags in inetd.conf and see if it helps ?

--

--