Personally I would suggest you raise this as a PHP bug. I have checked and this hasn't been mentioned, but that's not to say it isn't a bug as in your case it appears to be only happening with 5.2.10 and not 5.2.9. Though it's working fine for me, so I don't know - but it wouldn't hurt to raise it with PHP to see what they think...
If you can't get any traction with isolating and resolving this issue please open a ticket so we can verify none of the cPanel specific patches are at fault before the problem is forwarded upstream to the PHP dev team.
Please mark the ticket ATTN: JD
Thank you Spiral for taking a look at it for me and drilling down some causes for the compile.
I definitely do want to talk to you about some security options here in the near future, so I'll take that to email and go from there.
Many thanks for taking a look. I'll be checking the force cgi redirect and the others that you mentioned and retest a compile on one of the other test machines and see how things go.
Again, can't say thank you enough for even taking a look at this for me, it's very much appreciated!
Conor Treacy | Hands-on Web Hosting
cPanel eCommerce Hosting | X-Cart Web Hosting
SEO Consulting Omaha Nebraska
Yes. In the case of the original poster, he just had an issue with compile options and after his PHP was recompiled,Originally Posted by djerik
all is happy now and his fopen() is working as it should again and he is now fully upgraded to 5.2.10!
If you are having a problem with fopen() where you are at, it is possible that you have the same issue or
you could have an entirely different issue but in either case, the problem is not PHP 5.2.10 as we have
solidly confirmed that fopen() does indeed work perfectly on the new PHP version.
Areas where fopen() might be affected include:
- Conflicts with Mod_Security rules
- Issues with firewall application or other security settings
- Curlwrapper bug from Cpanel and EasyApache
- Improper compile options when upgrading PHP
- Wrong directives or options in PHP.INI
- Missing files, applications, or some system libraries
I'd be glad to help you try to sort your issue out. It could be as simple as the original post or more complex.
No problem! Glad to help! I sent you an email this morning with details how you can upgrade your other servers.
If you have any question about the details, feel uncomfortable with any part of doing the upgrade yourself, or
just need any general help, you know how to reach me. If I'm not available when you need me, you can also
contact my support team anytime and they would be glad to help you as well.
EDIT: I don't remember if I posted this here or not yet - http://support.myserverexpert.com
(post a support ticket and we'll try to help you out with this issue -- IE: fopen() not working)
Don't make me spit my coffee all over the screen laughing so hard!
For starters, nothing said anywhere has been directed at you specifically so chill out and relax. Actually, the comments my assistant told you were directed specifically towards and regarding some of the side comments made between handsonhosting and smithxxl and have absolutely nothing to do with you whatsoever although it would seem you've taken it all totally out of context as some sort of personal attack on you! LOL
Secondly, I didn't send any private messages to anyone. I have not even read any private messages either! After fixing the issue for handsonhosting, I asked my assistant last night to contact everyone else involved with this thread directly and out of courtesy and let all of you know two things:
1. That the issue had been identified and resolved for the main poster.
2. That the issue has NOTHING to do with PHP being version 5.2.10 and if anyone needs help,
that we'd be able to give anyone else a hand that is dealing with this same issue.
The main problem in the original poster's case specifically is that SuPHP really needs "--force-cgi-redirect" and if you forget that when you upgrade then that can cause you problems with among a number of other things fopen(). Incidentally, we couldn't replicate the fopen() issue on any server running PHP 5.2.10 or any other version for that matter other than what has been previously discussed but then after seeing handsonhosting's server and fixing that for him, we ran some more tests removing the "--force-cgi-redirect" from existing servers on 5.2.8, 5.2.9, and 5.2.10 and then were finally able to duplicate this user's fopen() issue on all the versions which also further says this isn't a 5.2.10 issue but rather an issue of wrong settings simply employed when upgrading and could happen on any version of PHP.
Anyone else having problems with fopen() may be this same issue or a totally different issue entirely. However, what we do know is that fopen() works perfectly fine with PHP 5.2.10 so if you are having an issue, you have something going on other than the PHP version and we'd be glad to help you investigate your issue if you are having problems with fopen().
Last edited by Spiral; 07-15-2009 at 07:23 PM.
Ok, I'll give you that one and suggest they get their own account!
(However, they are not on here much and was just helping me out last night)
Anyway back to the real issue at hand though, the fopen() issue has been
solved and if anyone needs any help fixing it on other servers, we are
available to help with that issue at our technical support and are not
billing any tickets from anyone asking for help with this specific item.
Last edited by Spiral; 07-15-2009 at 03:53 PM.
Your support site is borken. lol.. ok was. Fixed now
Method Not Implemented
Beforehand I like to excuse for my probably stupid questions.
My webhost is using cPanel and has upgraded from php 5.2.9 to 5.2.10.
After the upgrade, my script fails executing fopen. I constructed a simple test script and stated that something was wrong at their end, and not in my script. They think I am using fopen incorrectly and thinks that it must be incompatible with php 5.2.10.
I then pointed them to this thread, but because “force-cgi-redirect” is enabled they have not taking further action. What should I do? Should I ask them to create a ticket at your technical support? Or is it up to me to find the problem?
Regards
Tobias
Are you totally on crack or something?
You are lying about what? You made all of what up?
What is aimed at you? What message only to you?
Exactly, what the hell is wrong with you?
I've been more than patient with you thus far answering your somewhat
humerous posts above but let's make something perfectly clear here:
I didn't write you any private message and the one and only message
my assistant wrote last night was sent to EVERYONE was simply a
courtesy notice and nothing more to let you, and everyone else, know
that the issue in this thread had been solved since some of you may
by interested or also need additional one on one help as well!
Good grief! You would think someone is killing you! Nobody has said
anything bout you and nobody has done anything to you! LOL
Incidentally, you are hijaaking this thread!
If you want to discuss something more with fopen() and PHP 5.2.10
as is the subject of this thread then fine, otherwise topic closed!
The issue should be fixed in EasyApache 3 builds numbered 4764 and higher. It turned out to be a typo in the patch to prevent curlwrappers from taking over the handling of file:// streams. If your webhost compiled PHP 5.2.10 with curlwrappers enabled, they'll need to rerun EasyApache 3 for the fix.
Hello Tobias:
Regarding your questions, I should first off point out that while PHP 5.2.10
itself has no issues with fopen(), there are many things that could cause
it to fail totally independent of the version as we have all seen in this thread.
The original poster of this thread, handsonhosting, simply had forgotten a
compile directive when recompiling PHP that was the cause of his fopen()
issues but that by no means is the only thing that could cause problems
for fopen() as there are many other factors to consider as well.
As I said in my earliest post in this thread, there are a great many
PHP configuration directives that could cause you to have problems with
fopen(). In a similar fashion, having certain libraries and system files can
cause your PHP not to be built correctly and fopen() to fail, and depending
on your security configuration, some firewall and other security software
settings could interfere with fopen() making external network connections
and there is a bug with cpanel now with curlwrappers that could also effect
it indirectly which is a totally separate issue entirely but again could
cause it to fail.
You need to evaluate what is going on with your server and first rule
out all the obvious issues and also look at more closely exactly what is
or isn't happening in your case to determine if you are having the same
issue or a different issue and work your way down to the cause of your issue.
While handsonhosting needed a compile directive added, you may have
a firewall blocking outbound port 80 connections, or perhaps you are missing
libraries necessary to making socket or tcp connections on your server, or
perhaps you have something setup wrong in your PHP.INI file?
Regarding your question about asking your host to submit a support ticket,
yes you may do that if you like. My earlier post has an address where you or they
can submit a support a ticket and my staff or I will be glad to volunteer to take a
quick look and help try to sort things out.
As you said you are an end user and not an administrator (it sounds like),
it may be more difficult in determining your issues unless your host comes
by and asks for help directly as little could probably be done from your own
account unless it were possibly just a simple ini file issue in your case.
You make a pretty big assumptions that the user's issue is the curlwrappers bug!The issue should be fixed in EasyApache 3 builds numbered 4764 and higher. It turned out to be a typo in the patch to prevent curlwrappers from taking over the handling of file:// streams. If your webhost compiled PHP 5.2.10 with curlwrappers enabled, they'll need to rerun EasyApache 3 for the fix.
Without digging into things, you couldn't know this for certain. It could be that the user's
host upgraded with the problem version of EasyApache but then again it could be anything
from what I listed above as well. If the user were like the original poster, there may be no
relation to curlwrappers or EasyApache whatsoever.
However that given, it is good to hear you are addressing that item as well!
Last edited by Spiral; 07-15-2009 at 06:41 PM.
LinkBack URL
About LinkBacks