@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

@Kelly said in OpenSSH installed, but cannot use SCP:

Ok, I can now copy. Thanks for all the help. I have learned a lot in just this one issue.

Cool, just realized that this was solved. So marking it as such. Thanks.

@Dashrender argh. Cost 😞

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.

@antonit said:

What is the default db admin?

root

@scottalanmiller said in Linux: The Lay of the Land and the Filesystem Hierarchy Standard:

@BRRABill said in Linux: The Lay of the Land and the Filesystem Hierarchy Standard:

So to wrap this question up...

Anything to be shared with users not on the local machine should be stored in /var and probably /var/exports

So a file structure such as

/var/exports/HRdata
/var/exports/XObackups
/var/exports/userhomefolders
/var/exports/sharedDOCS

Would be what you are expecting to see on a Linux file server....?

Yes, that would be a very good approach.

Thanks!

Hope it was a good question.

Had a spare laptop laying around. Installing CentOS now. Also planning on installing NextCloud here soon as well. Creating a repository/shared calendar for the family with this machine.

Updated as I figured out where things have moved away from the documentation that I had. The five minute install video is for Stacki 1.x and they have changed quite a bit at the core so that is why the video does not reflect the needs of the current installer. Avoid the StackiQ video for installation.

For those stumbling in here down the road, the current consensus is that FreePBX is the better option for your new PBX. Elastix 4 did release, but is not being updated enough to remain a contender at this point.

No, there is nothing like that. The filesystem is just not there. It would warn you, though, so you would know not to be trying to save to something that doesn't exist.

@JaredBusch said:

@coliver said:

@JaredBusch said:

Disabke SELinux and see if it works. Then if so, add the port as allowed to SELinux?

Looks like it was SELinux, setting it to permissive allowed the port to be used. Now to figure out how to allow the port in SELinux.

semanage port -m -t http_port_t -p tcp 82

That did it thanks.

To enable all yum operations to use a proxy server, specify the proxy server details in /etc/yum.conf. The proxy setting must specify the proxy server as a complete URL, including the TCP port number. If your proxy server requires a username and password, specify these by adding proxy_username and proxy_password settings.

The settings below enable yum to use the proxy server mycache.mydomain.com, connecting to port 3128, with the username yum-user and the password qwerty.

# The proxy server - proxy server:port number proxy=http://mycache.mydomain.com:3128 # The account details for yum connections proxy_username=yum-user proxy_password=qwerty

@anonymous said:

@scottalanmiller That's the whole reason I want DNS setup. I want to be able to SSH by hostname, not IP address, however I guess your right, maybe I just need to setup the host names on the jumpbox.

that's all that I do. Maintain the /etc/hosts file and I never run into a need to use IP Addresses since I don't SSH from random box to random box.