Topic: [NEW HOWTO] Rocket.Chat

[guest22]

Something that might be helpful until the init script is working properly--install tmux (yum --enablerepo=epel install tmux).  Then create a new session (tmux new) and start Rocket.Chat inside that session (node main.js).  You can then detach from that session and leave it running (Ctrl-B d), log out of the server, etc.  When you log back in, run tmux a to re-attach to that session.  This will leave the server running while you log out.

Thanks Dan, screen ( https://www.gnu.org/software/screen/manual/screen.html ) would do the same and is already installed with SME Server by default.


The init script works great, but I need the correct sed command to add SME Server to the list of known distributions for the forever tool. Will take a few minutes, and the knowledge that it can be done easily had my focus on LDAP, which is not correctly working...

[guest22]

Edit: Though it seems account activation emails aren't being sent, and this message is appearing in the logs: "(Mail not sent; to enable sending, set the MAIL_URL environment variable.)".  I've configured the mail server in Administration/SMTP, and the test email button reports success, but no messages are actually sent.

Added to the TODO list on the wiki page.

[DanB35]

Thanks Dan, screen ( https://www.gnu.org/software/screen/manual/screen.html ) would do the same and is already installed with SME Server by default.

I expect so, I'm just a little more familiar with tmux.  But if the init script is taken care of anyway, this point becomes moot.

my focus on LDAP, which is not correctly working...

I'm not sure what's going on there.  The logs seem to say it's connecting just fine, but it doesn't pull the user list over.

[DanB35]

Added to the TODO list on the wiki page.

This issue looks like the same thing: https://github.com/RocketChat/Rocket.Chat/issues/2471

Restarting the Rocket.Chat server got rid of the "set MAIL_URL" message, but now it's showing this instead:

Code: [Select]

Exception while invoking method 'registerUser' DeliveryError: Message delivery failed: 552 Mail with no Date header not accepted here
    at Object.Future.wait (/opt/Rocket.Chat/programs/server/node_modules/fibers/future.js:398:15)
    at smtpSend (packages/email/email.js:86:1)
    at Object.Email.send (packages/email/email.js:185:1)
    at AccountsServer.Accounts.sendVerificationEmail (password_server.js:781:9)
    at [object Object].Meteor.methods.registerUser (server/methods/registerUser.coffee:20:13)
    at [object Object].methodsMap.(anonymous function) (server/lib/debug.js:23:26)
    at maybeAuditArgumentChecks (livedata_server.js:1698:12)
    at livedata_server.js:708:19
    at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
    at livedata_server.js:706:40
    - - - - -
    at SMTPConnectionPool._onConnectionReady (/opt/Rocket.Chat/programs/server/npm/email/node_modules/simplesmtp/lib/pool.js:287:21)
    at SMTPClient.emit (events.js:98:17)
    at SMTPClient._actionStream (/opt/Rocket.Chat/programs/server/npm/email/node_modules/simplesmtp/lib/client.js:946:14)
    at SMTPClient._onData (/opt/Rocket.Chat/programs/server/npm/email/node_modules/simplesmtp/lib/client.js:329:29)
    at CleartextStream.emit (events.js:95:17)
    at CleartextStream.<anonymous> (_stream_readable.js:765:14)
    at CleartextStream.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:427:10)
    at _stream_readable.js:420:7
    at process._tickDomainCallback (node.js:492:13)


[DanB35]

Looking at the subdomain instructions, it seems to me that the DocumentRoot setting is unnecessary--you're directing Apache to proxy the connection to a completely different server, so Apache won't be serving files out of /opt/Rocket.Chat (or anywhere else).  I left that property out on my installation (didn't make any sense anyway, since my rocket.chat install was on a different host), and it still seems to work without issue.

[guest22]

Looking at the subdomain instructions, it seems to me that the DocumentRoot setting is unnecessary--you're directing Apache to proxy the connection to a completely different server, so Apache won't be serving files out of /opt/Rocket.Chat (or anywhere else).  I left that property out on my installation (didn't make any sense anyway, since my rocket.chat install was on a different host), and it still seems to work without issue.

Would that be the same for the 'Content Primary' directive?

[DanB35]

Would that be the same for the 'Content Primary' directive?

I'd think so, but I haven't tried it that way yet.  Any time you set up a domain in the sever-manager, though, the system wants you to assign an ibay to it.  I'm not sure how it would deal with not having one.

Edit: At first glance, though, it seems to work with that property deleted as well.

[guest22]

@DanB35, would you be kind enough to test the auto start as per wiki here https://wiki.contribs.org/Rocket_Chat#Auto_start_Rocket.Chat_at_boot

Maybe the scripts in /etc/profile.d need to executable but I am not sure for there is a mix of legacy scripts in there with different chmod statuses.

TIA

[DanB35]

I followed those instructions, and they seem to have worked.  After running "service rocketchat start" and waiting a minute or so, I was able to access the installation.  After rebooting the VM, Rocketchat started automatically and I was able to access it.

I did note an oddity on restarting, though.  mongod took nearly 10 minutes to start.  The proxmox console showed a sustained disk read of about 5M (though it isn't labeled with units--whether that's Mbits/sec, Mbytes/min, or Mwords/fortnight isn't clear) during that time, at the end of which there was a write spike of ~38M.  I have no idea if this has anything to do with the packages installed--it could be my VM provisioning, my VM host's hardware, or any of a number of other things.

[guest22]

I followed those instructions, and they seem to have worked.  After running "service rocketchat start" and waiting a minute or so, I was able to access the installation.  After rebooting the VM, Rocketchat started automatically and I was able to access it.

Thanks, marked verified

I did note an oddity on restarting, though.  mongod took nearly 10 minutes to start.  The proxmox console showed a sustained disk read of about 5M (though it isn't labeled with units--whether that's Mbits/sec, Mbytes/min, or Mwords/fortnight isn't clear) during that time, at the end of which there was a write spike of ~38M.  I have no idea if this has anything to do with the packages installed--it could be my VM provisioning, my VM host's hardware, or any of a number of other things.

Let's put it on the TODO list. I had a sence it had something to do with MongoDB. Although I see a difference instead of using service, using /etc/rc.d/rocketchat restart etc directly. Need to find out this one.

[guest22]

Edit: Though it seems account activation emails aren't being sent, and this message is appearing in the logs: "(Mail not sent; to enable sending, set the MAIL_URL environment variable.)".  I've configured the mail server in Administration/SMTP, and the test email button reports success, but no messages are actually sent.

Please see https://github.com/RocketChat/Rocket.Chat/issues/2471

I've adapted the init script creation command to include it. Please stop Rocket.Chat, remove /etc/rc.d/init.d/rocketchat and follow this part again https://wiki.contribs.org/Rocket_Chat#Generate_the_Rocket.Chat_init_script

[guest22]

April 30th, corrected some typo's in the how-to.

[ReetP]

I want to try and run this myself. When I get some time over the next few weeks I may try and build an rpm but will need a hand if anyone is willing.

Is there a srpm for rocket out there anywhere ? Also wondering about how to automatically pull in node.js on install ?

Home Tuesday so will gave a look after that.

[guest22]

Is there a srpm for rocket out there anywhere ?

This may help https://copr-be.cloud.fedoraproject.org/results/mosquito/rocketchat/fedora-22-x86_64/00170401-rocketchat/

Please note that the current release schedule of Rocket.Chat is weekly....

[CharlieBrady]

Restarting the Rocket.Chat server got rid of the "set MAIL_URL" message, but now it's showing this instead:

Exception while invoking method 'registerUser' DeliveryError: Message delivery failed: 552 Mail with no Date header not accepted here

So the app needs to be fixed so that it sends RFC compliant mail messages - Date header is mandatory.