I'm having some issues with the new storage box I am testing using Solaris 11 Express. I've been busy so I haven't been testing with it for a number of days/weeks. I come back to the system and I notice that the dbus-daemon is using 100% CPU. That in itself is strange because I have a quad-core Xeon and the graphs show that all the core's percentages add up to 100% but each core is not at 100%. However I don't think it should be using even that much to begin with.
I did some googling and I see some references to a bug and possible memory leak... Great, just what I want in a stable storage platform. So I figure I'll just reboot it as I'm not using any of the storage yet. I reboot it through the GUI and now just trying to shut down is not working. It is scrolling the following down the screen:
It has been doing this for the last 45 minutes. Anyone have any ideas on this? I am a little reluctant to just hit the power because when I did that before, it took 2-3 days to boot up!! I don't know if it was doing some kind of thorough scrubbing of the disks or what but this is getting frustrating.
I did some googling and I see some references to a bug and possible memory leak... Great, just what I want in a stable storage platform. So I figure I'll just reboot it as I'm not using any of the storage yet. I reboot it through the GUI and now just trying to shut down is not working. It is scrolling the following down the screen:
svc.startd[9]: svc:/network/iscsi/target:default: Method or service exit timed out. Killing contract 19417.
It has been doing this for the last 45 minutes. Anyone have any ideas on this? I am a little reluctant to just hit the power because when I did that before, it took 2-3 days to boot up!! I don't know if it was doing some kind of thorough scrubbing of the disks or what but this is getting frustrating.