Re: Lets try to find a solution (module not found error) [Module troubleshooting]

1

Lets try to find a solution (module not found error)

2007/4/11 20:10
jdseymour
Friend of XOOPS
Posts: 3782
Since: 2004/11/11

Again working on a clients site I have come across this "module not found" error when attempting to install a module.

Last week just after I upgraded the site to 2.0.16 I was able to install them with no trouble. The site is on a private server with php version 4.4.6 and MySQL 4.1x.

To trouble shoot the problem I have done the following:

The connection to the server is through SSH, same as on my server.

I have used both SFTP and SCP protocols to upload the modules.
First I noticed that the files I uploaded were owned by root (thought that was a problem) so I chowned the files and folders to be owned by the user the server runs as. Still no glory.

I have removed all unused modules, checked the database for stray tables. I have checked all debug modes for errors, none relevant to the issue.

I have tried different modules, still get the same error in the module admin. Upload the same modules to my site shows without problem.

I need other ideas of what to check next. I have a few maintenance items left to do, but am stuck until I get this fixed.

Proactive Support for Sites and Servers

WebServerMasters.com | XOOPS Tutorials

2

Re: Lets try to find a solution (module not found error)

2007/4/11 21:21
JMorris
XOOPS is my life!
Posts: 2722
Since: 2004/4/11

Ar you getting the module not found message, like when you've uploaded the module file structure incorrectly (i.e.: xoops_version.php not in the root of the module)?

If so, it sounds like your folder permissions are correct, but the file permissions are not.

Have you set your umask to 0022 so that the modules have the correct chmod settings when uploading.

Just throwing that one out there in case.

Indeed. Odd one.

Insanity can be defined as "doing the same thing over and over and expecting different results."

Stupidity is not a crime. Therefore, you are free to go.

3

Re: Lets try to find a solution (module not found error)

2007/4/11 21:31
jdseymour
Friend of XOOPS
Posts: 3782
Since: 2004/11/11

Yes I have double checked the permissions, directories 755 files 644. Yes the folder structure is correct, double and triple checked that, as well as uploaded the same module to my server that worked as expected.

Really got me stumped.

Proactive Support for Sites and Servers

WebServerMasters.com | XOOPS Tutorials

4

Re: Lets try to find a solution (module not found error)

2007/4/11 22:12
vaughan
Friend of XOOPS
Posts: 680
Since: 2005/11/26

any particular PHP configuration differences between servers?

5

Re: Lets try to find a solution (module not found error)

2007/4/11 22:25
Catzwolf
Home away from home
Posts: 1392
Since: 2007/9/30

Couple of things,

1. I would suggest this debugging: In XOOPS moduleadmin, there is an install function. In there somewhere try echo out the path that XOOPS is using it install a module (ie, the path that XOOPS thinks it is.). If it is the same then...

2. Is there a problem with the module database? is this corrupt?

3. As a debugging: in the kernel directory, look for module.php. In this class there is a function called 'loadInfo'. You can a var_dump() of '$this->modinfo' (around line 205 (ish). Again this will output various information about the module. If this is empty you know that XOOPS cannot find it local.

4. Check to see if the module is installed in the database, try the modules database.

Somethings to try to debug I guess (If you haven't already done so :) )

Catz

6

Re: Lets try to find a solution (module not found error)

2007/4/12 1:14
MadFish
Friend of XOOPS
Posts: 1056
Since: 2003/9/27

Maybe try deleting cache/adminmenu.php. Sometimes I get problems on the module admin page and clearing this out often fixes it.

hhttps://xoops.org

7

Re: Lets try to find a solution (module not found error)

2007/4/12 1:28
jdseymour
Friend of XOOPS
Posts: 3782
Since: 2004/11/11

Thanks all for the suggestions. I did try deleting adminmenu.php (one of the first things I tried).

Just repaired his database, had a table with over 5 million PMs. Going to work out a script to keep that table smaller (was 4.2 gigs).

16,000 active (and actively using) members on that site. I will explore further on Friday. Going to first explore and optimize the database for anything else left over. Going to set up some cron jobs for preventive maintenance.

Will post when I find the solution. Keep the suggestions coming though.

Thanks again.