Environment
Situation
"EXT4-fs (sdb1): couldn't mount as ext3 due to feature
incompatibilities"
"Failed to mount /vatemp"
Resolution
If you need to export
the DB and import it to a new instantiation of an VA. Be warned that if this is done on a small,
all-in-one appliance, any attachments and avatars will not come across as they
are stored on /vastorage. In this case
you will also need to get what is under /vastorage/esn/filerepository/kablink
kablink.encryption.key=MTg5OTUwNjM2MQ==
pg_dump
--username=postgres --dbname=esn > 81dbexport.pgsql
3b. tar zcvf cachefilestore.gz
/vastorage/esn/cachefilestore/ and copy it to a local drive
DROP
DATABASE dbname;
CREATE
DATABASE dbname;
CREATE
ROLE role;
ALTER
ROLE role WITH CREATEDB;
ALTER
ROLE role WITH INHERIT;
ALTER
ROLE role WITH LOGIN;
7b. Import the new DB from the export
in step 2, psql –U postgresUsername dbName < dbexport.pgsql
psql
--username=postgresUsername --dbname=dbName < dbexported.pgsql
Under
/esninstall/db Open the postgres properties files and change the encrypted
passwords to novell or whatever the DB password is.
sh
manage-database.sh postgresql updateDatabase
You
may have to force this untar on the target system or just untar to a tmp
directory and then manually cp –R the contents of the untarred kablink
directory
12b. tar zxvf cachefilestore.gz
/vastorage/esn/cachefilestore/
run /opt/elasticsearch/plugins/search-guard-5/tools/hash.sh
tw-admin and again for tw-user and. . .
1. Specify
the passwords for each when prompted – set it to “novell” as this was the hard
coded value in the db at the time this particular migration process was done in
2018.
2. Copy the
hash of each and paste it their key value pairs in
/opt/elasticsearch/plugins/search-guard-5/sgconfig/sg_internal_users.yml
3. Run
/opt/elasticsearch/plugins/search-guard-5/tools/sgadmin_esn.sh
4. Restart
elasticsearch
***18. this step may or may not be
necessary: “update SS_LdapConnectionConfig set credentials = null;”
If it is necessary then step 15 will
apply as well.