Unsolved
This post is more than 5 years old
1 Message
0
9719
April 18th, 2011 13:00
VDI Assessment Database corruption issue
We have a VDI installation that has lost its connection to the Database.
The server is installed on in a Xen environment and set up for 2GB of RAM and 1 CPU. It was consuming 96% of the CPU resources, so we wanted to add 1 CPU and some more RAM. From the Web Interface, we didn’t find a graceful way to shut it down, so it was shut down via the Xen console power button. The CPU and RAM were added and, on restart, the web interface was not accessible by using the default admin name and password. We then shut the system down and removed the added CPU and RAM, and this had no positive effect. At this time it will not do a disk dump or connect to the database.
We have about 10 days worth of data and I really don't want to start over again. If anyone has an idea on how to get the database to cooperate again, we'd really appreciate it.
Alex
snayar
2 Posts
0
April 19th, 2012 14:00
I find this odd!
Yesterday (same day as you but a year later) I noticed I couldn't use the VDI Assessment Tool anymore and upon further inspection through the console, I found the "Could Not Connect to Database" error.
In retrospective, I remember that the tool's performance degraded over the last few days prior to the "database failure", it took longer than usual just to log in and even more noticeable on the reporting screen. In our case, we didn't tinker with the virtualization settings at all as it was working just fine.
The last time I was able to log in, I was processing a report and after hours of waiting for it to finish, it simply prompt an error (I forgot what it said), but I'm sure its got something to do with the failure.
In our case is even more critical since we had more than two month's worth of data and we are on a tight schedule!
Where you able to get something from Quest or somebody else?
I will try to contact Quest tech support and post my findings.
Cheers!
Sergio
mlevine1
14 Posts
0
April 20th, 2012 06:00
Hi Sergio,
I didn't pick up on Alex's post a year ago, but at a glance it doesn't seem like you have the same problem. As it was a year ago I don't know the outcome of Alex's problem - that said the appliance is released to run on either a VMWare or MS Hyper-V hypervisor - I've never tried to run it on Xen.
Back to your problem. It's going to be difficult to know what's happening without the appliance (Hub) logs.
One thing you can do is make sure there is enough space on /dev/sdb1 as the database is on /var/log/pgsql which is mounted on /dev/sdb1. If you need to increase the size of the disk, take a look at this discussion : http://communities.quest.com/thread/2270?tstart=0
I'll take this offline with you.
Thanks,
Mark.
snayar
2 Posts
0
May 3rd, 2012 15:00
Thank you for all your help Mark, you where a life-saver
The system's been woring fine since you helped me via email.
Cheers!
Sergio