apache error_log; showphoto

curriertech · January 28th, 2011, 08:05 AM

Hi Chuck,

I'm using SEO urls and everything works on the client/browser side, but I'm generating a ton of errors in apache when anyone hits showphoto. I just upgraded to 7.1 but it's been doing this since seo became an option. Apache 2.2.17, PHP 5.2.14 with xCache 1.3, mySQL 5.0.91.

[Fri Jan 28 08:55:59 2011] [error] [client xx.xxx.xx.xxx] File does not exist: /home/nestreet/public_html/gallery/member-galleries, referer: http://www.nestreetriders.com/gallery/member-galleries/p2734-drews-army.html

This was from me viewing that image and it loaded up fine, no errors in the browser at all.

I'd like to keep using the seo urls but I don't like the idea of so much unnecessary logging going on. Any idea of what I can do to fix this?

Thanks!

-Josh.

Chuck S · January 28th, 2011, 09:35 AM

whats the full error there as its hard to comment without seeing the full error. what file is it saying is missing? I see your error has a path.

I would suspect maybe the use of relative urls in your header maybe it all depends. You can not use relative paths when using spider or seo urls.

This could also be something in your apache setup. Nowhere in our actual code are we going to reference a directory structure like this so why is that in your error log. It is not coming from our code.

/home/nestreet/public_html/gallery/member-galleries

Your directory structure called only when locating the actual physical files would be

/home/nestreet/public_html/gallery/data

So reallly if you full error is indeed what you posted. The mystery is going to be where those server paths are coming from. Is this some type of Apache bug. Is this simply error reporting set too high?

curriertech · January 28th, 2011, 09:42 AM

Quote:

Originally Posted by Chuck S

whats the full error there as its hard to comment without seeing the full error. what file is it saying is missing? I see your error has a path.

I would suspect maybe the use of relative urls in your header maybe it all depends. You can not use relative paths when using spider or seo urls.

This could also be something in your apache setup. Nowhere in our actual code are we going to reference a directory structure like this so why is that in your error log. It is not coming from our code.

/home/nestreet/public_html/gallery/member-galleries

Your directory structure called only when locating the actual physical files would be

/home/nestreet/public_html/gallery/data

So reallly if you full error is indeed what you posted. The mystery is going to be where those server paths are coming from. Is this some type of Apache bug. Is this simply error reporting set too high?

I just edited the first post, part of the error got parsed as a link. I'll increase it a bit to see if I can get more detail. I had assumed that member-galleries was just part of the seo rewrite. I'll also check my header/footer paths.

curriertech · January 28th, 2011, 09:50 AM

No relative paths for any objects, only some links.

curriertech · January 28th, 2011, 10:10 AM

I don't think it's an Apache bug since it's done it across multiple versions, and my other rewrites don't generate any errors. That brings up another possibility though, that I'm running vbSEO for rewrites on the forum side. I can't think of a way that it would matter, but could they be conflicting? My forum is in /forum and the gallery is in /gallery.

I've been watching the error_log all morning and it generates that error on other seo'd links (like personal album), not just the member-galleries url.

Chuck S · January 28th, 2011, 03:35 PM

I here what your saying I just do not see anything in our code that is going to ask for any path like that. I will see if I can reproduce it and ask Michael if he has any ideas. I know I do not get anything like this in my server logs and I have been using the SEO urls for over a year now.

curriertech · January 28th, 2011, 07:08 PM

Quote:

Originally Posted by Chuck S

I here what your saying I just do not see anything in our code that is going to ask for any path like that. I will see if I can reproduce it and ask Michael if he has any ideas. I know I do not get anything like this in my server logs and I have been using the SEO urls for over a year now.

I'm in the same boat, I've parsed all the files and the database and I can't figure it out. I have another license but I don't have any non-vbseo forums that I can test on, to find out if it's the server.

Chuck S · January 28th, 2011, 07:50 PM

If you have another license just do a standalone install and test things out.

curriertech · January 28th, 2011, 07:58 PM

Quote:

Originally Posted by Chuck S

If you have another license just do a standalone install and test things out.

hah, duh. silly me!

Chuck S · January 28th, 2011, 11:18 PM

Yeah it doesnt have to be with a forum. thats just user integration etc the program code we run is the same no matter whether you have a forum.

curriertech · January 29th, 2011, 09:34 PM

Quote:

Originally Posted by Chuck S

Yeah it doesnt have to be with a forum. thats just user integration etc the program code we run is the same no matter whether you have a forum.

When I first started using PhotoPost it was a standalone install long before I started using it with a forum, but it's been so long I'd totally forgotten its roots.

Anyway, I just tried it on another site on another server and it's not generating any errors. There are few technical differences between the servers, mainly that the one with the problem is running Apache in DSO mode with XCache, and the one without the problem is running suPHP. Other than that they're running the same versions of everything, so the only remaining differences are the other scripts on the sites. I'll mess around with some things, and try turning vbSEO off to see if that has any impact.

Thanks for the tips and if I find anything worth sharing I'll post it back here.

Chuck S · January 30th, 2011, 12:48 AM

I would beleive it has to do with your apache setup on the one server.

You can test vbseo pretty easy can't you simply turn that off. I do not beleive vbseo does anything to our urls so dont think thats going to solve your issue

curriertech · January 30th, 2011, 11:48 AM

Quote:

Originally Posted by Chuck S

I would beleive it has to do with your apache setup on the one server.

You can test vbseo pretty easy can't you simply turn that off. I do not beleive vbseo does anything to our urls so dont think thats going to solve your issue

Yeah vbSEO and other htaccess files are ruled out as the cause, I couldn't duplicate the issue on my other server no matter what I tried, even with vbseo and the same htaccess files. As far as config differences between the servers the only differences are the ones I've already mentioned. I'm going to switch the problematic server over to suPHP at some point to see if that has any impact. I don't see how it would matter since rewrite is a function of apache, not php.

Chuck S · January 30th, 2011, 12:21 PM

Like I said I would suspect it is because of differences in the Apache setup in the servers but thats just me. It would have to be in either your one servers apache or php configs. We know its not in the applications since it is your server reporting the errors and they do not seem to have any indications in coding errors.

-RL- · November 16th, 2011, 04:49 PM

Big bump...

I just found this thread and I have the exact same problems as described here, so I just wondered if anyone has found the reason for these entries in the error logs??
I also suspect that it may be related to Apache, but I've tried several different settings there and the error still pops up in the log....

Chuck S · November 16th, 2011, 05:36 PM

As previously posted it is an apache only thing I am sure. There are no visible errors in our program nor the php errors logs on the server so I would not think it is a coding issue more rather something apache is translating incorrectly. It could be an apache bug in a specific version of apache.

However as noted in this thread I did ask for more precise full error messages as in what image it is saying is missing for a more accurate answer and without that type of information all I can do is give a general response.

-RL- · November 17th, 2011, 05:53 AM

Quote:

Originally Posted by Chuck S

However as noted in this thread I did ask for more precise full error messages as in what image it is saying is missing for a more accurate answer and without that type of information all I can do is give a general response.

It's not reporting missing image files, but missing directories...

The errors in the first post here are the complete error, and as you can see there it/apache(?) checks the parent directory URL of the rewritten image page URL, and all other rewritten URLs on that page as well.
But since that directory doesn't exist IRL Apache generates those errors for some reason...

Image page URL
/gallery/member-galleries/p2734-drews-army.html

Missing directory (since it's rewritten in the URL above, and doesn't exist on the server)
/gallery/member-galleries/

Quote:

It could be an apache bug in a specific version of apache.

Then it has to be for the entire 2.2 version... The first post here used 2.2.17 and I'm on the latest 2.2.21 version here and get the same errors.

curriertech · November 17th, 2011, 06:44 AM

I don't think it's an Apache issue at all because every other app on the planet that does SEO friendly url rewrites does so without generating these bogus errors.

Chuck S · November 17th, 2011, 08:12 AM

/gallery/member-galleries/p2734-drews-army.html

That url is valid and common place type of SEO url. It really doesnt matter what the url is as mod rewrite essentially translates that url to

/gallery/showphoto.php?photo=2734

There are no php error logging and scripting errors. Our urls are just like vbseo

/forum/general-discussion/146676-gallery-search-engine-optimization-url-issues.html

It is common place with seo urls that the actual directory would never exist because that directory as you call it is actually the category name.

-RL- · November 17th, 2011, 08:35 AM

But something (Apache/photopost/whatever...) is for some unknown reason actually checking if the parent directory exists under /gallery/member-galleries/p2734-drews-army.html, and for all other similar rewritten URLs on the image pages when using SEO URLs, and since the directory /gallery/member-galleries/ doesn't exist, rewritten or not, then those errors do appear in the log.

I have many different sites and scripts running on my servers with rewrites, and Photopost is actually the only script that generates these errors in the log, and that's quite strange.
But the difference between Photopost and VBSEO or other scripts that uses rewrites the directory/URL /gallery/member-galleries/ under /gallery/member-galleries/p2734-drews-army.html does not generate a 404 error since they do exist (through rewrites) or is redirected to the actual category page.