Importing a phpBB3 forum - starting over, looking at logs and finding errors?

Technical Support
  • Hi.

    With nodeBB happily running after a rocky start, I've started to look at importing a dump of my current phpBB3 forum. Everything points to nodebb-plugin-import and I've started initial testing with this. Took a few tries to iron out access to the temporary MySQL db I set up for the old forum (new hosting) and so on but that seems to work as I see the script read stuff from MySQL.

    At the import frontend http://example.org/admin/plugins/import the "Flush" option doesn't seem to nuke the exiting data in Redis but instead tries to import over what's already there. Is this intentional? How do I best properly nuke state so I can do a fresh import? flushdb/all in Redis works, I guess, but seems a bit excessive and I don't know if any intermediary state is lingering outside Redis.

    nodeBB v0.8.2 complains that import and import-phpbb aren't suitable for this version:

    28/9 13:37 [12773] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
     * nodebb-plugin-import
     * nodebb-plugin-import-phpbb
    

    This something I can do anything about? Installed via npm.

    The import reports an error early in the import but I can't see what actually fails. The frontend bugs out from time to time and simply stops and sometimes blanks out. The log isn't very informative:

    controller.config,[object Object]
    controller.state,[object Object]
    exporter.log,installing: nodebb-plugin-import-phpbb
    exporter.log,setup
    controller.state,[object Object]
    importer.start,
    importer.phase,[object Object]
    importer.progress,[object Object]
    importer.ready,
    exporter.ready,
    importer.progress,[object Object]
    

    Verbose doesn't seem to be more verbose initially so I can't see what fails at the start.

    Lastly, I looked at the developer console in Chrome while trying the import. At some point it reports an error trying what seems to be a GET on http://example.org/socket.io/?EIO=3&transport=polling&t=1443440233003-4 I run nodeBB through nginx and the error is a 502 bad gateway. Any ideas what can cause this?

  • After some more digging I found this: https://github.com/akhoury/nodebb-plugin-import/issues/131#issuecomment-143779814

    Basically import isn't ready for v0.8.2 just yet but akhoury is working on it. Personally I'll wait for an updated import rather than downgrade->import->upgrade given my trouble with plugins and v0.7.x from npm.


Suggested Topics


  • 0 Votes
    11 Posts
    624 Views

    @someoneyoulike We have set up instances where the db is not on the same machine as the server (mostly for horizontal scaling purposes, etc.)

    We don't notice any real-world degradation of performance. MongoDB is plenty fast, it's almost never the database (or network connections to the db) that are the bottleneck.

    Unless your app server is in Toronto and your database is in Singapore... but then you have other problems 😄

  • Login error

    Unsolved Technical Support
    8
    0 Votes
    8 Posts
    889 Views

    @ushi said in Login error:

    When I try to log in, I get such an error message
    "Login failed
    We are unable to connect you to the system, as it has been too long. please try again."
    What to do?

    I'll explain what the problem is,
    Apparently the forum server is too slow and did not load the ssl certificate.
    So you need to change the "http: //" in the url "https: //" and then try to connect again ... (I also translate from Hebrew, maybe you should add a category in Hebrew ...)

  • Nodebb Error

    Technical Support
    9
    0 Votes
    9 Posts
    928 Views

    @Nicolas-0 said in Nodebb Error:

    HI, I have error to install nodebb in debian:

    16/1 22:29:48 [20173] - error: [build] client side styles build failed
    16/1 22:29:48 [20173] - error: [build] Encountered error during build step: Inline JavaScript is not enabled. Is it set in your options?
    16/1 22:29:48 [20173] - error: message=Inline JavaScript is not enabled. Is it set in your options?, stack=undefined, type=Syntax, filename=/root/forum/nodebb/node_modules/nodebb-theme-persona/less/bootstrap/buttons.less, index=1134, line=51, column=4, callLine=NaN, callExtract=undefined, extract=[ pointer-events: none; // Future-proof disabling of clicks, .opacity(.65);, .box-shadow(none);]

    This is because less 3.x apparently does not support inline javascript.

    You probably ran "npm audit" which threw out four less vulnerabilities and prompted you to update less to fix them, which broke the client side styles build step of NodeBB.

    Fix it by downgrading less to the supported version by running "npm install [email protected]".

    That should cause the next ./nodebb build to process correctly.

  • Can't find SSO settings

    Technical Support
    2
    0 Votes
    2 Posts
    534 Views

    found it:

    needs ./nodebb build needs to open dev console to flush cache
  • 0 Votes
    4 Posts
    1k Views

    Wow.. Awesome guess I missed that.
    That did the job, thanks again.