Cool. I did a new port of my VMware appliance and like before I chose not to edit my conversion. This time I also didn't enable the Google Maps thingy, and I also applied the GoogleMaps patch -- but just the map patch. Are there others?
I'm not seeing the crashes that I was seeing and I am able to add some of my more complicated devices. However, my comlaint now is that the performance is very slow. It takes forever to do an add -- like 10 minutes or more -- and the device becomes unusable during that time. I also experience this problem fairly consistently, like this morning. > [EMAIL PROTECTED] /] /etc/init.d/mysqld status > mysqld dead but subsys locked zenoss is unusable at this point until I restart the mysql daemon of course. A quick review of the '/var/log/mysqld.log' file reveals about a dozen or more of these messages: > 071031 06:07:39 mysqld restarted > 071031 6:07:43 InnoDB: Database was not shut down normally! > InnoDB: Starting crash recovery. > InnoDB: Reading tablespace information from the .ibd files... > InnoDB: Restoring possible half-written data pages from the doublewrite > InnoDB: buffer... > 071031 6:07:45 InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 0 2934884. > InnoDB: Doing recovery: scanned up to log sequence number 0 2934884 > 071031 6:07:46 InnoDB: Started; log sequence number 0 2934884 Any ideas? Right now, I think I'm going to try out a CentOS deployment to see if I can get better performance and stability, but for now the appliance isn't for me. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=12539#12539 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
