The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

how to restart apache through cpanel command line?

Discussion in 'EasyApache' started by charliesxia, Jan 22, 2011.

Thread Status:
Not open for further replies.
  1. charliesxia

    charliesxia Member

    Joined:
    Aug 3, 2006
    Messages:
    18
    Likes Received:
    1
    Trophy Points:
    0
    my apache crushed today.
    I received a lot of letter

    httpd failed @ Sat Jan 22 19:54:57 2011. A restart was attempted automagically.
    Service Check Method: [tcp connect]

    Failure Reason: Unable to connect to port 80

    so I login into the shell
    but "httpd start" command does not work
    I use "kill -9 httpd"

    Code:
    httpd: no process killed
    and I have to login into the whm
    restart apache successfully

    and anyone give the command line how cp restart the httpd,
    so I donot have to login the WHM.
    Thank you very much.
     
    gaza331 likes this.
  2. rejected

    rejected Well-Known Member

    Joined:
    Sep 19, 2006
    Messages:
    48
    Likes Received:
    0
    Trophy Points:
    0
    apachectl start or /usr/local/apache/bin/apachectl start
     
  3. LinuxTechie

    LinuxTechie Well-Known Member

    Joined:
    Jan 22, 2011
    Messages:
    502
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Hello,

    You can also use the below given command


    >> service httpd restart
     
  4. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Of note, cPanel will automatically try to restart Apache with this message:

    This is what the part "A restart was attempted automagically." means. You can log into the server in root SSH and check if Apache is running after that without having to restart it yourself:

    Code:
    ps aux|grep httpd
    If you see running processes, then it's running and you don't need to restart it. You can also try to load sites in a browser or telnet to port 80 to see if it connects:

    Code:
    telnet localhost 80
    This would be run on the machine itself to see if localhost is working on port 80 (the normal Apache port).

    Now, I would highly suggest if you get a lot of these messages checking via netstat to see how many Apache processes are running, because it might not be connecting to port 80 not because it's going down but either a) it's reaching the maximum number of connections (MaxClients and/or ServerLimit), or b) it's getting a denial of service attack.

    In the event of a denial of service attack, you would check:

    How many Apache processes are running:

    Code:
    netstat -an | grep :80|wc -l
    How many Apache processes are in SYN_RECV state:

    Code:
    netstat -an | grep :80 | grep -i syn | wc -l
    You can see how many times various IPs are connecting on the machine with this command:

    Code:
    netstat -an|grep :80|grep SYN|awk {'print $5'}|cut -d: -f 1|sort|uniq -c
    To combat a denial of service attack, you could check into (D)DoS Deflate if it's a high number of connections from select IPs (normally you'd want to see at least 50+ connections from several of the IPs in the prior command to consider using (D)DoS Deflate, since you don't want to block lower level legitimate connections):

    http://deflate.medialayer.com/

    Another option might be to look into something like CSF where it can be configured to do some of these same types of actions:

    ConfigServer Security & Firewall

    If it's a slowloris, which would use up all the connections and then keep the connections for a prolonged period of time, rather than a synflood on port 80, you could try the following to reduce the impact in the firewall:

    Code:
    /sbin/iptables -I INPUT -p tcp -m state --state NEW --dport 80 -m recent --update --seconds 15 --hitcount 10 -j DROP
    A couple of other handy commands to see the pattern for the traffic on the machine:

    Code:
    tcpdump -nn 'tcp[13] == 2' and port 80 -c 100 -i any
    tcpdump -Annvvs 1500 'tcp[13] == 2' and port 80 -c 100 -i any
    (Thanks go to a colleague, Jeff, who provided these tcpdump commands recently and I'm taking his commands to provide here.)

    I do want to stress that denial of service attacks are outside what cPanel can provide for support. If you are unable to stem an attack that's a synflood or slowloris on the machine, then you'd want to be in contact with your datacenter, NOC or provider for filtering assistance. I'm giving the above to assist in some steps you can take to possibly cut down on a low level attack. Your datacenter, NOC or provider will be best able to help with a moderate to severe denial of service attack.

    If the issue isn't high connections that are in SYN_RECV state (the grep for syn in the prior command earlier), then you might check for any hits in /usr/local/apache/logs/error_log for hitting the MaxClients limit:

    Code:
    grep -i maxclient /usr/local/apache/logs/error_log
    You'd see something like the following if you are hitting MaxClients:

    To increase MaxClients, you can do that in WHM > Apache Configuration > Global Configuration area. Of note, you will also need to increase ServerLimit (in that same area) to the value you use for MaxClients, so keep them both the same as you cannot raise MaxClients above ServerLimit past a certain number (256 for MPM_Prefork and 16 for MPM_Worker and MPM_Event).
     
  5. crazyaboutlinux

    crazyaboutlinux Well-Known Member

    Joined:
    Nov 3, 2007
    Messages:
    938
    Likes Received:
    0
    Trophy Points:
    16
    we have got email from our dc regarding ddos attack, I ran tcpdump command see following result
    Code:
    -bash-3.2# tcpdump -nn 'tcp[13] == 2' and port 80 -c 100 -i any
    tcpdump: WARNING: Promiscuous mode not supported on the "any" device
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
    14:15:45.807718 IP 114.31.147.227.52132 > 56.89.401.211.80: S 1762747271:1762747271(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:15:46.937028 IP 14.97.32.124.51959 > 56.89.401.211.80: S 1059417953:1059417953(0) win 8192 <mss 1460,nop,wscale 2,nop,nop,sackOK>
    14:15:46.943446 IP 14.97.32.124.51960 > 56.89.401.211.80: S 1573647392:1573647392(0) win 8192 <mss 1460,nop,wscale 2,nop,nop,sackOK>
    14:15:47.827688 IP 114.31.147.227.52132 > 56.89.401.211.80: S 1762747271:1762747271(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:15:47.917688 IP 69.171.229.246.52758 > 56.89.401.211.80: S 2268649836:2268649836(0) win 14600 <mss 1460,sackOK,timestamp 3338032528 0,nop,wscale 9>
    14:15:48.112072 IP 27.116.49.131.1355 > 56.89.401.211.80: S 268992377:268992377(0) win 65535 <mss 1440,nop,wscale 1,nop,nop,sackOK>
    14:15:48.494127 IP 27.116.49.131.1360 > 56.89.401.211.80: S 969475912:969475912(0) win 65535 <mss 1440,nop,wscale 1,nop,nop,sackOK>
    14:15:48.498190 IP 27.116.49.131.1361 > 56.89.401.211.80: S 3833393622:3833393622(0) win 65535 <mss 1440,nop,wscale 1,nop,nop,sackOK>
    14:15:48.499779 IP 27.116.49.131.1363 > 56.89.401.211.80: S 3731262877:3731262877(0) win 65535 <mss 1440,nop,wscale 1,nop,nop,sackOK>
    14:15:48.657695 IP 14.97.32.124.51963 > 56.89.401.211.80: S 1419742103:1419742103(0) win 8192 <mss 1460,nop,wscale 2,nop,nop,sackOK>
    14:15:49.578105 IP 122.179.185.199.49654 > 56.89.401.211.80: S 2260810156:2260810156(0) win 65535 <mss 1440,nop,nop,sackOK>
    14:15:51.805329 IP 199.67.203.141.59349 > 56.89.401.211.80: S 3309343864:3309343864(0) win 65535 <mss 1460,sackOK,eol>
    14:15:52.355985 IP 69.41.170.87.57482 > 56.89.401.211.80: S 2478523268:2478523268(0) win 5840 <mss 1460,sackOK,timestamp 3144299427 0,nop,wscale 0>
    14:15:53.047689 IP 183.182.85.19.58055 > 56.89.401.211.80: S 3850625310:3850625310(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:15:53.932884 IP 122.179.185.199.49668 > 56.89.401.211.80: S 1361449170:1361449170(0) win 65535 <mss 1440,nop,nop,sackOK>
    14:15:54.545318 IP 125.89.75.100.37879 > 56.89.401.211.80: S 3439865972:3439865972(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:15:55.007926 IP 122.179.185.199.49669 > 56.89.401.211.80: S 2832617429:2832617429(0) win 65535 <mss 1440,nop,nop,sackOK>
    14:15:57.777656 IP 42.105.215.253.49980 > 56.89.401.211.80: S 1822683809:1822683809(0) win 8192 <mss 1360,nop,wscale 8,sackOK,timestamp 289058 0>
    14:15:57.830456 IP 66.249.72.54.60570 > 56.89.401.211.80: S 1966058704:1966058704(0) win 5840 <mss 1460,sackOK,timestamp 1323425434 0,nop,wscale 6>
    14:15:58.814024 IP 42.105.215.253.49981 > 56.89.401.211.80: S 660291920:660291920(0) win 8192 <mss 1360,nop,wscale 8,sackOK,timestamp 289093 0>
    14:15:58.821971 IP 199.67.203.141.63410 > 56.89.401.211.80: S 1339591264:1339591264(0) win 65535 <mss 1460,sackOK,eol>
    14:15:58.850891 IP 42.105.215.253.49982 > 56.89.401.211.80: S 2010332256:2010332256(0) win 8192 <mss 1360,nop,wscale 8,sackOK,timestamp 289093 0>
    14:15:58.988616 IP 66.249.72.67.34777 > 56.89.401.211.80: S 1991394561:1991394561(0) win 5840 <mss 1460,sackOK,timestamp 1323834253 0,nop,wscale 6>
    14:15:59.780063 IP 180.76.5.196.13325 > 56.89.401.211.80: S 778959591:778959591(0) win 5840 <mss 1460,sackOK,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,wscale 7>
    14:16:00.427914 IP 125.89.75.100.39204 > 56.89.401.211.80: S 3532075053:3532075053(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:06.581457 IP 81.30.76.204.12701 > 56.89.401.211.80: S 4186876460:4186876460(0) win 4380 <mss 1380,sackOK,timestamp 417378263 0,nop,wscale 6>
    14:16:08.770037 IP 122.169.65.179.56752 > 56.89.401.211.80: S 3874564023:3874564023(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:08.841020 IP 115.119.80.50.13582 > 56.89.401.211.80: S 223669150:223669150(0) win 65535 <mss 1380,nop,nop,sackOK>
    14:16:09.019340 IP 122.169.65.179.56753 > 56.89.401.211.80: S 1537072857:1537072857(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:09.759729 IP 122.169.65.179.56754 > 56.89.401.211.80: S 445301864:445301864(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:09.760200 IP 122.169.65.179.56755 > 56.89.401.211.80: S 2448043901:2448043901(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:09.762916 IP 122.169.65.179.56756 > 56.89.401.211.80: S 1722821331:1722821331(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:09.767662 IP 122.169.65.179.56757 > 56.89.401.211.80: S 3522489654:3522489654(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:12.510041 IP 62.61.175.157.28714 > 56.89.401.211.80: S 1116002714:1116002714(0) win 16384 <mss 1400,nop,nop,sackOK>
    14:16:14.103163 IP 27.116.49.131.1399 > 56.89.401.211.80: S 3851115846:3851115846(0) win 65535 <mss 1440,nop,wscale 1,nop,nop,sackOK>
    14:16:15.414800 IP 91.224.160.127.3701 > 56.89.401.211.80: S 1563996701:1563996701(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:16.028667 IP 220.181.108.185.51825 > 56.89.401.211.80: S 1974026901:1974026901(0) win 5840 <mss 1460,sackOK,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,wscale 7>
    14:16:16.132155 IP 91.224.160.127.3864 > 56.89.401.211.80: S 541268907:541268907(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:16.464307 IP 91.224.160.127.3930 > 56.89.401.211.80: S 1136533444:1136533444(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:16.837142 IP 91.224.160.127.4000 > 56.89.401.211.80: S 4148612094:4148612094(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:17.177583 IP 91.224.160.127.4084 > 56.89.401.211.80: S 2839143090:2839143090(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:17.605105 IP 122.169.65.179.56771 > 56.89.401.211.80: S 942113701:942113701(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:17.650097 IP 91.224.160.127.4201 > 56.89.401.211.80: S 2646331220:2646331220(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:17.824857 IP 14.97.32.124.51982 > 56.89.401.211.80: S 4187903315:4187903315(0) win 8192 <mss 1460,nop,wscale 2,nop,nop,sackOK>
    14:16:17.851938 IP 122.169.65.179.56772 > 56.89.401.211.80: S 448433924:448433924(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:18.020792 IP 91.224.160.127.4263 > 56.89.401.211.80: S 4249651480:4249651480(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:18.639915 IP 122.169.65.179.56773 > 56.89.401.211.80: S 1147187169:1147187169(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:18.645616 IP 122.169.65.179.56774 > 56.89.401.211.80: S 3392699703:3392699703(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:18.650935 IP 122.169.65.179.56775 > 56.89.401.211.80: S 2308806266:2308806266(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:18.655726 IP 122.169.65.179.56776 > 56.89.401.211.80: S 1291004607:1291004607(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:21.642986 IP 122.169.65.179.54066 > 56.89.401.211.80: S 2101243542:2101243542(0) win 5840 <mss 1452,sackOK,timestamp 3399360 0,nop,wscale 6>
    14:16:22.825037 IP 114.31.147.227.52135 > 56.89.401.211.80: S 3034774160:3034774160(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:22.857475 IP 67.195.115.96.51242 > 56.89.401.211.80: S 3620975298:3620975298(0) win 5840 <mss 1460,sackOK,timestamp 688240239 0,nop,wscale 8>
    14:16:23.345141 IP 114.31.147.227.52136 > 56.89.401.211.80: S 583003572:583003572(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:23.419557 IP 67.195.115.96.51288 > 56.89.401.211.80: S 3623294858:3623294858(0) win 5840 <mss 1460,sackOK,timestamp 688240816 0,nop,wscale 8>
    14:16:24.375195 IP 69.41.170.87.57483 > 56.89.401.211.80: S 2497360022:2497360022(0) win 5840 <mss 1460,sackOK,timestamp 3144331451 0,nop,wscale 0>
    14:16:25.845042 IP 114.31.147.227.52135 > 56.89.401.211.80: S 3034774160:3034774160(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:25.904889 IP 114.31.147.227.52136 > 56.89.401.211.80: S 583003572:583003572(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:28.069084 IP 122.169.65.179.56787 > 56.89.401.211.80: S 4020917778:4020917778(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:28.069828 IP 122.169.65.179.56788 > 56.89.401.211.80: S 1141633719:1141633719(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:16:30.618564 IP 66.249.72.131.34002 > 56.89.401.211.80: S 3426257031:3426257031(0) win 5840 <mss 1460,sackOK,timestamp 885613510 0,nop,wscale 6>
    14:16:31.317543 IP 112.200.233.242.41991 > 56.89.401.211.80: S 3383652172:3383652172(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:31.516360 IP 27.116.49.131.1415 > 56.89.401.211.80: S 3080076255:3080076255(0) win 65535 <mss 1440,nop,wscale 1,nop,nop,sackOK>
    14:16:34.085434 IP 114.31.147.227.52137 > 56.89.401.211.80: S 2699343245:2699343245(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:34.661772 IP 66.249.72.80.64788 > 56.89.401.211.80: S 2559363335:2559363335(0) win 5840 <mss 1460,sackOK,timestamp 1323834827 0,nop,wscale 6>
    14:16:34.705663 IP 114.31.147.227.52138 > 56.89.401.211.80: S 451725549:451725549(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:36.107520 IP 114.31.147.227.52137 > 56.89.401.211.80: S 2699343245:2699343245(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:37.706305 IP 114.31.147.227.52138 > 56.89.401.211.80: S 451725549:451725549(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:39.939095 IP 114.31.147.227.52139 > 56.89.401.211.80: S 720176069:720176069(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:40.308926 IP 122.169.65.179.54068 > 56.89.401.211.80: S 2392874207:2392874207(0) win 5840 <mss 1452,sackOK,timestamp 3404027 0,nop,wscale 6>
    14:16:43.295256 IP 173.192.238.44.58108 > 56.89.401.211.80: S 1836258476:1836258476(0) win 14600 <mss 1460,sackOK,timestamp 1769586876 0,nop,wscale 7>
    14:16:43.920662 IP 114.31.147.227.52139 > 56.89.401.211.80: S 720176069:720176069(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:44.739063 IP 208.80.194.26.35979 > 56.89.401.211.80: S 531212016:531212016(0) win 5840 <mss 1380,nop,nop,timestamp 61518084 0,nop,wscale 7>
    14:16:45.314438 IP 112.200.233.242.42015 > 56.89.401.211.80: S 3420165986:3420165986(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:16:45.783344 IP 184.77.7.137.52134 > 56.89.401.211.80: S 1713655559:1713655559(0) win 8192 <mss 1360,nop,wscale 2,nop,nop,sackOK>
    14:16:47.322348 IP 66.249.72.82.43404 > 56.89.401.211.80: S 2749574749:2749574749(0) win 5840 <mss 1460,sackOK,timestamp 1323847488 0,nop,wscale 6>
    14:17:02.315740 IP 123.125.71.15.42566 > 56.89.401.211.80: S 2271822245:2271822245(0) win 5840 <mss 1460,sackOK,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,wscale 7>
    14:17:02.392423 IP 220.181.108.83.49273 > 56.89.401.211.80: S 2432216130:2432216130(0) win 5840 <mss 1460,sackOK,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,wscale 2>
    14:17:03.854591 IP 220.181.108.90.38795 > 56.89.401.211.80: S 2436497881:2436497881(0) win 5840 <mss 1460,sackOK,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,wscale 2>
    14:17:04.639638 IP 180.76.5.66.11710 > 56.89.401.211.80: S 852143540:852143540(0) win 5840 <mss 1460,sackOK,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,wscale 7>
    14:17:05.144326 IP 66.249.72.80.64700 > 56.89.401.211.80: S 3028318955:3028318955(0) win 5840 <mss 1460,sackOK,timestamp 1323865310 0,nop,wscale 6>
    14:17:08.343588 IP 122.169.65.179.56795 > 56.89.401.211.80: S 756757580:756757580(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:17:08.593019 IP 122.169.65.179.56796 > 56.89.401.211.80: S 755481268:755481268(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:17:08.618634 IP 42.105.215.253.49996 > 56.89.401.211.80: S 1398634142:1398634142(0) win 8192 <mss 1360,nop,wscale 8,sackOK,timestamp 296146 0>
    14:17:08.736231 IP 42.105.215.253.49997 > 56.89.401.211.80: S 1856152140:1856152140(0) win 8192 <mss 1360,nop,wscale 8,sackOK,timestamp 296171 0>
    14:17:09.401575 IP 122.169.65.179.56797 > 56.89.401.211.80: S 1635967989:1635967989(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:17:09.402343 IP 122.169.65.179.56798 > 56.89.401.211.80: S 20820056:20820056(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:17:09.404564 IP 122.169.65.179.56799 > 56.89.401.211.80: S 481717318:481717318(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:17:09.410157 IP 122.169.65.179.56800 > 56.89.401.211.80: S 2196448098:2196448098(0) win 8192 <mss 1452,nop,nop,sackOK>
    14:17:09.708174 IP 8.12.44.154.12181 > 56.89.401.211.80: S 1257511962:1257511962(0) win 49640 <mss 1460,nop,wscale 0,nop,nop,sackOK>
    14:17:10.200445 IP 8.12.44.154.59352 > 56.89.401.211.80: S 465869847:465869847(0) win 49640 <mss 1460,nop,wscale 0,nop,nop,sackOK>
    14:17:10.692996 IP 8.12.44.154.61916 > 56.89.401.211.80: S 1507671036:1507671036(0) win 49640 <mss 1460,nop,wscale 0,nop,nop,sackOK>
    14:17:10.885640 IP 66.249.72.226.61399 > 56.89.401.211.80: S 3488553965:3488553965(0) win 5840 <mss 1460,sackOK,timestamp 3433299568 0,nop,wscale 6>
    14:17:11.186455 IP 8.12.44.154.40112 > 56.89.401.211.80: S 3279639289:3279639289(0) win 49640 <mss 1460,nop,wscale 0,nop,nop,sackOK>
    14:17:12.507911 IP 62.61.175.157.28715 > 56.89.401.211.80: S 2283605722:2283605722(0) win 16384 <mss 1400,nop,nop,sackOK>
    14:17:13.308783 IP 122.179.185.199.49792 > 56.89.401.211.80: S 31700553:31700553(0) win 65535 <mss 1440,nop,nop,sackOK>
    14:17:13.338603 IP 122.179.185.199.49793 > 56.89.401.211.80: S 3077186119:3077186119(0) win 65535 <mss 1440,nop,nop,sackOK>
    14:17:16.781323 IP 180.76.5.63.11013 > 56.89.401.211.80: S 863089114:863089114(0) win 5840 <mss 1460,sackOK,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,wscale 7>
    14:17:19.250922 IP 58.185.198.142.44975 > 56.89.401.211.80: S 2570781268:2570781268(0) win 65535 <mss 1460,nop,nop,sackOK>
    14:17:19.443250 IP 85.17.171.225.62077 > 56.89.401.211.80: S 1250517459:1250517459(0) win 8192 <mss 1460,nop,nop,sackOK>
    100 packets captured
    101 packets received by filter
    0 packets dropped by kernel
    let me know what to do next ??
     
    #5 crazyaboutlinux, Sep 16, 2011
    Last edited: Sep 16, 2011
  6. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    I've provided examples on what to do in my post above. Please let us know which you've attempted to do.
     
  7. fcbinfo

    fcbinfo Well-Known Member

    Joined:
    Dec 10, 2006
    Messages:
    120
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Tristan...

    I belive this forum without you, maybe will not work.

    Many times for many problems, when i try to find a solution, everytime the solutions is already posted by you.

    For me... you are the GOD!

    I need to say "THANKS" to you, and the cPanel support need say thanks for you too.

    I believe that many support requests are not forwarded to the support of cpanel because the solutions are already posted by you all here in this forum.

    YOU ARE THE SOLUTION MAN! SUPER HERO!

    And more ... when you reply, reply seems eager to help. Your responses are complete. I think you're one of the owners of cPanel.
     
    #7 fcbinfo, Jan 9, 2013
    Last edited: Jan 9, 2013
  8. xvn

    xvn Registered

    Joined:
    Apr 21, 2013
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Website Owner
    Greetings,
    I'm using WHM that has the following config:
    WHM 11.28.86
    CENTOS 5.5 x86_64 virtuozzo on vps
    The site use Joomla 2.5 CMS which I hope is not relevant to my question.

    I need a command line that restarts the apache and in particular, fastcgi, services exactly as they are started when the system is rebooted. I have tried all the options in this article and I'm hoping that posting here will generate more feedback than creating a brand new post as I've worked through this thread and the best luck that I've had is using "/scripts/restartsrv_apache" but even this script over time doesn't seem to be reliably shutting down the running services and then restarting a fresh set. This thread is the best resource that I've found in hours of looking into this so I hope that there is some joy here.
    Where would I look to determine exactly what is being done to start apache on reboot? I must be able to do the same from the command line until I can figure out what is causing fstcgi to stop responding (or at least that is what I think is happening). No matter what, I need to get this command line fix in place asap and appreciate any insight that you may have.
    thanks,
     
Loading...
Thread Status:
Not open for further replies.

Share This Page