Error after switching to PHP 8.0

Avatar
  • updated
  • Answered
I was on an old version of PHP which was becoming outdated, so I just switched to PHP 8.0. Now I am getting the following error at the bottom of every page:
Warning: PHP Startup: Unable to load dynamic library '/usr/lib64/monarx-protect/monarxprotect-php80.so' (tried: /usr/lib64/monarx-protect/monarxprotect-php80.so (/usr/lib64/monarx-protect/monarxprotect-php80.so: cannot open shared object file: No such file or directory), /opt/cpanel/ea-php80/root/usr/lib64/php/modules//usr/lib64/monarx-protect/monarxprotect-php80.so.so (/opt/cpanel/ea-php80/root/usr/lib64/php/modules//usr/lib64/monarx-protect/monarxprotect-php80.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0


This "monarx" is not something I've listed in my php.ini file. Not sure what needs done here.

Avatar
zak1
Quote from Chris M

Thank you for the update, zak1.  While there's no way for us to verify if this is the case, I would presume that the software you are running is calling for that package, which is possibly deprecated in the new PHP?   That's just a guess, since I don't know exactly what you are running. If possible, I would check with the developers of any software you're using, and they might be able to provide a patch or at least pass on some helpful information that might be of use to our support team.

With regard to the password reset issues, I was not able to replicate that particular issue, so it might have been a glitch. Rest assured we'll keep an eye out for any similar issues.

Not running software. I can literally create a NEW folder in my webspace, and create a single PHP file containing only the phpinfo() function, and the error shows up at the bottom of the page (when you have error reporting turned on in .htaccess).

Thanks for your time.

P.S., not sure what you meant in the email you sent about deleting my other post. Regarding being "unable to replicate this particular password reset issue", I'm not sure what you tried, but if you are going to test the links I posted, you need to be LOGGED OUT, as I was.

Avatar
Chris M
Quote from zak1

@Arnel C.: I had contacted Support, but they didn't give me a good answer. While rolling back to PHP version 5.4 results in me NOT getting the error code, it seems counterproductive to me to offer a version that is not working properly. While I was told that people who work on the code would be notified, there is no way for me to know when version 8.0 will be usable, which makes having it available right now a problematic thing.

As for not many people talking about the error, this may be because of 2 things:

1. In order to even SEE the error, you have to turn error reporting ON in your .htaccess file (which I do for development, for problems just such as this).

2. Your forum here seems to have some issues. Specifically, getting a password set, or reset, and activating one's account. None of the automated emails seem to be working properly. If you look at my other topic here, you will see the issues I have had. It is possible that other users cannot even get in to ACCESS the forum. I am a pretty resourceful coder, and even I could not figure this mess out...

Thank you for the update, zak1.  While there's no way for us to verify if this is the case, I would presume that the software you are running is calling for that package, which is possibly deprecated in the new PHP?   That's just a guess, since I don't know exactly what you are running. If possible, I would check with the developers of any software you're using, and they might be able to provide a patch or at least pass on some helpful information that might be of use to our support team.

With regard to the password reset issues, I was not able to replicate that particular issue, so it might have been a glitch. Rest assured we'll keep an eye out for any similar issues.

Avatar
zak1
Quote from Arnel C

Hello Zak,

Apologies for the confusion on the issue with Monarx-protect request error.  I checked around and it appears that you may have a support ticket in place for this issue.  If not, then I would highly recommend following up with one through our live technical support team.  They can escalate an issue like that to the T3 personnel who monitor the servers and work with the software on them.  We are a separate team and we do not have direct access to look at those particular logs.  

I did also try to find any documented cases on this error, and there is not much at all regarding it.  The best step is to look at the server logs to see what's happening when the error is occurring.  

I hope this helps to lead to a solution. If you need further assistance, please let us know!

Kindest regards,
Arnel C.

@Arnel C.: I had contacted Support, but they didn't give me a good answer. While rolling back to PHP version 5.4 results in me NOT getting the error code, it seems counterproductive to me to offer a version that is not working properly. While I was told that people who work on the code would be notified, there is no way for me to know when version 8.0 will be usable, which makes having it available right now a problematic thing.

As for not many people talking about the error, this may be because of 2 things:

1. In order to even SEE the error, you have to turn error reporting ON in your .htaccess file (which I do for development, for problems just such as this).

2. Your forum here seems to have some issues. Specifically, getting a password set, or reset, and activating one's account. None of the automated emails seem to be working properly. If you look at my other topic here, you will see the issues I have had. It is possible that other users cannot even get in to ACCESS the forum. I am a pretty resourceful coder, and even I could not figure this mess out...

Avatar
zak1

@JT S.: I'm afraid that that is NOT the case, as it even shows up on just a plain page with just the following code:

<?php phpinfo(); ?>

It shows up only on sites using the PHP 8.0 version. If I roll it back to PHP version 5.4 (which is what the InMotion Support Team recommended) then it works fine with no errors. So it MUST be that the monarx thingy was installed at some point, but the file was deleted from its folder. Since only the server admins can access the folder where the monarx file(s) are supposed to be, I cannot fix it myself, and I am only able to run on PHP version 5.4 at the moment...which is fine, but if 8.0 is broken, perhaps it should not be an option until it is working properly? Just saying.

Avatar
Arnel C

Hello Zak,

Apologies for the confusion on the issue with Monarx-protect request error.  I checked around and it appears that you may have a support ticket in place for this issue.  If not, then I would highly recommend following up with one through our live technical support team.  They can escalate an issue like that to the T3 personnel who monitor the servers and work with the software on them.  We are a separate team and we do not have direct access to look at those particular logs.  

I did also try to find any documented cases on this error, and there is not much at all regarding it.  The best step is to look at the server logs to see what's happening when the error is occurring.  

I hope this helps to lead to a solution. If you need further assistance, please let us know!

Kindest regards,
Arnel C.

Avatar
vcand

Did you ever find a solution? They're telling me the same thing and wanting to sell me an upgraded service in order to "solve" this issue. I have gone through everything on my site and there is nothing calling monarx... in fact, monarx with a security software program installed and operated by webhosts (not us, the end user).

Avatar
JT S.
  • Answered

Hi. It looks like something is requesting the Monarx application. I recommend checking your code to see if there's a legitimate request for it. Then, run a server scan with ClamAV or ImunifyAV.