Uploads not working after a server move
 

Hi we made a server move to a larger co-lo'd server with the same web hosts this last week.
Everything was transferred across for us file system and MySQL.
We kept the same file paths and the same username but I put in place much stronger passwords for Linux users and MySQL users.
So the only thing we theoretically had to change was the passwords, done that for Photopost and it came up fine and looks ok.
However when trying to upload a photo it get's stuck after it's uploaded it to the server and then presumably does more processing. I can see that when I go to try an upload again it says that I have 2 images in the queue.

I've spotted the previous post on changing permissions but on viewing they all appear to be in place. I'm just waiting to get my root password to apply them all again, but as they appear to be fine is that likely to be the case?
Any other ideas?

So further info.....
I click on this link I get a blank page.

Did you CHMOD the Uploads folder back to 777? Usually after a server move you may have to re CHMOD directories/files.

Thanks. I can see that the folder has 777 already.
I'm just waiting to get the root password and I'll reapply it again to see if that helps.

http://www.photopost.com/forum/photo...rectories.html

This should cover any concievable thing to do on a server move.

Yes thanks I've seen that post and have looked through and checked everything that I can. The photopost files have already been moved so I couldn't do things in the exact order specified.
I've got the root password now and have reapplied the chmod to check that side, but it's not making any difference.

Can anyone tell me what processes are happening when bulkupload script runs, and is there any further way to troubleshoot to find out what's going wrong.

Thanks

I think I've just spotted the problem.
The GD libraries are not installed!
I thought they were default on all Linux installations?

Is it worth me installing ImageMagick instead of GD?

Got the GD libraries installed but it's still not working.
Running out of ideas now.

well can you tell me what your actual error is? That would help alot here.

There is no error.
I get a blank page.
When I view the source of that page none has been created. It's totally blank.
It's whenever the URL below is called.

Some more investigation has proven that a new user not having posted to photopost can upload a photo, but existing users can't.
This seems to point to a permission/ownership problems that are eluded to in the post you directed me to below.
However that post doesn't talk explicitly about ownership, only permissions and I've done the permission side 4 times now just to make sure and have checked them all as far as I can manually. But I'm not sure what to check on the ownership side.
I did notice that some of the files and directories are owned by daemon, presumably the Apache daemon.
Bit stuck as to what to do next but I'll keep looking.
And thanks for the help. :D

Although not solved my web host tells me that the apache daemon changed when we moved across so this is likely the problem.
They will sort it for me.

yes your permissions would need to be sorted there. The uploads and data directories need to be 777 permissions recursively and safe mode needs to be off.

They are though that's the really weird thing.

Make sure the paths are also correct in global and storage options and permissions are correct.

Your host might know more but as long as paths permissions and safe mode are all ok things should be okay.

Ok checking the paths.
When referring to full paths should they have trailing slashes / at the end or not?

You data path should have a trailing slash as it notes in the line in global options.

There are no notes in the global options at all on whether a trailing slash is required.
If I add one, I can see on the bulkupload screen that it's now adding two slashes to the upload URL.

So: /net/www/photopost/uploads//1338

If I leave off the trailing slash it's correct.

So my global admin looks like this:

Full server path to the Photopost data directory: /net/www/photopost/data
Path to uploads directory: /net/www/photopost/uploads

I don't think the problem is here though, it's in the data directory.

I can clearly upload to the uploads folder as when I ftp in to that folder I can see my pictures sitting there, so the problem is either some processing that then happens or the permissions or ownership in the data folder.

All directories in the data folder have 777 permission applied, so if I my understanding of linux is correct that should negate any file ownership or group issues as anyone can write to that folder?

So that then points back to an processing issue, so it would be helpful to know what the http://myurl/photopost/bulkupload.ph...iew&defcat=500 script does in order so that I can troubleshoot that.

Also just as an aside there is a php "bug" that I'm aware of could this be the cause?
PHP Bugs: #45996: libxml2 2.7.1 causes breakage with character data in xml_parse() It is affecting my vBulletin installation but only with a few things.

Right I've solved this, but I don't understand why and I'd like to understand if possible.

I made the cardinal sin of changing too many things when I moved servers.
I changed php to allow larger uploads and changed the following:

post_max_size=36M
upload_max_filesize=32M
max_execution_time=180
max_input_time=120

The idea being to allow much larger pictures to be uploaded as this server was much more powerful.

When looking at the pictures in my bulk upload folder there was a large one for 4Mb. Deleting this allowed everything else to work fine.

So what's wrong with my php changes above and is there something I've missed which is causing Photopost to baulk at the 4MB pictures.

Thanks

Well I think I'm fine now.
If I add this line to my pp-inc.php file all large uploads are working fine now!

ini_set("memory_limit", "60M");

Wow what a journey!

Thanks for your help Chuck and Scott much appreciated.