Re: [CentOS] Tracking or checking backported kernel patches from upstream

2020-09-02 Thread Carlos A. Carnero Delgado 
El mié., 2 de sep. de 2020 a la(s) 11:17, Johnny Hughes (joh...@centos.org)
escribió:

> There is not really a 'procedure' to do that . certianly not in CentOS.
>

Eh... poor wording from my part. I meant procedure *for me* to check.

You CAN do a diff on the exploded tarball from the SRPM and either the
> last kernel released (to see what is in this update) .. or the
> kernel.org reference kernel .. to see what is different from the
> kernel.org release.
>

Yes, that's actually easy in this case.

Thanks a lot!
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Tracking or checking backported kernel patches from upstream

2020-09-02 Thread Carlos A. Carnero Delgado 
Hi!

I'm interested in finding out if a couple of upstream kernel patches were
backported into CentOS (RHEL), in particular this one

and this one

.

What's the procedure? After reading an article
,
I went into Red Hat's bugzilla, and tried several search terms (including
the kernel's commit ID) but found nothing.

Thanks!
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 7.7.1908, interface bonding, and default route

2019-09-20 Thread Carlos A. Carnero Delgado 
El vie., 20 de sep. de 2019 a la(s) 10:03, Alexander Dalloz (
ad+li...@uni-x.org) escribió:

> If you don't want to use NetworkManager, then define NM_CONTROLLED="no"
>

And *that* was the answer! Everything is working as expected now.

Thank you!
Carlos.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 7.7.1908, interface bonding, and default route

2019-09-20 Thread Carlos A. Carnero Delgado 
El vie., 20 de sep. de 2019 a la(s) 06:16, Giles Coochey (gi...@coochey.net)
escribió:

> I have a similar set up to you, and just did the upgrade to 1908, I
> didn't experience the problem you had, I can't see anything out of the
> ordinary in your network files.
>

I have reviewed the configuration several times now, and still can't see if
there's anything wrong with it. What I found is that, after the system has
booted up, if I systemctl restart network the default route does gets
applied.

Thanks a lot for your input!
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] 7.7.1908, interface bonding, and default route

2019-09-19 Thread Carlos A. Carnero Delgado 
Hi!

I just upgraded a machine to 7.7.1908 and the default route is not being
set on boot. This particular server has a bonded interface, and the
corresponding configuration for the master is (
/etc/sysconfig/network-scripts/ifcfg-bond0):

  TYPE=Bond
  BOOTPROTO=none
  DEFROUTE=yes
  IPV4_FAILURE_FATAL=yes
  NAME=bond0
  DEVICE=bond0
  ONBOOT=yes
  IPADDR=10.3.20.131
  PREFIX=24
  GATEWAY=10.3.20.1
  DNS1=10.3.2.8
  BONDING_MASTER=yes
  BONDING_OPTS="mode=802.3ad xmit_hash_policy=layer2 miimon=100"

The slaves (two of them) are configured like

  TYPE=Ethernet
  BOOTPROTO=none
  NAME=bond0-slave0
  DEVICE=em3
  ONBOOT=yes
  MASTER=bond0
  SLAVE=yes

After booting, the routing table is

  10.3.20.0/24 dev bond0 proto kernel scope link src 10.3.20.131 metric 300

with no default route configured (manually adding it will work, of course.)

This machine worked perfectly before, and it did during previous upgrades
and reboots. Has anyone ever had this problem before?

Thanks,
Carlos.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]

2016-08-18 Thread Carlos A. Carnero Delgado 
2016-08-18 13:32 GMT-04:00 JJB :

>
> I'm also seeing those errors in several servers, running under 5.5.
>> Currently investigating if this
>> > language=en_US=displayKC=1009996>
>> has anything to do (the resource overcommit bit).
>>
>
> Does this happen (only) while taking or consolidating snapshots? The VM is
> suspended during these operations and the OS isn't too crazy about it,
> especially if you have slow storage.
>

Nope, no snapshots. Just plain running. In fact, many times the guests are
under light usage (internal instrumentation, no external VMware stats).
We're investigating because we do have reasons to believe that our provider
is probably overcommitting or overselling (not out of malice, AFAIK).

HTH,
Carlos.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]

2016-08-18 Thread Carlos A. Carnero Delgado 
2016-08-18 12:39 GMT-04:00 correomm :

> This bug is reported only on the VM's with CentOS 7 running on on VMware
> ESXi 5.1.
> The vSphere performance graph shows high CPU consume and disk activity only
> on VM's with CentOS 7. Sometimes I can not connect remotely with ssh
> (timeout error).
>

I'm also seeing those errors in several servers, running under 5.5.
Currently investigating if this

has anything to do (the resource overcommit bit).

HTH,
Carlos.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] php55w-fpm on CentOS 7: settings location

2016-08-03 Thread Carlos A. Carnero Delgado 
2016-08-03 13:42 GMT-04:00 Boris Epstein :

> Does anybody know where to enter settings for php-fpm? I have tried a
> number of things, including starting it with "-c /etc/php.ini" but that
> seemed to have any effect. Any idea on how to control it? What am I doing
> wrong? :)
>

In my servers (for shared hosting) there's /etc/php-fpm.conf and the
/etc/php-fpm.d/ directory. I make minor modifications to the first file,
while put the bulk of settings in .conf files under the second directory.

HTH,
Carlos.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Squid for CentOS 7 and available file descriptors

2016-04-06 Thread Carlos A. Carnero Delgado 
Hi,

I'm installing a Squid instance for a large (ish) group of users. In the
past I've had to increase the number of available file descriptors for the
Squid process in order to avoid hitting the limits (and disrupting the
service).

It seems that the packaged Squid for CentOS 7 has a hardcoded value of
16386 maximum file descriptors
.
The relevant portion of that spec file is

  ⋮
  --with-aio \
  --with-default-user="squid" \
  --with-filedescriptors=16384 \
  --with-dl \
  --with-openssl \
  ⋮

Why this limit? Is there any merit to opening a bug or enhancement request
somewhere? Other than that, what could I do next? A custom Squid build?

Thanks a lot,
Carlos.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Systemd

2015-05-23 Thread Carlos A. Carnero Delgado 
El sáb., may. 23, 2015 10:37 PM, Kirk Bocek t...@kbocek.com escribió:

...

Ntpd runs just fine. But why isn't it loading at

boot...



 Did you run

systemctl enable ntp.service

after installing it?

HTH,
Carlos.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Delaying systemd reboot for a while

2015-05-14 Thread Carlos A. Carnero Delgado 
On Thu, May 14, 2015 at 9:59 AM, Matthew Miller mat...@mattdm.org wrote:

 Have you tried this? It's a symlink, but systemctl knows to act
 differently when called as shutdown, and the traditional use still
 works. No need to hack around anything — just use 'shutdown -r' as
 always.


Oh, yes! Both reboot and shutdown work as usual. I just wanted to know if
there was a one-to-one mapping to the systemctl version.

Thanks a lot,
Carlos.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Delaying systemd reboot for a while

2015-05-13 Thread Carlos A. Carnero Delgado 
Hi,

I'm in need of rebooting a server 1 minute after I give the command. I'm
used to

shutdown -r +1


which works as advertised. Now that shutdown is part of systemd
http://www.freedesktop.org/software/systemd/man/shutdown.html and it is
actually a link to it in CentOS 7, I've seen in the documentation
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/sect-Managing_Services_with_systemd-Power.html
that I can also use

systemctl reboot


But I can't find a way to provide a time specification in this latter form.
What's the correct incantation?

TIA,
Carlos.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Delaying systemd reboot for a while

2015-05-13 Thread Carlos A. Carnero Delgado 
Hi,

On Thu, May 14, 2015 at 1:11 AM, Peter Lawler cen...@bleeter.id.au wrote:

 On 14/05/15 13:44, Martin Cigorraga wrote:
  Hello Carlos,
  You can try the 'at' command to achieve the same result.
  Regards,
  -Martín

 or 'sleep'


Well, even though both could work, I fiinally went with the 'at' route,
which goes wonderfully with the configuration management system I'm using
http://www.ansible.com/home.

Thanks a lot!
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos