Total processing time: 86,410.27 seconds! - Is it abnormal?

This is what I got through email today:

Total Indexed URLs: 114472
Total Processing Time: 86,410.27 seconds

I'm using vBSEO 3.5.0 RC2 on vB 4.0.2 7 & vBSEO v2.6 (beta, I think).

I wish to know whether the processing time is normal.

Yes that is abnormal. This is likely because your sitemap never finished generating, so each time it ran during the night and paused, it kept the timer running.

You should think about increasing your wait timeout.

delete progress.dat and all xml.gz files from the /data folder and regenerate manually. if it times out, you will either need to reduce some sections (Showpost, archive, etc) or increase your memory_limit or wait_timeout settings on your server.

@Brian: Before I take that step, I'd like to inform that I've been running vbSEO and Sitemap generator since 2008. The software worked great and never had problems. I upgraded the forums and also got the RC of vBSEO (mentioned in post #1) before getting the error.

Shall I upgrade to RC3 and any recent version of the Sitemap generator?

Also, I see a sitemap (.gz) file in my forum root; can I delete it?

sitemap .gz in root is not from vbseo. If you're not using anything else (ie, wordpress, etc) then you can safely delete it too.

We recommend everyone upgrade to vb 4.0.3, vbseo rc3, and vbseo sitemap 2.6 beta 2 to be sure they are on the latest if using vb4.

You should delete all the /data/ folder xml.gz and prrogress.dat files and then generate the sitemap manually. If any errors occur, please report them here. You may need to disable albums and or tags (a known bug)

I deleted the xml.gz and progress.dat files and regenerated the sitemap. The script exceeded the PHP memory (currently 32 mb). I've asked my host to up it to 38 MB before I make another try.

What is the recommended php memory size?

Q2. The /data folder is 777. Isn't it security risk?

32 is the recommended bare minumum for vbseo to function. If you have a larger site, you may require more ram usage to php. This will depend on yoiur ram allotment on your server as well.

You may wish to disable some 'extra' sections that are not necessary, such as showpost, archive, etc.


Regarding the 777 issue, you should have an htaccess file in place on ALL writable directories as outlined here:
Security issue

Thanks for response, Brian. I already have .htaccess in /data folder which contains following text:

deny from all

Shall I replace it with:

<Files ~ "\.(php\d*|cgi|pl|phtml)$">
order allow,deny
deny from all
</Files>

deny from all is fine to leave. That will stop anything from running directly in there. The later in that other post only stops 'script' extensions from running (php, etc)