Re: [CentOS] How to stagger fsck executions
On 4/20/2015 9:08 PM, Hugh E Cruickshank wrote: The second idea was to set each filesystem to a different random count value. This would run the risk of having two or more executions at the same time but it would probably not be very frequent. Does anyone have a suggestion for a better way of doing this? use XFS, no fsck's until/unless something catastrophic happens to the file system. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] How to stagger fsck executions
On Tue, Apr 21, 2015 at 9:38 AM, Hugh E Cruickshank wrote: > CentOS 6 > > > My first idea was to manually run fsck on each filesystem, one every > couple of weeks. That way they will not all come due at the same time > if we reboot on a regular basis. > > The second idea was to set each filesystem to a different random count > value. This would run the risk of having two or more executions at > the same time but it would probably not be very frequent. > > Does anyone have a suggestion for a better way of doing this? > Take a look at 'man tune2fs' and 'man fstab' for modifying the fsck order in your system. HTH, -- Arun Khan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] How to stagger fsck executions
CentOS 6 Hi All: Over the weekend I had to reboot one of my systems and got hit with fsck runs on all of the filesystems. I would not mind so much except doing them all at once took over an hour. I would like to be able to stagger these, ideally only execute one fsck per reboot. I have been able to think of two possible solutions but neither is terrific. My first idea was to manually run fsck on each filesystem, one every couple of weeks. That way they will not all come due at the same time if we reboot on a regular basis. The second idea was to set each filesystem to a different random count value. This would run the risk of having two or more executions at the same time but it would probably not be very frequent. Does anyone have a suggestion for a better way of doing this? TIA Regards, Hugh -- Hugh E Cruickshank, Forward Software, www.forward-software.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS5 + lighttpd (EPEL) - fix Chrome security warning?
Thanks, I just found that one myself. In fact on a different platform the error message from Chrome actually explains it directly rather than just quote the error string. I was too focused on restricting the search to lighttpd and not enough on the error string. On Mon, Apr 20, 2015 at 3:20 PM, Frank Cox wrote: > On Mon, 20 Apr 2015 15:12:36 -0700 > Bart Schaefer wrote: > >> Is this just a configuration issue (in which case, what do I change?) > > Your certificate is apparently valid for longer than 39 months. > > Running your error message "NET::ERR_CERT_VALIDITY_TOO_LONG" through google > returns pages and pages of information explaining this issue. > > -- > MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com > ___ > 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] CentOS5 + lighttpd (EPEL) - fix Chrome security warning?
You need to reissue cert with stronger hash algorithm than sha1 Eero 21.4.2015 1.13 ap. "Bart Schaefer" kirjoitti: > Apologies if I should ask this elsewhere, google search is not helping. > > I've got a CentOS5 server with lighttpd installed from EPEL, > configured for https only (no connections on ports other than 443). I > have the latest security updates for openssl, etc. However, when > connecting to the server with recent Chrome from Windows or Android, I > get the "Your connection is not private" dialog with > "NET::ERR_CERT_VALIDITY_TOO_LONG". > > Is this just a configuration issue (in which case, what do I change?) > or do I need to further upgrade one of lighttpd or openssl? > > Thanks for any feedback. > ___ > 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] CentOS5 + lighttpd (EPEL) - fix Chrome security warning?
On 4/20/2015 3:12 PM, Bart Schaefer wrote: "NET::ERR_CERT_VALIDITY_TOO_LONG". Is this just a configuration issue (in which case, what do I change?) or do I need to further upgrade one of lighttpd or openssl? says your certificate's valid interval is too long. recent chrome rejects certs that are valid for 40+ months. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS5 + lighttpd (EPEL) - fix Chrome security warning?
On Mon, 20 Apr 2015 15:12:36 -0700 Bart Schaefer wrote: > Is this just a configuration issue (in which case, what do I change?) Your certificate is apparently valid for longer than 39 months. Running your error message "NET::ERR_CERT_VALIDITY_TOO_LONG" through google returns pages and pages of information explaining this issue. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS5 + lighttpd (EPEL) - fix Chrome security warning?
Apologies if I should ask this elsewhere, google search is not helping. I've got a CentOS5 server with lighttpd installed from EPEL, configured for https only (no connections on ports other than 443). I have the latest security updates for openssl, etc. However, when connecting to the server with recent Chrome from Windows or Android, I get the "Your connection is not private" dialog with "NET::ERR_CERT_VALIDITY_TOO_LONG". Is this just a configuration issue (in which case, what do I change?) or do I need to further upgrade one of lighttpd or openssl? Thanks for any feedback. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] wireshark 1.12.4
On 4/20/2015 2:07 PM, Warren Young wrote: On Apr 20, 2015, at 2:03 PM, Steve Clark wrote: > >Does anyone know where I could find wireshark-1.12.4 el6 rpm? CentOS is not the OS for you if you wish to have the very latest releases of software. The Wireshark project doesn’t provide Linux binaries, apparently since it’s already shipped by most every Linux distro. CentOS 6 ships 1.8.10. If you must have a newer feature than is available in 1.8, you’ll probably have to build it from source. and... if you do build it from source, I'd recommend building and installing it to run in /usr/local/bin or /opt/something, NOT replacing the RPM managed version in /usr/bin ... since wireshark is simply a program, and external stuff should have no dependencies on it, this should be fairly straight forward. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] mediacheck on kickstart
I am using a kickstart centos 1503 file. For some reason I am getting a mediacheck even though I do not have mediacheck in my kickstart file. Any ideas why? Something change on that? Jerry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] wireshark 1.12.4
On Apr 20, 2015, at 2:03 PM, Steve Clark wrote: > > Does anyone know where I could find wireshark-1.12.4 el6 rpm? CentOS is not the OS for you if you wish to have the very latest releases of software. The Wireshark project doesn’t provide Linux binaries, apparently since it’s already shipped by most every Linux distro. CentOS 6 ships 1.8.10. If you must have a newer feature than is available in 1.8, you’ll probably have to build it from source. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] wireshark 1.12.4
Hi, Does anyone know where I could find wireshark-1.12.4 el6 rpm? Thanks, -- Stephen Clark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Laptop for CentOS
On 4/16/2015 2:13 PM, Steve Clark wrote: > On 04/15/2015 12:55 PM, Steve Clark wrote: >> Hello, >> >> Has anyone used the Dell M3800 (ubuntu) laptop to run CentOS 6.x? If so how >> did it work out? >> >> Also does anyone have a fairly new laptop they are running CentOS 6.x on, >> that they are happy >> about? I am in the market for a new laptop and it must run CentOS 6.x. >> >> Thanks, >> > Thanks to all that replied, > > I am leaning towards the Dell M4800 mobile WS, it seems pretty impressive > and can be ordered with Either RHEL 6.4 $$$, or Ubuntu LTS (no $$$) so if I > get > it I will go that route. Only question I still have is whether to go AMD > FirePro 5100 (standard) > or a Nvidia option. > > Any thoughts or experiences. > > Thanks again. > I have the Nvidia one on my M6800, and it works without the nvidia proprietary drivers just fine. -chuck -- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 kworker uses 100% of single core on mulit-core processor usage inquiry
Greetings Johnathan. Thank you for the reply. I have run top, and iftop, etc... The only process that is listed is as follows: Tasks: 272 total, 2 running, 270 sleeping, 0 stopped, 0 zombie %Cpu(s): 7.1 us, 18.3 sy, 0.0 ni, 73.8 id, 0.7 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 32679644 total, 402520 free, 9889728 used, 22387396 buff/cache KiB Swap:0 total,0 free,0 used. 21951812 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 91 root 20 0 0 0 0 R 94.1 0.0 1540:35 kworker/7:1 This is the only worker that is currently taking up 100% of whatever core it is on. (Right now it is assigned core number 8) My kernel is version 3.10.0-229.1.2.el7.x86_64. I don't really have very much context to provide other than it wasn't a problem prior to restarting after I installed the new liquid cooler. If I can provide any further analysis, or information for a more clear view of the issue, then let me know. Thanks for getting back a reply. Respectfully, Martes G Wigglesworth ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS6.6 installation failure
On 04/20/2015 08:48 AM, lheck...@users.sourceforge.net wrote: > >> I would say to eliminate issues, the first thing to make sure is that >> your mailcap package is, indeed, good. > > Summary: it's a good package, but the wrong package for the location. > > I downloaded the package from a different mirror, and the install proceeds > past it. However, now it stops at redhat-logos, with the same error > > An interesting observation: I now have several copies of the mailcap package > on my system. When I compare md5sums, I see this: > > CentOS 6.4 tree: > > 029213d1c7b79c0dfa4f6d8063dbdce6 mailcap-2.1.31-2.el6.noarch.rpm (i386) > 65e231403f819bea3dce22adee5cb373 mailcap-2.1.31-2.el6.noarch.rpm (x86_64) > > CentOS 6.6 tree, where the x86_64 version was replaced with a fresh copy: > > 029213d1c7b79c0dfa4f6d8063dbdce6 mailcap-2.1.31-2.el6.noarch.rpm (i386) > 029213d1c7b79c0dfa4f6d8063dbdce6 mailcap-2.1.31-2.el6.noarch.rpm (x86_64) > 65e231403f819bea3dce22adee5cb373 mailcap-2.1.31-2.el6.noarch.rpm.dist > (previous) > > The packages in 6.4 are different for each arch, but in 6.6 they are the > same. > It appears this relates to how precisely you guys build a distribution? > > IIRC I took a shortcut when upgrading my repositories from 6.x -> 6.x+1 > by pre-populating the directories with the previous version to save some b/w. > This could be the reason for what I see here. > > Now, if there were checksum files for everything, I knew which rpms I need > to download again, but there aren't. Looks like the noarch packages are a > good start, though. All the noarch packages from now on will be the same ... in some of the earlier distros they were not. When you build i386/i686 and x86_64 separately, 2 noarch rpms are produced. It is not that they are significantly different, JUST the signature times were different before as they were signed separately .. but obviously we wanted to only have one package, so we have changed such that there is only one package (and all our metadata is also changed). We also will carry this forward for all versions all the time. Basically, if you remove all noarch files from the tree and rsync, you should be good. Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS6.6 installation failure
> I would say to eliminate issues, the first thing to make sure is that > your mailcap package is, indeed, good. Summary: it's a good package, but the wrong package for the location. I downloaded the package from a different mirror, and the install proceeds past it. However, now it stops at redhat-logos, with the same error An interesting observation: I now have several copies of the mailcap package on my system. When I compare md5sums, I see this: CentOS 6.4 tree: 029213d1c7b79c0dfa4f6d8063dbdce6 mailcap-2.1.31-2.el6.noarch.rpm (i386) 65e231403f819bea3dce22adee5cb373 mailcap-2.1.31-2.el6.noarch.rpm (x86_64) CentOS 6.6 tree, where the x86_64 version was replaced with a fresh copy: 029213d1c7b79c0dfa4f6d8063dbdce6 mailcap-2.1.31-2.el6.noarch.rpm (i386) 029213d1c7b79c0dfa4f6d8063dbdce6 mailcap-2.1.31-2.el6.noarch.rpm (x86_64) 65e231403f819bea3dce22adee5cb373 mailcap-2.1.31-2.el6.noarch.rpm.dist (previous) The packages in 6.4 are different for each arch, but in 6.6 they are the same. It appears this relates to how precisely you guys build a distribution? IIRC I took a shortcut when upgrading my repositories from 6.x -> 6.x+1 by pre-populating the directories with the previous version to save some b/w. This could be the reason for what I see here. Now, if there were checksum files for everything, I knew which rpms I need to download again, but there aren't. Looks like the noarch packages are a good start, though. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 kworker uses 100% of single core on mulit-core processor usage inquiry
On Mon, Apr 20, 2015 at 09:00:07AM -0400, Martes wrote: > Greetings again everyone. > > Can someone please respond to this? You just posted yesterday... Anyway, you didn't give much context. I can see from a google search why you provided the interrupts output, but judging from what you posted, that's not the problem. Perhaps you have a CPU task that's running at 100%? Did you try and run 'top'? Also, what version of CentOS are you running? Are you running the latest kernel? -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 7 kworker uses 100% of single core on mulit-core processor usage inquiry
Greetings again everyone. Can someone please respond to this? I am not sure what is causing this issue, however, others seem to have experienced it in the past. Could this be caused by the processor being damaged? Nothing has changed on the system, except for the heat warning shutoff when the water cooler died, and the system was not restarted until the new one was installed. Any input would be appreciated, however, no response at all is just disappointing. Thanks for any help that can be provided. Respectfully, Martes G Wigglesworth From: "Martes" To: "centos" Sent: Sunday, April 19, 2015 4:46:12 PM Subject: kworker 100% of single core on mulit-core processor usage inquiry Greetings everyone. I am experiencing the kworker issue where a kworker is using 100% of a given core. This behavior was only observed after having installed a new water cooler, to replace a cooler that had died. (Sealed closed loop device from Corsair) The processor is staying around 40 degrees celsius as reported by the MB UEFI interface. (ksysguard shows between 29 degrees and 30 degrees, when running KDE 4) I am unable to isolate a cause, or resolution for getting the kworker usage back to normal. Very basic description of specs are as follows: AMD FX-8350 (not overclocked) 32GB Corsair memory (1866Mhz non-overclocked) Sabortooth 990FX MB I have checked the locations for interrupts which has been indicated online, however, I do not have any specific interrupts that are showing as even having a high integer value to unset. Here is the result of running the referenced command to view interrupts. [sysadmin@imaginationland ~]$ grep . -r /sys/firmware/acpi/interrupts/ /sys/firmware/acpi/interrupts/sci: 0 /sys/firmware/acpi/interrupts/error: 0 /sys/firmware/acpi/interrupts/gpe00: 0 invalid /sys/firmware/acpi/interrupts/gpe01: 0 invalid /sys/firmware/acpi/interrupts/gpe02: 0 invalid /sys/firmware/acpi/interrupts/gpe03: 0 disabled /sys/firmware/acpi/interrupts/gpe04: 0 disabled /sys/firmware/acpi/interrupts/gpe05: 0 enabled /sys/firmware/acpi/interrupts/gpe06: 0 invalid /sys/firmware/acpi/interrupts/gpe07: 0 invalid /sys/firmware/acpi/interrupts/gpe08: 0 invalid /sys/firmware/acpi/interrupts/gpe09: 0 invalid /sys/firmware/acpi/interrupts/gpe10: 0 disabled /sys/firmware/acpi/interrupts/gpe11: 0 disabled /sys/firmware/acpi/interrupts/gpe12: 0 disabled /sys/firmware/acpi/interrupts/gpe13: 0 invalid /sys/firmware/acpi/interrupts/gpe14: 0 invalid /sys/firmware/acpi/interrupts/gpe15: 0 invalid /sys/firmware/acpi/interrupts/gpe16: 0 enabled /sys/firmware/acpi/interrupts/gpe0A: 0 enabled /sys/firmware/acpi/interrupts/gpe17: 0 invalid /sys/firmware/acpi/interrupts/gpe0B: 0 disabled /sys/firmware/acpi/interrupts/gpe18: 0 disabled /sys/firmware/acpi/interrupts/gpe0C: 0 invalid /sys/firmware/acpi/interrupts/gpe19: 0 invalid /sys/firmware/acpi/interrupts/gpe0D: 0 invalid /sys/firmware/acpi/interrupts/gpe0E: 0 invalid /sys/firmware/acpi/interrupts/gpe0F: 0 disabled /sys/firmware/acpi/interrupts/gpe1A: 0 invalid /sys/firmware/acpi/interrupts/gpe1B: 0 disabled /sys/firmware/acpi/interrupts/gpe1C: 0 invalid /sys/firmware/acpi/interrupts/gpe1D: 0 invalid /sys/firmware/acpi/interrupts/gpe1E: 0 invalid /sys/firmware/acpi/interrupts/gpe1F: 0 invalid /sys/firmware/acpi/interrupts/sci_not: 0 /sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid /sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled /sys/firmware/acpi/interrupts/gpe_all: 0 /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled /sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled /sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid Respectfully, Martes G Wigglesworth ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS6.6 installation failure
On 04/20/2015 07:21 AM, lheck...@users.sourceforge.net wrote: > > I have been installing CentOS for years using PXE, kickstart and NFS, but the > procedure fails with CentOS 6.6 for some reason. > > A PXE-initiated, manual install goes through all the setup steps, and once > rpm installation has started, it dies after a few packages: > > anaconda 13.21.229 exception report > Traceback (most recent call first): > File "/usr/lib/anaconda/yuminstall.py", line 1006, in _handleFailure > os.unlink(package.localPkg()) > File "/usr/lib/anaconda/yuminstall.py", line 196, in callback > self.ayum._handleFailure(po, trynumber) > OSError: [Errno 30] Read-only file system: > '/mnt/source/Packages/mailcap-2.1.31-2.el6.noarch.rpm' > > When a kickstart file is used instead, the installation dies at a different > package. > > I have tried providing the OS installation files from different machines, > checked package integrity etc., but cannot figure out what is happening here. > > The anaconda traceback file also has > > 12:19:59,354 WARNING : Failed to get > file:///mnt/source/Packages/mailcap-2.1.31- > 2.el6.noarch.rpm from mirror 1/1, or downloaded file is corrupt > 12:19:59,354 WARNING : package download failure, retrying automatically > > That said, installing 6.4 off the same NFS server works just fine. I would say to eliminate issues, the first thing to make sure is that your mailcap package is, indeed, good. signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS6.6 installation failure
I have been installing CentOS for years using PXE, kickstart and NFS, but the procedure fails with CentOS 6.6 for some reason. A PXE-initiated, manual install goes through all the setup steps, and once rpm installation has started, it dies after a few packages: anaconda 13.21.229 exception report Traceback (most recent call first): File "/usr/lib/anaconda/yuminstall.py", line 1006, in _handleFailure os.unlink(package.localPkg()) File "/usr/lib/anaconda/yuminstall.py", line 196, in callback self.ayum._handleFailure(po, trynumber) OSError: [Errno 30] Read-only file system: '/mnt/source/Packages/mailcap-2.1.31-2.el6.noarch.rpm' When a kickstart file is used instead, the installation dies at a different package. I have tried providing the OS installation files from different machines, checked package integrity etc., but cannot figure out what is happening here. The anaconda traceback file also has 12:19:59,354 WARNING : Failed to get file:///mnt/source/Packages/mailcap-2.1.31- 2.el6.noarch.rpm from mirror 1/1, or downloaded file is corrupt 12:19:59,354 WARNING : package download failure, retrying automatically That said, installing 6.4 off the same NFS server works just fine. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
