No, I am testing on the /example directory so I am using local HSQLDB I copied lock-clean.sh script from the /usr/share/manifoldcf/multiprocess-file-example to the /usr/share/manifoldcf/example to try to clean-up my situation, but perhaps the script isn’t good for me because I am using jetty on the example directory?
Thanks Da: Karl Wright <[email protected]> Inviato: martedì 12 giugno 2018 15:23 A: [email protected] Oggetto: Re: Job in aborting status Hi Mario, It appears you are trying to use embedded HSQLDB in a multiprocess environment. That is not possible. In a multiprocess environment, you have the following choices: (1) standalone HSQLDB (2) postgresql (3) mysql Thanks, Karl On Tue, Jun 12, 2018 at 9:06 AM Bisonti Mario <[email protected]<mailto:[email protected]>> wrote: Thanks Karl. I tried to execute lock-clean from my example directory after I stop manifoldcf but I obtain: administrator@sslrvivv01:/usr/share/manifoldcf/example$ sudo -E ./lock-clean.sh Configuration file successfully read Synchronization storage cleaned up 2018-06-12 15:03:35,395 Shutdown thread FATAL Unable to register shutdown hook because JVM is shutting down. java.lang.IllegalStateException: Cannot add new shutdown hook as this is not started. Current state: STOPPED at org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry.addShutdownCallback(DefaultShutdownCallbackRegistry.java:113) at org.apache.logging.log4j.core.impl.Log4jContextFactory.addShutdownCallback(Log4jContextFactory.java:271) at org.apache.logging.log4j.core.LoggerContext.setUpShutdownHook(LoggerContext.java:256) at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:216) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:146) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41) at org.apache.logging.log4j.LogManager.getContext(LogManager.java:270) at org.apache.log4j.Logger$PrivateManager.getContext(Logger.java:59) at org.apache.log4j.Logger.getLogger(Logger.java:37) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.hsqldb.lib.FrameworkLogger.<init>(Unknown Source) at org.hsqldb.lib.FrameworkLogger.getLog(Unknown Source) at org.hsqldb.lib.FrameworkLogger.getLog(Unknown Source) at org.hsqldb.persist.Logger.getEventLogger(Unknown Source) at org.hsqldb.persist.Logger.logInfoEvent(Unknown Source) at org.hsqldb.persist.DataFileCache.logInfoEvent(Unknown Source) at org.hsqldb.persist.DataFileCache.open(Unknown Source) at org.hsqldb.persist.Log.getCache(Unknown Source) at org.hsqldb.persist.Logger.getCache(Unknown Source) at org.hsqldb.persist.Logger.newStore(Unknown Source) at org.hsqldb.persist.PersistentStoreCollectionDatabase.getStore(Unknown Source) at org.hsqldb.Table.getRowStore(Unknown Source) at org.hsqldb.TableBase.isEmpty(Unknown Source) at org.hsqldb.TableWorks.addIndex(Unknown Source) at org.hsqldb.StatementSchema.getResult(Unknown Source) at org.hsqldb.StatementSchema.execute(Unknown Source) at org.hsqldb.Session.executeCompiledStatement(Unknown Source) at org.hsqldb.scriptio.ScriptReaderText.readDDL(Unknown Source) at org.hsqldb.scriptio.ScriptReaderBase.readAll(Unknown Source) at org.hsqldb.persist.Log.processScript(Unknown Source) at org.hsqldb.persist.Log.open(Unknown Source) at org.hsqldb.persist.Logger.open(Unknown Source) at org.hsqldb.Database.reopen(Unknown Source) at org.hsqldb.Database.open(Unknown Source) at org.hsqldb.DatabaseManager.getDatabase(Unknown Source) at org.hsqldb.DatabaseManager.newSession(Unknown Source) at org.hsqldb.jdbc.JDBCConnection.<init>(Unknown Source) at org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown Source) at org.hsqldb.jdbc.JDBCDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:664) at java.sql.DriverManager.getConnection(DriverManager.java:247) at org.apache.manifoldcf.core.database.DBInterfaceHSQLDB.closeDatabase(DBInterfaceHSQLDB.java:161) at org.apache.manifoldcf.core.system.ManifoldCF$DatabaseShutdown.closeDatabase(ManifoldCF.java:1680) at org.apache.manifoldcf.core.system.ManifoldCF$DatabaseShutdown.doCleanup(ManifoldCF.java:1664) at org.apache.manifoldcf.core.system.ManifoldCF.cleanUpEnvironment(ManifoldCF.java:1540) at org.apache.manifoldcf.core.system.ManifoldCF$ShutdownThread.run(ManifoldCF.java:1718) What could I do? Thank you very very much for your help. Mario Da: Karl Wright <[email protected]<mailto:[email protected]>> Inviato: martedì 12 giugno 2018 14:26 A: [email protected]<mailto:[email protected]> Oggetto: Re: Job in aborting status Hi Mario, Two things you should know. First, if you have very large jobs, it can take a while to abort them. This is because the documents need to have their document priority cleared, and that can take a while for a large job. Second, what you describe sounds like you may have stuck locks. This can happen if you are using a multiprocess setup and are using file-based synchronization and you kill jobs with kill -9. To clean this up, you need to perform the lock-clean procedure: (1) Shut down all manifoldcf processes (2) Execute the lock-clean script (3) Start up the manifoldcf processes Thanks, Karl On Tue, Jun 12, 2018 at 7:11 AM Bisonti Mario <[email protected]<mailto:[email protected]>> wrote: Hallo. I have jobs in aborting status and it hangs. I tried to restart manifoldcf, I restarted the machine, but the job hangs in aborting status. Now, I am not able to start every job because they stay in starting status How could I solve it? Thanks.
