Guys, I reinserted my backup.sql in an empty datab...
# troubleshoot
s
Guys, I reinserted my backup.sql in an empty database via sqlcmd because the file was too big to use using the datahub-cli:
Copy code
python3 -m datahub docker quickstart --restore --restore-file ../datahub/docker/quickstart/backup_2023_01_10.sql
but despite the data being already inserted in the database, I still don't see anything through the ui. What should I do? Because when I use the command above I receive [2023-01-10 233638,311] ERROR {datahub.cli.docker_cli:353} - Failed to run MySQL restore
✅ 1
h
If you are sure that data is already inserted into mysql database, you just need to restore indices for elasticsearch to be able to see it in UI. https://datahubproject.io/docs/how/restore-indices/
s
@hundreds-photographer-13496 I tried but only receiving it Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ebeanServer' defined in class path resource [com/linkedin/gms/factory/entity/EbeanServerFactory.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [io.ebean.EbeanServer]: Factory method 'createServer' threw exception; nested exception is java.lang.NullPointerException
h
okay.. this usually means that its not able to connect to mysql instance. Is mysql instance up ? Which command are you using to restore indices ? and where do you see this error ?
hmm.. could you stop the acryldata/datahub-upgrade container that you have explicitly started. and just try the quickstart command again ?
Noticed that
--network datahub_network
is missing in your connector run command but can stick to quickstart for now and try again. I wonder if the container created earlier interfered with quickstart restore indices
s
The first error was like that
Copy code
java.lang.RuntimeException: Request cannot be executed; I/O reactor status: STOPPED
IT WOOOOOOOOOOOORKED! @hundreds-photographer-13496
Copy code
sh /home/ubuntu/datahub/docker/datahub-upgrade/datahub-upgrade.sh -u RestoreIndices -a clean
h
That's great ! Although I am not sure exactly what was wrong earlier 😄