Modules Deactivate Automatically

Hangin' Around Joined: Nov 04, 2004 Posts: 34

I guess the subject of the post says it all. For some reason, 2 or 3 times a day, for no reason, the a few of my modules become deactivated. The only thing I can think is that the modules that deactivate were written by me. I dont think thats the problem because I had them on and running a few weeks before this started. It seems to only leave default modules activated. I can reactivate them and they will stay on many hours. But then it does it again. http://www.snafu3d.com/mae/ go there if you want to see which modules stay active. I have not reactivated the offending modules. Thank you to anyone that can help or give some info.

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

From time to time this problem crops up and I have never seen a reply that fixes it. I have seen it occur when a site is moved from one location to another on the same server. Also I have seen it occur when running under MacOS. Another occasion was a permission's error on one of the folders that the module needed. I have never been able to reproduce it. I have copied the person's site to my server and it works fine. Yet on his it doesn't.

What versions of the following are you using?
phpNuke
PHP
MySQL
Apache
Linux or Windows?

Posted: Sun Dec 05, 2004 9:53 pm

phpNuke 6.5
PHP 5.0
MySQL 4.0.22
(Not Apache) IIS 4.0
Windows 2000 Server

Also, i wanted to add. My configuration has been like this from the beginning. Its worked just fine up until now. I made no big changes before.

Posted: Sun Dec 05, 2004 9:59 pm

PHP 5.0 is not ready for prime time. Try backing down to 4.3.9

Subject Matter Expert Joined: Feb 23, 2004 Posts: 358

Agree with Raven... PHP 5 and Nuke haven't been tested enough yet (and we should all get on that.. soon!). Win IIS is an absolute nightmare of permissions that cause the weirdest behaviors that nobody can duplicate. If you don't abso-no_choice_about_it HAVE to use IIS, I'd suggest Apache 2 for Win32, it's quite stable... What also is kinda strange is that you seem to be using all of the latest language libraries and db engines, but you're running Nuke 6.5? I'd get that upgraded to 7.4 at a minimum, and do all of ChatGod's patches. I'm taking a liberty here and assuming that since you're using such an old version of Nuke that it may be heavily modded. If that's the case, then quite often some weird code gets into mainfile, or modules, and getting some fresh files may nail the problem.

Sorry man... this is not a common problem, and is not a Nuke bug that can be 'fixed' as far as I know. This is either a PHP problem, a server-side problem, or a file problem. Tough to sort... you have my sympathy!

PHrEEk

Posted: Mon Dec 06, 2004 6:07 am

Well I switched to PHP 4.0 and it seems to be fixed. By the way, I use 6.5 because when i use anything else, the site never works. I just gave up on the newwer ones for now.

Posted: Mon Dec 06, 2004 10:20 am

Use 4.3.9, not 4.0.

Posted: Mon Dec 06, 2004 10:51 am

Thats what i have. I said 4.0 by mistake because the file name is php4ts.dll

Posted: Tue Dec 07, 2004 10:53 pm

I spoke too soon... site is doing it again. Any other thoughts?

Posted: Tue Dec 07, 2004 11:12 pm

I'd create a new test client (I'm assuming from the config you posted that either this is a dedicated server you run, or is your actual local machine), and upload a fresh install of Nuke from here.. either 7.4 or .5, and see if the problem can be duplicated with the new site. If it does, then obviously we have a web server or permissions problem server-side. If not, then you have something in your 6.5 filesystem that is problematic.

If modules sees a folder in the /modules folder, it adds it automagically to the Admin panel for activation. If it's actually activated, then Nuke checks for that folder's existance each time. If it doesn't 'see it', it removes the active flag from the DB for that module, deactivating it. It doesn't unlink the folder or anything destructive. But it seems your database for some reason is deactivating these modules from 1 to 0, and Nuke does that as a part of module maintenance. That is where the problem is.. now as to why... :: scratches head :: that is the question...

PHrEEk

Posted: Wed Dec 08, 2004 1:50 am

This is just a thought but it is derived from experience. When I had a client who had this happening, I wrote a script that checked the module's status every minute or whatever. If the status was zero, it would reset it to 1 and also sms the owner. That seemed to work for a while; a short while. What started happening was MySQL was blocking access for as much of an unknown reason as the deactivation was! Use phpMyAdmin and run a repair on the nuke_modules table. You never know ......

Posted: Wed Dec 08, 2004 6:13 am

I just tried the repair with phpmyadmin. No success there. I'm about to try a new install. I'll let you know.

Posted: Thu Dec 09, 2004 10:25 am

Well i think its fixed. I reinstalled my webserver. All seems to be normal again. I'll let you know. Thanx to everyone for trying to help.

New Member Joined: Apr 29, 2005 Posts: 9

I'm having the same problem. I'm on Phpnuke 7.4 php4.x. Actually its IPBNUKE 7.4. And again only the modules written by me are affected.

Posted: Fri Apr 29, 2005 8:24 am

What webserver and version of PHP are you running?

Posted: Fri Apr 29, 2005 8:35 am

MrAnderson wrote:

What webserver and version of PHP are you running?

I think it directly related to the modules I've created.

I basically wanted to use iframes.

this is the code I did and placed the index.php file in a folder under /modules

Code:

<? 


   if (!eregi("modules.php", $_SERVER['PHP_SELF'])) 


   { 


      die ("You can't access this file directly..."); 


   }


   if(!IsSet($mainfile)) 


   { 


      include ("mainfile.php"); 


   } 


   $index=0; 


   $theme="DeepBlue"; 


   $go_to_address1="http://www.urbanpakistan.com/interviews/salman_ahmed_press_release_interview.htm"; 


   $go_to_address=rawurldecode($go_to_address1); 


   include("header.php"); 


   OpenTable(); 


   // echo "<center><h4><a href=\"index.php\">HOME</a></h4></center>"; 


   echo "<iframe SRC=\"".$go_to_address."\" width=\"100%\" height=\"3000\" framespacing=0 frameborder=no border=0 scrolling=auto></iframe>"; 


   // echo "<br><center></center><br>"; 


   CloseTable(); 


   include("footer.php"); 


   die; 


?>

Is this code doing something weird with things? I read this code in a how-to I got off google. Basically all u got to do is feed the url to ur document in the $go_to_address1 variable. Google didn't bring up many results to this problem, either.

Posted: Fri Apr 29, 2005 8:36 am

Have you checked your server error log? If Nuke can't load the module's index.php file, for any reason, it sets it to off.

Posted: Fri Apr 29, 2005 8:41 am

btw.

php 4.3.1
OS linux
Apache 1.3.33

I've bought webhosting, so I really can't tinker around with those things.

Posted: Fri Apr 29, 2005 8:42 am

Raven wrote:

Have you checked your server error log? If Nuke can't load the module's index.php file, for any reason, it sets it to off.

hmmmm, u might be onto something there.... I'll get back to ya.

Posted: Fri Apr 29, 2005 8:58 am

nope I got nothing. I don't even understand the code, I just copy pasted it and modified the link a little. I'm pretty certain thats screwing it up. Since the dude up there, said its only the modules that he wrote are deactivating.

Posted: Fri Apr 29, 2005 9:04 am

Change IsSet to isset

Posted: Fri Apr 29, 2005 10:50 am

it doesn't active at all now.

registered · Posted: Fri Apr 29, 2005 12:20 pm

A passing thought...

I'm running PHP-Nuke 6.5 Final, patched & mod'ed, and it doesn't care much for the MySQL 4.x layer. That is, the canned Nuke features don't have a problem with MySQL 4.x, but many of my modules, blocks, et cetera, do.

So, in 'config.php', I always stipulate...

Code:

$dbtype = "MySQL";

...instead of...

Code:

$dbtype = "mysql4";

...even though I use MySQL 4.0.22 for the sql db on my site.

Just thought I'd throw that out for public consumption... Wink

Posted: Fri Apr 29, 2005 1:45 pm

Why aren't many people affected by this problem!?

haha not wishing it on others, but just that there would be a solution out there if there were plenty of people affected by this. google shows up with very little results.

Posted: Sat Apr 30, 2005 12:10 am

I've seen this one before but so far there doesn't seem to be a common cause, people with this problem have seen it get fixed by optimizing the db tables and by dropping the modules db table and creating it again among other things, one of the most seen causes is that of running two Nuke sites with both using the same database or sitting in the same server under different sub-directories, a user in particular had a test site stored in a sub-folder of his main site, when he got rid of it the modules stopped deactivating themselves.