Re: [CentOS] [CentOS-devel] https://blog.centos.org/2020/12/future-is-centos-stream/
On 12/9/20 04:46, Andrea Biscuola wrote: IMHO, if you based the most critical part of your infrastructure on CentOS, you did it wrong. [...] We also just switched to CentOS 8 from CentOS 6 spending around 6 months of work in doing so, but the most important part of our infrastructure is on paid RHEL licenses (i.e. hypervisors). Back in the Before Times and RHEL 7 was at .1 or .2 I had a persistent kernel oops on a set of RHEL7 hypervisors. Since we had fairly well tricked out RHEL support licenses I opened a ticket and within a couple of weeks I had confirmation that yep, there was a known issue, and there was a fix entering testing. I asked for access to the fixed kernel. I was told no. I asked if there was a particular kernel version I could deploy temporarily until the fix was released. Silence. I asked for a bug ID so I could maybe use that to figure out what kernel I could deploy until RH released the fix. Silence. Meanwhile hypervisors are oopsing on me because the project didn't want to deviate from the vendor baseline. Then I learned about Centos Plus. I reprovisioned a machine, picked a Plus kernel, and happy sailing. The project decided functionality was superior to arbitrary compliance in this case. Rebuilt the rest of that rack to CentOS 7 and never looked back. Or bothered renewing as many and that level of support because the one time I really could have used it it was effectively denied. Sometimes basing the most critical part of your infrastructure on CentOS was the only way forward. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 答复: Iptables blocks out going connetion some times
On 4/24/19 10:31, likun wrote: Hello, Stephen, thank you for input. Yes, these servers have the same firewall rules, and both of them have the same problem from time to time, most of time they are good. Actually, these servers are newly installed to be used as the Glusterfs storage server, so not much data flowing at this time. As a WAG - have you double checked to make sure there aren't any IP addressing conflicts in play? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 and backup solution
On 1/27/19 06:56, Alessandro Baggi wrote: Hey there, what type of backup solution do you use on C7? Thanks in advance AMANDA - one config to encrypted LTO that are sent offsite and intended primarily for DR purposes, another config dumps a differently curated DLE list to virtual tapes kept on a local server. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IBM buying RedHat
On 10/28/18 19:07, mark wrote: On 10/28/18 17:54, Zube wrote: On Sun Oct 28 10:20:31 PM, Alain péan wrote: Le 28/10/2018 à 22:10, Albert McCann a écrit : Damn, this is bad enough to make one weep. Red Hat would stay as a distinct entity inside IBM. IBM has also contributed to Free software, and especially Linux kernel. I don't know how bad it is and the implications for CentOS... That old war wound started aching again. IBM:Redhat :: Oracle:Sun Actually, it could have been *much8 worse: *Oracle* could have bought RH. That *really* would have been an order of magnitude worse. Not for Canonical... ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Mail has quit working
On 08/27/2018 09:05 AM, TE Dukes wrote: -Original Message- From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:58 AM To: CentOS mailing list Subject: Re: [CentOS] Mail has quit working Date: Monday, August 27, 2018 07:42:48 -0400 From: TE Dukes From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Richard Sent: Monday, August 27, 2018 7:29 AM Since the localhost4 approach worked, commend out the ipv6 localhost entries in your /etc/hosts file, then try: IP6 is commented out dig @localhost localhost a That works again. If that works try: telnet localhost 143 This also works once again. If those work, it would seem that your ipv6 is messed up and your system is trying it first and not falling back to ipv4. Regarding your nameserver list in /etc/resolv.conf. If you have a working 127.0.0.1 nameserver you generally don't include external nameservers in that list. So, if non-ipv6 things seem to work, I'd remove the two non-127 nameservers from that list. Removed the two nameservers. Still can't access mail. Getting connection to storage server failed on the roundcube login page. That you can now successfully get to "localhost" is good progress. Seems you want to stay away from ipv6 networking issues unless/until you resolve whatever that issue is. Roundcube is, potentially, a totally separate issue. I don't use it, so can only suggest minimal debugging ideas. What is the hostname that you use to get to your roundcube instance? Can you resolve that: dig a If you get an answer, is the ipnumber correct? ; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> mail.palmettodomains.com a ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40652 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 3 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mail.palmettodomains.com. IN A ;; ANSWER SECTION: mail.palmettodomains.com. 86400 IN A 192.169.1.110 ;; AUTHORITY SECTION: palmettodomains.com.86400 IN NS dns1.palmettodomains.com. ;; ADDITIONAL SECTION: dns1.palmettodomains.com. 86400 IN A 192.168.1.110 dns1.palmettodomains.com. 86400 IN :::110 ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Mon Aug 27 09:01:48 EDT 2018 ;; MSG SIZE rcvd: 132 Note, if the hostname for your roundcube instance is one of the ipv6 entries in your /etc/hosts file, I'd remove that - and either put in an ipv4 entry or put an entry for it in your dns. Thanks again! I still think it's a mail issue. I can't get mail using usermin either. Think I'm going to remove the TLS stuff from postfix main.cf that I added yesterday and retry. If I missed this further up thread my apologies - is SELinux enabled and are there any relevant exceptions being logged? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos