Discuss March 2014

discuss@lists.centos.org

167 participants
144 discussions

Chromium 31.0.1650.63-2.el6 for CentOS 6
by Johnny Hughes 04 Apr '14

04 Apr '14

All, As has already been brought up, we have not yet been able to build the new version of Chromium-32 for CentOS, and the current version (31.0.1650.63-1.el6) needs updating. We have also recently been informed that we may not redistribute the PepperFlash Library from the Google site (libpepflashplayer.so) as we did in 31.0.1650.63-1.el6. Therefore, I have had to rebuild the currently released version to remove the libpepflashplayer.so library. What this means for all Chromium users is that after upgrade, you will no longer have built in flash. I apologize for the inconvenience, but we have no real choice in the matter. While the CentOS team can not redistribute that library, end users can still get it ... here is how: 1. Become root and create a temporary working directory to download the package .. I recommend /tmp/working/ mkdir /tmp/working/ cd /tmp/working/ 2. Get the latest google chrome rpm from google for your arch (either x86_64 or i386): wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm (or if needing the 32bit version, substitute i386 for x86_64 in the above path) 3. Extract the RPM using this command: rpm2cpio google-chrome-stable_current_x86_64.rpm | cpio -idv (again, substitute i386 for x86_64 if required) 4. Create the PepperFlash directory where the library will live: mkdir /opt/chromium-browser/PepperFlash/ 5. Copy the chome PepperFlash library and json file to the new directory: cp opt/google/chrome/PepperFlash/* /opt/chromium-browser/PepperFlash/ 6. Restart chromium and test that flash works. Thanks, Johnny Hughes

9 17

Booting OpenBSD with pxelinux
by Paul Heinlein 02 Apr '14

02 Apr '14

I've got PXE/TFTP setup for various Linux distributions and some utilities (clonezilla, dban, etc). I'm now starting in on OpenBSD. As far as I've been able to figure out via internet searches, pxelinux (from the syslinux package) is unable to pass control of a machine directly to a BSD kernel. Instead, you have to use the BSD-supplied 'pxeboot' loader. The naming conventions enforced by pxelinux mean that pxeboot must be called pxeboot.0. Here's a simplified view of my tftpboot directory: etc/ `-- boot.conf images/openbsd/ `-- 5.4 | -- amd64 | | -- bsd | `-- pxeboot.0 `-- i386 | -- bsd `-- pxeboot.0 And here's a relevent snippet of my PXE menu file: LABEL openbsd-5.4.amd64 MENU LABEL OpenBSD 5.4 amd64 KERNEL images/openbsd/5.4/amd64/pxeboot.0 So far so good. If I boot the image listed above, I get the BSD boot loader -- but, and this is the crux of my question, afaict I have to type the location of the actual kernel manually: boot> boot images/openbsd/5.4/amd64/bsd After I type that, the OpenBSD installation kernel boots without a hitch. But manually typing the kernel path is prone to error, and it's not scriptable. It appears that you can have one (and only one!) boot.conf file from which pxeboot can get some directions. Since I want to be able to serve up at least two different images (32- and 64-bits), I can't specify a kernel in boot.conf. The best I can do is print a banner, e.g., echo ********************************************************** echo The OpenBSD pxeboot utility cannot be passed an alterative echo kernel path. So you'll have to issue one of the following echo commands manually from the boot> prompt: echo echo boot images/openbsd/5.4/amd64/bsd echo boot images/openbsd/5.4/i386/bsd echo ********************************************************** My question: Does anyone else know a better way? Can I pass an alternative kernel path or boot.conf to pxeboot? -- Paul Heinlein heinlein(a)madboa.com 45°38' N, 122°6' W

2 1

CENTOS 6.5 NO syslog.conf file. How to fix?
by mcclnx mcc 01 Apr '14

01 Apr '14

We just install Centos 6.5 as an ORACLE server. We found /etc/syslog.conf file is gone. Some of our applications used to setup on CENTOS 5.X /etc/syslog.conf are not work. Can anyone tell me how to fix Centos 6.X no /etc/syslog.conf issue? Thanks.

4 3

about new Centos SIG distro releases
by Edward M 31 Mar '14

31 Mar '14

Hello, Kinda confused, will CentOS new SIGs: CentOS Storage, CentOS Cloud, and CentOS Virtualization, CentOS Core,etc be a developmental path to future RHEL releases, or will they continue be an exact clone of RHEL, like Centos currently is? http://www.zdnet.com/red-hat-reveals-centos-plans-7000027812/

5 11

Centos and Selinux issue
by Alessandro Baggi 31 Mar '14

31 Mar '14

Hi list, I'm new to Centos and I've a very small knowledge of selinux use. I can disable it, but I prefer take it on for study. I've a second mirrored device that I use for file sharing. This is the scenario: /dev/md2 mounted on /mnt/data To make samba working I must set the file context to the path at samba_share_t on /mnt/data. After this samba works. Now I'm setting up postgresql on the same machine, and for first disk size I must use /dev/md2. After configuring postgresql script to init the db, and setting up the alternative data path pointing to /mnt/data/pgsql/data, initdb or start postgresql fail. This issue is selinux related. Now, directory /mnt/data/pgsql/data, has fcontext to samba_share_t and postgresql init script give permission denied on /mnt/data/pgsql/data/postgresql.conf. At this point I've tried to set with chcon /mnt/data at postgresql_db_t, rerun initdb and /etc/init.d/postgresql start and all works fine, except for samba. I can't access anymore the share (for context change). I've tried to set: /mnt/data to samba_share_t /mnt/data/pgsql to postgresql_db_t but with this config is pgsql that does not work. At this point, is possible set to /mnt/data a multiple context to make samba and postgresql to get working on the same path, or I must use "public....." It's a better choice mount /dev/md2 on /mnt/data, make to dirs, one for pgsql and another for sambashare, set relative context and start services? Thanks in advance. Alessandro.

3 2

Supervise Directory With TRIPWIRE
by Rodrigo Pichiñual Norin 31 Mar '14

31 Mar '14

Hi all I have a question, I need supervise a directory of apache on centos The directory it is: /var/www/html/application/........ But I not know if this it is possible... Tripwire Can supervise the directory and all files within ????? this it is possible mofidy the policies for default??? Thank

2 1

Re: [CentOS] Centos and Selinux issue
by m.roth＠5-cent.us 31 Mar '14

31 Mar '14

Alessandro Baggi wrote: > Hi list, > I'm new to Centos and I've a very small knowledge of selinux use. > > I can disable it, but I prefer take it on for study. Ok, first thing you want to do is set it to permissive mode (setenforce 0, and edit /etc/selinux/config to Permissive from Enforcing). That way, you'll get all the alerts and, of course, denials... but it will let it operate. Second: chcon is fine for setting user_u. Maybe role. DON'T USE IT unless you *must* for types. The reason for that is that it does NOT last across reboots. Use semanage (file that under user surly, at the very least). Read the manpage for that, and look at the examples. Nasty gotchas that I've had to fight through: a) it's *not* the wildcards I'm used to. To get a directory and its contents, give the *FULL* pathname, then end as the example: semanage fcontext -a -t whatsit_t "/mnt/what/dunno(/.*)?" Notes: the -a says add this context. if it's got a wildcard, USE THE QUOTES around the path. If it's just one file, you don't need the quotes, but use the *full* path. Selinux does not play with relative paths. b) assuming you get past that, then run restorecon -R -v - /path -R is recursive, and -v is verbose, so you *see* it doing what you expect it to do (or not). To your specific issue, /mnt is, I believe, not one of their paths that the policy knows what to do with, so you'll have to label it all. For things that policy doesn't know, and relabelling still didn't fix the problem, you'll need to create a policy (but be *VERY* chary about that). Make sure auditd is running, and that setroubleshoot is installed. Trying to read the AVC's tends to be a study in frustration. The sealerts that will show up in messages will *usually* be more helpful (unless your users or organization are doing stuff that's not what everyone else does (like not having your website stuff under /var/www). Last detail: subscribe <selinux(a)lists.fedoraproject.org> <SNIP> mark "no, I don't like selinux, but I'm stuck having to live with it, even though we mostly have it in permissive mode"

1 0

vncserver does not start gnome-sessioin automatically
by Yawei Guo 31 Mar '14

31 Mar '14

I installed RHEL 5.8 x86_64 today. To my surprise, when I connect it using vnc viewer it does not start gnome-session automatically. The last line in .vnc/xstartup is twm& Before I removed RHEL 6.1 a few days ago, vncserver always starts gnome-session every time I open vncviewer. Is that related to RHEL version or vnc-server version? Best Regards, Yawei

2 7

The repodata directory is currently broken on several, if not all, mirrors for the 6.5 iso files
by jshields＠hostgator.com 31 Mar '14

31 Mar '14

The repodata directory on all 6.5 isos that I have sampled have an issue where the file names don't have extensions resulting in a yum repo error on installation just after disk partitioning. This error prompts you with the choice between either allowing you choose another repo or to exit the installer. I remedied this issue with the following: [root@testserv /root/test/centos]$ find repodata/ -type f -not -name repomd.xml -exec sh -c 'mv {} -v $(grep -Po "(?<=href=\")({}.*?)(?=\"/>)" repodata/repomd.xml)' \; ‘repodata/b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632’ -> ‘repodata/b4e0b9342ef85d3059ff095fa7f140f654c2cb492837de689a58c581207d9632-c6-x86_64-comps.xml’ ‘repodata/5af8199bd0ffb441c34ef946582d0d06c1ad770755e631690771e0bceb0ad222’ -> ‘repodata/5af8199bd0ffb441c34ef946582d0d06c1ad770755e631690771e0bceb0ad222-other.xml.gz’ ‘repodata/594d4bb4a79ed01d66635adbcf76c45ca4a85b30fc3e3c3c28316e64f0a83f21’ -> ‘repodata/594d4bb4a79ed01d66635adbcf76c45ca4a85b30fc3e3c3c28316e64f0a83f21-filelists.sqlite.bz2’ ‘repodata/6ac72f497df511cc2dc584eaa59779884fc572c1618e7c62dbd631ab8babf53d’ -> ‘repodata/6ac72f497df511cc2dc584eaa59779884fc572c1618e7c62dbd631ab8babf53d-filelists.xml.gz’ ‘repodata/0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c’ -> ‘repodata/0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c-primary.sqlite.bz2’ ‘repodata/ca525c73086186bfcb81ad9edd45796026dac7e4e50524e0f2daf901532aaf66’ -> ‘repodata/ca525c73086186bfcb81ad9edd45796026dac7e4e50524e0f2daf901532aaf66-c6-x86_64-comps.xml.gz’ ‘repodata/fdd542ef36b0cde54ee0521fae90b98911db06483163aa1c049995b6d109349b’ -> ‘repodata/fdd542ef36b0cde54ee0521fae90b98911db06483163aa1c049995b6d109349b-other.sqlite.bz2’ ‘repodata/495d3964f864fbab835ea1afb8a5272352cd12ded13d607205109fefaddd0ab6’ -> ‘repodata/495d3964f864fbab835ea1afb8a5272352cd12ded13d607205109fefaddd0ab6-primary.xml.gz’ The repomd.xml file has the correct names for the files, the files in this directory just have the sha sums as their file names, not the full path name as defined in the xml file. This results in yum breaking just after partitioning. The only way I was able to get around this before modifying the iso file was to follow the onscreen prompt and enter in a valid mirror as an HTTP/FTP host. This issue is currently afflicting all variants of 6.5. As of this writing the two test files I just confirmed have this issue are: http://mirror.cisp.com/CentOS/6.5/isos/x86_64/CentOS-6.5-x86_64-minimal.iso http://mirrors.bluehost.com/centos/6.5/isos/x86_64/CentOS-6.5-x86_64-minima… Last night I downloaded the minimal, livecd, livedvd and netinstall isos from 10+ mirrors. All of them triggered the error from the files not being named correctly. --Shields

4 3

rsyslog not loading relp
by Mauricio Tavares 31 Mar '14

31 Mar '14

centos 6.4, setup to be syslog server. Doing remote syslog using tcp works fine, so now want to add relp. I installed the rsyslog-relp package and told rsyslog.conf to use it: # RELP Syslog Server: $ModLoad imrelp # provides RELP syslog reception $InputRELPServerRun 20514 when I restart rsyslog I am told it does not like my InputRELPServerRun line: Oct 28 13:43:54 scan rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="7102" x-info="http://www.rsyslog.com"] start Oct 28 13:43:54 scan rsyslogd: the last error occured in /etc/rsyslog.conf, line 23:"$InputRELPServerRun 20514" Any clues?

5 17

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss March 2014