No, that's not a problem. I'm having some error messages that are probably related to imagemagic, but that's not causing me any problems. The problem is that using the cli script to load multiple files is crashing the main hierarchy. Cleaning the cache or rebuilding the hierarchy is not working also.
Tks,
Roberto
--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/559f6e4a-d141-490c-b42d-d2d341b858c3n%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/d7b31617-38d6-418e-bf31-fa96ecd1b68c%40gmail.com.
Yes,
I've tried that, unfortunately it didn't work.
Tks.
I've tried setting this variable (batch_mode), and it worked only partially.
After setting it, I ran the command to load the objects into the Atom nested set. This time, the nested tree did not crash, and when clicking on the root of the branch with all the objects, it did actually show the thumbnails of the objects. The problem is that when I tried open the branch itself, it wouldn't open, it did only show the animation for opening, but never opened. I've tried to repopulate the search cache, clear the cache, rebuild the nested set, restart nginx, php, memcached, but it still wouldn't open. I ended restoring atom from a snapshot....
Any other ideas?
Tks,
Roberto
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/d070bfec-ebc5-42a5-9491-291ba1d0e44fn%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/35CZiuNKlCM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/cf20c84a-f3a5-4904-9ae2-7eaa61e537d1n%40googlegroups.com.
After a lot of time I THINK i managed to solve the problem with the hierarchy breaking. I have new physical servers, so I bumped up the CPU and memory settings for the VM. Java, which had only 1GB as Xmx and Xms, now has 5GB. I increased disk space (both root partition and the partition where nginx/atom is), and, what I think really made the difference, increased the buffer sizes for MySQL. The usual recommended size for innodb buffer size is (usually) 75% of the size of your DB size. In my case my DB size was already at ~1.5GB and I had a meager 256MB for InnoDB. Now that RAM is no longer a problem I increased it to 2GB and it SEEMS that this solved the problem. Also those changes improved considerably the response time of Atom.
In any case, Monday I will continue loading more files and will report back again.
Roberto
To view this discussion visit https://groups.google.com/d/msgid/ica-atom-users/CAO3wKhqaqb8tuQY_%3D9EoGBbZmQziGcdxvTBv6z_z3OdydOuz1g%40mail.gmail.com.