I have never been able to cascade a change fully through my site. Most recently was a URL change on the site asset and it stalled at about 30%. I cancelled the HIPO job and then set the rest manually.
Similarly when I have previously tried to apply workflow / metadata / permissions to the site asset it will never reach 100% but stall at some percentage before. No errors.
My site has 5 main branches. If I try 5 cascades on these branches they complete on all except one branch that contains the most assets.
Is there anything I can do/tweak to assist the site asset cascade changes without freezing?
Anyone else had this problem before?
[quote]Is there anything I can do/tweak to assist the site asset cascade changes without freezing?
[right][post=“8740”]<{POST_SNAPBACK}>[/post][/right][/quote]
The usual cause is the Squiz Server process running out of memory. Check /path/to/squiz_server/bin/start_server.php and try increasing the amount of memory the Squiz Server is allowed to use. By default, its 8 or 16mb (can’t remember which, to be honest).
[quote]Similarly when I have previously tried to apply workflow / metadata / permissions to the site asset it will never reach 100% but stall at some percentage before. No errors.
[right][post=“8740”]<{POST_SNAPBACK}>[/post][/right][/quote]
In the case of these HIPOs in particular, if it hangs between 33% and 66%, then the locks that it acquired in the first section of the HIPO may have expired by the time the actual processing occurs. In this case the only remedy is to increase the lock length on the system, if only temporarily.
Oh, good one, Luke. I forgot about Lock timeouts. 
Thanks I will look at both and give it another go.
Would these be the same things to try if I can't generate a Link report?
Only running it on the smallest branch of the site but it gets to 92% and stalls - continually refreshes on 92% until I eventually cancel the HIPO.
[quote]Would these be the same things to try if I can’t generate a Link report?
[right][post=“8750”]<{POST_SNAPBACK}>[/post][/right][/quote]
A Link Report doesn’t lock any assets, so this is probably a memory issue.
Increased the Squiz Server allocated memory to 64M in our CMS test installation.
The broken link report doesn't get past 0%.
Are broken link reports simply a matter of adding the Links Report asset, setting a root node (or leaving blank for the entire site) and then selecting the generate checkbox and committing? I have made the report live too.
Not sure what is wrong?
That HIPO is slightly misleading: It'll sit on 0% for a LONG time as it gathers Link information from the content. This can take a while. Then, it'll go through each link testing it, so your webserver needs to be able to make outbound web connections (or every external link will fail).
Try running the report on a single page (with no children) just to make sure the process completes properly. Then broaden out the scope and you'll get a feel for the time involved to collect all the links.
I think something is wrong. I have tried running it in our test installation on a single page that doesn't have children. The page is completely blank except for one broken hyperlink. The report has been sitting on 0% for almost two hours.
[quote]I think something is wrong. I have tried running it in our test installation on a single page that doesn’t have children. The page is completely blank except for one broken hyperlink. The report has been sitting on 0% for almost two hours.
[right][post=“8762”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yeah, that’s not right at all. I’ll have to test this out tomorrow. Which version of Matrix are you running?
[quote]Yeah, that’s not right at all. I’ll have to test this out tomorrow. Which version of Matrix are you running?
[right][post=“8768”]<{POST_SNAPBACK}>[/post][/right][/quote]
Thanks we’re running 3.6.4
I believe we did successfully run a links report on a previous version of Matrix (either 3.6.1 or 3.6.2) when we pointed it at a single page without children.
It still used to fall over when attempting to run the report on the entire site but that was probably the memory issue.
I have a 3.6.4 system happily running a Links Report on quite a large site. I recommend raising this with support so that someone can take a look at your installation.