@scale - Suitably impressed at Spiceworld London. Jason Collier was very helpful.

Definitely on the books to consider for server installs.

We are very happy to see these. Nearly 11K Read IOPS, that's awesome.

Youtube Video

I'll definitely share! ))

The cluster is back online and we are spinning up workloads now. Very excited.

For those who were still having problems getting Mattermost running on CentOS 7, I was also having the same problems and couldn't get beyond the postgres install. I found another guide and with a few tweaks, I was able to get this running.

https://www.howtoforge.com/tutorial/install-mattermost-with-postgresql-and-nginx-on-centos7/

The change that was required from this guide was in the "Download and Extract Mattermost"

Instead of...
[root@mattermost ~]# wget -q "https://github.com/mattermost/platform/releases/download/v2.0.0/mattermost.tar.gz" -O mattermost.tar.gz

Use this...
wget https://releases.mattermost.com/3.3.0/mattermost-team-3.3.0-linux-amd64.tar.gz

Then in the next block, instead of...
tar -xvzf mattermost.tar.gz

Use this...
tar -xvzf mattermost-team-3.3.0-linux-amd64.tar.gz

After that, follow the guide to the letter and it will get you to this...
0_1473265786807_upload-d89fe07b-7d71-4d39-8dd7-e00395f6aa84

@aaronxiang @wirestyle22 @scottalanmiller

@BBigford said:

Looks like there is quite a bit included in the free version for up to 10 premium users, and 10 basic users. Interesting.

Yes, it is quite extensive.

@scottalanmiller Thanks for this post and answering all my questions. @travisdh1 Thanks for answering all my questions as well. Good Thread!

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

Scott, you mentioned that this is all at the kernel level - could you roll your own version of this?

Sure, you'd have to write your own storage layer, though. So it's not trivial in any way.

OH.. that's where I was confused I guess... I thought the storage layer was part of KVM (that's the hypervisor they use, right?)

Not part of KVM itself. The Scale HC3 is unique, there is no software version available on the market.

So they wrote the storage layer? Cool - good to know/understand that.

Yes, Scale is primarily a storage vendor. Before they made their Hyperconverged product, they made scale out storage only. That was before KVM was mature enough to make the HC3 product. They no longer sell the storage layer, it is now developed purely and designed solely around the needs of the HC3 product so is completely unique to that. It's the storage layer and the storage integration (and support) that are their selling points. That's what makes them special and unique. KVM and the hardware on its own you could do yourself and you could easily make due with a different interface.

@dafyre said:

@JaredBusch said:

@dafyre said:

As a matter of correctness... Do you have EPEL /REMI or any other repos installed in your CentOS 7 image?

The script is connecting the Gitlab RPM, that is all. The base image he uses for all of these is CentOS 7 minimal, release 1511 unless he has changed the base template on his scale cluster.

Right. I'm just curious if he has added the epel-release or any other repos to it.

Definitely no EPEL. I often use it, but avoid it in the base image.

@wirestyle22 said:

@coliver said:

@wirestyle22 said:

I have to look up SSL certification on CentOS 7 now. I've only ever done it on our Barracuda SSL VPN which was just an upload. Here we go

I think you need to look up SSL for Apache if you are trying to encrypt ownCloud. I think someone has a guide on here somewhere about it.

I think @JaredBusch has it in his 8.2 guide. I think he did self signed though. I'm unsure of how to do this on linux with digicert or something similar

It was a self signed for the example. but I use letsencrypt myself. Some clients using ownCloud have StartSSL certs.

I just used this myself to make a new block device in a single line. Awesome 🙂

@travisdh1 said in Installing Zimbra Email 8.6 on CentOS 7:

@scottalanmiller said in Installing Zimbra Email 8.6 on CentOS 7:

8.8.9 is out now...

https://files.zimbra.com/downloads/8.8.9_GA/zcs-NETWORK-8.8.9_GA_2055.RHEL7_64.20180703080917.tgz

8.8.10 is now out
https://files.zimbra.com/downloads/8.8.10_GA/zcs-8.8.10_GA_3039.RHEL6_64.20180928094617.tgz

There is also a patch for 8.8.10 as well
https://blog.zimbra.com/2018/10/new-zimbra-patches-8-8-10-patch-1-and-8-8-9-patch-6/

Graylog has updated and no longer relies on the old version of ElasticSearch. It will use ElasticSearch 2 now. So time to revisit.

@scottalanmiller said in Building ELK on CentOS 7:

@dafyre said in Building ELK on CentOS 7:

So... I went through and ran the script and it seems to have worked fine... What next?

Edit: To collect logs from the local server, I also had to install filebeat on this server. So I reckon I can now go and install it on all my other systems as well.

Yes, install Filebeat and point it to ELK. Check my Filebeat article for more info.

Didn't realize you had one. 8-) But I'm good now. Logs are collecting as we speak. Bonus: Fail2Ban and Apache logs also work great in ELK.

@ou_snaaksie said in Installing Rocket.Chat on CentOS 7:

The installation worked perfetly, but after restarting the server I am unable to access Rocketchat.

I've run the line:
/opt/Rocket.Chat/node_modules/forever/bin/forever start /opt/Rocket.Chat/main.js

but it is still not working.

Use this command to see what is listening...

netstat -tulpn

@scottalanmiller said in Installing MongoDB 3.2 on CentOS 7:

Just tested and deployed to CentOS 7.2 on Linode.

This failed me, so I went to the mongo docs and the baseurl contains the variable $releasever.

using that results in redhat//mongodb in the file, which is why I assume you hard coded that bit.

Escaping the $ fixes it.

cat > /etc/yum.repos.d/mongodb-org-3.2.repo <<EOF [mongodb-org-3.2] name=MongoDB Repository baseurl=https://repo.mongodb.org/yum/redhat/\$releasever/mongodb-org/3.2/x86_64/ gpgcheck=1 enabled=1 gpgkey=https://www.mongodb.org/static/pgp/server-3.2.asc EOF

So I decided to try hooking up a new install of openfire to my domain controller (Zentyal). Turns out you need a more recent version of prototype.js to make it work correctly.

cd /opt/openfire/plugins/admin/webapp/js; mv prototype.js prototype.js.old; wget https://ajax.googleapis.com/ajax/libs/prototype/1.7.1.0/prototype.js systemctl restart openfire

At that point clear your browser cache if you had started the setup configuration via web browser already, and you should be able to complete the setup using your Active Directory information.

I know, I know, way beyond the article scope, but I figured it would save some of us a little headache.