Discuss September 2015

discuss@lists.centos.org

136 participants
130 discussions

php DOMDocument and entities
by Alice Wonder 24 Sep '15

24 Sep '15

This is not CentOS specific but I hope someone here knows so I do not have to subscribe to another list. I'm using php DOMDocument to create an XSL that needs a non-breaking space between two values. Basically: $xslvalueof = $dom->createElement('xsl:value-of'); $xslvalueof->setAttribute('select', '../@month'); $caption->appendChild($xslvalueof); $nbsp = $dom->createTextNode(' '); $caption->appendChild($nbsp); $xslvalueof = $dom->createElement('xsl:value-of'); $xslvalueof->setAttribute('select', '../@year'); $caption->appendChild($xslvalueof); That's what I am trying to do. createTextNode() however tries to protect the users, and automatically turns any & into & So I tried $nbsp = $dom->createEntityReference('#160'); That however gives a dom error, it seems createEntityReference only works with named entities. $nbsp = $dom->createEntityReference('nbsp'); works, but then I would have to modify the DTD for both XSL and the target XML because neither have nbsp defined. How can I create the literal string ' ' using DOMDocument as a text node between two other nodes? This is driving me nuts. I could I suppose put it inside a span &nbsp = $dom->createElement('span', ' '); That works but is hackish. It seems to work though by generating the actual UTF8 character itself. I really wish the XML spec itself had named entities for the various whitespace characters that tend to get eaten by XML parsers if not done as a numbered entity. Ah well. Using   works just fine when the XSL is a text file. It is dynamically creating it via DOMDocument where I have a problem. Thanks for any suggestions. -- -=- Sent my from my laptop, may not be able to respond timely

1 0

Bug in init scripts for ipset?
by tony＠softins.co.uk 24 Sep '15

24 Sep '15

I've just started experimenting with ipset under CentOS 6, and have found what appears to be a bug (or poor design) in the init scripts for ipset, /etc/rc.d/init.d/ipset In stop(), save() and status(), it does lsmod to check for the existence of the ip_set module. If the module is not found, it exits without performing any action. This doesn't take account of a kernel where the ip_set code is compiled in instead of being a loadable module. An example would be my CentOS 6 virtual machine at Linode. It has a Linode-compiled kernel 4.1.0 with no separately-loaded modules. It certainly supports ipset, as I have successfully tried some test rules. However, I wondered why giving the command "service ipset save" didn't result in /etc/sysconfig/ipset being written, and discovered the cause I described above. Surely there should be a better way of determining whether the kernel includes ipset support than just looking for a module? Cheers Tony -- Tony Mountifield Work: tony(a)softins.co.uk - http://www.softins.co.uk Play: tony(a)mountifield.org - http://tony.mountifield.org

2 1

Logrotate problems
by Andrew Holway 24 Sep '15

24 Sep '15

Hi Y'all, We have nginx set up and we are having problems with logrotate. The permissions and users do not seem to be any different from other machines that are working ok however the /var/log/nginx does have a directory in there that we are using to collect some special log stuff. Could this subdirectory be interfering with the logrotate process? ta Andrew [root@ ~]# logrotate -d /etc/logrotate.d/nginx reading config file /etc/logrotate.d/nginx Handling 1 logs rotating pattern: /var/log/nginx/*log after 1 days (10 rotations) empty log files are not rotated, old logs are removed considering log /var/log/nginx/access.log error: skipping "/var/log/nginx/access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. considering log /var/log/nginx/error.log error: skipping "/var/log/nginx/error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.

2 5

decode http hack attempt?
by James B. Byrne 24 Sep '15

24 Sep '15

Can anyone de-cypher the second entry for me? --------------------- httpd Begin ------------------------ Requests with error response codes 403 Forbidden /: 9 Time(s) /?c=4e5e5d7364f443e28fbf0d3ae744a59a: 3 Time(s) I have found the string via Google but have not located any explanation. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

3 2

amanda-client does not recognise 'dump'
by Tom Robinson 24 Sep '15

24 Sep '15

CentOS Linux release 7.1.1503 (Core) amanda-3.3.3-13.el7.x86_64 amanda-client-3.3.3-13.el7.x86_64 amanda-libs-3.3.3-13.el7.x86_64 dump-0.4-0.22.b44.el7.x86_64 Hi, I have been using amanda backup for quite a long time now. I'm busy migrating some older hosts to CentOS 7 but have found that the available amanda packages (see above) have not been compiled on a host that has the 'dump' program installed. Is this just an oversight or are we trying to not use 'dump' anymore? If the former, who is responsible for re-compiling this on a host that has 'dump' installed. Please see http://archives.zmanda.com/amanda-archives/viewtopic.php?t=7390 for more details Kind regards, Tom -- Tom Robinson IT Manager/System Administrator MoTeC Pty Ltd 121 Merrindale Drive Croydon South 3136 Victoria Australia T: +61 3 9761 5050 F: +61 3 9761 5051 E: tom.robinson(a)motec.com.au

2 1

Help with systemd
by Clint Dilks 24 Sep '15

24 Sep '15

Hi I am trying to get Greenstone3 http://www.greenstone.org/download to work with systemd. So far I have come up with the following which works but feels more like a hack than a solution. Does anyone have any suggestions on how to do this better ? # cat /etc/tmpfiles.d/greenstone3.conf d /run/greenstone3 0755 gs3 gs3 - # cat /etc/systemd/system/greenstone3.service # Systemd unit file for Greenstone 3 [Unit] Description=Greenstone 3 Server After=syslog.target network.target [Service] Type=forking PIDFile=/run/greenstone3/greenstone3.pid Environment=PATH=/usr/apache-ant-1.9.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin ExecStart=/usr/bin/bash -c "cd /greenstone/gs3/ && ant start ; /usr/sbin/pidof java | awk '{print $1}' > /run/greenstone3/greenstone3.pid" SuccessExitStatus=143 User=gs3 Group=gs3 [Install] WantedBy=multi-user.target Thanks

4 6

ISC DHCP failover
by Chris Adams 24 Sep '15

24 Sep '15

Anybody have any experience with setting up dhcpd in failover mode between two servers? I set this up on a couple of servers, and it seems to be working, but I don't think it is working "right". It appears both servers are replying to all requests (which for renewals works okay because they both give the same address, but new requests get two different responses). I thought that only one server would reply to a particular request. Also, every DHCPACK is followed by a message like this in the log: Sep 23 15:45:50 rad2 dhcpd: bind update on x.x.x.x from mypeer rejected: incoming update is less critical than outgoing update Any ideas? I subscribed and asked over on the ISC-operated dhcp-users list but haven't had any responses. Google finds others asking about the same log message, and the only responses seem to be "well, if you get it for every update, there's probably some configuration issue" (but nobody ever says what issue might lead to it). -- Chris Adams <linux(a)cmadams.net>

4 3

Updating intel graphics driver on CentOS7
by C. L. Martinez 23 Sep '15

23 Sep '15

Hi all, Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe with elrepo's packages: http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-… It seems it doesn't exists driver in the upstream: https://01.org/linuxgraphics Thanks,

4 5

Re: [CentOS] OT: closing a port on home router
by James B. Byrne 23 Sep '15

23 Sep '15

On Wed, September 23, 2015 00:11, Always Learning wrote: > > > That is great. When I started on Linux that was one of the very > first things I did. Every machine, including servers, has port 22 > replaced by a unique alternative port. Port 22 is also blocked in > IPtables. > > There is an army of dangerous nutters attempting to break-in to > everything. They often mask their attacks using compromised Windoze > computers all around the world. > Changing the port that sshd listens on solves nothing from a security perspective. The only people that this action deflects are the script-kiddies. Who are admittedly numerous and who can be dangerous but usually are just low-talent opportunists. Moving the port by itself still opens a functioning connection to the internet on a service that is inherently susceptible to brute force and rainbow attacks. The 'dangerous' people on the Internet will find this port in a heartbeat and they are far more worrisome than the script-kiddies. Since you absolutely must build a defence against these opponents anyway then you might as well leave the service on the default port to avoid screwing up legitimate users expectations. I grant that dealing with an excessive logfile volume can be a consideration. However, this issue is often best dealt with through scripting your own analysis and reporting programs or employing someone else's. And is often solved with an aggressive set of firewall rules. In fact, the volume of entries should be a good indication of how well your defence is serving you. As you tighten the access rules and dynamically block persistent abusers then the volumes should drop and stay fairly low. Moving the port by itself is like rearranging the deck chairs on a sinking ship. It does not address the fundamental issue. Plus assignment to a non-standard port adds to maintenance and support load since it must be separately accounted for each time it is referenced. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Update from 6.6 to 6.7 > automount logs error message
by Ralf Aumüller 23 Sep '15

23 Sep '15

Hello, after an update from 6.6 to 6.7 the following error message is logged to /var/log/messages when I login (per ssh): Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get passwd info from getpwuid_r Checked all log-files of my systems running 6.6 with same configuration -- never got such a message (We use NFS/autofs for home-directories, NIS and tcsh (login shell)). Everything seems to work -- but before I update all machines to 6.7 I want to know whats going on. Any comments? Best regards, Ralf

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss September 2015