Help please!
I just installed gallery2-2005-02-21 (brand new install), and got it installed correctly. I can manually upload photos fine and they work, other things seem normal.
However- when I go to migrate my Gallery1 site, as soon as the migration starts, it stops. It takes the path to the files and shows the album list, and then I proceed.. It starts on the first album, first photo, and then the browser just stops (even with different albums). No errors are printed anywhere. Going back to the main Gallery page, that one album is created but without photos.
I've enabled debugging but don't see any noticable errors.
Is it possible my gal1 albums directory needs more open perms for gal2 to parse? Or it this a possible bug in the 2005-02-21 CVS? Any ideas of where to go for assistance? A search of the forums didn't get me anywhere.
Thank you!
jt
----
Gallery URL (optional):
Gallery version: v2-2005-02-21
Webserver (with version): apache2
Datatabase (with version): mysql 3
PHP version (eg 4.2.1):
phpinfo URL (optional):
Graphics Toolkit(s): netpbm, ig
Operating system: fedora c3
Web browser/version: ie6
Posts: 80
Looks like theres some sort of memory usage/leak issue with the migration now. I tried an import with the latest cut last night and it had consumed 1.5G of memory by the 3rd album. Things crawled to a halt once the system started paging.
Posts: 6
My problem though starts on the first photo, immediately (like 2 seconds). If it's memory-related, wouldn't it take awhile before I saw it?
Seems more like a config problem on my end...?
jt
Posts: 974
johnnytaco:
What sort of debugging did you enable? Please try 'immediate'
Also, does your apache error log have a cryptic error about php not being able to allocate x bytes?
fedak: I'm looking for a memory/cpu leak but I haven't been able to nail anything down. I think that there may be a g1-version-dependant problem. For me it is only about 100k per item (only!).
Posts: 6
I was not using immediate. Now that I am, I still don't see anything obvious showing an error...
However... This error was in Apache's error_log several times:
Allowed memory size of 8388608 bytes exhausted (tried to allocate 0 bytes)
I had edited my php.ini and added the .htaccess file with 16M in both.
After doing that, now I'm getting:
PHP Fatal error: Call to undefined function: mysql_pconnect()
in the httpd log.. So now I'm chasing this problem.
I think I'm closer...
jt
Posts: 6
Well that was weird. I somehow didn't have php-mysql installed, yet it worked for awhile without it. Anyway, it's installed now and the migration is cranking away.
I had to set memory_limit to 16 in php.ini. Either my .htaccess file is not being read or the syntax is wrong:
php_value memory_limit 16M
See anything wrong with that?
jt
Posts: 7994
It looks fine to me -- I'd verify that Apache is actually obeying your .htaccess file.