Port 2087/2083 daily issues

[JeremyL]

For some reason, on a daily basis when I try to go to https://server.doamin.net:2087/ I get a \"The page cannot be displayed\". At the same time I can go to http://server.doamin.net:2086/ and can log into the WHM. At first I though it was SSL failing on the server, but if I go to https://www.livedomain.com at the same time and SSL on that domain works fine. So I\'m not sure if it\'s just the SSL cert for localhost failing or if it\'s because of port 2087 shutting down for some reason. The only way to fix it is by rebooting the server. And then a day later it happens again. Any idea why?

Now on to the next. Port 2083 is showing page cannot be displayed on a permanent basis and rebooting does not help at all. For example if I go to http://www.rockhosting.com:2082/ I can login fine. But if I go to https://www.rockhosting.com:2083/ I get the page cannot be displayed on a permanent basis.

How can I rectify this? It appears to be either a SSL or a CPanel issue.


[Edited on 12/1/01 by JeremyL]

[feanor]

Hummmmmmmmmmm....

Look at your portsentry configruation.... anything weird that would be yanking those ports into oblivion? Try killing all portsentry processes, leave them dead, then /etc/rc.d/init.d/cpanel3 restart

dice? no dice?
Firewall issues beyond your box?


Travis

[JeremyL]

Well restarting portsentry seemed to have fixed it. It works with it back on now to. but it\'s really weird. i can find nothing to tell me why it was doing it and I checked every file of portsentry I could find.

/var/lock/subsys/portsentry
/var/portsentry/portsentry.blocked.tcp
/var/portsentry/portsentry.blocked.udp
/var/portsentry/portsentry.history
/etc/portsentry/portsentry.conf
/etc/portsentry/portsentry.ignore

Now I just have to wait and see if it comes back.

Thanks for the help.

[feanor]

You can basically count on the problem to resurface- portsentry by habit scrutinizes everything above the 1000 ports... all the time, no matter what you tell it basically. It\'s anal once you go over tcp port 1024, no matter how you think you have it configured to ignore higher ports.

Basically I cron a portsentry/cpanel cycle script that runs 2 to 3 times a day on our machines.... it keeps everything in sync, you just have to find a schedule that fits w/ your machines / your environment.


peace.

[JeremyL]

So just cron a file to do


#!/bin/sh

/etc/rc.d/init.d/portsentry stop
sleep
/etc/rc.d/init.d/cpanel restart
sleep
/etc/rc.d/init.d/portsentry start

every day or twice a day then?

[feanor]

Basically- sure!
There are other things you could build into something like that, but for what you were having a problem with.... that will take care of it, or at least make sure that things are available much more often.

Good luck.



Travis

[JeremyL]

It was originally thought that portsentry had something to do with it. I can now verify portsentry has nothing to do with it. It is all a cpanel issue. To correct the issue all I have to do is restart cpanel and not portsentry so I am pretty sure it\'s an issue with cpanel only.

I now have a cron set to restart cpanel every hour on the hour but still when I go to do stuff in WHM it fails all the time and I have to restart cpanel manually before the hour is up. It\'s really annoying and I don\'t dare run the cron more than once an hour because it would affect my customers to much if the panel was restarted every 15 minutes.

There really needs to be a fix for this.

[Curious Too]

I have the same problem accessing port 2087. Several times a day a \"server cannot be found\" error is returned when trying to access port 2087 (problem only exists on one server) but SSL still works and access via port 2086 still works. I had to resort to creating a cron job that started stunnel every 10 minutes. There is no error messages in any of the server logs.

[rpmws]

you guys sure this isn\'t that stupid problem IE browsers have with SSL with in/out errors? Try with Netscape and see. I know that I have to force IE into SSL1.0 to keep it from dropping pages I access with forms and stuff using SSL. It\'s a common problem with IE.

[JeremyL]

I am positive it\'s not an IE issue. I have seen it do this on both netscrape and IE and if it was IE it wouldn\'t work just because CPanel was restarted.

[rpmws]

Just wanted to make sure. When I run mine on 2087 I get \"Page Not Found\" errors at times in IE and I simply can\'t get a page back unless I close out and come back in. Restarting cpanel would also force you to do that so that may could be an issue. But I guess you know what you are doing.. I only wanted to make sure you didn\'t have the same problem I have. Good luck with it.

[feanor]

Kill portsentry forever and I bet this wouldn\'t be an issue for you ever again. And/or your network is causing you not to be able to hit that port at times....

I have this occur once or twice a week uniquely on random machines- tops. But then again I\'m sure it has been more frequent in the past and will be again in the future.

Worthy of a bug submission perhaps? If you are using portsentry you have to keep in mind that the seizing of higher ports is always always a possibility regardless of what\'s running when and how important it might be.

There are many catch-22\'s with this product admittedly....


Love.

[MrHits]

I have never had a problem with using port 2087

Are you aware, that YOU MUST enter

http:// in your browswer when using ports?

If you just type in:
yourdomain.com:2087
you will get the error you describe.

If you type in:
https://yourdomain.com:2087
you should be ok.

I am not saying that this is your problem, as i have read your post above, and you have the correct url listed.

Good luck.

- Jeremy

[Edited on 12/13/01 by MrHits]

[JeremyL]

No it\'s nothing like that. I have been using Cpanel/WHM for awhile and this just started happeing. It has also been verified by my dedicated server provider and we are trying different things to correct it.

It seems the more I have cron restart cpanel the more it happens. If cron never restarts cpanel it maybe happens once a day but if I have cron restart it one an hour it almost always fails before the hour is over.

[feanor]

See that\'s interesting actually.
What is in /var/log/messages in the same ballpark of time as when port 2087 allegedly stops listening? Also, is there anything that even wildly corresponds to something fishy in /var/log/messages at or around the time when cron restarts cpanel?

There might be some weirdness occuring with another service and examining logs along with timeframes may get us somewhere.......