computer lockups [solved]

[Victor T.]

My computer constantly locks up and I am at a loss to figure why. I've tried monitoring using top in a console. I've also checked the log files. I get a message that " vnstatd (2200) error:database load failed even when using backup. aborting."

The nest line states "last message repeated X times." This line repeats and repeats.

I have Mandriva 2010 power pack installed on a computer with AMD athlon 64 2x on a gigabyte motherboard. I have a second computer set up almost identical to this one and it has no problems.

What database is vnstatd trying to access? The lockups are very frustrating. The only recovery method is the reset button on the front of the computer. Any help is appreciated.

[ianw1974]

Have you tried running memtest? Before you do this, go into the BIOS and choose Load Optimised Defaults (if your BIOS has this), and then run memtest.

[Victor T.]

I tested my memory awhile back and it passed. I have 4 gigs installed and the system monitor shows 3.7 gig available.

The crashes have been very erratic. some days I start up the computer and after the system completely loads it is locked up and I have to reset. Then it starts up okay and I can run for awhile and it locks up again. I cannot reproduce the problem. It

seems random and the only thing is the message bout vnstatd error that keeps repeating

[Victor T.]

I just redid the memtest. It took about 2 and a half hours and my computer passed. I'll keep monitoring the system log viewer. The error message is still getting repeated. Later I'll try to Kill the process and see if I can go without a lockup.

[daniewicz]

I found this solution at the following website: http://fernando-acero.livejournal.com/

 

translation by Google

 

 

 

vnstatd[xxxx]: Error: Database load failed even when using backup. vnstatd [xxxx]: Error: Database load failed even when using backup. Aborting. Aborting.

 

The solution is to open a console as root, go to / var / lib / vnstat and delete all files in it, considering that there are hidden files, for example using mandates, which would eliminate the primary database and the security (hidden file) of the eth0 interface.

 

rm -rf eth0 rm-rf eth0

rm -rf .eth0 rm-rf. eth0

 

Then, create a new database using the term.

 

vnstat -u -i eth0 vnstat-u-i eth0

 

This command must be repeated with each interface in the system we have, for example, using the usb modem, we must also create a database for PP0 interface through the command:

 

vnstat -u -i pp0 vnstat-u-i PP0

[Victor T.]

This is heavy!! I'll give it a try . In the meantime this is what happened today.

 

I turned on my computer and it opened up to the dsktop. I moved the mouse and it immediately locked up. I hit reset and reloaded. I opened up the log files and while I was reading the files it locked up again.

I hit rest and reloaded. I immediately went ot the log files and found the entry where it locked up and took a snapshot and mhere is the snapshot. Right after the vnstatd message it claims there is a bug. Can this also be part of the problem?

 

In the meantime let me see about trying to fix it according to your directions.

[Victor T.]

I found this solution at the following website: http://fernando-acero.livejournal.com/

 

translation by Google

...

 

Thank you for this post. I finally struggled through entering the commands in a terminal. I am not an epert in the trminal and so it took a couple of tries to get the commands to be accepted.

 

The eth0 file got recreated in the vnstat folder but the hidden .vnstat did not. However I see in the logs filed=s that vnstatd gets opened and the eror message no longer appear.

 

However I am still experiencing computer lockups so the vnstat was not entirely at fault.

 

Does anyone have any suggestions short of reinstalling the operating system which at this time may be all that I know how to do??

[daniewicz]

Well since your memory tested OK my next guess would be a defective power supply. Do you have another you could use temporarily for testing?

[Victor T.]

Yesterday i couldn't get my computer to boot. I kept stopping at ar about the Tomoyo program whatever that is. So in frustration I reinstalled the Mandriva poweer pack opeerating system.

I remember reading about some people having troubles and it was the memory boards not being fully seated so today i took mine out of their sockets and swapped them and made damn surre they are prorperly snapped into their sockets.

So right now the only problem I am seeing is the difficulty of getting my HP printer back i the good figureation that it was before.

Now it is a matter of time to see if the problem crops up again

So thank you and I'll close this for now.

[daniewicz]

some people having troubles and it was the memory boards not being fully seated so today i took mine out of their sockets and swapped them and made damn surre they are prorperly snapped into their sockets.

 

If the memory sticks were not properly inserted then memest would detect errors.

[Ixthusdan]

Memory, hard drive, power supply, in that order.

 

If it takes time to error, I would go for hard drive or power supply, as it may indicate a thermal issue. If it happens immediately, I would look at the memory or the processor. (note: with a possible processor problem, you also have to evaluate the chip set.)