Unable to delete Certain Space,files and folders

[predatorz]

Hi All,

I have a problem here (As topic)
I mapped a network drive to alfresco in my workstation, created a folder and was transferring a lot of stuff over to alfresco and my workstation hanged. After which, those folders and files that were transferred over to alfresco, I am not able to remove them away.

I tried from the network mapping to delete them away after halfway but it will fail.

What can i do?

Using Alfresco Community 2.1.0.

[predatorz]

Hi, i did re-index the lucene indexes, the logs show recovery 100% but when change back index.recovery.mode back to VALIDATE (Original Setting), alfresco is unable to start up. the process is running but unable to access the web ui or via CIFS. Below are the logs.

10:54:34,036 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent] Index recovery started: 50,251 transactions.
10:55:41,805 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    10 % complete.
11:00:09,048 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    20 % complete.
11:10:12,883 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    30 % complete.
11:29:05,892 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    40 % complete.
11:55:47,768 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    50 % complete.
12:32:21,396 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    60 % complete.
13:19:51,435 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    70 % complete.
14:17:30,896 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    80 % complete.
15:25:58,420 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    90 % complete.
16:30:04,704 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent]    100 % complete.
16:30:04,778 INFO  [org.alfresco.repo.node.index.FullIndexRecoveryComponent] Index recovery completed.

16:38:59,299 ERROR [org.alfresco.repo.content.transform.magick.AbstractImageMagickContentTransformer] ImageMagickContentTransformer not available: Failed to perform ImageMagick transformation:
Execution result:
   os:         Linux
   command:    convert /opt/alfresco/tomcat/temp/Alfresco/ImageMagickContentTransformer_init_source_24997.gif  /opt/alfresco/tomcat/temp/Alfresco/ImageMagickContentTransformer_init_target_24998.png
   succeeded:  false
   exit code:  1
   out:
   err:        java.io.IOException: convert: not found
16:39:05,043 WARN  [org.springframework.remoting.rmi.RmiRegistryFactoryBean] Could not detect RMI registry - creating new one
16:39:06,945 WARN  [org.alfresco.util.OpenOfficeConnectionTester] A connection to OpenOffice could not be established.
16:39:11,825 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] Schema managed by database dialect org.hibernate.dialect.MySQLInnoDBDialect.
16:39:18,916 INFO  [org.alfresco.repo.domain.schema.SchemaBootstrap] No changes were made to the schema.
16:39:22,731 DEBUG [org.alfresco.repo.node.index.FullIndexRecoveryComponent] Performing index recovery for type: VALIDATE
16:39:26,645 WARN  [org.alfresco.repo.admin.ConfigurationChecker] The Alfresco 'dir.root' property is set to a relative path './alf_data'.  'dir.root' should be overridden to point to a specific folder.
16:39:26,645 INFO  [org.alfresco.repo.admin.ConfigurationChecker] The Alfresco root data directory ('dir.root') is: ./alf_data
16:39:27,085 ERROR [org.alfresco.repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: Indexes not found for 5 stores.
16:39:27,085 INFO  [org.alfresco.repo.admin.ConfigurationChecker] You may set 'index.recovery.mode=FULL' if you need to rebuild the indexes.
16:39:27,085 ERROR [org.alfresco.repo.admin.ConfigurationChecker] Ensure that the 'dir.root' property is pointing to the correct data location.
16:39:27,090 ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: Ensure that the 'dir.root' property is pointing to the correct data location.
"alfresco.log" 597L, 54720C


I tried index.recovery.mode=NONE,AUTO,VALIDATE and all return similar errors. What can i do?  :cry:
i change dir.root to the full absolute path also the same problem.

[predatorz]

Oh, i have tried to rebuild the lucene index for 3 times, all 3 times when i try to start alfresco, it throws the below error.  :cry:

[mruflin]

Unfortunately it's really hard to help you with that little information.

Does Alfresco run correctly when starting with index.recovery.mode=FULL? Can you access the web client when running Alfresco in recovery.mode=FULL? Does search work? Can you check in alf_data whether the lucene indexes directories have been created?

Note that you have to wait until Alfresco really responds to user request before restarting again with another recovery.mode. You can let Alfresco run after starting it with mode.FULL, this flag is only checked during startup, so once you started Alfresco just change the mode back but don't restart right away.

[predatorz]

Does Alfresco run correctly when starting with index.recovery.mode=FULL?Can you access the web client when running Alfresco in recovery.mode=FULL? Does search work? Can you check in alf_data whether the lucene indexes directories have been created?

After the logs show index 100% recovery, still unable to access to the web client, but the whole system will be very very slow, crawling, with nothing new lines appended to the logs. I can see the directory lucene index in alf_data but the size of the lucene index directory is very small.

The above happen everytime i rebuild the lucene indexes.
Does this mean the alfresco is still rebuilding?
ops:

[mruflin]

Yes. Wait until Alfresco is fully loaded, thus until you are able to access the web client again. After that point Alfresco will still index in the background but has finished the mandatory indexing steps (don't ask me what those are though…)

[predatorz]

Hi,
i have set to debug mode for logging.
I tried doing the index recovery again, and this time, leaving it over the weekends (>2 days), but still unable to access to the web client.
After seeing that the lucene-indexes directory is not increasing in size, i stop the alfresco and start the alfresco again.
When i tail the catalina.out, i saw alfresco re-indexing transactions again. After the reindex is completed, even after waiting and waiting, still unable to access to the web client like before. but the size of the lucene-indexes directory increase in size again.

i did this stop and start of alfresco for a few times with index.recovery.mode=FULL, the logs always show that alfresco is re-indexing transactions. again after a long time, web client still unable to access but size of lucene-indexes directory increase in size again. i Do not know what to do to get alfresco working again.

do i need to post the whole catalina.out?

[workingpeter]

I hit the same problem as the original post. Uploading files via webdav failed halfway, leaving a number of incomplete files in the repository. I could not delete the files or the parent space.

I found this was due to the names that had been given to the semi-uploaded files - they contained either '?' or other characters the fail an Alfresco validation regex constraint check. Renaming them to something sensible allowed me to delete them. Not sure if this solves the same problem as  the original poster, but hope it helps.

I would be very interested if there is any feedback on how the inconsistency might have occurred. I am using 2.9B Community on Linux with MySQL and innoDB tables.

[predatorz]

Hi,

I did a delete of lucene-indexes diectory and tried to do a recovery of lucene-indexes, but now my alfresco can't even start. :cry:  :cry:  :cry:

[luã_smiguelsequ]

Ouch. I was expecting that this particular topic would have a quick fix — not such a lot of bad experiences in failed re-indexing.

I'm basically stuck at precisely the same issue. With a difference. My client has an insanely old and outdated hardware (those "temporary" things that tend to become "definitive") so I don't even see the INFO [org.alfresco.repo.node.index.FullIndexRecoveryComponent] Index recovery started: XXXXX transactions. line.

It starts rather well with:

03:50:58,733 INFO  [repo.admin.ConfigurationChecker] The Alfresco root data directory ('dir.root') is: /var/www/vhosts/datex.tpfplanege.pt/httpdocs/tomcat/alf_data
03:50:58,790 ERROR [repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: System content not found in content store.
03:50:58,790 ERROR [repo.admin.ConfigurationChecker] Ensure that the 'dir.root' property is pointing to the correct data location.
03:50:58,797 ERROR [web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: Ensure that the 'dir.root' property is pointing to the correct data location.
‍‍‍‍‍‍

(which it is, as can be seen from the first line)

It goes on with the expected:

Apr 16, 2008 3:50:58 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Apr 16, 2008 3:50:58 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/alfresco] startup failed due to previous errors
‍‍‍‍‍‍

waits a bit, and then:

Apr 16, 2008 3:51:44 AM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already.  Could not load org.quartz.StatefulJob.  The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
[…]
Apr 16, 2008 3:51:49 AM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already.  Could not load org.alfresco.repo.avm.OrphanReaper$1TxnWork.  The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
‍‍‍‍‍‍‍

which I believe is just because Alfresco is not running…

At this stage, what I saw on these forums, is that you'll start seeing Alfresco rebuilding the index, and getting things like INFO [org.alfresco.repo.node.index.FullIndexRecoveryComponent] Index recovery started: XXXXX transactions.

Well, I see that something is happening. The empty lucene-indexes folder now has the following structure:

# ls -lR lucene-indexes/
lucene-indexes/:
total 8
drwxr-xr-x  2 root root 4096 Apr 16 03:50 locks
drwxr-xr-x  3 root root 4096 Apr 16 03:50 system

lucene-indexes/locks:
total 0

lucene-indexes/system:
total 4
drwxr-xr-x  3 root root 4096 Apr 16 03:50 system

lucene-indexes/system/system:
total 12
drwxr-xr-x  2 root root 4096 Apr 16 03:50 8eff9eb1-0b57-11dd-a3a7-edc09c57bc22
-rw-r–r–  1 root root  107 Apr 16 03:50 IndexInfo
-rw-r–r–  1 root root  107 Apr 16 03:50 IndexInfoBackup

lucene-indexes/system/system/8eff9eb1-0b57-11dd-a3a7-edc09c57bc22:
total 16
-rw-r–r–  1 root root 2922 Apr 16 03:50 _1.cfs
-rw-r–r–  1 root root    4 Apr 16 03:50 deletable
-rw-r–r–  1 root root   58 Apr 16 03:50 IndexInfoDeletions
-rw-r–r–  1 root root   27 Apr 16 03:50 segments
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

All very nice, but still a lot of the "regular" directories under lucene-indexes are missing. The java process doesn't die, but I have no feedback of if it's doing anything at all! Machine load is very low. And of course, Alfresco is not running under Tomcat.

No further logs appear after 20 minutes. Not even a message saying if anything is happening at all! I've seen lots of people mentioning that "re-indexing takes a long time and may happen in the background". Good! What process should I be watching for? Where is it being launched from? Where does it write its logs? Where do I see the magic "Index recovery started" messages appearing? Definitely they're not appearing either on catalina.out or alfresco.log… unless they take HOURS to appear… is there any "temporary" log that I can check to see if Alfresco is doing anything at all?

Would you recommend starting over with the semi-corrupted lucene-indexes files (I have backups) and use "AUTO" instead of "FULL" recovery? The results are as disappointing (I've tried it often) as clearing that directory and starting with FULL. I don't see any differences on the logs in either case.

Using Apache Tomcat/5.5.20, jdk1.5.0_10, installed on MySQL 4.1.21 (fully and thoroughly checked and re-checked; all Alfresco tables on MySQL are fine). Software is not upgradeable (and definitely NOT when the whole of Alfresco is down!).

Notice that the server was running flawlessly for 400 days without requiring a single reboot (or Alfresco shutdown…), with several dozens of Alfresco users regularly uploading files. They complained for the past few days of an "increased slowness" which made me investigate what was going on.

[luã_smiguelsequ]

Replying to myself — launching Alfresco with system.bootstrap.config_check.strict=false on repository.properties and with the old (corrupted?) indexes will launch Alfresco, but it refuses to authenticate any user.

At least it launches…

Now I just need to figure out why no user can be authenticated (absolutely no errors are given).