Batch-add files not responding

[rob944s2]

Hi everyone. I'm having some trouble with my batch add files function and was hoping someone could help clue me in. I have a gallery that is installed on godaddy servers, it was working fine but they had a ftp problem and needed to move me to a new server. Everything seemed to copy over fine and everything works as before, except now the batch add files doesn't respond after being clicked. It just hangs and after several minutes shows "Page cannot be displayed".

I'm working with godaddy support, but they haven't been able to get it fixed. Anybody have an idea what might cause something like this? Thanks a lot.

Robert

[Joachim Müller]

http://coppermine-gallery.net/demo/cpg14x/docs/index.htm#upload_trouble

[shutterweb]

I am having the same problem. I was uploading just fine this morning, then noticed that not all the files I had uploaded to the folder went into the gallery. They are italicized in black, no image show, and cannot be added. THere are others that I reuploaded and am trying to add them and I get page cannot be displayed when I am trying to put them in an album via batch add. I read, and re-read, the link provided for troubleshooting and set the maintenance settings as suggested to no avail. Any thoughts on what the problem may be?

www.brianandshelia.com/photos

test
test

[mr.goose]

I know this is quite an old thread but I hope that my experience might help someone. A similar problem occurred on our site http://www.garfnet.org.uk/coppermine last night. I was really tearing my hair out. Even got my ISP physically to reboot the machine.

We use SSH (secure shell) to control our servers remotely and when I ran "top" (a Linux program that shows memory and processor usage), every time someone clicked the "batch-add" button and the "searchnew.php" script was activated, an Apache2 process snaffled 99% of the machine's processor resources and the rest of the machines services ran at a snail's pace. This lasted until eventually "searchnew.php" script timed out. However there were no Coppermine/PHP error messages and nothing unusual in either the Apache access or error logs.

I even installed a second Coppermine with a blank dataset and no files. Initially this ran fine - whch eliminated any MySQL & PHP issues - though we regularly "apt-get upgrade" for security reasons anyway. However when I copied our image files to the new installation the "batch-add" also failed - even before I had started to populate the new Coppermine database. This suggested that the problem may lie with our files and not with Coppermine.

So I used Konquerer (part of the KDE desktop for Linux) "fish" protocol securely to browse the files on our server (much more secure than FTP). That is when I stumbled across the problem. It was caused by circular symbolic links - and frankly gross stupidity on my part for allowing the situation to occur in the first place! Let me explain...

Unix allows you to create links to other files and folders as if they were in your current folder. In my case...

• There was a symlink from /var/www/garfnet/coppermine/albums to /var/www/garfnet/media.
• There was a second symlink from /var/www/garfnet/media to /var/www/garfnet/sounds. So far so good.
• However a third link from /var/www/garfnet/sounds to /var/www/garfnet/coppermine meant that whenever the "searchnew.php" went hunting for files, it was going round in circles.
  

Deleting that third symlink fixed the issue instantly and the system is working fine again - though I am finding it hard to come to terms with my embarrassment! Anyway, the moral of the story is that a "batch-add" not responding issue could be related to your file structure rather than to Coppermine. Or perhaps the moral is, don't drink too much Jagermeister whilst creating symlinks.

In any event, I hope this is of some help to someone.

Best wishes, G.

[Joachim Müller]

@shutterweb: don't hijack other's threads in the future. That's why nobody answered.

@mr. goose: thanks for sharing your solution. The majority of coppermine users is hosted on shared webhosting without shell access, so I doubt that they are able to create symlinks that could cause endless loops.