Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
16
Apache / Re: Long restart time
« on: December 23, 2017, 12:18:17 PM »
about 50 accounts
6 Core (2600 MHz) Xenon E5-2670
8GB RAM
6 Core (2600 MHz) Xenon E5-2670
8GB RAM
17
Apache / Long restart time
« on: December 22, 2017, 11:36:06 PM »
I have a problem with long restart apache time.
after service httpd restart
restart took 1.5 min
This is what I see in log:
[Fri Dec 22 23:53:23.845043 2017] [mpm_event:notice] [pid 3334:tid 140523955419008] AH00492: caught SIGWINCH, shutting down gracefully
[Fri Dec 22 23:53:27.218636 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13757 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:27.218688 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13668 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:27.218705 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13669 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:29.220637 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13757 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:29.220689 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13668 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:29.220707 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13669 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:31.222638 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13757 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:31.222698 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13668 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:31.222711 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13669 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:33.224470 2017] [core:error] [pid 3334:tid 140523955419008] AH00046: child process 13757 still did not exit, sending a SIGKILL
[Fri Dec 22 23:53:33.224536 2017] [core:error] [pid 3334:tid 140523955419008] AH00046: child process 13669 still did not exit, sending a SIGKILL
[Fri Dec 22 23:55:04.540712 2017] [ssl:warn] [pid 15643:tid 140254855550848] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
[Fri Dec 22 23:55:04.550639 2017] [mpm_event:notice] [pid 15643:tid 140254855550848] AH00489: Apache/2.4.29 (Unix) OpenSSL/1.0.1e-fips configured -- resuming normal operations
[Fri Dec 22 23:55:04.550677 2017] [core:notice] [pid 15643:tid 140254855550848] AH00094: Command line: '/usr/local/apache/bin/httpd'
what couse long restart time ?
after service httpd restart
restart took 1.5 min
This is what I see in log:
[Fri Dec 22 23:53:23.845043 2017] [mpm_event:notice] [pid 3334:tid 140523955419008] AH00492: caught SIGWINCH, shutting down gracefully
[Fri Dec 22 23:53:27.218636 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13757 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:27.218688 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13668 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:27.218705 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13669 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:29.220637 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13757 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:29.220689 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13668 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:29.220707 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13669 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:31.222638 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13757 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:31.222698 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13668 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:31.222711 2017] [core:warn] [pid 3334:tid 140523955419008] AH00045: child process 13669 still did not exit, sending a SIGTERM
[Fri Dec 22 23:53:33.224470 2017] [core:error] [pid 3334:tid 140523955419008] AH00046: child process 13757 still did not exit, sending a SIGKILL
[Fri Dec 22 23:53:33.224536 2017] [core:error] [pid 3334:tid 140523955419008] AH00046: child process 13669 still did not exit, sending a SIGKILL
[Fri Dec 22 23:55:04.540712 2017] [ssl:warn] [pid 15643:tid 140254855550848] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
[Fri Dec 22 23:55:04.550639 2017] [mpm_event:notice] [pid 15643:tid 140254855550848] AH00489: Apache/2.4.29 (Unix) OpenSSL/1.0.1e-fips configured -- resuming normal operations
[Fri Dec 22 23:55:04.550677 2017] [core:notice] [pid 15643:tid 140254855550848] AH00094: Command line: '/usr/local/apache/bin/httpd'
what couse long restart time ?
18
CentOS-WebPanel Bugs / Re: Link to webmail dosn't work
« on: December 19, 2017, 02:21:01 PM »Is it fresh/new CWP installation?
no
19
How to / Server down
« on: December 13, 2017, 03:25:20 PM »
Today one of my server go down.
I get information that main server was not restarted.
How can I check at my VPS what caused shoutdown ??
centos 7
I get information that main server was not restarted.
How can I check at my VPS what caused shoutdown ??
centos 7
20
CentOS-WebPanel Bugs / support section - dosnt work
« on: December 12, 2017, 06:18:45 PM »
under cwp logo there is button "support section"
I do not know what is it for - it dosn't work - It should be removed it is not used
I do not know what is it for - it dosn't work - It should be removed it is not used
21
CentOS-WebPanel Bugs / wrong calculate of usage on email account
« on: December 12, 2017, 06:15:34 PM »
User Panel.
List email account show that email usage is 100%. But I never defined max amount.
How is it calculated ?
List email account show that email usage is 100%. But I never defined max amount.
How is it calculated ?
22
CentOS-WebPanel Bugs / user can't change account password
« on: December 12, 2017, 06:13:43 PM »
There is no confirm button to change user account password
23
CentOS-WebPanel Bugs / fix account permision dosn't chown hidden files
« on: December 12, 2017, 05:21:46 PM »
fix account permision dosn't chown hidden files
.htaccess and so on
.htaccess and so on
24
CentOS-WebPanel Bugs / Link to webmail dosn't work
« on: December 11, 2017, 04:43:25 PM »
login to Client panel.
Go to: Email accounts
There is link to webmail.
It opens URL: http://domain.com:2095/autologin.php?idsession=XXXXXX
Result is:
404 Not Found
cwpsrv
Go to: Email accounts
There is link to webmail.
It opens URL: http://domain.com:2095/autologin.php?idsession=XXXXXX
Result is:
404 Not Found
cwpsrv
25
CentOS-WebPanel Bugs / Re: BIG WHOLE - totally insecured fix urgent
« on: December 06, 2017, 09:02:02 PM »
It was fixed with last CWP update (new theme). I will check it with addon hacking test 
26
Information / Re: Did You make CWP update today ?
« on: December 06, 2017, 04:25:36 PM »
I do not have access for CWP source - becouse it is encoded.
27
Information / Re: Did You make CWP update today ?
« on: December 06, 2017, 09:13:37 AM »
Best is that I can help develop CWP but I get no answer.
I'm a perfectionist, I know it's a defect but I can use it well. I could make this panel best in the market.
I'm a perfectionist, I know it's a defect but I can use it well. I could make this panel best in the market.
28
Information / Re: Did You make CWP update today ?
« on: December 06, 2017, 06:49:50 AM »
I am developing software more then 15 years. Cwp is not piece of cake. But for me lots off problem are easy to fix.
And yes - developing system like this is not a joke. Should not be joke becosue cwp is used in real word not at home.
And yes - developing system like this is not a joke. Should not be joke becosue cwp is used in real word not at home.
29
Information / Re: Did You make CWP update today ?
« on: December 05, 2017, 09:13:13 PM »
@Gogo
1. I known about new CWP "is comming". It was few weeks ago. For me there should be information for example one day before CWP started deploy new version. I call it: professionalism.
2. I do not hate CWP. I get angry (yes I can be angry) about something that happend but should not. It dosn't matter if software is FREE or PAYED. This (1) should not happend.
3. CWP is good software and I want it will be the best. I use it becouse I see potential with it. Complain should be used for better developing - not for crying.
4. I write answer for problems on forum, writed CWP module - for FREE. You can use it. I do not expect any respect from anyone. I do this becouse I love it but I can't respect when something goes wrong. I want this software will be better but don't want worries about its future.
5. 99% problems are posted by me ? Really. Do not be so ignorant
Try to count it again.
1. I known about new CWP "is comming". It was few weeks ago. For me there should be information for example one day before CWP started deploy new version. I call it: professionalism.
2. I do not hate CWP. I get angry (yes I can be angry) about something that happend but should not. It dosn't matter if software is FREE or PAYED. This (1) should not happend.
3. CWP is good software and I want it will be the best. I use it becouse I see potential with it. Complain should be used for better developing - not for crying.
4. I write answer for problems on forum, writed CWP module - for FREE. You can use it. I do not expect any respect from anyone. I do this becouse I love it but I can't respect when something goes wrong. I want this software will be better but don't want worries about its future.
5. 99% problems are posted by me ? Really. Do not be so ignorant
Try to count it again.
