• HOME
    • PRODUCT
    • PRICING
    • ABOUT
    • COMMUNITY
    Menu
    • HOME
    • PRODUCT
    • PRICING
    • ABOUT
    • COMMUNITY
    Get in touch
    Get in touch
    Menu
    • HOME
    • PRODUCT
    • PRICING
    • ABOUT
    • COMMUNITY
    • Sign in
    • Start free trial
    • Get in touch
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    • Users
    • Groups
    • Documentation
      • Home
      • Read API
      • Write API
      • Plugin Development
    1. Home
    2. xidui
    • Profile
    • Following 2
    • Followers 1
    • Topics 11
    • Posts 44
    • Best 5
    • Controversial 0
    • Groups 0

    xidui

    @xidui

    5
    Reputation
    749
    Profile views
    44
    Posts
    1
    Followers
    2
    Following
    Joined Last Online
    Website xidui.github.io Location Shanghai

    xidui Unfollow Follow

    Best posts made by xidui

    • 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.

      posted in Technical Support
      xidui
      xidui
    • How can I stop subcategory to show at home page

      In a parent category I have plenty of subcategories, larger than 100. If show all of them at home page, It looks ugly.

      posted in Feature Requests
      xidui
      xidui
    • RE: socket.io log flooding

      @xidui said in socket.io log flooding:

      I added this config:

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

      The flooding error seems less than before. But still need to monitor over several days.

      The performance seems better after I applied this change in config.

      1. Behaviors before change:

        • Most of the logs are io emit timeout or io emit transport close . Only very rare portion (less than 10 percent) of requests successfully processed.
        • Every time I restart the site it can not response for about 5 minutes or longer even I see in the log that process has already listened to 4567.
        • Some of the socket.io/EIO?xxxx requests failed at client side.
      2. Behaviors after change:

        • No io emit timeout was found ever
        • io emit transport close still exists, about 50% or less at peak hour and 10% at valley hour.
        • The site is fast enough at peak hour and it can recover quickly even I restart.
        • None of the requests failed at client side.

      @administrators
      I think my issue has accidentally and surprisingly solved by this small change temporarily. I wonder why and is this config recommended or ["polling", "websocket"] is better? And do you have some idea on the root cause of the issue when I use ["polling", "websocket"]?

      posted in Bug Reports
      xidui
      xidui
    • RE: Can I sort topics by votes or views or date?

      We have made this plugin. Try it and having fun~
      https://github.com/wktang/nodebb-plugin-category-sort-by-votes

      posted in NodeBB Development
      xidui
      xidui
    • RE: mongodb always down

      @AOKP
      Thank you for your offer. After the change in this issue, my mongo db has not went down until now. It seems to be more stable.

      posted in Technical Support
      xidui
      xidui

    Latest posts made by xidui

    • RE: socket.io log flooding

      Thanks for every one!

      This issue seems to disappear after the change in config. Our site is more stable than ever before in the last week with a rather short response time during the whole week.

      Thanks again and welcome to have a visit. Advices on the site is always welcomed.

      posted in Bug Reports
      xidui
      xidui
    • RE: mongodb always down

      @AOKP
      Thank you for your offer. After the change in this issue, my mongo db has not went down until now. It seems to be more stable.

      posted in Technical Support
      xidui
      xidui
    • RE: mongodb always down

      @pichalite
      Thanks for the information. Do you have some idea on how those team deal with the issue that mongodb may down every several days? Mongodb Cluster or something else?
      As I see it, mongodb cluster is too heavy for such an deployment with NodeBB.

      @Jop-V
      Thank you 🙂

      posted in Technical Support
      xidui
      xidui
    • RE: socket.io log flooding

      @xidui said in socket.io log flooding:

      I added this config:

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

      The flooding error seems less than before. But still need to monitor over several days.

      The performance seems better after I applied this change in config.

      1. Behaviors before change:

        • Most of the logs are io emit timeout or io emit transport close . Only very rare portion (less than 10 percent) of requests successfully processed.
        • Every time I restart the site it can not response for about 5 minutes or longer even I see in the log that process has already listened to 4567.
        • Some of the socket.io/EIO?xxxx requests failed at client side.
      2. Behaviors after change:

        • No io emit timeout was found ever
        • io emit transport close still exists, about 50% or less at peak hour and 10% at valley hour.
        • The site is fast enough at peak hour and it can recover quickly even I restart.
        • None of the requests failed at client side.

      @administrators
      I think my issue has accidentally and surprisingly solved by this small change temporarily. I wonder why and is this config recommended or ["polling", "websocket"] is better? And do you have some idea on the root cause of the issue when I use ["polling", "websocket"]?

      posted in Bug Reports
      xidui
      xidui
    • RE: how can nodebb print log according to each request

      @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.

      posted in Technical Support
      xidui
      xidui
    • RE: how can nodebb print log according to each request

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

      posted in Technical Support
      xidui
      xidui
    • RE: how can nodebb print log according to each request

      @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

      [email protected]:~/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:

      [email protected]:~/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

      [email protected]:~/NodeBB$ cat /proc/sys/fs/file-max
      70000
      
      posted in Technical Support
      xidui
      xidui
    • RE: mongodb always down

      @Adam-Poniatowski
      Try systemctl enable mongod if you use Centos7.
      It will link some scripts to the upstart dir.

      posted in Technical Support
      xidui
      xidui
    • RE: socket.io log flooding

      @baris

      That's single machine, 4 processes and the 1000 is active user not online user.

      posted in Bug Reports
      xidui
      xidui
    • RE: socket.io log flooding

      I added this config:

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

      The flooding error seems less than before. But still need to monitor over several days.

      posted in Bug Reports
      xidui
      xidui

    Get Started

    • Product
    • Pricing

    Resources

    • Demo Site
    • Answers
    • Docs
    • Bug Bounty

    Company

    • About
    • Blog
    • Contact
    Start Free Trial
    Github Facebook Instagram Twitter
    © 2014 – 2022 NodeBB, Inc. — Made in Canada.
    • Terms
    • Privacy
    • GDPR
    • DMCA
    • Contact
    Menu
    • Terms
    • Privacy
    • GDPR
    • DMCA
    • Contact