Skip to content
Sudonix

sudonix

Mongo Eror with v3 beta-1

Solved Customisation
  • undefined

    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?

    undefined undefined 3 Replies
    0
  • undefined phenomlab

    @cagatay what’s the output of

    sudo service mongodb start
    undefined

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

    1
  • undefined cagatay

    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?

    undefined

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

    1
  • undefined Sala

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

    undefined

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

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    1
  • undefined cagatay

    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?

    undefined

    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
    0
  • undefined Sala

    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
    undefined

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

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • undefined cagatay

    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?

    undefined

    @cagatay what’s the output of

    sudo service mongodb start

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    0
  • undefined phenomlab

    @cagatay what’s the output of

    sudo service mongodb start
    undefined

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

    1
  • undefined cagatay has marked this topic as solved on 22 Jan 2023, 13:55
  • undefined cagatay

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

    undefined

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

    Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…

    1
    • 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 💗
Log in to reply

1/8

22 Jan 2023, 09:23


Related Topics
  • JACundefined

    Forum customisation

    Customisation
    8 17 Oct 2024, 21:39
    17 Oct 2024, 21:39
    2
    6 Votes
    11 Posts
    326 Views
    JACundefined
    Thank you Mark, the changes look fantastic!!
  • DownPWundefined

    Fancybox zoom

    Unsolved Customisation
    8 24 Sept 2024, 20:38
    24 Sept 2024, 20:38
    1
    0 Votes
    2 Posts
    95 Views
    undefined
    @DownPW Technically, it should be possible with the addition of the below Toolbar: { display: { left: ["infobar"], middle: [ "zoomIn", "zoomOut", "toggle1to1", "rotateCCW", "rotateCW", "flipX", "flipY", ], right: ["slideshow", "thumbs", "close"], }, }, Meaning your code block becomes function fancybox() { if (top.location.pathname !== '/login') { $(document).ready(function() { $('a').not('.forum-logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() { $('a[href*=".jpg"], a[href*=".jpeg"], a[href*=".png"], a[href*=".gif"], a[href*=".webp"], a[href*=".svg"]').addClass("noanimate"); }); }); Fancybox.bind( 'a[href*=".jpg"], a[href*=".jpeg"], a[href*=".png"], a[href*=".gif"], a[href*=".webp"], a[href*=".svg"]', { Toolbar: { display: { left: ["infobar"], middle: [ "zoomIn", "zoomOut", "toggle1to1", "rotateCCW", "rotateCW", "flipX", "flipY", ], right: ["slideshow", "thumbs", "close"], }, }, } ); } } Note, that you just need to add/remove the elements in the toolbar you do not need. Obviously, zoomIn and zoomOut are the ones you are specifically interested in. However, if Fancybox detects that the image has already been zoomed as far as possible, then this will not work. You’d need an external library such as zoom.js to add this functionality, or perhaps simpler https://www.jacklmoore.com/zoom/ A good example of how you’d make these two independent libraries work together is below https://codepen.io/ezra_siton/pen/VgrjKw It’s worth nothing that this specific code is based on Fancybox 3, so may need to be refactored to work with the latest version 5.
  • Pandaundefined

    Sudonix and fediverse

    Solved Customisation
    8 17 Aug 2024, 13:04
    17 Aug 2024, 13:04
    4 Votes
    16 Posts
    376 Views
    undefined
    @Panda said in Sudonix and fediverse: Federation will have huge advantages, especially for starting off forums that would otherwise be quiet, because it can bring in posts from similar sites to increase content. Can’t say I agree with this statement. To me, if I visit a new forum, I’d much rather be viewing original content rather than that which I can easily consume elsewhere. I understand that new forums are often empty with not much content, but the growth needs to be organic rather than ingested from elsewhere to make it look busy. Using RSS feeds to pull in content from remote sites is fine as long as you use it for reading reference and create a discussion around the topic you are referring to (as I do with Sudonix), but absolutely pointless if you include the entire article and all associated responses - you may as well just visit the origin site instead. Another issue is SEO and the impact duplicated content will have on your own forum when it comes to Google indexing your site. Duplicated content negatively impacts SEO and in addition, that same content may be proprietary meaning you need permission to include it on your site. Potentially, it’s a legal minefield which should be treated with trepidation to ensure no copyright infringement takes place.
  • JACundefined

    NodeBB recent cards customisation

    Solved Customisation
    8 6 Aug 2024, 18:16
    6 Aug 2024, 18:16
    1
    2 Votes
    3 Posts
    147 Views
    JACundefined
    @phenomlab thank you very much for the assistance Mark, massively appreciated as always. The great thing about this is it’s all documented for other NodeBB users that come looking for solutions . Looks far better .
  • undefined

    Header Menu After Upgrading V3.1.1

    Solved Customisation
    8 14 May 2023, 14:05
    14 May 2023, 14:05
    1
    2 Votes
    2 Posts
    206 Views
    undefined
    @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
  • undefined

    NodeBB v3 Vote Icon

    Solved Customisation
    8 9 May 2023, 06:21
    9 May 2023, 06:21
    2 Votes
    9 Posts
    766 Views
    undefined
    @phenomlab forget it, look likes good with your codes.
  • undefined

    NodeBB v3

    Announcements
    8 29 Oct 2022, 05:59
    29 Oct 2022, 05:59
    3 Votes
    2 Posts
    257 Views
    undefined
    @cagatay JS will work fine - no changes there, and there are no plans to drop support for jQuery. More of an issue is the CSS - for which there are quite a few breaking changes. Keep an eye on sudonix.dev (my development site) where you can see progress in relation to how I am tackling the compatibility issues.
  • DownPWundefined

    [NODEBB] Help for my custom CSS

    Solved Customisation
    8 20 Jan 2022, 20:34
    20 Jan 2022, 20:34
    40 Votes
    204 Posts
    34k Views
    DownPWundefined
    @phenomlab Find him : [image: 1738443295726-76089049-894e-490f-bafa-10469193aca0-image.png] But I use this code for control image on topics and Shoutbox EDIT: I disabled this code and it seems to be OK Thanks @phenomlab