[Solved] Internal Server Error - Softaculous Apps Installer

[webdevsemo]

I get a 500 internal server error when I try to access Softaculous from my cpanel. Should this be working? Thanks

[Guest yikes]

Depends on what server. Johnny has issues with a lot of stuff.

[webdevsemo]

I'm on Tommy

[Sn1F3rt]

Sofaculous on Tommy works fine for me. Maybe, at the time you're trying to access Sofaculous, the server qas under high load. Just try again, it should be alright.

[wolstech]

Was this sometime last night?

 

I was having issues on tommy last night and he had a load of 116 (!!!) at one point (normal is usually 5-10).

[webdevsemo]

working now, thanks

[webdevsemo]

Oy, oh now, not working again. I don't know, but it seems related to something I'm doing on the site, because the problem has reoccured twice now, each time after doing the same thing, which is to try to restore my website from a backup with a backup/restore tool in Wordpress. Each time it has failed, which has motivated me to just wipe the site clean and restore from the backup to a new site. But when I go to do this I get the following message when I click on the Softaculous link: 

 

Internal Server Error

500

 

No response from subprocess (cpanel (cpanel)): The subprocess reported error number 72,057,594,037,927,935 when it ended. The process dumped a core file.

cpsrvd Server at tommy.heliohost.org

[Sn1F3rt]

Actually that has got to do with load itself. Maybe you were unlucky again, as you'd have tried to access Sofaculous when the server was under high load again. Shouldn't be anything to do with your account TBH.

[wolstech]

The backup tools in WP are likely the cause here. WP itself is notorious for being very heavy and causing load. Also, the restore failing is probably the PHP process running them timing out and being killed because they exceed the max allowed execution time.

 

To be honest, I'm surprised you didn't end up suspended for load due to those restores. You must've been lucky and tried when load was low.

 

The best solution to WP issues is, as always, to simply not use WP. It is terribly coded and consequently is horribly inefficient, not to mention insecure. Just about any other CMS in existence is faster.