Hi, I'd suggest to revert to 3.8.3, it should be fairly easy with the /etc/one and DB backups.
If possible, try to keep or replicate your current 4.0.1 installation so we can try to find out what went wrong. At least the DB. I would need to take a look at the exact command that crashes oned, and the xml resources involved. Maybe we can see something in the onevm list -x and oneimage list -x output, please send those (off-list if you prefer). Regards -- Join us at OpenNebulaConf2013 <http://opennebulaconf.com> in Berlin, 24-26 September, 2013 -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula<http://twitter.com/opennebula><[email protected]> On Fri, Jun 21, 2013 at 12:09 PM, André Monteiro <[email protected]>wrote: > Hi, > > I've migrated from 3.8.3 to 4.0.1 yesterday, but I'm getting a lot of > errors. > > 1. oned returns segmentation fault after a couple of actions, either on > cli or sunstone. downloaded latest files from repository /src/nebula, > compiled and replaced oned, it's more stable but crashes sometimes > > 2. onedb migration said successful, but vm list on sunstone is empty and > onevm list lists well > > 3. registered images on datastore 1 (default) are listed and have all > properties, but all have 0MB and cannot be used > > Any ideas? I have 50 Msc students depending on ONE... > > Opennebula running smoothly on SL6.2 x64 for over 2 years. > > -- > André Monteiro > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
