Seems that one of my installations have a corrupt database.
It prevents that the vsom instance starts.
170116 13:45:33 InnoDB: Using Linux native AIO
170116 13:45:33 InnoDB: Initializing buffer pool, size = 64.0M
170116 13:45:33 InnoDB: Completed initialization of buffer pool
170116 13:45:33 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
170116 13:45:33 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: Database page corruption on disk or a failed
InnoDB: file read of page 45.
InnoDB: You may have to recover from a backup.
170116 13:45:33 InnoDB: Page dump in ascii and hex (16384 bytes):
I wanted to star fresh with a new DB instance instad of reinstalling everyhting from scrach.
database_creat.sh does not work unless the mysql starts propery.
Any idea how I can fix this? Would deleteing the DBs and restart the sql service help?
Thanks for your hint.
Thanks very much for your hint. I fully agree, but in this case, the VSOM service does not start and therefore I have no access to any web gui.
My question would be: can I delete the database and run one of those db scripts?
I can live with a fresh setup, saves me still time than starting from scratch.
While it's possible the BU may not be pleased with me for relaying this information, there *is* a shell script in the upgrade packages that can quickly 'pave' a VSM install.
# Name : install_VSM.sh
# and will also
# This script can
# 1. "-dev" option for
# 2. "-uninstall" option to uninstall VSM.
# 3. "-uninstall-Cisco" option to uninstall Cisco RPMs.
# 4. Fresh install of Cisco & OS RPMs extracted from upgrade image.
# 5. Upgrade to
# 6. Upgrade when VSM-version.xml file is missing.
I typically run an '-uninstall' and then a typical install. Be patient as the post processing after the script has ended may still be restarting services and triggering changes.
I've been keeping a VSM7.8 source directory tucked away in a media repo on our own lab server, along with
Thankfully, at least Cisco is acknowledging they have a problem now:
CSCvc16759 Mysql fails to start after a hard power failure
Thanks for your helpful hint (again). I also was wandering through those many .sh files in the hope to find a useful one.
Indeed, the problem started with a power issue. Since this is one of mine own ones, no worries with TAC... :-)
Same boat for me. Glad I could be of some assistance :-)
P.S. - I've since actually gone the extra step of getting a small USB UPS attached to the VSM lab box. The LINUX 'NUT' project has
Great idea. That is worth a try and I wonder why this is not already part of the GUI. Will have a talk to the PM about that in a few weeks.