piping error

odzsolut

Hi there,
I have osticket installed on a shared host and since 2 weeks ago, every time a client is sending an email at helpdesk@xxxxxx, adress wich is piping to osticket, they receive a mail with the error below:

"This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

pipe to |/home/xxxx/helpdesk.xxxxxx.ro/api/pipe.php
generated by xxx@xxxxx.xx

The following text was generated during the delivery attempt:

------ pipe to |/home/xxx/helpdesk.xxx.ro/api/pipe.php
generated by xxx@xxx.ro ------

Failed loading /opt/cpanel/ea-php70/root/usr/lib64/php/modules/ioncube_loader_lin_7.0.so: /opt/cpanel/ea-php70/root/usr/lib64/php/modules/ioncube_loader_lin_7.0.so: cannot open shared object file: No such file or directory
Content-type: text/html; charset=utf-8

Reporting-MTA: dns; cloud425.xxx.ro

Action: failed
Final-Recipient: rfc822;|/home/xxx/helpdesk.xxxxx.ro/api/pipe.php
Status: 5.0.0"

\So I talked with my hosting provider that said there is no problem with my domain, the ioncube loader is installed and on every domain and subdomain I have PHP 7.0.

Does anybody know what should I do?

ramrajone

odzsolut
your error issues might be permission or incorrect location:
cannot open shared object file: No such file or directory

odzsolut

ramrajone Hi there,
I tried to modify the permissions at file pipe.php because that's the only one that I can acces.
Being a shared host I don't have access to /opt/cpanel/ea-php70/root/usr/lib64/php/modules/ioncube_loader_lin_7.0.so: /opt/cpanel/ea-php70/root/usr/lib64/php/modules/ioncube_loader_lin_7.0.so
and my host provider said that the problem is not on server, is with osTicket.

I'm available to try anything to solve this ?

Thank you

ntozier

Does the webserver use a different config file than commandline php does? (this can happen if a host provides access to more than one version of PHP)

odzsolut

ntozier Hi there and thank you for your answer,

Yes, I have available a MultiPHP Manager, from where I can select what version of PHP I want to use for every domain or subdomain.
I tried to change there to verion 7.0 as it shows in error but the problem persist.
I tried to modify php.ini to other version of ioncube loader but nothing.
What is curios for me is that the problem started 2 weeks ago and I didn't do anything.

Thank you

ramrajone

odzsolut
ask your hosting provider to give you the full path to PHP version is installed which your shared hosting executing osTicket, then update that path.

other option to test is setup another osTicket fresh and test it, if everything good, then you can back up the database of a current and import it on to new.

ntozier

osTicket does not use ioncube_loader... so the problem is definitely on the server side. Heck I dont even know what that extension is/does. I have never heard of it.

Piping using command line php. So you might have to execute it using the full path to php instead of just the system shortcut of php. I do not know how you would do that on a third party host.

odzsolut

Hi,
So I have some updates but not necessary good: i asked my hosting provider to check the server and they said that everything is ok on their side. I tried to set up a new installation but the problem is still there.

I will try to update the path after I get an answer from them.

odzsolut

Hi there and thank you for your answers again,

My hosting provider replyed to me and told me that the full path to PHP version is "/opt/cpanel/ea-php72/root/usr/bin/php" but they mentioned that it is posible to don't work because it's a shared server and the existing accounts doesn't have access to that destination.

Taking this in consideration and my low knowledgebase, could you please tell me from where I can try to update the path?

Thank you very much.

ntozier

You would have to ask your host if you can using piping with postfix (or whatever mta they gave you) and point it to use a different version of PHP than the one that it uses now.

Although honestly it starting to sound like you are better off running IMAP and divorcing yourself from the headache of getting piping working with that host.