Host Limiting Directory Path

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

I've got one site being hosted on Invision Power Service (same folks that make Invision Power Board).

Server Specs:
Linux server24.ipslink.com
MYSQL (4.1.21-standard)
PHP Version: 5.2.1 (apache)

I had been running RavenNuke(tm) v2.02.00 for six months on this server without any problems. Just within the past 3 days RN doesn't work correctly anymore. When in Admin Control Panel, clicking on modules only the first 4 modules in the modules directory are displayed.

I thought that they screwed with files or database so I created a /portal directory and loaded RavenNuke(tm) v2.02.02 fresh install. Then I tried RavenNuke(tm) v2.10.00 fresh install. Both install just fine, except they have the same problem as the original install, only 4 modules will display.

Qustion is: Can the host selectively restrict the directory depth in a specific directory, /modules in this case. I submitted a trouble ticket to them and indicated that they did something to the server in the past few days and phpNuke is not working anymore. There response was:

Quote:

Hello,

We do not support any 3rd party applications. You might want to contact the author of these applications for any problems you may have with them.

Any ideas?

hitwalker · Sells PC To Pay For Divorce Joined: Posts: 5661

no..
a directory shows its contents or not..
your host just sends the basic support answer...
they just say...good luck with it... Laughing

think something else happend...

Susann · Posted: Fri Apr 06, 2007 5:56 pm

Was the PHP Version in the past 6 months the same ?

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

PHP version has always been 5.X something. I believe they just went to 5.2.1. I'm running all the above versions of RN on xampp with php 5.2.1 and mysql 4.1.21 without any problems.

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

Update:

Here is what is happening. Upon a fresh install of any RN the database nuke_modules indicates the correct number of modules.

Entering admin and clicking on the Modules icon produces this result and the database nuke_modules indicates zero modules.

Only registered users can see links on this board!
Get registered or login to the forums!

Clicking the Modules icon a second time produces this result and the database nuke_modules indicates four modules.

Only registered users can see links on this board!
Get registered or login to the forums!

Click the Modules a third time shows zero modules, clicking a forth time shows 4 modules, etc.

If I delete the first four modules Advertising, AvantGo, Content and Downloads. It will show the next four modules.

I wish I knew what they did so I can tell them to fix 'Their Problem'.

fkelly · Posted: Sat Apr 07, 2007 8:39 am

What happens if you look at the directory structure thru FTP? Do all the modules show? Do they have a tool like Cpanel or Vdeck where you can look at your file structure? What shows there?

The modules program within the admin panel simply reads the modules directory and displays everything it finds there. So if the modules are out on disk it should be able to find them. I was going to say that it almost sounds like your admin control programs got fouled up in the process of transferring them but since you've done it twice with different versions and the same results that seems less likely. You could stick some echoes in the part of the control panel where it does the file reads, sorry I don't have the code open right in front of me to point more specifically. But I'd look at FTP first and make sure the modules are really there.

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

Viewing FTP all modules are visible. Viewing cPanel all modules are visible. modules directory permissions -> 755 and all modules permissions are 755.

Just this morning I uploaded straight phpNuke 7.6. Same problem as with RN versions.

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

Got an answer from IPS tech support. They just upgaded to PHP Version: 5.2.1.

montego · Posted: Sun Apr 08, 2007 10:10 am

I am also running PHP 5.2.x, so I am not sure if that is it. Did they, by chance, also upgrade mySQL? If so, what version did they upgrade to? I am running 5.0.x with no issues as yet.

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

montego wrote:

I am also running PHP 5.2.x, so I am not sure if that is it. Did they, by chance, also upgrade mySQL? If so, what version did they upgrade to? I am running 5.0.x with no issues as yet.

No they did not upgrade mySQL. MySQL is still 4.1.21. They admitted to upgrading to php 5.2.1. Like I indicated in a post above I'm running xampp with php 5.2.1 and mysql 4.1.21 without any problems. I still think they are doing something to run me off with phpNUke.

montego · Posted: Tue Apr 10, 2007 6:31 am

Unfortunately, I am just at a complete loss for what this could be. I've never seen it myself, nor heard of it until now, and outside of what I've already posted, I am fresh out of ideas. They have definitely changed something, but I had no idea what.

Any others have any more thoughts on what could be causing this?

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

Well I corrected the problem or maybe just delayed the problem for awhile. I swiched hosts.

New Host is running:

MySQL version 4.1.21-standard - Same as old host
PHP version 4.4.6 - Old host version was 5.2.1

I'm still investigating the original problem. When and if I find an answer I'll post the answer here.

montego · Posted: Fri Apr 13, 2007 6:50 am

Yes, definitely do post back if you find out why. It has to be host related. I just cannot see how it could not given how this is the first time in 3 years that I have ever seen this.

gregexp · Posted: Mon Apr 30, 2007 6:54 am

Hey guys, I know this thread isnt really being used anymore, but I figured Id drop in and tell you all about how I fixed the same issue.

There were multiple problems, one being that excution time was low, I dont believe that had any issues, but Mysql took a dive when its cache was low, /var directory on Linux, it could only write so much at one time and /tmp was not properly set, so If anyone does run into this problem, check your /tmp directory and /var directory, make sure both have plenty of room to grow.

[shell]df

output should be similar to this:
/dev/sda5 10317828 352988 9440724 4% /
/dev/sda1 101086 16825 79042 18% /boot
none 1036920 0 1036920 0% /dev/shm
/dev/sda7 207108528 38035200 158552764 20% /home
/dev/sda8 1035660 52380 930672 6% /tmp
/dev/sda3 10317860 2816344 6977396 29% /usr
/dev/sdb1 134409516 13604568 113977328 11% /var
/tmp 1035660 52380 930672 6% /var/tmp
/dev/sdb2 105953020 26828396 73742448 27% /backup

I have multiple drives and have configured the partitions to leave More then enough room for /var and /tmp

Solution to this problem can be found online, and I will provide the ssh commands to make /var much larger but will not right now, Its risky and until you know everything that you need to know, I wont tell you how, dont want you to destroy current work.

montego · Posted: Mon Apr 30, 2007 5:46 pm

That is odd that this is only having the issue with the reading of the modules directory (or the mySQL calls as a part of this function). If it was /var or /tmp related, I would have expected problems all over the place with the site. But, given his switch in hosts "fixed" it, I guess anything is possible.

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

Well, this is really starting to suck. Last night or early this morning the host update MySQL from 4.1.21 to 4.1.22. PHP is still at 4.4.6. Now I can't log in as Admin or as a user.

When I try to log in as Admin the page just refreshes back to login. When logging in as user, get error message 'Sorry, this Module isn't active!'.

I made a Fresh install of RavenNuke76_v2.02.00 in another database on same server and get the same errors. I looked in the database and all modules are active, but when I click on any of them I get 'Sorry, this Module isn't active!' Evil or Very Mad

Display errors is enabled but doesn't show any other errors. All modules are uploaded correctly (2 times). I have even disabled NukeSentinel.

gregexp · Posted: Fri May 04, 2007 2:23 pm

It happened because it was merely trying to enter information and the files could not be written, reading was fine.

As for the modules not being written, that is why, but if you were able to write lets say News articles, then no thats not your issue.

As for Captain_Computer, I recomend you find a STABLE host. Im not sure why you are experiencing those errors, it makes little sense, other then MYSQL is not configured properly. It makes little sense to me. You will always find a good host in Raven I know that for a fact.

Captain_Computer · Hangin' Around Joined: May 30, 2004 Posts: 46

This thread is all over the place, starting with what I thought was an Apache problem. Going to maybe php and now MySQL. But I'll continue with thread.

I've installed Joomla and Mambo and they run perfect. What I have discovered is that when a module is called

Only registered users can see links on this board!
Get registered or login to the forums!

that the "name" is not being passed to modules.php where it would be $name. So at about line 22 in modules.php when the db call

Code:

$result = $db->sql_query("SELECT * FROM `".$prefix."_modules` WHERE `title`='$name'");

is made title is not found because it doesn't know what $name is.

montego · Posted: Fri May 11, 2007 7:01 am

Captain_Computer, I am a bit confused with this here:

Quote:

What I have discovered is that when a module is called

Only registered users can see links on this board!
Get registered or login to the forums!

that the "name" is not being passed to modules.php where it would be $name.

The reason is that the thread originated with having issues seeing the modules in the administration control panel --> modules function. Did you find a resolution to that?

Regardless, if you have installed the latest RN 2.10.00/01, I know this package works. So, I am now thinking that there may be a PHP 5.2.1 setting in the php.ini that is causing this. Problem is, I just don't know what that would be. Can you somehow get your host to review the original php.ini to the revised or replaced one from the upgrade?