Starting issue

[island219]

Hey,

I've compiled Node and installed NodeBB using NPM. All the required dependencies 'should' be installed.

I'm getting this error however

root@uk:/var/nodebb/NodeBB-0.0.5# node app
Info: NodeBB v0.0.5 Copyright (C) 2013 DesignCreatePlay Inc.
Info: This program comes with ABSOLUTELY NO WARRANTY.
Info: This is free software, and you are welcome to redistribute it under certain conditions.
Info: ===
Info: Initializing NodeBB v0.0.5, on port 4567, using Redis store at 127.0.0.1:6379.
Info: Base Configuration OK.
Info: Checking categories...
node: symbol lookup error: /var/nodebb/NodeBB-0.0.5/node_modules/reds/node_modules/redis/node_modules/hiredis/build/Release/hiredis.node: undefined symbol: _ZN2v86Object32SetAlignedPointerInInternalFieldEiPv

Is anybody able to help me out? I've probably made some rookie mistake (New to node + web development!)

[julian]

Hey island219,

Did you also run node app --setup right after?

1. git clone ...
2. npm install
3. node app --setup

Normally, the setup should automatically initialize, although since we've recently added reds, perhaps that is conflicting on new installs.

Thanks for this, we'll look into it!

[island219]

Yeah, that's the order I ran it in. I'm running build v0.9.12 of NodeJS and 1.2.12 of NPM it it helps.

If you need any more info feel free to ask!
Loving how NodeBB operates so far!

[julian]

Hm... do you have redis installed and running as well?

[island219]

Yep. I do indeed!

[julian]

Hm... I'm confident that it may have to do something with reds not playing nice with initial installs. We'll look into it!

[island219]

I tried an install on my second server. It runs fine but looks like this:

http://scrn.joshuabaldwin.eu/8ZEnr.png "Uh Oh"

[julian]

Interesting... mind if you share your config.json file with us?

[island219]

Here's my config. Disregard the weak secret!

{
    "base_url": "http://localhost",
    "port": 4567,
    "use_port": true,
    "redis": {
        "host": "127.0.0.1",
        "port": 6379,
        "password": ""
    },
    "secret": "lolfail",
    "bcrypt_rounds": 12,
    "upload_path": "/public/uploads",
    "relative_path": ""
}

[julian]

Also, can you post the file at /public/config.json?

Sorry, should've mentioned that earlier

From what we can tell, the api calls seem to be failing... what do you see in Firebug/Developer Tools?

[island219]

Here's the one from /public/config.json

{
    "socket": {
        "address": "http://localhost",
        "port": 4567
    },
    "api_url": "http://localhost:4567/api/",
    "relative_path": ""
}

This is the javascript / http log
This is the source for the page

It seems to have everything it should, but it's getting rewritten and does not display that way.

[island219]

I just took a look at the source for the page. It seems to contain everything as it should. I just isn't displaying correctly.

Here's a link to the page source.

Here's the log from my browser](http://pastie.org/pastes/8251050/text)

[baris]

[20:12:46.861] GET http://localhost:4567/api/home [0ms]

Can you see the return of that call? It should return a json object of all the data required for the home page, if that data is missing then the page will not render correctly.

[julian]

Alternatively, go directly to localhost/api/home via browser, and see what you get.

[island219]

This post is deleted!

[island219]

The drag-drop to add images keeps popping up whilst I'm doing stuff. Really annoying as stuff seems to break when it appears.

This is the link!
http://pastie.org/pastes/8251395/text

[island219]

Humph, Can't see replies and my posts seem to be disappearing and reappearing.

[island219]

Setup the modules globally and reinstalled NodeBB. Suddenly started working.

[julian]

Humph, Can't see replies and my posts seem to be disappearing and reappearing.

We have an infinite loader for posts, so the next "page" loads automatically. That might explain why some posts don't seem to appear for you

[julian]

As for the drag-drop, that overlay should only appear if you are dragging a file onto the browser window... in what instance is it appearing erroneously?