Recent content by yasha

  1. yasha

    access logs - request duration

    "time in milliseconds" - i think it is in microseconds, but this is less important. I want to know from wich event it starts counting - the 'start' timestamp. from your answer i understand it is the timestamp of recieving the request. handshake is not included. which event stops the counting -...
  2. yasha

    access logs - request duration

    Hi we want to know how long it takes to fulfill a response from client request. we use the access logs for this matter. the access logs configuration: logFormat "%t %a %s %H %m %B %D %U" in /usr/local/lsws/conf/httpd_config.conf. an example of log entry: "[28/May/2024:10:57:16 +0300]...
  3. yasha

    OpenLiteSpeed logs

    Hi I want to see only the QUIC logs, more precicly, the congestion control module from the QUIC library. How can I configure the OLS server to disable all other logs and show only the logs from QUIC. How can I configure the QUIC inside the OLS to show only the logs from the congestion control...
  4. yasha

    Failed to build OpenLiteSpeed from src

    the compiled binary works fine, thank u very mach for the time and help
  5. yasha

    Failed to build OpenLiteSpeed from src

    starting from scratch, created a new vm root@vu-VirtualBox:vu # uname -a Linux vu-VirtualBox 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux if u need more info about the system, compilers,... pls tell me. first time running ./build.sh, got...
  6. yasha

    Failed to build OpenLiteSpeed from src

    boringssl fails to build: root@server:openlitespeed-1.7.12 # cd ../third-party/src/ root@server:src <master># rm -rf boringssl/ root@server:src <master># cd ../script/ root@server:script <master># ./build_bssl.sh Cloning into 'boringssl'... remote: Enumerating objects: 83257, done. remote...
  7. yasha

    Failed to build OpenLiteSpeed from src

    it fails: root@server:script <master># pwd /home/oper/third-party/script root@server:script <master># ./build_bssl.sh HEAD is now at a2278d4d2 Include bn/internal.h for non-bcm.c builds. Previous HEAD position was a2278d4d2 Include bn/internal.h for non-bcm.c builds. Switched to branch 'master'...
  8. yasha

    Failed to build OpenLiteSpeed from src

    trying to build again resolves in smaller log: OS is Linux, APP_MGR_CMD is apt. Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://dl.google.com/linux/chrome/deb stable InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:4...
  9. yasha

    Failed to build OpenLiteSpeed from src

    removed the ../third-party directory, still not building. attached log of the build.
  10. yasha

    Failed to build OpenLiteSpeed from src

    Hi I want to include a different congestion control for QUIC protocol - PCC. for these, I am building the openlitespeed from source from these link openlitespeed. according to these documentation building litespeed from src, I run ./build.sh, but build fails. running ./build.sh for the second...
  11. yasha

    QUIC cc logs

    how can I change the QUIC log level? currently all I have in /usr/local/lsws/logs/error.log is: 2021-07-19 14:25:21.100326 [NOTICE] [135932] [AutoRestarter] child process with pid=135936 exited with status=0! 2021-07-19 14:25:21.100440 [NOTICE] [135932] [AutoRestarter] cleanup children processes...
  12. yasha

    QUIC cc logs

    Hi I'm using OLS server whith QUIC - lsquic, protocol and BBR or PCC as the congestion controls. how can i configure the QUIC, more specifically, QUIC congestion control, log level and where can I see it logs.
  13. yasha

    Using QUIC cc protocol with OpenLiteSpeed

    reconfigured the httpd_config.conf: ... listener Default { address *:443 secure 0 keyFile /home/oper/compiralabs_certs/compiralabs.key certFile /home/oper/compiralabs_certs/fbfda24f235b14b9.crt certChain 1...
  14. yasha

    Using QUIC cc protocol with OpenLiteSpeed

    Hi I can not configure the ols server to listen on udp 443 port on Quic. there is no listener on port 443. this is the /usr/local/lsws/conf/httpd_config.conf output: # # PLAIN TEXT CONFIGURATION FILE # #It not set, will use host name as serverName serverName user nobody...
Top