buddycloud/buddycloud-server — Issue #32: buddycloud server does not appear to start properly
Author: jdeisenberg
Created: 2011-12-10 05:48:04+00:00
State: open

I have installed buddycloud-server v0.1.6 at dsn-test.com and the latest webclient at http://buddycloud.dsn-test.com

Here is the output from the log file, the /etc/init.d script, and the JavaScript console in Chrome. When I run under chrome, the login screen takes 99.8% of CPU according to top.

# startup output from init script

+ PATH=/sbin:/usr/sbin:/bin:/usr/bin
+ DESC=buddycloud server
+ NAME=buddycloud
+ RUN_AS_USER=buddycloud
+ DAEMON=/opt/buddycloud-server/bin/node
+ RUNDIR=/opt/buddycloud-server/lib/node_modules/buddycloud-server
+ DAEMON_ARGS=build/Release/main.js --nobuild
+ PIDFILE=/var/run/buddycloud.pid
+ SCRIPTNAME=/etc/init.d/buddycloud
+ [ -x /opt/buddycloud-server/bin/node ]
+ [ -r /etc/default/buddycloud ]
+ . /lib/init/vars.sh
+ [ -f /etc/default/rcS ]
+ . /etc/default/rcS
+ TMPTIME=0
+ SULOGIN=no
+ DELAYLOGIN=no
+ UTC=yes
+ VERBOSE=no
+ FSCKFIX=no
+ [ -r /proc/cmdline ]
+ grep -qw noswap /proc/cmdline
+ NOSWAP=no
+ [ ! -e /proc/cmdline ]
+ egrep -qw quiet /proc/cmdline
+ [ ]
+ true
+ . /lib/lsb/init-functions
+ FANCYTTY=
+ [ -e /etc/lsb-base-logging.sh ]
+ . /etc/lsb-base-logging.sh
+ LOG_DAEMON_MSG=
+ [ no != no ]
+ do_start
+ start-stop-daemon --start --quiet --pidfile /var/run/buddycloud.pid --exec /opt/buddycloud-server/bin/node --chuid buddycloud --test
+ start-stop-daemon --start --quiet --background --pidfile /var/run/buddycloud.pid --chdir /opt/buddycloud-server/lib/node_modules/buddycloud-server --chuid buddycloud --exec /opt/buddycloud-server/bin/node -- build/Release/main.js --nobuild
+ [ no != no ]
+ :

# log file:
[Sat, 10 Dec 2011 05:06:57 GMT] INFO [main] XMPP connection established
[Sat, 10 Dec 2011 05:21:53 GMT] INFO [main] XMPP connection established

# JavaScript from Chrome
DEBUG: ["nr of channels in cache: 0"]
app.js:1DEBUG: ["nr of users in cache: 0"]
app.js:1DEBUG: ["CONNECT", "jdeisenberg@dsn-test.com",
a
]
app.js:1DEBUG: ["connection_event", "connecting"]
app.js:1STROPHE: 1 _connect_cb was called
app.js:1DEBUG: ["connection_event", "authenticating"]
app.js:1DEBUG: ["OUT", ""]
app.js:1DEBUG: ["OUT", "dXNlcm5hbWU9ImpkZWlzZW5iZXJnIixyZWFsbT0iIixub25jZT0iMjQ3OTg2NjIwOCIsY25vbmNlPSI4Y2IxMGMwZGE4ZDFkYjQ0MDkyZGUyMjZmYWI2YTNjNSIsbmM9IjAwMDAwMDAxIixxb3A9ImF1dGgiLGRpZ2VzdC11cmk9InhtcHAvZHNuLXRlc3QuY29tIixyZXNwb25zZT0iYTM0YmFkODNiOGM1NDMwZmNmZjg2YzU0OGY0M2ZkODciLGNoYXJzZXQ9InV0Zi04Ig=="]
app.js:1DEBUG: ["OUT", ""]
app.js:1STROPHE: 1 SASL authentication succeeded.
app.js:1DEBUG: ["OUT", ""]
app.js:1DEBUG: ["OUT", ""]
app.js:1discover dsn-test.com
app.js:1DEBUG: ["OUT", ""]
app.js:1DEBUG: ["IN", "
"]
app.js:1DEBUG: ["OUT", ""]
app.js:1DEBUG: ["OUT", ""]
app.js:1DEBUG: ["OUT", ""]
app.js:1DEBUG: ["OUT", ""]
app.js:1DEBUG: ["OUT", ""]
app.js:1DEBUG: ["IN", "http://jabber.org/network/serverinfo"]
app.js:1DEBUG: ["IN", "http://jabber.org/network/serverinfo"]
app.js:1DEBUG: ["IN", "http://jabber.org/network/serverinfo"]
app.js:1DEBUG: ["IN", "http://jabber.org/network/serverinfo"]
app.js:1DEBUG: ["IN", "http://jabber.org/network/serverinfo"]
app.js:1DEBUG: ["discover_channel_server error",
Arguments[0]
]
app.js:1STROPHE: 1 no requests during idle cycle, sending blank request