216.118.116.105:time

[MikeMc]

Hi,
I have noticed when I do netstat (netstat -anp) on my server that the ip 216.118.116.105 is connected and reported as :

216.118.116.105:time ESTABLISHED PID/rdate

But this ip is the ip of the server that hosts this forum. I mean is an ip related to Darkorb. First I don't like the fact (maybe I'm just strange) that a server that hosts this board do also other jobs for Darkorb. I believe that this ip connects to my server for time sync reasons/tasks. But if this is correct why does it stay connected for that long. I saw this ip connected for hours. Has anybody noticed this? Is this a normal fact or not?

Thank you guys.

 

[MikeMc]

Almost 3 hours later and the connection from that ip to my server is still there. Anyone could explain this. I don't want to block a Darkorb ip as maybe the block could cause problems during updates etc. Don't know really why this ip should always be connected to my server? Any explanation?

Thanks.

 

[Website Rob]

Interesting that you get &105& as I get &104& : 216.118.116.104:80 CLOSE_WAIT

I'm presuming this is for the DarkORB & Security Package Updates; plus Cpanel updates. Do you show that IP also? Maybe the wrong IP was inputted by someone?

 

[MikeMc]

Hi, the last 2-3 days that I have noticed this fact (that a Darkorb ip connects that often to my server) I always saw the ip 216.118.116.105.

Monitoring this fact closely today I see that this ip is permanently connected to my server. I don't see what is the need of a permanent connection to my server. And the connection always is reported as ESTABLISHED.

 

[MikeMc]

Maybe I'm dreaming or I'm just too confused today. But I have killed the connection of the Darkorb ip to my server ...doing kill PID , and guess what....One second after started the process of packaging accounts, upcp etc....8 hours earlier from the scheduled time. Killing the connection acted like a trigger that launched the cron for the main cpanel tasks. Any explanation for this?

 

[Website Rob]

I would guess that first some determinations are required.

My setup is:
WHM 5.3.0 Cpanel 5.3.0-E85 RedHat 7.3
manual updates

Regardless of what version you are using, I can only guess that if you have &automatic& updates enabled, that might have something to do with the situation.

What happens to the connection if you switch to manual -- presuming you have currently have &automatic& enabled, and what happens after the switch, killing the process?

 

[MikeMc]

Hi, I'm on 5.3.0 - S69 (redhat 7.3) and the update preferences are all set to manual : Manual Updates Only (STABLE tree) for the Cpanel/WHM Updates and Manual Updates Only for DarkORB Package Updates and Security Package Updates.

I'd like to note that the main cron task ran and didn't do any updates, respecting my Update Preferences in WHM. The strange thing is that the main cron task started when I killed the connection to the Darkorb server, and did some tasks....well actually did ...backed up some accounts...not all of them !!!! also did upcp (correctly without upgrading). I don't really know why this happened.

(The main cron task should run in 7 hours from now, instead ran when I killed the connection to the Darkorb server).

 

[MikeMc]

Sorry for insisting on this, but has anyone ever experienced this? Thank you.

I would really appreciate an official reply from Darkorb if possible. Maybe should I open a support ticket?

 

[moronhead]

MikeMc,

You seem to be under surveillance from the DarkOrb team! What illegal actions have you been pursuing lately?

No, I've never seen that IP in netstat.

Regards,

Norman

 

[MikeMc]

I wish that it is (was) just a surveillance thing only
Anyway at least now the ip seems to have stopped loving my server. Maybe this will be another mystery...dropped in the net's black hole .

In any case if Darkorb has any infos to add on this issue I'll be glad to hear them. Thanks.

Thanks to Website Rob & moronhead for spending some of their time replying to my thread. Thanks guys.