similar to: python problem while trying to fix a separate issue

Question for the list: I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance

I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance tests, I believe the processor

On Sun, Aug 9, 2020 at 1:40 PM Chuck Campbell <campbell at accelinc.com> wrote: > ... > dnf copr enable abn/throttled > dnf install -y throttled > > but I get this output: > Error: > Problem: conflicting requests > - nothing provides python3-configparser needed by throttled0.7-1.x86_64 > > I have no guess what to do about this. Well, that dependency is

Does anyone know how to get procmail and dovecot to play happily together with mboxes? I'm on Centos 6.5, fully patched. I'm getting tons of lock timeouts which is killing performance. I tried using dovecot's lda from procmail, which prompted many adjustments to selinux, which I managed, but it still gives permission problems, and I haven't succeeded in getting it to deliver

I have a raid 50 array on a 3ware controller. The box is running centos 6.5 and the file system is ext4. I'm going to try some other filesystems, but could anyone suggest any alternative raid setups as well as stripe sizes I should try? The old server uses the same controller on a centos 5.10 setup, using ext3, and it performs much faster i/o. The old 3ware setup is raid 5. -chuck --

I have followed the guides on setting up postfix relay to my account at network solutions. I added these to main.cf: inet_interfaces = localhost relayhost = [mail.mydomain.com]:587 smtp_sasl_auth_enable = yes smtp_sasl_security_options = noanonymous smtp_sasl_password_maps = hash:/etc/postfix/sasl_password smtp_use_tls = yes smtp_tls_CAfile = /etc/pki/tls/certs/sendmail.pem The username and

Is there a Centos 6.x to Centos 7.x guide somewhere? What has changed, that I need to learn about as an admin, before I jump in and flounder? thanks, -chuck -- ACCEL Services, Inc.| Specialists in Gravity, Magnetics | (713)993-0671 ph. | and Integrated Interpretation | (713)993-0608 fax 448 W. 19th St. #325| Since 1992 | (713)306-5794 cell

On 1/7/2015 9:46 AM, Chuck Campbell wrote: > On 1/7/2015 12:06 AM, Alexander Dalloz wrote: >> Am 06.01.2015 um 23:55 schrieb Chuck Campbell: >>> I'm running centos 6.6 with the default 2.0.9-xxx dovecot. >>> >>> I run sa-learn against my spam_to_learn folder, then I wan to move those emails >>> to a learned_spam folder. >>> when I do a

I must have something mis-configured in my bond setup. Things are working, but I'm getting TONS of this sort of stuff in my log: +2001:502:ad09::4#53: 1 Time(s) network unreachable resolving 'kns1.kuwaitnet.net/A/IN': +2001:503:231d::2:30#53: 1 Time(s) network unreachable resolving 'kns1.kuwaitnet.net/A/IN': +2001:503:a83e::2:30#53: 1 Time(s) network unreachable

I've built a new mail system with Centos 6.5, and I'm running fetchmail - sendmail - procmail to maildir. I have all of this working at the moment.(I know, postfix was the default, but for lots of other reasons, I switched, and that isn't an issue, I don't think). I am using dovecot as an imap server. Procmail won't update indexes during email delivery, so I'm having some

I did a complete clean install of CentOS 5 from CD yesterday. I took the default selinux configuration. After that I ran yum update and found 600 plus updates and installs. I let it go to do the updates and during that process I saw a large number of issues in the selinux troubleshooter. I also see these kinds of things in /var/log/messages: **Unmatched Entries** (Only first 10 out of 49031

Is this mis-configuration, or just noise in my log? ??? 29-Apr-2018 00:50:26.056 general: warning: managed-keys-zone: No DNSKEY RRSIGs found for '.': success: 1 Time(s) ??? 29-Apr-2018 00:50:26.120 general: warning: managed-keys-zone: No DNSKEY RRSIGs found for 'dlv.isc.org': success: 1 Time(s) -chuck -- ACCEL Services, Inc.| Specialists in Gravity, Magnetics |

On 1/7/2015 4:01 PM, Peter wrote: > On 01/08/2015 05:39 AM, Chuck Campbell wrote: >> I tried this using yum install dovecot22, but I get a lot of these: >> file xxx from install of dovecot22-1:2.2.15-1.gf.el6.x86_64 conflicts with file >> from package dovecot-1:2.0.9-8.el6_6.4.x86_64 >> >> I tried yum update dovecot22, but I get: >> Package(s) dovecot22

when I do yum update, elrepo offers kmod-nvifdia, but yum does this: --> Processing Dependency: kernel(sme_me_mask) = 0x17fbce60 for package: kmod-nvidia-390.48-2.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(reservation_object_add_excl_fence) = 0xea98efc0 for package: kmod-nvidia-390.48-2.el7_5.elrepo.x86_64 --> Processing Dependency: kernel(drm_vblank_init) = 0xdcd50a49 for

I've recently built a new mail server with centos6.5, and decided to bite the bullet and leave SELinux running. I've stumbled through making things work and am mostly there. I've got my own spam and ham corpus as mbox files in /home/user/Mail/learned. These files came from my backup of the centos 5 server this machine is replacing. The folder is owned by the user (the following is

Okay, I've traced it to a bug in configparser, which on my python 2.7.4 system is a backport of configparser from python 3. Here is a clean patch that works around the problem. Geoffrey On Wed, Nov 6, 2013 at 10:24 AM, Geoffrey Irving <irving at naml.us> wrote: > LLVM builds with me on the release_33 branch, but fails on trunk. I > bisected the problem to this commit: > >

I'm running Centos 7.8.2003, with firewalld. I was getting huge numbers of ssh attempts per day from a few specific ip blocks. The offenders are 45.0.0.0/24, 49.0.0.0/24, 51.0.0.0/24, 111.0.0.0/24 and 118.0.0.0/24, and they amounted to a multiple thousands of attempts per day. I installed and configured fail2ban, but still saw a lot of attempts in the logs, and the ipset created was

LLVM builds with me on the release_33 branch, but fails on trunk. I bisected the problem to this commit: commit b49fb7bcd5001567d2da06f6a6e1c7ba79649e1b Author: Daniel Dunbar <daniel at zuster.org> Date: Wed Aug 14 23:15:39 2013 +0000 [llvm-build] Make Py3 compatible. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 188424 91177308-0d34-0410-b5e6-96231b3b80d8

I'm running fail2ban to attempt to block malicious brute-force password dictionary attacks against ssh. They seem to be rolling through a block of ip addresses as the source to defeat this kind of screening, so I've set some ip addresses to be blocked in iptables. Here is the output of iptables -L (edited): Chain INPUT (policy ACCEPT) target prot opt source destination

Having done my fresh 5.0 install a couple months ago I'm slowly getting things back in to working condition. Decided last night to try setting up lmsensors. Got it all set up (modules, etc taken care of) and it runs and reports values, but some of 'em a clearly wrong with the default sensors.conf Trying to use the old sensors.conf I used on Centos 4 produces even more whacked-out results,