Finished:
(or so it seems)

After examining the Solr logs, I discovered many complaints about the 
'tlog' files not being in /dspace/solr/statistics/data/tlog. In fact there 
were no 'data' directory created at all.

I performed a full system reboot, and then conducted the dcspace utility 
/dspace/bin/dspace index-discovery (which took a while to perform). The 
Dspace installation was running normally again and now the previously 
missing directories and files had appeared.

Summary: I am not exactly sure where my problem came from, but it may be 
important to repeat... This was a fresh install, made as a practice effort 
to see if I could fully backup and restore a live machine on to another 
remote server. I installed the prerequisites on my new, test system. I 
performed a DSpace installation and was able to reach the default home page 
with my web browser (from another machine on my network). I used the Dspace 
command line utility (via SSH) to create an administrator user. I then used 
AIP package import utility to install a pre-existing database, as mentioned 
earlier in this thread. This all completed well, but here is where I began 
to see problems. I believe my error was in not re-loading daemons or 
rebooting entirely, after the basic DSpace installation. Although Tomcat 
was running and was able to serve the default DSpace page, I am presuming 
there were other initial tasks needed, which would happen with a reboot. 
My test system has now been idle for about 10 hours and is still performing 
normally, so I am presuming my strange problem is fixed. Restart, or 
re-boot after making major system changes! It seems to be a wise general 
policy.

On Wednesday, June 17, 2020 at 6:09:43 PM UTC-4, Chris Clawson wrote:
>
> Update:
>
> My /dspace/solr/statistics/data directory doesn't exist. Solr tries to use 
> directories in this area and throws errors. Perhaps this is what breaks 
> things. I have no idea why these directories were not created. 
> After installing Dspace, with maven and ant, all I did before importing 
> the AIP was to define an admin user. 
>
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/47c837b4-870d-4121-b783-a374992556efo%40googlegroups.com.

Reply via email to