[indiana-discuss] Problems with ifconfig and others

[Brian Banister]

I'm running Indiana, snv_111, with xvm as my dom0 for a home server.  The system has generally been flaky, not just with 111 but prior versions as well.  When I run "ifconfig -a", I see the information for lo0 and the first line of information for rge0.  Ifconfig is then hung and I must issue a Ctrl-C to kill it.  Oddly, if I run the command shortly after bootup, it will often complete.  For example, with an uptime of 5 minutes, it works.  At 8 minutes of uptime, it no longer works.

Other odd behaviors: (many likely unrelated, but trying to be complete)

- starting bind (SUNWbind) often fails during boot because the directory /var/run/named does not exist.  Resolved by "mkdir /var/run/named; svcadm clear dns/server" until next reboot.

- xen occasionally gets lost.  If I stop and start a domU a few times, xen may stop being able to start vms.

- shutdowns - the vms may not shut down properly, making the dom0 take a long time (if ever) to shut down or reboot.

- nfs/rquota and rpc/rstat do not start.  Logs show messages like "Property 'name' of instance svc:/network/nfs/rquota:default is missing, inconsistent or invalid"  I've never altered the properties for these so I don't know why they should be invalid etc.

- OpenOffice lacks spell checking.

I've also had problems with the network simply disappearing for a period of time, perhaps many minutes.  Based upon this and ifconfig hanging, I assumed bad hardware  so I replaced the motherboard but the ifconfig problems remain.  I've been up on the new motherboard for less than 24 hours so I can't comment yet on if the network outage problems are fixed.

Should I be assuming I have a confused install?  Is there a way to force a re-install of all packages as a means to try to clean up some of this?  Should I still be suspecting hardware problems?
-- 
This message posted from opensolaris.org