Suspended page problem

[MikeMc]

Hi,
I have suspended today a reseller and all the accounts under him. Suspension is done correctly, although the suspended page doesn't show. Which wouldn't be a great problem..but in my case when someone is trying to reach a suspended site, the page seems to load forever and I get hundred of entries in the domologs/somesite.

I have read all the previous posts related to suspended pages, on this forum, I have tried all the solutions but without result.

I need a solution on this before the domainlogs get out of control. It enters like 3-4 entries/second , so you understand the situation. I'm on the latest build.

Thank you.

 

[MikeMc]

I have used the suspend function via the Reseller Center in WHM.

 

[Annette]

Check under /home/user/public_html in the suspended account for a .htaccess. This should tell you where the system is looking for the suspended page. If it is not in that location, place it there. If the site is on a shared IP and you have not reordered the entries in the httpd.conf, you may need to place your serverwide suspended page in /usr/local/apache/htdocs to make it appear.

 

[MikeMc]

Thank you Annette , I really appreciate it. I'll try your advices right away. Thanks again.

 

[MikeMc]

In the .htaccess there is the correct url for the suspended.page and the suspended page is in the correct place and contains the index.html file.

The suspended.page is also present in /usr/local/apache/htdocs and contains the index.html file

Anything else I could check?

 

[Annette]

Things I can think of without the benefit of any caffeine in my system as yet....

- check the domlogs. What's the 404 saying for the suspended page?
- is the page readable or are the permissions somehow causing it not to be displayed?
- is there some sort of weird refresh on the suspended page causing it to loop indefinitely? We had a reseller do something like this, which caused suspended pages to continually refresh itself in a loop of death.

I'm sure there's more, but I'd be interested in the results from the first item.

 

[MikeMc]

Exactly it's the non stop loop that you're talking, that happens. A wierd refresh never ending. But I have no idea what could cause that.

I'm checking the rest you asked, now.

 

[MikeMc]

In the domlogs of the reseller's main domain get added lines like this :

..some ip... - - [17/Sep/2002:16:56:11 +0200] &GET /suspended.page/index.html HTTP/1.1& 302 306 &-& &Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)&


The permissions of the directory suspended.page are : drwxr-xr-x 2 username username 4096 Aug 30 11:17 suspended.page/

The index.html page in the suspended.page dir has this type of permissions :
-rw-r--r-- 1 username username 3506 Sep 17 16:55 index.html

 

[MikeMc]

Annette thank you very much. The problem is still present. I haven't managed to resolve it. But in any case thank you very much. Thank you for your time.

If there is somebody else that has any idea on how to resolve this, I would really appreciate it.

 

[Annette]

I dug around and finally found a suspended resold site. Like yours, the permissions on /home/reseller/public_html/suspended.page and the index under it are fine.

I'm curious about the status returned by apache in your example, though. Ideally, you'd just see a 200 as it served up the page, like this:

[17/Sep/2002:11:25:03 -0400] &GET /suspended.page/ HTTP/1.1& 200 3460 &-& &Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)&

Does the reseller have a .htaccess within their web root or within the suspended.page directory? 302 is a temporary redirect status code.

 

[MikeMc]

In the suspended.page directory of the reseller main domain there is no .htaccess file.

There isn't a .htaccess file in his root directory too.

There is the normal .htaccess (with the redirect to the suspension page) file in his public_html directory and another file named .htaccess.103....numbers (this last one is empty)

 

[Annette]

FP extensions - those excess .htaccess files are just garbage files.

If his .htaccess doesn't contain anything other than normal FP directives (or is empty due to removal of the extensions), that's not the issue. Have you looked at the source of the index file itself in suspended.page to see if there is some refresh within it? That's the last thing that comes to mind at the moment, without being able to move around on the box and poke at things.

 

[MikeMc]

The source of the suspended page is normal..there isn't present any code that could cause the refresh.

Annette you can't immagine how much I appreciate this you're doing. Anyway, I'll try to change some things and see if it will work. Please don't lose any more time with this. I hope that it won't cause me any serious problem with the domlogs increasing like this.

In case I find a solution I'll write here.

Thank you again. Best Regards
Mike

 

[Annette]

No problem. If anything else comes to mind, I'll send up a flag. Hope the mystery is solved soon.

 

[MikeMc]

I had to terminate the account, so I had no more time to examine the problem..so no solution but since the account got terminated...no worries at the moment...hope it takes long till the next time I'll have to suspend an account

Annette thanks again.

 

[Annette]

Ah, well - sometimes we do have to live with these little mysteries in our lives. :D

 

[JustinK]

Don't mean to bring things up from the dead, but found this when looking for something else and thought I'd remove the mystery to this one. Since it was a reseller account that was suspended, the suspended page attempts to load the suspended page from the resellers account. It basically goes into a loop because any requests for files under the account are redirected (mod_rewrite at work) to the suspended page.

Thus your infinite loop is born.

 

[Annette]

That could very well be it. We typically have root maintain ownership of the reseller accounts themselves, so don't really run into this on the rare occasion we have to suspend a reseller.

 

[MikeMc]

[quote:d5c041bbd0][i:d5c041bbd0]Originally posted by JustinK[/i:d5c041bbd0]

Don't mean to bring things up from the dead, but found this when looking for something else and thought I'd remove the mystery to this one. Since it was a reseller account that was suspended, the suspended page attempts to load the suspended page from the resellers account. It basically goes into a loop because any requests for files under the account are redirected (mod_rewrite at work) to the suspended page.

Thus your infinite loop is born. [/quote:d5c041bbd0]

Yes, you're right...I thought of this some days later (after the problem, but still had no occasion to test it and reproduce the whole situation). Thanks Justin. It's great to have mysteries resolved. Although I consider it as bug really. Isn't it? I don't know if they have fixed it at a later stage and so there is no such problem anymore (hadn't chance to test it).

Best regards
MikeMc

 

[mrbill]

Thank you everyone

thanks again to the forum and its members, another one of my problems solved.