Skip to content

Mongo Eror with v3 beta-1

Solved Customisation
  • Hi everyone
    I created new dev web site finally, it was v2.8.2 and upgraded to v3 beta 1.
    When i started to nodebb faced below problem;

    Hit Ctrl-C to exit

    For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
    
    Clustering enabled: Spinning up 1 process(es).
    
    2023-01-22T09:19:17.958Z [4568/1276989] - info: Initializing NodeBB v3.0.0-beta.                               1 https://www.uzayyolu.org
    2023-01-22T09:19:48.126Z [4568/1276989] - error: MongoServerSelectionError: conn                               ect ECONNREFUSED 127.0.0.1:27017
        at Timeout._onTimeout (/home/nojor/nodebb/node_modules/mongodb/lib/sdam/topo                               logy.js:285:38)
        at listOnTimeout (internal/timers.js:557:17)
        at processTimers (internal/timers.js:500:7)
    [cluster] Child Process (1276989) has exited (code: 0, signal: null)
    

    Oh my god my other web site also shut downed 😞
    i think this is a problem with mango db?

  • @cagatay what’s the output of

    sudo service mongodb start
    

    @phenomlab i fixed it.

    yes two sites using same db and same iframely server as you know Mark.
    i upgraded one of to v.3 beta other one working v2.8
    after upgraded i faced the previous problem when i upgraded to v3.
    but i closed all process which worked on shell.
    then restarted my vps.
    activited all process again
    all sites is working 🙂

  • Hi everyone
    I created new dev web site finally, it was v2.8.2 and upgraded to v3 beta 1.
    When i started to nodebb faced below problem;

    Hit Ctrl-C to exit

    For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
    
    Clustering enabled: Spinning up 1 process(es).
    
    2023-01-22T09:19:17.958Z [4568/1276989] - info: Initializing NodeBB v3.0.0-beta.                               1 https://www.uzayyolu.org
    2023-01-22T09:19:48.126Z [4568/1276989] - error: MongoServerSelectionError: conn                               ect ECONNREFUSED 127.0.0.1:27017
        at Timeout._onTimeout (/home/nojor/nodebb/node_modules/mongodb/lib/sdam/topo                               logy.js:285:38)
        at listOnTimeout (internal/timers.js:557:17)
        at processTimers (internal/timers.js:500:7)
    [cluster] Child Process (1276989) has exited (code: 0, signal: null)
    

    Oh my god my other web site also shut downed 😞
    i think this is a problem with mango db?

    Looks like the Mongoserver to database isn’t connecting or Its not available.

  • Looks like the Mongoserver to database isn’t connecting or Its not available.

    @cagatay are you using the same database for production as you are for development? It certainly looks to be the case.

  • Hi everyone
    I created new dev web site finally, it was v2.8.2 and upgraded to v3 beta 1.
    When i started to nodebb faced below problem;

    Hit Ctrl-C to exit

    For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
    
    Clustering enabled: Spinning up 1 process(es).
    
    2023-01-22T09:19:17.958Z [4568/1276989] - info: Initializing NodeBB v3.0.0-beta.                               1 https://www.uzayyolu.org
    2023-01-22T09:19:48.126Z [4568/1276989] - error: MongoServerSelectionError: conn                               ect ECONNREFUSED 127.0.0.1:27017
        at Timeout._onTimeout (/home/nojor/nodebb/node_modules/mongodb/lib/sdam/topo                               logy.js:285:38)
        at listOnTimeout (internal/timers.js:557:17)
        at processTimers (internal/timers.js:500:7)
    [cluster] Child Process (1276989) has exited (code: 0, signal: null)
    

    Oh my god my other web site also shut downed 😞
    i think this is a problem with mango db?

    Try to change localhost to 127.0.0.1

    If it doesn’t work maybe you don’t have Mongoserver at all. So try to restart it on this New fresh install

    Example on Mac

    brew services start mongodb-community@5.0
    
  • Try to change localhost to 127.0.0.1

    If it doesn’t work maybe you don’t have Mongoserver at all. So try to restart it on this New fresh install

    Example on Mac

    brew services start mongodb-community@5.0
    

    @Sala MongoDB is definitely there as I built the server. The command below is designed for MAC and won’t work on Linux.

  • Hi everyone
    I created new dev web site finally, it was v2.8.2 and upgraded to v3 beta 1.
    When i started to nodebb faced below problem;

    Hit Ctrl-C to exit

    For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
    
    Clustering enabled: Spinning up 1 process(es).
    
    2023-01-22T09:19:17.958Z [4568/1276989] - info: Initializing NodeBB v3.0.0-beta.                               1 https://www.uzayyolu.org
    2023-01-22T09:19:48.126Z [4568/1276989] - error: MongoServerSelectionError: conn                               ect ECONNREFUSED 127.0.0.1:27017
        at Timeout._onTimeout (/home/nojor/nodebb/node_modules/mongodb/lib/sdam/topo                               logy.js:285:38)
        at listOnTimeout (internal/timers.js:557:17)
        at processTimers (internal/timers.js:500:7)
    [cluster] Child Process (1276989) has exited (code: 0, signal: null)
    

    Oh my god my other web site also shut downed 😞
    i think this is a problem with mango db?

    @cagatay what’s the output of

    sudo service mongodb start
    
  • @cagatay what’s the output of

    sudo service mongodb start
    

    @phenomlab i fixed it.

    yes two sites using same db and same iframely server as you know Mark.
    i upgraded one of to v.3 beta other one working v2.8
    after upgraded i faced the previous problem when i upgraded to v3.
    but i closed all process which worked on shell.
    then restarted my vps.
    activited all process again
    all sites is working 🙂

  • cagatayundefined cagatay has marked this topic as solved on
  • @phenomlab i fixed it.

    yes two sites using same db and same iframely server as you know Mark.
    i upgraded one of to v.3 beta other one working v2.8
    after upgraded i faced the previous problem when i upgraded to v3.
    but i closed all process which worked on shell.
    then restarted my vps.
    activited all process again
    all sites is working 🙂

    @cagatay ok. You should use a copy of the production database or a completely new one. Never share a database between two instances of NodeBB.


Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • navbar

    Solved Customisation
    2
    2 Votes
    2 Posts
    9 Views
    Marking as resolved, based on https://community.nodebb.org/topic/18625/navbar/2
  • Forum customisation

    Customisation
    11
    2
    6 Votes
    11 Posts
    320 Views
    Thank you Mark, the changes look fantastic!!
  • 14 Votes
    17 Posts
    388 Views
    No problem dude ! I hope you have a good vacation. Enjoy your loved ones!
  • 3 Votes
    6 Posts
    667 Views
    @kadir-ay-0 marking as resolved based on https://community.nodebb.org/topic/17109/manual-build-a-night-mode-for-harmony/5 Please do not raise requests in two places - here and the NodeBB forums. All this does is create unnecessary load for both parties.
  • Page control arrows for PWA

    Solved Customisation
    27
    25 Votes
    27 Posts
    2k Views
    @crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems. /** * Determine the mobile operating system. * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'. * * @returns {String} */ function getMobileOperatingSystem() { var userAgent = navigator.userAgent || navigator.vendor || window.opera; // Windows Phone must come first because its UA also contains "Android" if (/windows phone/i.test(userAgent)) { return "Windows Phone"; } if (/android/i.test(userAgent)) { return "Android"; } if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream) { return "iOS"; } return "unknown"; // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android } Once you’re in that rabbit hole, it’s impossible to get out of it.
  • Header Menu After Upgrading V3.1.1

    Solved Customisation
    2
    1
    2 Votes
    2 Posts
    205 Views
    @cagatay this relates to a change the css classes used for the brand header meaning it will now float to the left instead of right. If you’d like to retain the original behavior, you can add this css class [data-widget-area="brand-header"] { justify-content: end; display: flex; } Further information here https://community.nodebb.org/topic/17090/manual-build-a-custom-header-in-harmony/19?_=1684069325296
  • Issues with Progress Bar on v3

    Solved Customisation
    48
    1
    14 Votes
    48 Posts
    3k Views
    @Panda You could use the below .page-topic .pagination-block.ready { display: none; }
  • NodeBB v3 Chat Very Slow

    Moved Performance
    47
    11 Votes
    47 Posts
    4k Views
    @DownPW Seems fine.