Well, figures after I make a cry for help, I got it to start behaving.
AFter probably the 10th reinstall of the guest, I started getting
of the name I was using. This may have no bearing on what the real
problem was but.... I was calling this guest wwwint and I already have a
guest named www. Two days ago when I started this whole thing, I decided
to call the new guest www2. Well, the system built it okay, but then it
confused www with www2. Had all kinds of problems with that. I assumed
it didn't like a numeric in the name. So decided wwwint. This go around,
I deleted the guest again, and changed the name to intwww. Rebooted the
entire machine. Now it's happy. Netstat doesn't hang any more and the
base-config completed okay. So this is making me think that there was
some resident confusion with the guest names both starting with "www".
Seems odd to me, but it sure fixed my problem...!
> sounds like base-config does mess with the networking,
> let's check the following here:
> - /proc/virtual/<xid>/status (for caps)
> - ip addr ls (before and after the base-config)
> - ip route ls (again, before and after)
> (you might need to install the 'ip' utility from iproute2)
> that sounds like a wget bug, would not be the first one :)
> > None of my other vservers have this problem and neither does the root
> > server.
> > Any ideas as to how to troubleshoot this better than I'm obviously
> > doing here?
> yep, try to provide the data mentioned above, and/or pay
> a visit to the irc channel (#vserver @ irc.oftc.net) for
> a more interactive experience :)
> > Thanks again for the help.
> > Kathy
> > _______________________________________________
> > Vserver mailing list
> > Vserver@list.linux-vserver.org
> > http://list.linux-vserver.org/mailman/listinfo/vserver
Vserver mailing list
Received on Fri Aug 25 05:27:51 2006