a bit

[Kamran]

Hello,

After lots of ticket exchange with HG they could not yet fix my issue after one week. here are the ticket exchanges and it seems I am just wasting my time to talk about my problem with HG.

--------------------------------------------------------------------


Me:
Hello,

after lots of testing we believe the cron job conflicts the two php.ini files of both php4 and php5 since cPanel11 allows switching between php4 and php5.
I mean regardless we are using php4 or php5 we get this error in cron email which means cron job doesn't understand what is
the curent php version to look into which php.ini to run the appropriate ionCube Loader version.
This is an issue you should really look into it.
This is the error we get in cron email:

Failed loading /usr/local/ioncube/ioncube_loader_lin_4.4.so: /usr/local/ioncube/ioncube_loader_lin_4.4.so: cannot open shared
object file: No such file or directory
Site error: the file <b>/home/[username]/public_html/[folder]/script.php</b> requires the ionCube PHP Loader
ioncube_loader_lin_5.2.so to be installed by the site administrator.

Please look into it more further and fix it soon as we can't run our crons.

Thanks,
================================
HG:

Hello,
I fixed the php.ini file that is being used for the cronjobs. If you have any questions, just let us know.
================================
Me:

Hello,

No, Not yet solved. even with that AddHandler in .htaccess nor you've corrected symlink of php.ini nor it works with
extension_dir = ./
I am still getting this error in cron email:

Failed loading /usr/local/ioncube/ioncube_loader_lin_4.4.so: /usr/local/ioncube/ioncube_loader_lin_4.4.so: cannot open shared
object file: No such file or directory
Site error: the file <b>/home/[username]/public_html/[folder]/script.php</b> requires the ionCube PHP Loader
ioncube_loader_lin_5.2.so to be installed by the site administrator.

tio test it, please set the cron time of:
php -q -f /home/[username]/public_html/[folder]/script.php
to ****** (every minute) then change the cron email from mine to yours, then you will get that error in cron email.
Can't you fix this?
Thanks,
================================
HG:
Hello,

The extension dir should not be set how it was. I have set it to / since we reference our extensions explicitly. I have also
updated the pathing for the 4.4 and 5.2 extensions so they don't go through symlinks. I ran your cron and exported the errors
to a file, after it was done running no errors were present. I see that you have renamed your php.ini in public_html. Having
your extension_dir will cause these ioncube errors each time PHP processes, but it does not mean that the cron didn't run.
This will error each time php runs but will only affect scripts that explicitly require ioncube. Do you want us to remove
your symlinks?

Please let us know if we can be of further assistance.
Thank you,
================================
Me:
Hello,

I am still getting that error! :-(
as I said it works fine when I run the script directly via browser, and I guess this is why it worked for you too.
for better testing and track the issue. I told you to not check it via root but via our cPanel. Please login to our cPanel and
change the schedule of /home/[username]/public_html/[folder]/script.php too ****** (every minute) and change the cron
email in our cPanel from ours to your email that you can receive that cron email.
then you will see what error I am talking about.

Please check it and let us know.

Thanks,
===============================
HG:
Hello,

The extension dir should not be set how it was. I have set it to / since we reference our extensions explicitly. I have also
updated the pathing for the 4.4 and 5.2 extensions so they don't go through symlinks. I ran your cron and exported the errors
to a file, after it was done running no errors were present. I see that you have renamed your php.ini in public_html. Having
your extension_dir will cause these ioncube errors each time PHP processes, but it does not mean that the cron didn't run.
This will error each time php runs but will only affect scripts that explicitly require ioncube. Do you want us to remove
your symlinks?

Please let us know if we can be of further assistance.
Thank you,
================================
Me:
Hello,

I renamed _php.ini_ back to php.ini with extension_dir = ./ and I still get that error in cron email so actually you did not
bother to test like you said! :-(
I also noticed you even did not try to test like the way I told you to set the schedule to every minute and change my email to
yours in my cpanel, that you can get a cron email from my cpanel to see which error I am talking about.

I am really tired to keep emailing you about the same issue over and over, if you are not able to fix it please ask one of
your seniour server admins to look into it.
as about symlink do whatever is the best, I just want this cron runs properly VIA MY CPANEL AND NOT VIA YOUR SHELL/ROOT.

Thanks,

[Kamran]

I just hope Brent Oxeley would see this thread to know how his staff are wasting his users' time by giving them nonsense answers.

[Kamran]

I've just emailed them to let them know that I can't use fopen. they said they symlinked php.ini to use it.

continuosly I am receiving emails about different issues: "I've removed your symlink to solve the cron issue" and "I've symlinked to solve the fopen issue". I see the tech support don't know what they are doing!

Thanks,

[Kamran]

well, the cron is fixed now! but why after several tickets in a week? and why not at first ticket????
Now, I would say HG is extremely good! :-)

[GatorCarl]

I apologize for all of the confusion between the different admins. It looks like your cronjobs are working now. If you have any more questions, or problems, just let us know.

[Kamran]

I apologize if I did sound a bit rude about this, but you don't know how annoying it was for me to keep ticketing for the same thing....

Again, Thanks a lot for your time to fix it for me!

This thread is closed by me.