Re: [CentOS] logrotate script not working

[Alexander Dalloz]

Am 08.01.2015 um 03:54 schrieb Tim Dunphy:

Hey guys,

  Got a quick question and I hope this is an easy one!

  In my /etc/logrotate.conf file I have the following entry:

  # rotate all of the apache logs  -- we'll rotate them here
/var/log/mysqld.log  {
 weekly
 size  50M
 create 0644 mysql mysql
 rotate 1
}

And from that I would expect the log to rotate when it reaches 50M in size.
However I just caught that log weighing in at 356MB!!  So how can I get
this log file to rotate when it hits 50MB?


That's because the MySQL daemon has his hands on the log's file 
descriptor and still write the log while it has been moved by logrotate.


You will have to add a command to the logrotate definition which causes 
the MySQL daemon to write into a new log file (mysqladmin flush-logs).


https://dev.mysql.com/doc/refman/5.5/en/log-file-maintenance.html


Any ideas, advice and help at all would be appreciated.

Thanks
Tim


Alexander



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

Re: [CentOS] Design changes are done in Fedora

[Rob Kampen]

On 01/07/2015 01:06 PM, Always Learning wrote:

On Tue, 2015-01-06 at 16:07 -0700, Warren Young wrote:



 "There is nothing new to be discovered in physics now. All that
  remains is more and more precise measurement.”

  — William Thomson, Lord Kelvin, 1900

Now means the current time. Now is not, and never will be, The (unknown)
Future.

In the real world of using computers productively for repetitive tasks,
people want stability and perhaps faster running programmes. No one ever
wants a major upset of being forced to use a different method to perform
the same tasks.

Young men are enthusiastic about implementing new ideas. Old men with
substantially more experience wisely want to avoid disrupting
well-running systems. Time is money. Disruptions waste money and cause
errors.
New disruption causing ideas are also the food for innovation and 
progress. Bring them on, we need them.
I think RH / CentOS strike a reasonable / measured balance, more or less 
freeze a set of function / capability for each major release - only 
release security patches and changes that are necessary to maintain 
functioning across the www.
Then with each major release do a jump - yes this is disruptive - yes it 
means learning new ways of doing old things, hopefully those making 
these decisions in RH have the knowledge and perspective to make the 
calls / evaluations necessary.

If you think you can do better, go get a job at RH.




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

Re: [CentOS] logrotate script not working

[Christopher Jacoby]

Check for selinux denials for logrotate.

Chris
On Jan 7, 2015 8:09 PM, "Mateusz Guz"  wrote:

> Have u tried removing the 'weekly' directive?
> You might consider replacing size with maxsize (details below)
>
> maxsize size
> Log files are rotated when they grow bigger than size bytes even before
> the additionally specified time interval (daily, weekly, monthly, or
> yearly). The related size option is similar except that it is mutually
> exclusive with the time interval options, and it causes log files to be
> rotated without regard for the last rotation time. When maxsize is used,
> both the size and timestamp of a log file are considered.
>
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Tim Dunphy
> Sent: Thursday, January 08, 2015 3:55 AM
> To: CentOS mailing list
> Subject: [CentOS] logrotate script not working
>
> Hey guys,
>
>  Got a quick question and I hope this is an easy one!
>
>  In my /etc/logrotate.conf file I have the following entry:
>
>  # rotate all of the apache logs  -- we'll rotate them here
> /var/log/mysqld.log  {
> weekly
> size  50M
> create 0644 mysql mysql
> rotate 1
> }
>
> And from that I would expect the log to rotate when it reaches 50M in size.
> However I just caught that log weighing in at 356MB!!  So how can I get
> this log file to rotate when it hits 50MB?
>
> Any ideas, advice and help at all would be appreciated.
>
> Thanks
> Tim
>
> --
> GPG me!!
>
> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] logrotate script not working

[Mateusz Guz]

Have u tried removing the 'weekly' directive?
You might consider replacing size with maxsize (details below)

maxsize size
Log files are rotated when they grow bigger than size bytes even before the 
additionally specified time interval (daily, weekly, monthly, or yearly). The 
related size option is similar except that it is mutually exclusive with the 
time interval options, and it causes log files to be rotated without regard for 
the last rotation time. When maxsize is used, both the size and timestamp of a 
log file are considered.


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Tim Dunphy
Sent: Thursday, January 08, 2015 3:55 AM
To: CentOS mailing list
Subject: [CentOS] logrotate script not working

Hey guys,

 Got a quick question and I hope this is an easy one!

 In my /etc/logrotate.conf file I have the following entry:

 # rotate all of the apache logs  -- we'll rotate them here
/var/log/mysqld.log  {
weekly
size  50M
create 0644 mysql mysql
rotate 1
}

And from that I would expect the log to rotate when it reaches 50M in size.
However I just caught that log weighing in at 356MB!!  So how can I get
this log file to rotate when it hits 50MB?

Any ideas, advice and help at all would be appreciated.

Thanks
Tim

-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] logrotate script not working

[Tim Dunphy]

Hey guys,

 Got a quick question and I hope this is an easy one!

 In my /etc/logrotate.conf file I have the following entry:

 # rotate all of the apache logs  -- we'll rotate them here
/var/log/mysqld.log  {
weekly
size  50M
create 0644 mysql mysql
rotate 1
}

And from that I would expect the log to rotate when it reaches 50M in size.
However I just caught that log weighing in at 356MB!!  So how can I get
this log file to rotate when it hits 50MB?

Any ideas, advice and help at all would be appreciated.

Thanks
Tim

-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] dovecot move doesn't work: RESLOVED

[Peter]

On 01/08/2015 12:16 PM, Chuck Campbell wrote:
> Peter,
> thank you, I was guessing this is what might be needed, and I appreciate the
> heads up on what to expect when I do the update.
> 
> The resolution I achieved is a bit more convoluted, but it consists of the
> following, and remains consistent with centos 6.6 version of dovecot:

You're welcome and while I'm flattered that you would consider my build
of dovecot I do tend to recommend that people only use it if they have a
real need for features that are not in 2.0 so I'm not disappointed that
you decided to stay with the CentOS version for now.  I don't pretend to
be as reliable in keeping my packages up to date as RedHat (and hence
CentOS) is, either as I have to do it in my spare time of which I do not
have a lot.  That said if you want to experiment and eventually move to
2.2 I'm happy that you want to use my package for it.

Good luck and I'm happy to help if you have further need.


Peter
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] When will CentOS Publish Errata?

[Somers-Harris, David | David | OPS]

On 01/07/2015 3:04 AM, Liam O'Toole wrote:
>> Maybe you missed the big announcement:
>> http://lists.centos.org/pipermail/centos-announce/2014-January/020100.html

Thanks for this Liam!
It gave me a lot of context I was missing.

On 01/07/2015 4:25 AM, Jim Perrin wrote:
> Nope. We're still air-gapped from the RHEL business units. We have lines of 
> communication to other RH community projects, but nothing that would line up 
> with this thread.

Maybe I'm being a bit of an optimist - I don't know much about Red Hat Inc.'s 
culture - but can't somebody just pop into the Red Hat Legal department and ask 
some clarifying questions?
Maybe they're more willing to help improve CentOS than we think ... would it 
hurt to ask?

On 01/07/2015 12:25 AM, Johnny Hughes wrote:
> What we need is a way to get that info from another place.
> Maybe the oval data, if it has all the required information and if the Terms 
> of Service allow for that.
> Someone in the Community needs to research that and see if it is usable or if 
> there is some other source for the information that can then be modified to 
> create the updateinfo.xml file.

How do we know if the ToU allow for it? Is there a way to check?
Whatever we do we have to look at the metadata provided via RHN or Red Hat 
website in order to make judgments about what the purpose of the change is.
What does the CentOS Project currently do for Release Notes? 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] dovecot move doesn't work: RESLOVED

[Chuck Campbell]

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 available, but not installed.
>>
>> What is the right way to do this?
> yum shell
> remove dovecot
> install dovecot22
> run
>
> I should warn you that there are subtle changes to dovecot config
> between 2.0 and 2.2 that may give you issues when switching.  You will
> likely have to tweak a few config options to get it to work the way you
> want.
>
> If you're using MailDir storage then you can simply move the messages
> yourself, it's as easy as using the mv command to move them from one
> directory to another and you won't need the doveadm move command.
>
> If you have any more questions feel free to ask them here or in
> #ghettoforge on FreeNode IRC.
>
>
> Peter
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

Peter,
thank you, I was guessing this is what might be needed, and I appreciate the
heads up on what to expect when I do the update.

The resolution I achieved is a bit more convoluted, but it consists of the
following, and remains consistent with centos 6.6 version of dovecot:

wrote a cron script that does the following:

stop fetchmail process
stop sendmail process
stop spamassassin process
run sa-learn against the user's spam_to_learn mailbox
run 'doveadm mailbox unsubscribe' to unsubscribe the spam_to_learn mailbox
run 'doveadm mailbox rename' to rename the spam_to_learn mailbox to
${date}_spam_learned
run 'doveadm mailbox subscribe' to subscribe the ${date}_spam_learned mailbox
(for testing and validation purposes, I will disable this eventually)
run 'doveadm mailbox create' to create a new spam_to_learn mailbox
run 'doveadm mailbox subscribe' to subscribe the new spam_to_learn mailbox
then
run sa-learn against the user's ham_to_learn mailbox
run 'doveadm mailbox unsubscribe' to unsubscribe the ham_to_learn mailbox
run 'doveadm mailbox rename' to rename the ham_to_learn mailbox to
${date}_ham_learned
run 'doveadm mailbox subscribe' to subscribe the ${date}_ham_learned mailbox
(for testing and validation purposes, I will disable this eventually)
run 'doveadm mailbox create' to create a new ham_to_learn mailbox
run 'doveadm mailbox subscribe' to subscribe the new ham_to_learn mailbox
start spamassassin
start sendmail
start fetchmail

Note that the doveadm-mailbox help indicates that some of these steps can be
combined by using the -s option to subscribe or unsubscribe, depending on the
function invoked (rename, create, delete), but they don't work. You need to do
the steps manually, one at a time as I have them listed here.

When I have more time, I will go ahead with a dovecot 2.2x install and report on
any issues I find.

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
 Houston, TX, 77008 |  Chuck Campbell   | campb...@accelinc.com
|  President & Senior Geoscientist  |

 "Integration means more than having all the maps at the same scale!"

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

Re: [CentOS] dovecot move doesn't work

[Peter]

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 available, but not installed.
> 
> What is the right way to do this?

yum shell
remove dovecot
install dovecot22
run

I should warn you that there are subtle changes to dovecot config
between 2.0 and 2.2 that may give you issues when switching.  You will
likely have to tweak a few config options to get it to work the way you
want.

If you're using MailDir storage then you can simply move the messages
yourself, it's as easy as using the mv command to move them from one
directory to another and you won't need the doveadm move command.

If you have any more questions feel free to ask them here or in
#ghettoforge on FreeNode IRC.


Peter
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Gary Greene]

> On Jan 7, 2015, at 12:08 PM, John R Pierce  wrote:
> 
> On 1/7/2015 11:30 AM, Gary Greene wrote:
>> During the reboot, most card’s drivers on init, will invalidate the cache on 
>> the card to ensure dirty pages of data don’t get flushed to disk, to prevent 
>> scribbling junk data to the platters. From what I recall, this is true of 
>> both the megaraid and adaptec based cards.
> 
> Presumably, this cache invalidation is only on cards that don't have battery 
> (or flash) backed write cache? Doing that on a BB/FBWC system would 
> negate the usefulness of said battery backed cache entirely.
> 


The ones with batteries will try to properly write the content of the cache to 
the disk right before the cache invalidate occurs. This is one of the few times 
when they aren’t lazy in their write patterns.

Regarding cheap vs. enterprise drives, agreed. You should absolutely never 
trust the disks to do the “right” thing with cheap models.

--
Gary L. Greene, Jr.
Sr. Systems Administrator
IT Operations
Minerva Networks, Inc.
Cell: +1 (650) 704-6633

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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Les Mikesell]

On Wed, Jan 7, 2015 at 3:30 PM, John R Pierce  wrote:
>>
>> Right... but only cost 133% (about) more than consumer drives, as opposed
>> to the 300% that the "server/enterprise" grade drives' cost.
>
>
> well, those $$$ drives are likely SAS rather than SATA, and that has other
> advantages...  10k or 15k RPM gives you up to double the IOPS per spindle of
> a 7200rpm SATA drive (and WD Reds are only 5900 RPM, I believe?)...   2.5"
> enterprise disks let you have more smaller spindles in the same space (24-25
> per 2U vs 12 for 3.5") for higher IO concurrency, and SAS supports
> multipathing (dual porting) for higher IO bandwidth, also SAS has tagged
> command queueing which often performs better than SATA NCQ under high IO
> concurrency workloads, like database servers.

These particular drives are enterprise SAS versions, but about as old
as they made them.

-- 
  Les Mikesell
lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[John R Pierce]

On 1/7/2015 12:50 PM, m.r...@5-cent.us wrote:

Right... but only cost 133% (about) more than consumer drives, as opposed
to the 300% that the "server/enterprise" grade drives' cost.


well, those $$$ drives are likely SAS rather than SATA, and that has 
other advantages...  10k or 15k RPM gives you up to double the IOPS per 
spindle of a 7200rpm SATA drive (and WD Reds are only 5900 RPM, I 
believe?)...   2.5" enterprise disks let you have more smaller spindles 
in the same space (24-25 per 2U vs 12 for 3.5") for higher IO 
concurrency, and SAS supports multipathing (dual porting) for higher IO 
bandwidth, also SAS has tagged command queueing which often performs 
better than SATA NCQ under high IO concurrency workloads, like database 
servers.



--
john r pierce  37N 122W
somewhere on the middle of the left coast

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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[John R Pierce]

On 1/7/2015 12:15 PM, m.r...@5-cent.us wrote:

Actually, the WD Reds and similar are just fine.


those are specifically sold for use in small NAS (raid) environments, so 
yeah, they are configured 'correctly'.




--
john r pierce  37N 122W
somewhere on the middle of the left coast

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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[John R Pierce]

On 1/7/2015 11:30 AM, Gary Greene wrote:

During the reboot, most card’s drivers on init, will invalidate the cache on 
the card to ensure dirty pages of data don’t get flushed to disk, to prevent 
scribbling junk data to the platters. From what I recall, this is true of both 
the megaraid and adaptec based cards.


Presumably, this cache invalidation is only on cards that don't have 
battery (or flash) backed write cache? Doing that on a BB/FBWC 
system would negate the usefulness of said battery backed cache entirely.


IMHO, an even bigger problem is using cheap desktop class SATA drives 
for server storage.These FREQUENTLY lie about write commits.This 
sort of behavior is a VERY good reason to stick with vendor qualified 
and branded server drives that have been tested to work with the 
specific controller + backplane configurations they are sold with.   And 
yes, those drives cost 2-3X more than your Newegg/Amazon elcheapo 
desktop stuff.


All of this controller and drive behavior is a VERY good argument for 
the use of end to end checksumming like ZFS does...  a ZFS 'scrub' 
operation WILL detect any data corruption on the file system and raid, 
whatever the source, and many inconsistencies can be corrected, such as 
one disk of a mirror having a stale block.


--
john r pierce  37N 122W
somewhere on the middle of the left coast

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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Les Mikesell]

On Wed, Jan 7, 2015 at 1:37 PM, Gary Greene  wrote:
>>
> Problem is, Gordon, the layer I’m talking about is _below_ the logical layer 
> that filesystems live at, in the block layer, at the mercy of drivers, and 
> firmware that the kernel has zero control over. While in a perfect world, the 
> controller would do strictly only what the Kernel tells it, that just isn’t 
> true for a while now with the large caches that drives and controllers have 
> now.
>
> In most cases, this should never trigger, however in some buggy drivers, or 
> controllers that have buggy firmware, the writes can be seriously delayed to 
> disk, which can cause data to never make it to the platter.
>

I'd have to shut one down and get into the bios config to see, but I
think these default to write-through if they aren't battery backed -
caching may not even be an option.   This one might have a battery
going bad, though.

I see a bunch of entries like:
ioatdma :00:08.0: Channel halted, chanerr = 2
ioatdma :00:08.0: Channel halted, chanerr = 0
in the logs and one of these:
hrtimer: interrupt took 258633 ns

Not sure what those mean.   We do have considerably more systems
running windows than linux on this hardware and I don't think anyone
has noticed a systemic problem there.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Gary Greene]

> On Jan 6, 2015, at 9:23 PM, Gordon Messmer  wrote:
> 
> On 01/06/2015 04:37 PM, Gary Greene wrote:
>> This has been discussed to death on various lists, including the
>> LKML...
>> 
>> Almost every controller and drive out there now lies about what is
>> and isn’t flushed to disk, making it nigh on impossible for the
>> Kernel to reliably know 100% of the time that the data HAS been
>> flushed to disk. This is part of the reason why it is always a Good
>> Idea™ to have some sort of pause in the shut down to ensure that it
>> IS flushed.
> 
> That's pretty much entirely irrelevant to the original question.
> 
> (Feel free to correct me if I'm wrong in the following)
> 
> A filesystem has three states: Clean, Dirty, and Dirty with errors.
> 
> When a filesystem is unmounted, the cache is flushed and it is marked clean 
> last.  This is the expected state when a filesystem is mounted.
> 
> Once a filesystem is mounted read/write, then it is marked dirty.  If a 
> filesystem is dirty when it is mounted, then it wasn't unmounted properly.  
> In the case of a journaled filesystem, typically the journal will be replayed 
> and the filesystem will then be mounted.
> 
> The last case, dirty with errors indicates that the kernel found invalid data 
> while the filesystem was mounted, and recorded that fact in the filesystem 
> metadata.  This will normally be the only condition that will force an fsck 
> on boot.  It will also normally result in logs being generated when the 
> errors are encountered.  If your filesystems are force-checked on boot, then 
> the logs should usually tell you why.  It's not a matter of a timeout or some 
> device not flushing its cache.
> 
> Of course, the other possibility is simply that you've formatted your own 
> filesystems, and they have a maximum mount count or a check interval.  Use 
> 'tune2fs -l' to check those two values.  If either of them are set, then 
> there is no problem with your system.  It is behaving as designed, and 
> forcing a periodic check because that is the default behavior.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

Problem is, Gordon, the layer I’m talking about is _below_ the logical layer 
that filesystems live at, in the block layer, at the mercy of drivers, and 
firmware that the kernel has zero control over. While in a perfect world, the 
controller would do strictly only what the Kernel tells it, that just isn’t 
true for a while now with the large caches that drives and controllers have now.

In most cases, this should never trigger, however in some buggy drivers, or 
controllers that have buggy firmware, the writes can be seriously delayed to 
disk, which can cause data to never make it to the platter.

--
Gary L. Greene, Jr.
Sr. Systems Administrator
IT Operations
Minerva Networks, Inc.
Cell: +1 (650) 704-6633





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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Gary Greene]

> On Jan 6, 2015, at 5:50 PM, Les Mikesell  wrote:
> 
> On Tue, Jan 6, 2015 at 6:37 PM, Gary Greene  
> wrote:
>> 
>> 
>> Almost every controller and drive out there now lies about what is and isn’t 
>> flushed to disk, making it nigh on impossible for the Kernel to reliably 
>> know 100% of the time that the data HAS been flushed to disk. This is part 
>> of the reason why it is always a Good Idea™ to have some sort of pause in 
>> the shut down to ensure that it IS flushed.
>> 
>> This is also why server grade gear uses battery backed buffers, etc. which 
>> are supposed to allow drives to properly flush the data to disk. There is 
>> still a slim chance in these cases that the data still will not reach the 
>> platter before power off or reboot, especially in catastrophic cases.
>> 
> 
> This was a reboot from software, not a power drop.  Does that do
> something to kill the disk cache if anything happened to still be
> there?

In most cases intentional reboots _shouldn’t_ trigger this, but I cannot say 
that with a 100% certainty since, again, controllers CAN and DO lie. If the 
controller is not battery backed, the certainty is even more shaky, since the 
card's firmware can be in the process of lazy writing the content to disk when 
the main board drops power to the card's slot on the main board during the 
reboot, which without the extra battery would cause the data to be lost.

During the reboot, most card’s drivers on init, will invalidate the cache on 
the card to ensure dirty pages of data don’t get flushed to disk, to prevent 
scribbling junk data to the platters. From what I recall, this is true of both 
the megaraid and adaptec based cards.

--
Gary L. Greene, Jr.
Sr. Systems Administrator
IT Operations
Minerva Networks, Inc.
Cell: +1 (650) 704-6633





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

Re: [CentOS] dovecot move doesn't work

[Chuck Campbell]

On 1/7/2015 10:52 AM, Johnny Hughes wrote:
> On 01/07/2015 10:39 AM, Chuck Campbell wrote:
>> 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 doveadm -Dv move -u user learned_spam mailbox 'spam_to_learn' 
> ALL
>
> I get this result:
> usage: doveadm [-Dv] [-f ]  []
 [ ... ]

> this doesn't even list a move command, yet the dovecot pages show it and 
> give
> examples.
 The dovecot version provided by CentOS 6 simply does not have that 
 feature implemented. The wiki.dovecot.org documentation reflects the 
 current stable upstream status of things.

> any suggestions?
 You may use the dovecot22 package provided by the ghettoforge plus 
 repository, providing dovecot release 2.2.15.
>> 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 available, but not installed.
>>
>> What is the right way to do this?
> My suggestion would be to contact the ghettoforge people as this is no
> longer really a CentOS issue.  Certainly this list can be used if they
> are on it.
I'm not sure, I'll await a response from them. I do believe the Centos list
might have someone who went down this path, or a similar one, with a different
package though, that is why I am asking.
>
> But instead of using a repo I have personally never heard of, I would
> instead look at the documentation for version of dovecot that is in
> CentOS 6.
The documentation for dovecot 2.0.9xxx in Centos 6 does not indicate the
functionality exists. Further looking shows it is in a newer version that I am
trying to implement. The dovecot version 2.2 exists in other repos as well. I am
aware of the perils of mixing repos, hence I was asking the Centos list if
anyone has been here before.
>
> The purpose of running CentOS is to have enterprise level server
> software .. if you instead want latest and greatest server software, I
> would recommend that you just run the latest Fedora Server.
I agree with the Centos philosophy and have happily lived without running other
distro/repo packages until now. Since I believe providing a way for users of
this server to train spamassassin with the spam they have identified, and the
false positive messages as well is within the limits of sanity, I am attempting
to get there from here (TM). I don't believe switching the entire OS to a
bleeding edge one is appropriate. I would rather attempt one bleeding edge
(dovecot 2.2x) than everything this machine provides all in one fell swoop.

I only need to understand the mechanics of installing a package with yum, which
conflicts with the package it is intended to replace. I will live with the peril
of testing this and understand it might break something else. Meanwhile the
unbroken bits will keep functioning.

I suspect I need to 'yum remove dovecot-2.0.9x', then 'yum install
dovecot22-2.2.x' to get there, but was hoping someone on the Centos list had
been there before me.

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
 Houston, TX, 77008 |  Chuck Campbell   | campb...@accelinc.com
|  President & Senior Geoscientist  |

 "Integration means more than having all the maps at the same scale!"

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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Valeri Galtsev]

On Wed, January 7, 2015 10:54 am, Les Mikesell wrote:
> On Wed, Jan 7, 2015 at 10:43 AM, Valeri Galtsev
>  wrote:
>>>
>>> Not junk - these are mostly IBM 3550/3650 boxes - pretty much top of
>>> the line in their day (before the M2/3/4 versions),  They have
>>> Adaptec raid contollers,
>>
>> I never had Adaptec in _my_ list of good RAID hardware... But certainly
>> I
>> can note be the one to offer judgement on hardware I avoid to the best
>> of
>> my ability. If you can afford, I would do the test: replace Adaptec with
>> something else (in my list it would be either 3ware or LSI or areca),
>> leaving the rest of hardware as it is. And see it the problems continue.
>> I
>> do realize that there is more to it than just pulling one card and
>> sticking another in its place (that's why I said if you can "afford" it
>> meaning in more general sense, not just monetary).
>
> It's not something happening as a repeatable thing or that I could
> consider better/worse after replacing something.  Maybe 3 times a year
> across a few hundred machines and generally not repeating on the same
> ones. But if there is anything in common it is on very 'active'
> filesystems.
>

Too bad... Reminds me one of my 32 node clusters in which one of the nodes
crashed in a crashed once a month (always different node, so probability
of run is 32 Month before crash ;-( Too bad for troubleshooting. Only
after 6 Months I pinpointed particular brand of RAM mixed in into each
node - when I got rid of it, the trouble ended... I would bet on Adaptec
cards in your case... though ideally I shouldn't be offering judgement on
hardware of the brand I almost never use. Good luck!

Valeri


Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Les Mikesell]

On Wed, Jan 7, 2015 at 10:15 AM,   wrote:
>>>
>> Yes - the unattended fsck fails.   Personally, I'd prefer for the
>> default run to use '-y' in the first place.  It's not like I'm more
>> likely than fsck to know how to fix it and it is very inconvenient on
>> remote machines.   The recent case was an opennms system updating a
> 
>
> In some ways, I prefer the fsck run by reboot to fail - that way, I see
> it, and it most probably tells me that it's time to look at replacing the
> disk.

Seems random to me - not repeating on the same box, and rare enough
that it is hard to make any generalization except that it is painful
to talk some remote helper through the recovery process - usually
involving emailing some cell phone photos of the console to figure out
which partition has the problem.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Les Mikesell]

On Wed, Jan 7, 2015 at 10:43 AM, Valeri Galtsev
 wrote:
>>
>> Not junk - these are mostly IBM 3550/3650 boxes - pretty much top of
>> the line in their day (before the M2/3/4 versions),  They have
>> Adaptec raid contollers,
>
> I never had Adaptec in _my_ list of good RAID hardware... But certainly I
> can note be the one to offer judgement on hardware I avoid to the best of
> my ability. If you can afford, I would do the test: replace Adaptec with
> something else (in my list it would be either 3ware or LSI or areca),
> leaving the rest of hardware as it is. And see it the problems continue. I
> do realize that there is more to it than just pulling one card and
> sticking another in its place (that's why I said if you can "afford" it
> meaning in more general sense, not just monetary).

It's not something happening as a repeatable thing or that I could
consider better/worse after replacing something.  Maybe 3 times a year
across a few hundred machines and generally not repeating on the same
ones. But if there is anything in common it is on very 'active'
filesystems.

-- 
Les Mikesell
   lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] dovecot move doesn't work

[Johnny Hughes]

On 01/07/2015 10:39 AM, Chuck Campbell wrote:
> 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 doveadm -Dv move -u user learned_spam mailbox 'spam_to_learn' 
 ALL

 I get this result:
 usage: doveadm [-Dv] [-f ]  []
>>> [ ... ]
>>>
 this doesn't even list a move command, yet the dovecot pages show it and 
 give
 examples.
>>> The dovecot version provided by CentOS 6 simply does not have that 
>>> feature implemented. The wiki.dovecot.org documentation reflects the 
>>> current stable upstream status of things.
>>>
 any suggestions?
>>> You may use the dovecot22 package provided by the ghettoforge plus 
>>> repository, providing dovecot release 2.2.15.
> 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 available, but not installed.
> 
> What is the right way to do this?

My suggestion would be to contact the ghettoforge people as this is no
longer really a CentOS issue.  Certainly this list can be used if they
are on it.

But instead of using a repo I have personally never heard of, I would
instead look at the documentation for version of dovecot that is in
CentOS 6.

The purpose of running CentOS is to have enterprise level server
software .. if you instead want latest and greatest server software, I
would recommend that you just run the latest Fedora Server.




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Valeri Galtsev]

On Wed, January 7, 2015 10:33 am, Les Mikesell wrote:
> On Wed, Jan 7, 2015 at 9:52 AM, Gordon Messmer 
> wrote:
>>
>> Every regular file's directory entry on your system is a hard link.
>> There's
>> nothing particular about links (files) that make a filesystem fragile.
>
> Agreed, although when there are millions, the fsck fixing it is somewhat
> slow.
>
>>> It is mostly on aging hardware, so it
>>> is possible that there are underlying controller issues.  I also see
>>> some rare cases on similar machines where a filesystem will go
>>> read-only with some scsi errors logged, but didn't look for that yet
>>> in this case.
>>
>>
>> It's probably a similar cause in all cases.  I don't know how many times
>> I've seen you on this list defending running old hardware / obsolete
>> hardware.  Corruption and failure are more or less what I'd expect if
>> your
>> hardware is junk.
>
> Not junk - these are mostly IBM 3550/3650 boxes - pretty much top of
> the line in their day (before the M2/3/4 versions),  They have
> Adaptec raid contollers,

I never had Adaptec in _my_ list of good RAID hardware... But certainly I
can note be the one to offer judgement on hardware I avoid to the best of
my ability. If you can afford, I would do the test: replace Adaptec with
something else (in my list it would be either 3ware or LSI or areca),
leaving the rest of hardware as it is. And see it the problems continue. I
do realize that there is more to it than just pulling one card and
sticking another in its place (that's why I said if you can "afford" it
meaning in more general sense, not just monetary).

Valeri

> SAS drives, mostly configured as RAID1
> mirrors.  I realize that hardware isn't perfect and this is not
> happening on a large percentage of them.   But, I don't see anything
> that looks like scsi errors in this log and I'm surprised that after
> running apparently error-free there would be problems detected after a
> software reboot.
>
> I think the newer M2 and later models went to a different RAID
> controller, though.   Maybe there was a reason.
>
> --
>Les Mikesell
>   lesmikes...@gmail.com
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] dovecot move doesn't work

[Chuck Campbell]

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 doveadm -Dv move -u user learned_spam mailbox 'spam_to_learn' 
>>> ALL
>>>
>>> I get this result:
>>> usage: doveadm [-Dv] [-f ]  []
>> [ ... ]
>>
>>> this doesn't even list a move command, yet the dovecot pages show it and 
>>> give
>>> examples.
>> The dovecot version provided by CentOS 6 simply does not have that 
>> feature implemented. The wiki.dovecot.org documentation reflects the 
>> current stable upstream status of things.
>>
>>> any suggestions?
>> You may use the dovecot22 package provided by the ghettoforge plus 
>> repository, providing dovecot release 2.2.15.
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 available, but not installed.

What is the right way to do this?

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
 Houston, TX, 77008 |  Chuck Campbell   | campb...@accelinc.com
|  President & Senior Geoscientist  |

 "Integration means more than having all the maps at the same scale!"

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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Les Mikesell]

On Wed, Jan 7, 2015 at 9:52 AM, Gordon Messmer  wrote:
>
> Every regular file's directory entry on your system is a hard link. There's
> nothing particular about links (files) that make a filesystem fragile.

Agreed, although when there are millions, the fsck fixing it is somewhat slow.

>> It is mostly on aging hardware, so it
>> is possible that there are underlying controller issues.  I also see
>> some rare cases on similar machines where a filesystem will go
>> read-only with some scsi errors logged, but didn't look for that yet
>> in this case.
>
>
> It's probably a similar cause in all cases.  I don't know how many times
> I've seen you on this list defending running old hardware / obsolete
> hardware.  Corruption and failure are more or less what I'd expect if your
> hardware is junk.

Not junk - these are mostly IBM 3550/3650 boxes - pretty much top of
the line in their day (before the M2/3/4 versions),  They have
Adaptec raid contollers, SAS drives, mostly configured as RAID1
mirrors.  I realize that hardware isn't perfect and this is not
happening on a large percentage of them.   But, I don't see anything
that looks like scsi errors in this log and I'm surprised that after
running apparently error-free there would be problems detected after a
software reboot.

I think the newer M2 and later models went to a different RAID
controller, though.   Maybe there was a reason.

-- 
   Les Mikesell
  lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Steve Clark]

On 01/07/2015 08:53 AM, Les Mikesell wrote:

On Wed, Jan 7, 2015 at 12:10 AM, Keith Keller
 wrote:

On 2015-01-07, Gordon Messmer  wrote:

Of course, the other possibility is simply that you've formatted your
own filesystems, and they have a maximum mount count or a check
interval.

If Les is having to run fsck manually, as he wrote in his OP, then this
is unlikely to be the cause of the issues he described in that post.
There must be some sort of errors on the filesystem that caused the
unattended fsck to exit nonzero.


Yes - the unattended fsck fails.   Personally, I'd prefer for the
default run to use '-y' in the first place.  It's not like I'm more
likely than fsck to know how to fix it and it is very inconvenient on
remote machines.   The recent case was an opennms system updating a
lot of rrd files, but I've also seen it on backuppc archives with lots
of files and lots of hard links.  Some of these have been on VMware
ESXi hosts where the physical host wasn't rebooted and the
controller/power not involved at all.  Eventually these will be
replaced with CentOS7 systems, probably using XFS but I don't know if
that will be better or worse.   It is mostly on aging hardware, so it
is possible that there are underlying controller issues.  I also see
some rare cases on similar machines where a filesystem will go
read-only with some scsi errors logged, but didn't look for that yet
in this case.


I know that I have seen it take 10 ot 15 minutes to sync a 7200 rpm 3 TB WD 
drive that had over
2 million rrd files being updated by ntopng when the system had 32GB of ram. 
The system is a
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz but one cpu will in in constant IO wait 
state until the
sync finishes. I have never tried shutting it down when it was syncing though.

--
Stephen Clark
*NetWolves Managed Services, LLC.*
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Gordon Messmer]

On 01/07/2015 05:53 AM, Les Mikesell wrote:


Yes - the unattended fsck fails.


In that case, there should be logs indicating the cause of the error 
when it was detected by the kernel.  There's probably something wrong 
with your controller or other hardware.



Personally, I'd prefer for the
default run to use '-y' in the first place.  It's not like I'm more
likely than fsck to know how to fix it and it is very inconvenient on
remote machines.   The recent case was an opennms system updating a
lot of rrd files, but I've also seen it on backuppc archives with lots
of files and lots of hard links.


Every regular file's directory entry on your system is a hard link. 
There's nothing particular about links (files) that make a filesystem 
fragile.



It is mostly on aging hardware, so it
is possible that there are underlying controller issues.  I also see
some rare cases on similar machines where a filesystem will go
read-only with some scsi errors logged, but didn't look for that yet
in this case.


It's probably a similar cause in all cases.  I don't know how many times 
I've seen you on this list defending running old hardware / obsolete 
hardware.  Corruption and failure are more or less what I'd expect if 
your hardware is junk.

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

Re: [CentOS] dovecot move doesn't work

[Chuck Campbell]

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 doveadm -Dv move -u user learned_spam mailbox 'spam_to_learn' ALL
>>
>> I get this result:
>> usage: doveadm [-Dv] [-f ]  []
> [ ... ]
>
>> this doesn't even list a move command, yet the dovecot pages show it and give
>> examples.
> The dovecot version provided by CentOS 6 simply does not have that 
> feature implemented. The wiki.dovecot.org documentation reflects the 
> current stable upstream status of things.
>
>> any suggestions?
> You may use the dovecot22 package provided by the ghettoforge plus 
> repository, providing dovecot release 2.2.15.
>
>> thanks,
>> -chuck
> Alexander
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

Has anyone else installed the 2.2x version of dovecot in centos? Any issues or
gotchas? I am loathe to just hammer on our working installation, but I need to
sort out this issue as well.

The dovecot pages indicate that ATrpms has a current 2.2x version, but I don't
see it when I try to do a yum update with ATrpms turned on. I may just have to
grab the rpms from the packages directory on ATrpms. Does anyone know if the
ATrpms layout is significantly different than elrepo? What kinds of issues might
I expect with just banging their dovecot rpm into my machine?

Sigh, I may have to set up another machine as a test mule...

thanks,
-chuck

-- 

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

Re: [CentOS] Design changes are done in Fedora

[Jonathan Billings]

On Tue, Jan 06, 2015 at 08:45:29PM -0600, John R. Dennison wrote:
> It's not relevant in _any_ sense.  CentOS is nothing more than (at it's
> core) a rebuild of RHEL.  This type of nonsense should be directed to
> Red Hat in a Red Hat venue.  It's nothing but off-topic noise here as
> CentOS will not deviate from its upstream in its core offerings.

Agreed.

If you want to participate in how the upstream OS is being shaped, I
suggest looking at the Fedora Project, which is driven by volunteers.

If you notice the Subject: of this thread, it is "Design changes are
done in Fedora".  Pretty clear message.

-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Design changes are done in Fedora

[Always Learning]

On Wed, 2015-01-07 at 08:31 -0500, Darr247 wrote:

> On 07 January 2015 @01:37 zulu, Always Learning wrote:
> > You seem to forget. Computers were invented to perform repetitive tasks.
> 
> Or maybe, some of us just seem to remember it differently.
> In my opinion, robots/automatons were invented to perform repetitive 
> tasks; computers were invented to perform logic operations faster and 
> more-reliably than humans.

My recollection was influenced by my discovery in 1966 of Power Samas
(later acquired by ICT) 40? 36? column small punch cards feed-in to a
printing machine to produce invoices for a then major international
publisher.  The replacement/upgrade was a Honeywell 1200 with tapes, 80
column card reader, printer and the ubiquitous air conditioning and
humidity control system. Luxuries like keyboards, disks, screens had not
been invented. It was plain, simple, effective and fairly reliable Data
Processing.

Two years later on a smaller H-120 I was writing commercial Cobol
programmes for a Norwegian angling distributor - orders, invoices,
statements, stock control. Again it was essentially repetitive
processing done much faster than before the usage of mainframes.

Computers can not function without logic. One of the the most important
advancements was of the "stored programme" feature instead of having to
reload the data processing programme, contained on punched cards in
strict sequence, every time a job needed doing.

Never bumped into "robots/automatons" anywhere at all in Data Processing
nor encountered anyone using that term. Computers evolved very slowly
from automated machine processing. A major advancement was made at the
USA's famous Bell Labs (subsequently destroyed in the interests of
shareholder profits) who invented the DTMF. It was the IC.

SPAM was another USA invention and so too were Microsoft-suitable
viruses.

-- 
Regards,

Paul.
England, EU.

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

Re: [CentOS] Design changes are done in Fedora

[Les Mikesell]

On Wed, Jan 7, 2015 at 7:31 AM, Darr247  wrote:
> On 07 January 2015 @01:37 zulu, Always Learning wrote:
>>
>> You seem to forget. Computers were invented to perform repetitive tasks.
>
>
> Or maybe, some of us just seem to remember it differently.
> In my opinion, robots/automatons were invented to perform repetitive tasks;
> computers were invented to perform logic operations faster and more-reliably
> than humans.

There's still a very odd mix of art and science involved.  This is
part of the fun, but still it seems like when everyone has the same
problem from the same causes there would be some way to automate or
re-use the knowledge of the fix instead of making everyone spend time
on their own new creative version.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Radeon graphics problems with CentOS 6.6

[Darby Vicker]

I sent this last night but it didn't show up in the archives.  Trying
again without the attachment.  Are messages with attachments blocked
on this list?

On Tue, Jan 6, 2015 at 11:50 PM, Darby Vicker  wrote:
> Thanks a ton for the suggestions and info everyone.
>
>> Two things I think you should consider doing...
>> 1) in your next post (and any bugs you open), include the `uname -a` of
>> the last known to work correctly CentOS/RHEL kernel, and the `uname -a`
>> of the first known to not work correctly CentOS/RHEL kernel and the
>> respective versions of radeon &| flrgx drivers.
>
> Sure.
>
> Last known kernel to work (pretty sure this is the last update under
> CentOS 6.5):
> Linux c6 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 
> x86_64 x86_64 GNU/Linux
>
> Kernels I've tried that don't work:
>
> kernel-2.6.32-504.el6.x86_64
> kernel-2.6.32-504.1.3.el6.x86_64
> kernel-2.6.32-504.3.3.el6.x86_64
> kernel-2.6.32-504.3.3.el6.centos.plus.x86_64
>
> Graphics card:
>
> 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
> BeaverCreek [Radeon HD 6530D]
>
> Open source driver version:
>
> xorg-x11-drv-ati-7.3.99-2.el6.x86_64
>
> I tried the proprietary drivers from elrepo too:
>
> fglrx-x11-drv-14.9-1.el6.elrepo.x86_64
>
> But it crashes X and also renders the system unreachable via ssh.  When
> X crashes with the open source driver, I can still get in via ssh.  I
> can boot to an older kernel with the fglrx drivers but graphics
> performance is awful for some reason.
>
>> 2) try out elrepo's el6 kernel-lt & kernel-ml and see if they work
>> correctly for you.  I suggest this, because for me it did workaround an
>> issue with intel chips (I guess I need to see what it will take to get
>> the elrepo folks to make just a back-ported intel driver from 3.17
>> [first known to work again, 3.16 does not]) .
>> http://lists.centos.org/pipermail/centos/2014-November/147579.html
>
> Great suggestion.  I just installed and booted the following kernel-ml.
>
> Linux c6 3.18.1-1.el6.elrepo.x86_64 #1 SMP Tue Dec 16 20:44:33 EST 2014 
> x86_64 x86_64 x86_64 GNU/Linux
>
> And it works!  I got A LOT of bad-looking errors on boot but it did
> boot and everything seems to work fine.  I've attached the boot.log
> just FYI.  I have not tried kernel-lt but I suspect it will work fine
> since it would install a 3.10 kernel.  (Based on the bugs below this
> problem doesn't appear in the 3.X branch until about 3.16).
>
> After searching the RHEL bug tracker, I do see some very similar bugs
> to what I'm experiencing.
> https://bugzilla.redhat.com/show_bug.cgi?id=1161321
> https://bugzilla.redhat.com/show_bug.cgi?id=1151757
>
> Both are on 3.X kernels under Fedora so not completely applicable.  The
> first one even has the same graphics card as I do - no activity
> though.  The second one is also very similar.and in one of the comments
> it was suggested to do this:
>
>> 2) If not, it looks like everyone else is using an ATI Radeon card and
>> likely something broke between 3.15 and 3.16. Please boot with "nomodeset" as
>> a grub option and report back. If it boots correctly, try modprobing radeon 
>> and
>> see if the screen goes black right away
>
> This sounded worthwhile so I booted successfully on the
> 2.6.32-504.3.3.el6.x86_64 kernel with "nomodeset".  I tried this before
> (as described in my xorg thread) and I get a lot of artifacts in the
> graphics but it does work.  However, the radeon driver is already
> loaded after I boot.  This is directly after the boot:
>
> [root@c6 ~]# lsmod | grep rad
> radeon   1536476  0
> ttm81172  1 radeon
> drm_kms_helper 82994  1 radeon
> drm   291284  3 radeon,ttm,drm_kms_helper
> i2c_algo_bit5711  1 radeon
> i2c_core   29964  12 
> tda18271,s5h1411,cx25840,cx23885,v4l2_common,videodev,tveeprom,i2c_piix4,radeon,drm_kms_helper,drm,i2c_algo_bit
> [root@c6 ~]#
>
>
>>> http://bugs.centos.org/view.php?id=4586
>>
>> Actually, I ask that people open a new ticket for each request. :)
>>
>> Akemi
>
> Akemi, maybe its not clear yet but would you prefer I submit this bug
> under the CentOS or RHEL tracker?  (And do you know if I can submit to
> the RHEL tracker without a RHEL subscription?)  Any advice on where to
> submit this info to get this fixed in the CentOS 6 line would be
> appreciated.
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Design changes are done in Fedora

[Александр Кириллов]

John R. Dennison писал 2015-01-07 04:49:

Quick question, if I may?  What does this have to do with CentOS?


I for one read this thread with interest. Let it be.
And IMHO the topics are relevant for anybody professionally involved 
with computers.


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

Re: [CentOS] reboot - is there a timeout on filesystem flush?

[Les Mikesell]

On Wed, Jan 7, 2015 at 12:10 AM, Keith Keller
 wrote:
> On 2015-01-07, Gordon Messmer  wrote:
>>
>> Of course, the other possibility is simply that you've formatted your
>> own filesystems, and they have a maximum mount count or a check
>> interval.
>
> If Les is having to run fsck manually, as he wrote in his OP, then this
> is unlikely to be the cause of the issues he described in that post.
> There must be some sort of errors on the filesystem that caused the
> unattended fsck to exit nonzero.
>

Yes - the unattended fsck fails.   Personally, I'd prefer for the
default run to use '-y' in the first place.  It's not like I'm more
likely than fsck to know how to fix it and it is very inconvenient on
remote machines.   The recent case was an opennms system updating a
lot of rrd files, but I've also seen it on backuppc archives with lots
of files and lots of hard links.  Some of these have been on VMware
ESXi hosts where the physical host wasn't rebooted and the
controller/power not involved at all.  Eventually these will be
replaced with CentOS7 systems, probably using XFS but I don't know if
that will be better or worse.   It is mostly on aging hardware, so it
is possible that there are underlying controller issues.  I also see
some rare cases on similar machines where a filesystem will go
read-only with some scsi errors logged, but didn't look for that yet
in this case.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Design changes are done in Fedora

[Darr247]

On 07 January 2015 @01:37 zulu, Always Learning wrote:

You seem to forget. Computers were invented to perform repetitive tasks.


Or maybe, some of us just seem to remember it differently.
In my opinion, robots/automatons were invented to perform repetitive 
tasks; computers were invented to perform logic operations faster and 
more-reliably than humans.

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

[CentOS] Password Must Change using SSSD in Samba 4.1.10

[Ashish Yadav]

Hi,

I am trying to implement the *password must change at next logon* in CentOS
6.5 client using sssd 1.11.6 where Samba 4.1.10 is my backend server.

Here are the list of things which I have done,

1. I have setup the CentOS to do the Domain login using sssd service. I can
able to login into the CentOS client using Domain user's credentials from
display
and from SSH also, no problem at all.

2. Next thing which I want to implement is that password must change
feature into Samba 4.1.10 server. To do that, I have been using Windows 7
ultimate
which is already in Domain and I am using RSAT tools for users and groups
where I have a option to check "password must change at next logon" option
for particular user.
After doing that Windows machine is honoring this and telling user to
change the password and allowing user to login after changing the password.

3. As far as the CentOS client is concerned, it was not honoring the
password must change and allowing user to login without asking for password
change using sssd with current password.

Here is the configuration file of sssd service,

[sssd]
config_file_version = 2
services = nss, pam
domains = EXAMPLE
sbus_timeout = 30

[nss]
filter_users = root
filter_groups = root
reconnection_retries = 3

[pam]
reconnection_retries = 3
offline_credentials_expiration = 0

[domain/EXAMPLE]
entry_cache_timeout = 600
entry_cache_group_timeout = 600
min_id = 1000
id_provider = ldap
auth_provider = krb5
chpass_provider = krb5
ldap_schema = rfc2307bis
ldap_uri = ldap://smbad.intra.example.com:390/
ldap_search_base = dc=intra,dc=example,dc=com
cache_credentials = true
krb5_server = smbad.intra.example.com:8880
krb5_realm= INTRA.EXAMPLE.COM 


ldap_default_bind_dn = cn=admin,dc=intra,dc=example,dc=com

ldap_default_authtok_type = password
ldap_default_authtok = 6pNEn7Eo3zmz9MxciGLx

4. I have also tried to achieve above thing using command line tool
"pdbedit" but without any luck. Here is the link <
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/passdb.html#pdbeditthing
>
which I have followed.

Please share your thoughts in order to help me and move forward to solve
this problem.

Thanks very much and regards,
Ashishkumar S. Yadav
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos