If anyone is curious, you do not have to tell it to start on boot as the setup step does that. You can see it linking the service in the screenshot.

@JaredBusch said in Dropping a black box on a client network: A Dell R230 on Xbyte shows $599 to start. "To start"...in that case it's without CPU, memory or disk. So it's a server that does not start. Get a new one instead from Dell. Dell R240, 8GB ECC RAM, Dual-core G4900 CPU, 1TB disk. $709 ready to go on dell.com G4900 is latest gen CPU, more than you need. To step up to 4 cores it's $176 to get a Xeon E-series CPU in the same machine. Supermicro is never going to be a cheap as Dell or HP low end models so there's no point even looking at it. PS. Also you get 1 year basic HW warranty on site in that price but you could extend to 3 year for $100 or whatever the customer wants.

@scottalanmiller said in Zimbra Services Fail to Start; Removing Stale PIDs: @dbeato said in Zimbra Services Fail to Start; Removing Stale PIDs: @dbeato said in Zimbra Services Fail to Start; Removing Stale PIDs: @scottalanmiller said in Zimbra Services Fail to Start; Removing Stale PIDs: @dbeato said in Zimbra Services Fail to Start; Removing Stale PIDs: I have only had this happened on the upgrades between versions and OS upgrade. This happened to us while simply up and running. Middle of the day. Very odd. Weird What version? 8.8.10_GA_3716 Hmmm I just upgraded from 8.8.9 to 8.8.11 last week or two weeks ago.

@black3dynamite said in Deploying NodeBB 1.11.1 on CentOS 7 with MongoDB 4: @scottalanmiller said in Deploying NodeBB 1.11.1 on CentOS 7 with MongoDB 4: @black3dynamite said in Deploying NodeBB 1.11.1 on CentOS 7 with MongoDB 4: @scottalanmiller said in Deploying NodeBB 1.11.1 on CentOS 7 with MongoDB 4: @JaredBusch said in Deploying NodeBB 1.11.1 on CentOS 7 with MongoDB 4: Otherwise, there is no reason to use CentOS, nor avoid the Fedora RPM packages. Actually there is, the RPM packages for MongoDB are "breaking". You can't auto-update with them without bringing your forum down. Several updates in the last two years were not just breaking, but very breaking. Fedora RPM for NodeJS is acceptable, but would put you several versions behind typically. For MongoDB, it would put you behind with updates while creating a risk that a seemingly trivial update to the OS would be expected to totally hose the database (3.4 to 3.6 to 4.0 are all updates that have to be manually handled for MongoDB with the actual data being massaged to handle it, but the OS just changes the engine version and lets the data stop working.) Its probably be best to start using the MongoDB repo instead of using RHEL and Fedora repo, with the news about them planning on removing MongoDB from their repo. I do that anyway. MongoDB is very good about their repos. You do the same with nodejs on Fedora too? There are lots of ways to do it, but I like this model for control. NVM is good, too.

So, circling back. How is the backup project going?

@flaxking said in vTigerCRM Installation - Troubleshooting: Is SuiteCRM's Cases feature decent? Not a sales guy, not sure how it is.

@StorageNinja said in Why I Feel KVM Is the Easiest HyperVisor to Learn the Basics On: @Dashrender said in Why I Feel KVM Is the Easiest HyperVisor to Learn the Basics On: The question is - why is the quality so bad? Isn't the process supposed to catch bad quality? Their process is consider the windows insider group (extreme power users) to be a good enough replacement for proper QE teams, and writing automated build tests. Right, the new process isn't to catch bad things, it's actually to see bad things as "not all that bad." Presumably because a shift from viewing their products as being for business to being for entertainment. Remember when Windows 95 was a key tool for businesses, but by Windows 98 they had made sure to put a "for entertainment purposes only" label on the product to make sure no one confused it with something that was intended for business use? I feel like that's where they are now. At least internally, no one is really thinking of this as a business tool.

@dbeato said in Zimbra Update Fails with Validating LDAP Configuration, Cannot Create TLS Connection to LDAP Masters: @scottalanmiller said in Zimbra Update Fails with Validating LDAP Configuration, Cannot Create TLS Connection to LDAP Masters: So it worked by rebooting. WTF Weird. Very

Good to know, I use Ubuntu/Debian so I will check for that.

Sorry, ignore me. I got this figured out. I was being really dumb and had the wrong config.json file open and didn't know what I was looking at. Just ignore. Yes, the socket.io settings were missing, but were on my screen so I was sure that they were there.

@black3dynamite said in Red Hat Discontinuing KDE in RHEL and CentOS: @travisdh1 said in Red Hat Discontinuing KDE in RHEL and CentOS: @scottalanmiller said in Red Hat Discontinuing KDE in RHEL and CentOS: @travisdh1 said in Red Hat Discontinuing KDE in RHEL and CentOS: @black3dynamite Aha! They both did it! Yes, I have a thing about an entire desktop worth of space getting forced down into one little bar, and the menu being at least 2 clicks deeper than it was. Why is the menu deeper? I don't prefer this setup either, but it's no deeper. It's still a button on the desktop for me. Because as the admin/geek, everything I want/need to use is a submenu of the all programs menu. Granted I mostly just favorite a terminal emulator and be done with it, but it is much farther to move around and menus for me to get through. Give me Cinnamon with a hotkey set for the menu any day. As long as the search function works, I usually find what I need by searching for it. ^ this

@jaredbusch said in FusionPBX Install Error on CentOS 7: @fateknollogee said in FusionPBX Install Error on CentOS 7: Just emailed Mark at Fusion. He said "Yes, the official FusionPBX install script works fine with Debian 9 and Freeswitch 1.8." So outdated documentation? Or what? Seems like just one page of it wasn't updated. The rest was.

@dustinb3403 Hi, You cant but the /boot as raid However the / or root part can be placed as raid, I did this and I will show you how to do this, but please don't do it. Here where it gets bad. You wish to update the system and kernel and all this can affect the RAID/ now the config for the raid is done in the kernel and stored in boot part, so you always updating this and your always keeping the disks busy, even on network packet level. Everything happens will happen on the / What you want to do is look into purchasing a small reliable drive Like 64 GB or 128 GB NVMe SSD and using that as your / or If that is too fancy or expensive, get USB thumb drive and pair it with samsung SD card and install the root part Then create RAID 10 on the 4 other drives, cause even if the /root fails it wont matter . pop another one and it will auto detect the raid , with cockpit it is very easy to detect the RAID and activate it and mount it

@dafyre said in Centos AND Ubuntu Package Mirrors Down: I disable IPv6 as a matter of defaults on my home network... I'd like to do it at work too, but I never have any issues like that there. Mee neither. It was weird thing I rebooted everything from the router side and it got fixed, so disregard.

yum-cron and dnf-automatic do not use postfix or any other MTA. They simply open and send with a direct SMTP connection by default.

Thanks to you guys I got it sorted out now!

@jnaugle also worth noting, no one actually delivers PRI today, that entire market is a scam. It's actually SIP and then they translate the SIP to PRI on your network edge to make it "sound cool" for people who are out of date and remember when PRI was both still available and actually practical (early 1990s and earlier.) PRI is not nearly as powerful as SIP, nor as cheap, so phone providers long ago "all" moved to providing SIP instead (PRI isn't possible without a physical T1) and "virtualizing" PRI on top of it. All the PRI does it increase cost and lower performance, flexibility and reliability. So the best solution is to get the phone provider to stop pretending to do PRI and just give you the raw SIP. This improves your phone quality by removing unnecessary steps and limitations, removes the need for you to convert back to SIP (gateway, card, however you do it) and makes everything better for everyone. The PRI interface has no advantages, only disadvantages. It takes the better SIP, and cripples it. For people running ancient phone systems from before VoIP, SIP isn't possible, so these terrible PRI interfaces are useful for them to continue to be able to hook up those ancient phone systems while still being able to connect to current phone companies. They aren't totally useless, but they are useful only for that one terrible niche case.

Wow this must be an old server. pam_tally was replaced with faillock in RHEL 6.

@dustinb3403 said in CentOS 7.5 not listing ports when added to firewall-cmd: @jaredbusch Look at the OP, i have telnet listening to those ports. Ahh, didn't scroll enough.

@stacksofplates said in Looking to migrate Nginx and LetsEncrypt: @jaredbusch said in Looking to migrate Nginx and LetsEncrypt: @stacksofplates said in Looking to migrate Nginx and LetsEncrypt: If you start over with a new system so you still get notifications of old certs expiring? Aren't these handled at the domain level so it knows that a new system has a newer cert? Honestly asking since I haven't run into this yet. No. It is handled on the cert serial number level. Ah ok. I've moved things in the past by simply reissuing on the new server, and dealing with the expiring certs is an annoyance.

@francesco-provino said in Linux: History: @stacksofplates said in Linux: History: you can just do gedit ~/.bash_history or if you like the cli cat ~/.bash_history Obv only Bash if that's what you're using. Why conCATenate? Just use LESS. You can do either or any combination. Mostly just pointing you you don't need the gui.

@iroal said in Guacamole 0.9.14 on CentOS 7: @jackmartins_ said in Guacamole 0.9.14 on CentOS 7: @iroal Did you solve this problem? I got the same error I reinstall using this tutorial. https://cstan.io/?p=11405&lang=en Regards. Those instructions is pretty good. He did leave out information about the default user and password for it.

@scottalanmiller Did you ever fix this?

@dustinb3403 said in CentOS 7 Telnet Port Change: Cockpit isn't included in CentOS 7 by default (is it?. . . .) Not with a minimal install. With the problem you are having, I was assuming the issue was with port 9090.

@dustinb3403 said in CentOS 7 enabling Telnet: And I got the port forwarding to work. firewall-cmd --zone=public --add-forward-port=port=9090:proto=tcp:toport=23 I can now telnet to my server on port 9090 (which forward to 23). Nice!

@emad-r said in CentOS 7 - Why Did [Almost] Everyone Switch to Fedora?: the other guy who is knowledgeable but not as nice as Scott Hahahahahahahahahahh

@dustinb3403 said in Weird question - How often are CentOS packages updated: @jaredbusch said in Weird question - How often are CentOS packages updated: @dustinb3403 said in Weird question - How often are CentOS packages updated: @jaredbusch said in Weird question - How often are CentOS packages updated: @dustinb3403 said in Weird question - How often are CentOS packages updated: @stuartjordan said in Weird question - How often are CentOS packages updated: Don't you want to use a cron so you don't have to check daily? I have other processes that require manual intervention, so checking only takes a moment. I would still use yum-cron to do it. Just don't tell it to install if you don't want it to. You will still get the email when things are available. That does seem useful. No timers to set like needs handled with dnf-automatic just install and edit the conf file. Installing it and configuring it now... If you do yes / yes / no it will even have them downloaded for you. not that that is much of an issue generally.

@dustinb3403 said in Need some help with crontab: Ok and that is what it was. Simply needed to make a bash script out of it and have it scheduled to run, rather than using the commands directly in cron. Problem solved. Solution: pwd /usr/bin/local touch expiring-alert.sh vi expiring-alert.sh /usr/bin/php /var/www/html/snipeit/artisan snipeit:expiring-alerts sudo vi /etc/crontab 35 * * * 1 <user> /usr/local/bin/expiring-alert.sh Presumably changing this to be @daily or @weekly would work as well. MOst of the time that is how I have it setup on my crontab, same for my certbot scripts too.

@dustinb3403 said in Virtualizing Your Cudatel Appliance: @scottalanmiller said in Virtualizing Your Cudatel Appliance: Go ahead, download FreePBX and start playing with it. You could have installed it while reading this article! Any good installation guides here on ML? @JaredBusch has a great series of posts for FreePBX here. https://mangolassi.it/topic/11805/freepbx-13-setup-guide

@black3dynamite said in Meltdown Shows Why to Avoid LTS Releases: What makes Red Hat and SUSE exempt compare to CentOS and OpenSUSE leap? Because we are paying for the support? Nothing makes them exempt, they ARE CentOS and Leap, just paid for instead of free. They suffer just the same.