Discuss April 2017

discuss@lists.centos.org

114 participants
91 discussions

can't create printers after upgrading cups
by Vanhorn, Mike 26 Apr '17

26 Apr '17

After upgrading cups on my CentOS 6 systems from version 1.4.2-72.el6 to 1.4.2-77.el6, I am no longer able to create working printers, either with lpadmin from the command line or with system-config-printer. When I try to run lpadmin, I get this simple error: [root@vlsi66 ~]# lpadmin -p newprinter -v lpd://printserver/serverqueue-E -P /path/to/ppd/thing.ppd lpadmin: Unknown [root@vlsi66 ~]# Sometimes, the printer does get created (i.e. it shows up in the output of ‘lpstat –a’ and printers.conf gets updated), but sometimes it doesn’t. If the printer does get created, then there is no new ppd in /etc/cups/ppd. If I try to create the printer using system-config-printer, I get an error of CUPS server error (adding printer newprinter) There was an error during the CUPS operation: ‘server-error-service-unavailable’. I’ve looked at file and directory permissions, and checked that cupsd is, in fact, running. There is nothing obvious in the logs, except for this, which happens at exactly the time the printer should get created: localhost - - [26/Apr/2017:09:34:01 -0400] "POST /admin/ HTTP/1.1" 401 0 - - This also occurs if I access localhost:631 from a web browser; and everything works fine up to the point of “Add Printer”, and then the web page shows and Error: box with “Unknown” (from the lpadmin command), and the 401 error shows up in the log. I can’t figure out why it would be a 401 (unauthorized), since everything else worked. Has anyone else run into this problem, where you can’t create a new printer? Thanks! --- Mike VanHorn Senior Computer Systems Administrator College of Engineering and Computer Science Wright State University 265 Russ Engineering Center 937-775-5157 michael.vanhorn(a)wright.edu

1 0

rsyslog and zipping up "rotated" files
by Ian Diddams 26 Apr '17

26 Apr '17

I have a rsyslog config that suffixes the date to the filename and holds the log files in a non stabdard log directory based on its srver name (long story). Example - config includes: ... $template mailLog,"/var/log/external/%fromhost%/maillog-%$YEAR%%$MONTH%%$DAY%.log"... # Log all the mail messages in one place.mail.* -?mailLog... so that I get over time .. /var/log/external/server/maillog-20170424.log /var/log/external/server/maillog-20170425.log /var/log/external/server/maillog-20170426.log etc. Over time of course these build up, so i have a cronjob to trim any such logs okder than 30 days. To also save on space I copmpress all the files except todays via a cronjobbed script. so in fact I get ... /var/log/external/server/maillog-20170424.log.gz /var/log/external/server/maillog-20170425.log.gz /var/log/external/server/maillog-20170426.log My questions are therefore... - is there a way for rsyslog to compress these logs once a new log is created at midnight - is theer a way for rsyslog to remove any logs older than 30 days? I am of course aware that logrotate does this also, but for the purposes of m,y enquiry I am only interested in using rsyslog if at all possible. I expect the removing of older, zipped logs via rsyslog isn;t available. But the pssibility of zipping files would be of great interest. cheers Ian

1 0

saslauth logging
by Jobst Schmalenbach 26 Apr '17

26 Apr '17

Hi Not sure whether this is the correct list to ask ... if it's not please direct me to the correct one. Is it possible on to log a bit more detail when auth failure occurs when using saslauthd? saslauthd[2119]: do_auth : auth failure: [user=DELETED] [service=smtp] [realm=DELETED] [mech=pam] [reason=PAM auth error] What I want is the IP address and if possible the incorrect password (just to see how far they are off). Is this possible? thanks Jobst -- If a pig loses its voice, is it disgruntled? | |0| | Jobst Schmalenbach | | |0| jobst(a)barrett.com.au |0|0|0| General Manager

4 6

kde panels not retaining launcher icon
by geo.inbox.ignored 26 Apr '17

26 Apr '17

greetings one and all. new install of centos 6.8. 3 kde panels @ left, top, right sides. left and top panel are for program selection. right panel for active running programs. added 'launcher' icons to left and top panels, but panels are not retaining launcher icons. when i close kde to save ~/.kde file and reopen kde, 1, 2, or all 3 panels will be missing launcher. has anyone else seen such or know of cure? much help appreciated. tia. -- The important thing is not to stop questioning. - Albert Einstein CentOS GNU/Linux 6.8 -- KDE 4.3.4 Firefox 45.7.0 -- Thunderbird 45.6.0 GNUCash 2.4.15 -- zoneminder 1.30.0 peace out. tc,hago. g . =+= Tired of having your microsoft os hacked? Change to Linux os, used by microsoft hackers. =+= in a world with out fences, who needs gates. =+=

1 0

Odd disk automount issue on C7.3.1611
by Lamar Owen 25 Apr '17

25 Apr '17

I'm posting here before going through all the fun to do up a real bug report to see if anyone else has seen this behavior. I have two identical Dynex external USB3 drive enclosures with identical 3TB drives in each enclosure. The dmesg output shows: $ dmesg |grep TOSHIBA [ 59.942546] scsi 7:0:0:0: Direct-Access TOSHIBA DT01ACA300 PQ: 0 ANSI: 6 [ 86.301123] scsi 8:0:0:0: Direct-Access TOSHIBA DT01ACA300 PQ: 0 ANSI: 6 $ HOWEVER, the 'Disks' utility program only sees the first one plugged-in, and not the second one. It doesn't matter which one I plug in first; the second one won't get seen by Disks nor will it get automounted. It doesn't even do the 'USB device inserted' sound, for that matter. As another oddity, one of the drives has a LUKS-encrypted ext4 filesystem; the other has an XFS filesystem; if I plug in the XFS-formatted drive first, the LUKS-encrypted on will no longer automount even if the XFS-formatted drive is unmounted and unplugged first, but the the converse does work (mount LUKS+ext4; unmount and unplug; plug in XFS, it gets automounted). If I plug in the LUKS+ext4 disk first, enter the passphrase, and let it mount, then plug in the XFS drive, I can then manually (from the command line) mount it just fine and both drives work just fine. Both drives work fine when used singly, but not when both are plugged-in. So, has anyone else seen this? I don't mind filing a bug report, but I am at a bit of a loss as to what component to file it under. I haven't dug into too many logs or other files as yet, but I can if I need to do so. I ran into this making an encrypted copy of the contents of the XFS disk, which will be wiped and reformated LUKS+ext4, and I'd like to make these two drives back each other up. If I plug in a different USB3 drive, such as my 4TB Seagate, everything works as expected; it seems to only be the identical drives that confuse whatever process is detecting this. -- Lamar Owen Chief Information Officer Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 828-862-5554 www.pari.edu

1 0

Bonding mode balance-alb (6): How to control the assigned MAC address?
by Frank Thommen 25 Apr '17

25 Apr '17

Hi, we are trying to switch our bonding modes from 1 (active-backup) to 6 (balance-alb). However it seems, that these bond devices are not always getting the MAC address from the same slave. Sometimes the device gets the MAC address of the first and sometimes of the second slave. Since only the MAC address of the first slave device is (can be) registered in DHCP, this breaks connectivity (about) every second time we boot the computer. Is there a way to control which MAC address is assigned to the bonding device w/o configuring it explicitely in the ifcfg file? Cheers frank

2 1

systemd override.conf question
by Robert Moskowitz 24 Apr '17

24 Apr '17

Does the override.conf file need the section headers? For example: # cat /etc/systemd/system/postfix.service.d/override.conf [Unit] After=syslog.target network.target time-sync.target Will it work with just the After line, or is the [Unit] line needed to control the merge function. thanks

2 2

Re: [CentOS] OT: systemd Poll - So Long, and Thanks for All the fish.
by James B. Byrne 24 Apr '17

24 Apr '17

On Wed, April 19, 2017 16:22, Chris Murphy wrote: > > Apple has had massively disruptive changes on OS X and iOS. Windows > has had a fairly disruptive set of changes in Windows 10. About the > only things that don't change are industrial OS's. > I have no idea how this reference applies to my earlier post. We do not use Apple or Windows servers and the desktop environment is stabilised at Win7pro. There will be be no Windows 10 here ever. OSX / iOS employment is limited to personal devices, none of which are permitted on premise in any case. > When it comes to breaking user space, there's explicit rules against > that in Linux kernel development. And internally consistent API/ABI > stability is something you're getting in CentOS/RHEL kernels, it's one > of the points the distributions exist. But the idea that Windows and > OS X have better overall API stability I think is untrue, having > spoken to a very wide assortment of developers who build primarily > user space apps. This may be true. It is likely important to software developers. It is also totally irrelevant to a business. Businesses, other than software development houses and consultants, are software users. When a vendor massively rearranges things in their software, deprecates scripting syntax that has existed for years if not decades, and fundamentally changes the way the administration of an operating system is presented it really matter not a wit to a business that the internal kernel level api remains unchanged. It is the accumulated administrative experience that is lost in consequence that concerns a business given that replacing that loss will cost either directly in retraining or indirectly in error and resultant disruption; or both. > > What does happen, in kernel ABI changes can break your driver, as > there's no upstream promise for ABI compatibility within the kernel > itself. The effect of this is very real on say, Android, and might be > one of the reasons for Google's Fuscia project which puts most of the > drivers, including video drivers, into user space. And Microsoft also > rarely changes things in their kernel, so again drivers tend to not > break. > > And this illustrates the point that I attempting to make. A business owner assumes that whatever OS is used it will deal with the various devices that make up its hardware environment. For if it does not then they seek an OS that does. However, vanishingly few firms in my experience (i.e.NONE) have ever had operational programming staff write or even modify a device driver. A business is in existence to make money for its owners not dick around with esoteric computer theory and practice. Red Hat, again in my sole opinion, increasingly appears to me to be emulating another company notorious for shuffling the user interface to little evident purpose other than profit. That is good business for them. It is not good for us. Bear in mind that we have been RedHat/Whitebox/CA-OS/CentOS users since 1998 so it is not like we are moving away from Linux with anything like enthusiasm. But this upgrade treadmill that has developed within RH is simply too costly for us to bear any longer. The idea that one has to rebuild from scratch entire host systems and then laboriously port over data and customised portions to a new host simply to upgrade the underlying OS is absolutely ludicrous. Consider the tremendous labour costs regularly incurred in accomplishing what amounts to maintaining the status quo. We just upgraded a FreeBSD host from 10.3 to 11.0 in situ without problem; and with very little downtime (three reboots in the space of 30 minutes). This was no standalone device either. It was the OS running the metal for multiple BHyve virtual machines, themselves running various operating systems (but mainly FreeBSD-11). One of said vms being our Samba-4 AD-DC. And, had it all gone south then, given we use ZFS in FreeBSD, and that we snapshot regularly, getting back to 10.3 would have been, and still could be, nearly instantaneous. Think about what that would take in terms of man hours to accomplish moving from EL6 to 7. And moving from 5 to 6 was not much better. This is just too expensive to repeat every three years. And allow me to forestall any claims that the chimera that is 'cloud computing' is the answer. All that does is make creating the requisite new platforms marginally less tedious. And that small advantage is purchased at the cost of handling over control of all your data to entities who are thoroughly discredited with respect to security and privacy. I am not anti or pro systemd, upstart, or etc/rc (or any other software although I admit to holding a generally dim view of things from Redmond). I do not really care what is used so long as it works and that introducing it does not greatly diminish the value of existing user skills and knowledge. However, I am past the point of patience with gratuitous changes that offer no appreciable benefit to the parties tasked with dealing them. Systemd is not the problem. It is a symptom of a deeper malaise, indifference. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by 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

6 7

How to PXE kickstart hosts with little memory (Error: "Warning: /dev/root does not exist")?
by Frank Thommen 24 Apr '17

24 Apr '17

Hi, while kickstarting our virtual machines with PXE we often run into kickstart/anaconda failing with [...] [...] dracut-mount[xxx]: Warning: Can't mount root filesystem [...] dracut-mount[xxx]: Warning: /dev/root does not exist [...] dracut-mount[xxx]:/lib/dracut-lib.sh: line 1030: echo write error: No space left on device Starting Dracut Emergency Shell... Warning: /dev/root does not exist Generating "/run/initramfs/rsdosreport.txt" [...] It seems, that this is not related to local disk space - as I initally thought - but to too small memory. It only happens with VMs with little RAM (1024 MB). As soon as we raise the available memory to 2048 MB, kickstarting works fine. The RHEL 7 installation guide states, that the minimal memory requirement is 1 GB, so the network installation /should/ work. Is there a way to install such hosts w/o having to temporarily raise the available memory? Cheers frank

2 2

Need a bit of 'archeocomputing' help on CentOS 7.
by Lamar Owen 24 Apr '17

24 Apr '17

I have an application with is binary-only, does its job well, and is only available for either libc5 (!) or early early glibc2.0 (!!). It has been running on a Red Hat Linux 5.2 (NOT RHEL; RHL) server for a really long time, and it honestly does its job and it's not easily replaced by an open-source solution at the moment. So, I need to do one of the following things: 1.) Run Red Hat Linux 5.2 (or similar vintage) on KVM on CentOS 7; 2.) Build libc5 (!) for CentOS 7 and run it on C7 (if that's even possible). The latest version of libc5 I know of that was shipped by Red Hat is in RHL 6.2, libc-5.3.12. (There is a 5.4, but not sure of stability or compatibility). So, I have RHL 5.2 (Apollo) running on KVM on C7, but I'm not getting any networking working. The only two non-virtio NICs are e1000 and rtl8139. As I recall kernel 2.0.36 and rtl8139 were pretty iffy together, and e1000 drivers are not likely available (I couldn't find any). The host's bridge sees the MAC of the guest, but the guest isn't seeing any traffic. So, has anyone tried doing anything this old with modern kvm (I'm using the qemu-ev packages, incidentally)? I've successfully set up the bridging; a CentOS 7 VM on the same host has full connectivity. So it's something about the rtl8139 and the 2.0.36 kernel. What is the oldest distribution you've done on KVM on C7?

3 4

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2017