Re: Debian box go sleep now.
What version of autoup.sh did you use? Are you getting the hamm
files from a local mirror, files in your current directory, or by ftp
from a mirror? Version 0.21 has a bug that prevents it from
retrieving oldlibs/libc5_*.deb, and from failing due to that. In that
case, it will fail as soon as it starts the upgrade.
autoup.sh is designed to fail safely before it starts the upgrade
if it cannot find any of the required files. Do you have a transcript
(from /usr/bin/script) of your autoup session? That would be helpful
in determining what went wrong.
The autoup script produces a file "removed-`date +%m%d-%T`"
listing all files it removed from your system. Not all of these files
are automatically replaced by the script - only enough to make the
system stable enough to use dselect to complete the upgrade. I
suggest you review this file and make sure all removed packages have
been replaced with their equivalent hamm version (in some cases, the
hamm equivalent has a different name than was used in bo).
My first suggestion would be to check the status of the netstd
package, since most of your problems seem to be related to commands
provided by this package. If that doesn't help, perhaps someone more
knowledgeable about these networking programs will come to your
rescue.
--
_
|_) _ |_ Robert D. Hilliard <hilliard@metrolink.net>
|_) (_) |_) Palm City, FL USA PGP Key ID: A8E40EB9
--
Dale Harrison <dth@cns.aust.com> wrote:
> Got a bit of a problem here. Actually, it a LOT of a problem.
>
> I had a fairly standard bo installation. I ran the autoupgrade.sh script,
> which seemed to work, kind of. It missed a whole lot of stuff in /oldlibs
> and some stuff in /base when retrieving everything, so the system was in a
> half upgraded state.
>
> Well, since then, I manually upgraded everything. Everything now seems to
> work... for about 3 hours. No, I kid you not.
>
> After the 3 hour mark [or thereabouts], all hell breaks loose.
>
> - I can't telnet to the outside world from the box
> - I CAN telnet into it
> - I can't telnet to myself [localhost]
> - I can't ftp in or out of the box
> - I CAN use ssh to get out of the box.
> - Sendmail won't accept connections on port 25
>
> Confused? Yeah, me too.
>
> % telnet localhost
> Trying 127.0.0.1...
>
> [sits there indefinitely]
>
> % telnet outside.world.com
> Trying 123.123.123.123...
>
> [sits there indefinitely]
>
> As I said, I can telnet into the box from the outside world (technically
> then, shouldn't sendmail accept stuff?), just not the other way round.
>
> It's not a problem with the ISP (I wish it was...) any ideas what could be
> causing something like this? At the moment my solution entails rebooting
> them machine every 2.5 hours via cron :)
>
> I've looked through the logs to see if anything out of the ordinary has
> popped up.. seems not.
>
> Please, please, I beg of you, help me in my hour of need. :)
>
> Thanks,
> D.
>
>
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> debian-user-request@lists.debian.org .
> Trouble? e-mail to templin@bucknell.edu .
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: