upgrade nightmare!

[Robert Martinovic]

----- Original Message -----
From: <david at prometheus.com.au>
To: Robert Martinovic <mlaich at bigpond.com>
Sent: Wednesday, August 08, 2001 7:26 PM
Subject: Re: upgrade nightmare!


> Robert Martinovic wrote:
> >
> > ----- Original Message -----
> > From: <david at prometheus.com.au>
> > To: Robert Martinovic <mlaich at bigpond.com>
> > Sent: Wednesday, August 08, 2001 6:44 PM
> > Subject: Re: upgrade nightmare!
> >
> > > Robert Martinovic wrote:
> > > >
> > > > I really don't know what has happened. I upgraded my debian system
last
> > > > night to unstable, and when I booted today, everything seems broken.
For
> > > > instance, on bootup, iptables spits out a whole bunch of errors, and
I
> > get
> > > > this:
> > > >
> > > > 'portmapper inactive - RPC services unavailable'
> > > >
> > > > I can log on to the net, but it is useless as no DNS is available. I
> > cannot
> > > > ping another machine on my home lan.
> > > >
> > > > Help! I have tried everything I could think of
> > >
> > > Most likely portmap isn't running. Take a look under /etc/rc.d . I
don't
> > > know exactly how that works under debian, but under redhat, it would
be
> > > something like this.
> > >
> > > Look in /etc/rc.d/rc5.d (or rc3.d if you normally run without X). Look
> > > for a file called S??portmap where ?? is a two digit number. It should
> > > be a symlink to /etc/rc.d/init.d/portmap . It is probably a good idea
if
> > > the number is greater than the similar one for S??network, but less
than
> > > the other related network ones such as nfs, inet and so on.
> > >
> > > If you have some nice GUI admin tool, it might have a way to configure
> > > these sorts of things, but it's worth looking at the actual files in
the
> > > system as well to make sure the GUI didn't stuff up.
> > daemon        187    0.0    0.3    1392    460    ?            S
17:49
> > 0:00    /sbin/portmap
> > root             7859   0.0    0.3    1356    500    pts/2      S
18:50
> > 0:00    grep portmap
>
> This shows that portmap is running, which is a start. Obviously it isn't
> working very well.
>
> Try (as root)
>
> netstat -t -a -p | grep sunrpc
>
> You should get a line looking like
>
> tcp        0      0 *:sunrpc                *:*           LISTEN
> 247/portmap
>
> That would show that portmap is actually listening on a port, as it
> should.
>
> Maybe the next thing after that would be to kill portmap, kill iptables,
> then restart portmap with a command something like
>
> /sbin/portmap -d -v

I did this, as when I tried to re-enter the iptables, I get this, something
I've never seen before:

iptables v1.2.2: Couldn't load target
'standard':/usr/local/lib/iptables/libipt_standard.so: cannot open shared
object file: No such file or directory

I am absolutely stumped with this one.

> That will make it run in the foreground with logging to the screen. If
> that doesn't instantly show you the trouble, start iptables by hand (in
> a different Xterm/console/whatever) and then look back at the portmap
> screen to see if it says anything useful. (BTW i don't actually know
> what iptables is or how you start it. Hope you do. Is it the new kind of
> firewalling?)
>
> Hopefully all this will give you a better class of error message.
>