how can nodebb print log according to each request



  • Is there any way in nodebb to see the log for each request? I find the ./nodebb log gives rare information.


  • Admin

    Try /admin/development/logger.



  • @baris
    Thanks!

    But the log is just like those in nginx log, right?
    Can I get the response time of each request?

    My site sometime is very slow at peak time. I want to find out the bottle neck.



  • @baris

    io: 0 emit [ 'disconnecting', 'ping timeout' ]
    io: 0 emit [ 'disconnect', 'ping timeout' ]
    io: 0 emit [ 'disconnecting', 'ping timeout' ]
    io: 0 emit [ 'disconnect', 'ping timeout' ]
    io: 0 emit [ 'disconnecting', 'transport close' ]
    io: 0 emit [ 'disconnect', 'transport close' ]
    io: 0 emit [ 'disconnecting', 'ping timeout' ]
    io: 0 emit [ 'disconnect', 'ping timeout' ]
    io: 0 emit [ 'disconnecting', 'transport close' ]
    io: 0 emit [ 'disconnect', 'transport close' ]
    io: 0 emit [ 'disconnecting', 'transport close' ]
    io: 0 emit [ 'disconnect', 'transport close' ]
    io: 0 emit [ 'disconnecting', 'ping timeout' ]
    io: 0 emit [ 'disconnect', 'ping timeout' ]
    io: 0 emit [ 'disconnecting', 'transport close' ]
    

    Plenty of such error... do you have some idea? and the website is very slow if such log is flooding.


  • Admin

    My site sometime is very slow at peak time. I want to find out the bottle neck.

    Please provide the output of ss -s during peak hours when site is "slow"



  • @julian

    Thanks for the instruction!
    This is the data for the normal hours, I will provide the peak data several hours later.

    Total: 7472 (kernel 0)
    TCP:   39360 (estab 7309, closed 31841, orphaned 193, synrecv 0, timewait 31841/0), ports 0
    
    Transport Total     IP        IPv6
    *         0         -         -
    RAW       0         0         0
    UDP       0         0         0
    TCP       7519      5865      1654
    INET      7519      5865      1654
    FRAG      0         0         0
    

    follows by the ulimit

    admin@discuss:~/NodeBB$ ulimit -a
    core file size          (blocks, -c) 0
    data seg size           (kbytes, -d) unlimited
    scheduling priority             (-e) 0
    file size               (blocks, -f) unlimited
    pending signals                 (-i) 63711
    max locked memory       (kbytes, -l) 64
    max memory size         (kbytes, -m) unlimited
    open files                      (-n) 10000
    pipe size            (512 bytes, -p) 8
    POSIX message queues     (bytes, -q) 819200
    real-time priority              (-r) 0
    stack size              (kbytes, -s) 8192
    cpu time               (seconds, -t) unlimited
    max user processes              (-u) 63711
    virtual memory          (kbytes, -v) unlimited
    file locks                      (-x) unlimited
    

    the file limit in /etc/sysctl.conf:

    # Digital Ocean Recommended Settings:
    net.core.wmem_max=12582912
    net.core.rmem_max=12582912
    net.ipv4.tcp_rmem= 10240 87380 12582912
    net.ipv4.tcp_wmem= 10240 87380 12582912
    vm.swappiness = 10
    fs.file-max = 70000
    

    file limit for the node process:

    admin@discuss:~/NodeBB$ cat /proc/15565/limits
    Limit                     Soft Limit           Hard Limit           Units
    Max cpu time              unlimited            unlimited            seconds
    Max file size             unlimited            unlimited            bytes
    Max data size             unlimited            unlimited            bytes
    Max stack size            8388608              unlimited            bytes
    Max core file size        0                    unlimited            bytes
    Max resident set          unlimited            unlimited            bytes
    Max processes             63711                63711                processes
    Max open files            30000                30000                files
    Max locked memory         65536                65536                bytes
    Max address space         unlimited            unlimited            bytes
    Max file locks            unlimited            unlimited            locks
    Max pending signals       63711                63711                signals
    Max msgqueue size         819200               819200               bytes
    Max nice priority         0                    0
    Max realtime priority     0                    0
    Max realtime timeout      unlimited            unlimited            us
    

    file limit in /etc/security/limits.conf:

    * soft nofile 10000
    * hard nofile 30000
    root soft nofile 10000
    root hard nofile 30000
    

    file limit in /proc/sys/fs/file-max

    admin@discuss:~/NodeBB$ cat /proc/sys/fs/file-max
    70000
    


  • @julian
    I am not sure which file limit actually counts, just provides all... hahaha



  • @julian

    This is the peak today(about 75% of history peak).

    Total: 13965 (kernel 0)
    TCP:   46823 (estab 13808, closed 32768, orphaned 231, synrecv 0, timewait 32768/0), ports 0
    
    Transport Total     IP        IPv6
    *         0         -         -
    RAW       0         0         0
    UDP       0         0         0
    TCP       14055     10241     3814
    INET      14055     10241     3814
    FRAG      0         0         0
    

    0_1478143628965_upload-11fe38fe-e73a-4561-a8eb-0ccceb91c223

    Actually, the performance today is better and fast after I applied a change in config:

    "socket.io": {
        "transports": ["websocket"]
    }
    

    That issue was at this link.


Log in to reply
 

Looks like your connection to NodeBB was lost, please wait while we try to reconnect.