needhelppp
Verified User
- Joined
- Jul 1, 2020
- Messages
- 88
Hi. I've been reinstalling my system many times now, and i noticed strange thing. When I select certain option in Edit Options tab (for example ModSecurity and Modsecurity ruleset) upon new installation, and I try to Update or Build it after, it opens a process window "Executing process". In it it downloads something the script needs (or sometimes stucks in the beginning), and then everything stucks. One example of the TAIL text is:
```
```
Then I have a button Close and Kill process. I press Close, then the screen becomes darker and everything is stuck - nothing can be done. So i have to refresh the page and do it again. Typically on second try it works as indtended. But Im not sure if it builds everything correctly and if it is done only once with no unneeded processes and files. So its messy and thats really annoying.
Anyone else noticed that BUG?And Maybe somone has some suggestions on how to avoid this/fix this?
Server has 4GB of RAM and plenty of CPU power. (KVM virtualisation).
Keep in mind that this happens not only with ModSecurity, but pretty much with any option selected and building afterwards.
Thanks
```
- Executing /usr/local/directadmin/plugins/custombuild/admin/build modsecurity_rules...
- Installing Comodo Rule Set for ModSecurity...
- Downloading cwaf_rules-1.230.tgz...
- --2020-07-08 02:49:47-- https://waf.comodo.com/api/da_vendor?file=cwaf_rules-1.230.tgz
- Resolving waf.comodo.com (waf.comodo.com)... 178.255.86.135
- Connecting to waf.comodo.com (waf.comodo.com)|178.255.86.135|:443... connected.
- WARNING: The certificate of 'waf.comodo.com' is not trusted.
- WARNING: The certificate of 'waf.comodo.com' has expired.
- HTTP request sent, awaiting response... 200 OK
- Length: 363567 (355K) [application/x-gzip]
- Saving to: '/usr/local/directadmin/custombuild/cwaf_rules-1.230.tgz'
- 0K .......... .......... .......... .......... .......... 14% 745K 0s
- 50K .......... .......... .......... .......... .......... 28% 2.15M 0s
- 100K .......... .......... .......... .......... .......... 42% 2.02M 0s
- 150K .......... .......... .......... .......... .......... 56% 2.31M 0s
- 200K .......... .......... .......... .......... .......... 70% 12.6M 0s
- 250K .......... .......... .......... .......... .......... 84% 2.78M 0s
- 300K .......... .......... .......... .......... .......... 98% 11.6M 0s
- 350K ..... 100% 32.0M=0.2s
- 2020-07-08 02:49:47 (2.15 MB/s) - '/usr/local/directadmin/custombuild/cwaf_rules-1.230.tgz' saved [363567/363567]
- 0K .......... .......... .......... .......... .......... 14% 753K 0s
- 50K .......... .......... .......... .......... .......... 28% 2.03M 0s
- 100K .......... .......... .......... .......... .......... 42% 2.31M 0s
- 150K .......... .......... .......... .......... .......... 56% 2.60M 0s
- 200K .......... .......... .......... .......... .......... 70% 11.9M 0s
- 250K .......... .......... .......... .......... .......... 84% 2.66M 0s
- 300K .......... .......... .......... .......... .......... 98% 12.2M 0s
- 350K ..... 100% 21.0M=0.2s
- 2020-07-08 02:49:47 (2.21 MB/s) - '/usr/local/directadmin/custombuild/cwaf_rules-1.230.tgz' saved [363567/363567]
```
Then I have a button Close and Kill process. I press Close, then the screen becomes darker and everything is stuck - nothing can be done. So i have to refresh the page and do it again. Typically on second try it works as indtended. But Im not sure if it builds everything correctly and if it is done only once with no unneeded processes and files. So its messy and thats really annoying.
Anyone else noticed that BUG?And Maybe somone has some suggestions on how to avoid this/fix this?
Server has 4GB of RAM and plenty of CPU power. (KVM virtualisation).
Keep in mind that this happens not only with ModSecurity, but pretty much with any option selected and building afterwards.
Thanks