Search found 10 matches

by theoriginalguru
2018/10/13 20:03:19
Forum: CentOS 7 - Hardware Support
Topic: need help decoding EDAC memory error messages
Replies: 0
Views: 48

need help decoding EDAC memory error messages

I've spent this past week researching my problem online from various online sources, but I'm not getting consistent information and I'm not confident about what is wrong. These errors are coming from a production machine (not life threatening mission critical, but i do need to minimize downtime), an...
by theoriginalguru
2018/08/26 23:45:55
Forum: CentOS 7 - Software Support
Topic: issues running clamdscan from cron
Replies: 4
Views: 330

Re: issues running clamdscan from cron

tunk wrote:
2018/08/26 23:38:28
I don't know what your problem is, but I think systemd timers are the preferred method.
what do you mean by "systemd timers" ? preferred method for what? please elaborate..
by theoriginalguru
2018/08/21 18:29:30
Forum: CentOS 7 - Software Support
Topic: issues running clamdscan from cron
Replies: 4
Views: 330

issues running clamdscan from cron

I have a CentOS 7.5 system running. I want to setup regular clamdscans on certain file systems. I have clamd running and it appears to all work fine when I run clamdscan manually: # clamdscan -c /etc/clamd.d/scan.conf --fdpass --no-summary --infected --multiscan /data /etc /data/eicar.com: Eicar-Tes...
by theoriginalguru
2018/06/26 22:28:08
Forum: CentOS 7 - Hardware Support
Topic: Blank console output since CentOS 7.5 upgrade?
Replies: 1
Views: 253

Blank console output since CentOS 7.5 upgrade?

I've now encountered 2 machines with this problem since upgrading to 7.5 and booting the latest kernel. I can confirm the problem goes away by booting the last 7.4 kernel 3.10.0-693.21.1.el7.x86_64. Basically, during boot up, the kernel messages do not show after grub (this is without "rhgb" and "qu...
by theoriginalguru
2017/05/10 21:28:36
Forum: CentOS 7 - Security Support
Topic: Getting abnormal SELinux context after chroot install
Replies: 3
Views: 1210

Re: Getting abnormal SELinux context after chroot install

A bit outdated reply (and probably it`s been fixed since) 8-) Probably the relabeling tool used all files in /etc/selinux/targeted/contexts/files/ - while it should have used only file_contexts and file_contexts.homedirs Specifically this error would have showed up if file_contexts.subs_dist would ...
by theoriginalguru
2016/06/28 00:28:18
Forum: CentOS 7 - General Support
Topic: where can i find the programs/scripts that run in rescue mode?
Replies: 0
Views: 848

where can i find the programs/scripts that run in rescue mode?

Hello, I need to understand in detail how the rescue mode works on CentOS 7. In particular, when you boot in rescue mode of the ISO image, there is an option to automatically detect your system and mount it under /mnt/sysimage in the rescue environment. I need to know exactly what this option (#1) d...
by theoriginalguru
2016/06/22 17:58:50
Forum: CentOS 7 - Security Support
Topic: Getting abnormal SELinux context after chroot install
Replies: 3
Views: 1210

Getting abnormal SELinux context after chroot install

I'm installing CentOS 7 in a chroot'd environment to build new images of CentOS 7 for a private cloud environment. I've done this successfully before with CentOS 6 and we have an automated process of doing that now. I'm now porting our process to do similarly for CentOS 7. However, after our process...
by theoriginalguru
2009/04/10 09:19:59
Forum: CentOS 5 - General Support
Topic: XFS Root Filesystem corrupt after 5.3 upgrade
Replies: 4
Views: 1019

Re: XFS Root Filesystem corrupt after 5.3 upgrade

maybe this is related too?

http://bugs.centos.org/view.php?id=3485

Looks like this patch might fix it?

http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs.git;a=commitdiff;h=e5889e90dda328443161e9512f1123c9814d03de;hp=7666ab5fb378678a9d5eb3c0dc8d3170e274e7a4
by theoriginalguru
2009/04/10 08:18:05
Forum: CentOS 5 - General Support
Topic: XFS Root Filesystem corrupt after 5.3 upgrade
Replies: 4
Views: 1019

Re: XFS Root Filesystem corrupt after 5.3 upgrade

that error message sounds eerily familiar. Fedora 8 had a similar issue a little over 1 year ago, when some patch to the kernel affected the XFS driver, causing it to corrupt XFS filesystems. Upon reboot, you would see "attempt to access beyond end of device" error messages. The XFS problem was late...