Hi again, > Does anyone have any thoughts, suggestions, pointers etc on how I might > resolve this issue
I think I may have (finally!) stumbled on the 'root' of the problem - it looks like it was a permissions issue (argh!). I finally realised that /tmp/DSpaceHibernateCache and its contents were owned by root - I chowned these to tomcat8:tomcat8 (the user my dspace runs as) and it looks like things have started to work again (I tested ./dspace sub-daily and the subscription email was sent this time!). So, apologies for the noise - I'm not at all sure how (or when) these permissions may have got set wrong, but hopefully (at the very least), if anyone else hits this problem then this thread will help them resolve the issue! Cheers, Mike Michael White Senior Developer Business Applications and Integrations T: (01786) 466877 E: michael.wh...@stir.ac.uk<mailto:michael.wh...@stir.ac.uk> A: 4B19, Cottrell, University of Stirling, Stirling, FK9 4LA From: Michael White Sent: 10 July 2019 10:15 To: dspace-tech@googlegroups.com Subject: Problem with dspace launcher Hi, DSpace v6.2, JSPUI, Debian, openjdk v1.8.0_212, Tomcat 8 . . . I have just noticed that our overnight cron jobs that make use of the dspace launcher (e.g. dspace generate-sitemaps, dspace sub-daily, dspace index-discovery, etc) have not been running - and it looks like they haven't been running for a while (although I'm 99.9% sure they were all working when I upgraded to DSpace v6.2 18 months ago!). I first realised that I wasn't get the daily subscription emails any more, so implemented the fix(es) outlined here: https://jira.duraspace.org/browse/DS-3769 This worked perfectly on my DEV system, but on my PROD system, I still wasn't getting the subscription emails, so investigated further and realised that none of the overnight cron jobs were running. Scanning the logs, I can see the same output at the point when each of these jobs is supposed to run: 2019-07-10 09:40:09,718 WARN net.sf.ehcache.CacheManager @ Creating a new instance of CacheManager using the diskStorePath "/tmp/DSpaceHibernateCache" which is already used by an existing CacheManager. The source of the configuration was net.sf.ehcache.config.generator.ConfigurationSource$URLConfigurationSource@abf2fb3<mailto:net.sf.ehcache.config.generator.ConfigurationSource$URLConfigurationSource@abf2fb3>. The diskStore path for this CacheManager will be set to /tmp/DSpaceHibernateCache/ehcache_auto_created_1562748009718. To avoid this warning consider using the CacheManager factory methods to create a singleton CacheManager or specifying a separate ehcache configuration (ehcache.xml) for each CacheManager instance. 2019-07-10 09:40:09,732 FATAL org.dspace.core.Context @ Cannot obtain the bean which provides a database connection. Check previous entries in the dspace.log to find why the db failed to initialize. The schema validator returned: Unable to create requested service [org.hibernate.engine.spi.CacheImplementor] 2019-07-10 09:40:09,733 FATAL org.dspace.eperson.SubscribeCLITool @ org.dspace.core.exception.DatabaseSchemaValidationException: The schema validator returned: Unable to create requested service [org.hibernate.engine.spi.CacheImplementor] But the database connection test works: ------------------------------------------- tomcat8@dspace:/usr/local/dspace/bin$ ./dspace database test Attempting to connect to database Connected successfully! Database Type: postgres Database URL: jdbc:postgresql://localhost:5432/dspace Database Schema: public Database Username: dspace Database Software: PostgreSQL version 9.6.13 Database Driver: PostgreSQL Native Driver version PostgreSQL 9.4.1211 PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3) ------------------------------------------- And so does sending a Test email: ------------------------------------------- tomcat8@dspace:/usr/local/dspace/bin$ ./dspace test-email About to send test email: - To: michael.wh...@stir.ac.uk<mailto:michael.wh...@stir.ac.uk> - Subject: DSpace test email - Server: smarthost.stir.ac.uk Email sent successfully! ------------------------------------------- - so it seems to be "OK" for 'simple' use cases (test email, database connection test), but fails for more 'complex' use cases (generate-sitemaps, sub-daily, index-discovery) . . . (?) I have tried "turning it off and on again" but that didn't seem to change anything (Tomcat restart - no joy; rebuild/redeploy - no joy; restart the server - no joy). I also tried increasing the memory allocated to Java in the launcher script: ------------------------------------------- #Allow user to specify java options through JAVA_OPTS variable if [ "$JAVA_OPTS" = "" ]; then #Default Java to use 256MB of memory JAVA_OPTS="-Xmx1024m -Dfile.encoding=UTF-8" fi ------------------------------------------- - but that doesn't seem to have helped either. I've tried Googling for all the various log messages, but that hasn't turned up anything thus far . . . Does anyone have any thoughts, suggestions, pointers etc on how I might resolve this issue (as it is obviously fairly critical that we get all these jobs running again!)? Many thanks as ever, Mike Michael White Senior Developer Business Applications and Integrations T: (01786) 466877 E: michael.wh...@stir.ac.uk<mailto:michael.wh...@stir.ac.uk> A: 4B19, Cottrell, University of Stirling, Stirling, FK9 4LA ________________________________ The University achieved an overall 5 stars in the QS World University Rankings 2018 The University of Stirling is a charity registered in Scotland, number SC 011159. -- 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 Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/DB7PR03MB50970F95A92658D0DFD253FDD4F00%40DB7PR03MB5097.eurprd03.prod.outlook.com.
