Discuss September 2015

discuss@lists.centos.org

136 participants
132 discussions

setting up solr/tomcat gives 404 page
by Tim Dunphy 10 Sep '15

10 Sep '15

Hey all, I tried following a few guides and I'm struggling with trying to setup apache solr 4.10 under apache tomcat 7.0.64 along with the drupal config necessary to get that this working with drupal. The latest guide I followed was this one which seemed like it might work: http://duntuk.com/how-install-apache-solr-46-apache-tomcat-7-use-drupal I followed everything to the letter and ended up with a 404 status page when I hit http://ipaddress:8080/solr I think the answer lies in putting the renaming the 'collection1' core to the right location under the name 'drupal'. But how to do that seems to be left out of that tutorial. In the tomcat logs I just see the following: 100.116.32.93 - - [09/Sep/2015:16:52:56 -0400] "GET /solr HTTP/1.1" 404 959 Which isn't very informative!! Any chance I can get some help in getting this working? Thanks, Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

2 1

Re: [CentOS] rsync question
by Carl E. Hartung 10 Sep '15

10 Sep '15

On Wed, 9 Sep 2015 05:51:38 -0700 (PDT) Mark Milhollan wrote: > On Tue, 8 Sep 2015, Carl E. Hartung wrote: > >On Tue, 8 Sep 2015 10:25:33 -0700 (PDT) Mark Milhollan wrote: > > >> -e specifies the *local* transport command to use > > > >What?! Straight from the documentation: > > > >" -e, --rsh=COMMAND specify the remote shell to use" > > If only one can properly interpret the meaning... COMMAND is the > local command to run to obtain a remote (non-interactive) shell, so > it isn't that the remote shell program (invoked once the transport is > connected) is being specified, i.e., it is which `remsh' to use. The > -p and -l provided thereby may be necessary, since the one is not the > default and the other isn't known to us to be the same as the local > user, which you glossed over as if one never has a need to specify. > > Orthogonal to Robert's problem, the switch from default use of rsh to > ssh has made it a requirement for (good) automation to always supply > a -e to ensure the correct command is used to account for all > potential versions of rsync that may be used. > > >> , and in this case it also specifies the remote port (613) and user > >> (root). Granted one should probably use their ssh configuration to > >> do that but it isn't realy "wrong" (to be questioned) to do it via > >> options. > > > >I didn't explicitly state that it was "wrong," just implied > >(correctly) that it was unnecessary. > > Potentially unnecessary. Just because you might see putting the port > and user in the ssh config file as the right thing to do, and which I > also do whenever possible, doesn't mean Robert necessarily wants to > or can do so, and after all -e does exist. Your questioning its use > as you did implied using it is wrong, to which I object. Luckily you > decided to reply to the list quoting me so eventually Robert was > supplied with the clue you didn't provide, that it might be > pre-configured. > > > /mark Mark, I would prefer it if you would please send your replies to the list and not to me personally. I *do* get them if you send them to the list. All of these fine grained points you've made regarding options that are "required for (good) automation" are irrelevant. Robert's post concerned invoking rsync manually "for backup purposes" -- not for "automation" as you're envisioning. He wrote "This is not an automated system. It is typically a onetime thing ..." Moreover, my "Why '-e'?" query was paired with a second very specific question: "Are these systems running disparate operating systems?" The implication seems pretty clear to me -- not that '-e' was somehow "wrong" but simply likely unnecessary in his scenario. I stand by that somewhat informal (less strict than you) evaluation unless and until we learn that he's actually operating on truly disparate systems. regards, Carl

2 2

named Update Problem
by Günther J. Niederwimmer 10 Sep '15

10 Sep '15

Hello, I have enabled for a Domain DNSSEC and it working correct, after I change the rights for /var/named to root:named 0770 but after a update it is always change back to root:named 0750 after this, DNSSEC don't work any more? named have no right to write his secure files. Is there a way to fix this Thanks, -- mit freundlichen Grüssen / best regards, Günther J. Niederwimmer

2 4

(no subject)
by Jeremy Conklin 10 Sep '15

10 Sep '15

Jconklin7887(a)hotmail.com

1 0

How to rebuild logrotate.status
by Robert Moskowitz 10 Sep '15

10 Sep '15

I have a problem in that at first all my log files were dated 12-31-1969 and logrotate has: # more /var/lib/logrotate.status logrotate state -- version 2 "/var/log/yum.log" 1969-12-31-20:26:1 "/var/named/data/named.run" 1969-12-31-20:26:1 "/var/log/httpd/error_log" 2015-8-27-4:43:1 "/var/log/wtmp" 1969-12-31-20:26:1 "/var/log/chrony/*.log" 2015-8-19-22:0:0 "/var/log/spooler" 1969-12-31-20:26:1 "/var/log/btmp" 1969-12-31-20:26:1 "/var/log/maillog" 1969-12-31-20:26:1 "/var/log/wpa_supplicant.log" 2015-8-19-22:0:0 "/var/log/secure" 1969-12-31-20:26:1 "/var/log/ppp/connect-errors" 2015-8-19-22:0:0 "/var/log/messages" 1969-12-31-20:26:1 "/var/log/cron" 1969-12-31-20:26:1 "/var/log/httpd/access_log" 2015-8-27-4:43:1 How do I get this file rebuilt with the dates currently on the files listed?

2 1

NFS client kernel panic
by David Goudet 10 Sep '15

10 Sep '15

Hi everyone, I have an issue with NFS client when the NFS client loose connection with the NFS server. In certain conditions the NFS client freeze and the result is kernel panic. It seems that kernel panic occurs when the NFS client try to unmount the unreachable remote NFS partition. This case occurs about one time each two days. CentOS version: CentOS Linux release 7.1.1503 (Core) Kernel version: Linux foo.bar 3.10.0-229.4.2.el7.x86_64 #1 SMP Wed May 13 10:06:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux NFS packages: nfs-utils-1.3.0-0.8.el7.x86_64, libnfsidmap-0.25-11.el7.x86_64 This issue is present only on Centos7 NFS client (not present with Centos6). Any ideas? Is it known problem with Centos7 NFS client? Logs and stack trace here after: nfs: server foo.bar not responding, timed out nfs: server foo.bar not responding, timed out nfs: server foo.bar not responding, timed out nfs: server foo.bar not responding, timed out nfs: server foo.bar not responding, timed out BUG: Dentry ffff8800ca82f380{i=138c0,n=foo.png} still in use (2) [unmount of nfs4 0:41] ------------[ cut here ]------------ kernel BUG at fs/dcache.c:945! invalid opcode: 0000 [#1] SMP Modules linked in: ipt_REJECT rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache binfmt_misc xt_multiport iptable_filter ip_tables dm_crypt nfsd mgag200 auth_rpcgss syscopyarea nfs_acl sysfillrect lockd sysimgblt i2c_algo_bit ttm coretemp sunrpc drm_kms_helper iTCO_wdt iTCO_vendor_support i7core_edac ipmi_devintf lpc_ich kvm drm bnx2 ipmi_si dcdbas crc32c_intel serio_raw pcspkr i2c_core mfd_core edac_core ipmi_msghandler shpchp acpi_power_meter xfs libcrc32c sd_mod crc_t10dif crct10dif_common sr_mod cdrom ata_generic pata_acpi mptsas scsi_transport_sas ata_piix mptscsih libata mptbase dm_mirror dm_region_hash dm_log dm_mod CPU: 12 PID: 21364 Comm: umount.nfs4 Not tainted 3.10.0-229.4.2.el7.x86_64 #1 Hardware name: Dell Inc. PowerEdge R410/0N051F, BIOS 1.2.4 11/02/2009 task: ffff880075b3ad80 ti: ffff88007744c000 task.ti: ffff88007744c000 RIP: 0010:[<ffffffff811dddcc>] [<ffffffff811dddcc>] shrink_dcache_for_umount_subtree+0x1ac/0x1c0 RSP: 0018:ffff88007744fe10 EFLAGS: 00010246 RAX: 000000000000005e RBX: ffff8800ca82f380 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff88022fccd488 RDI: 0000000000000246 RBP: ffff88007744fe28 R08: 0000000000000096 R09: 0000000000000627 R10: 0000000000000000 R11: ffff88007744fb26 R12: ffff8801ffb08780 R13: ffffffffa04f27a0 R14: ffff88021f3c0f40 R15: ffff88021f3c0f20 FS: 00007ff58b134880(0000) GS:ffff88022fcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ff58aad15a0 CR3: 00000001ffe7f000 CR4: 00000000000007e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Stack: ffff880036a9fb20 ffff880036a9f800 ffff880036a9a000 ffff88007744fe40 ffffffff811df969 ffff880036a9f800 ffff88007744fe68 ffffffff811c8fe1 0000000000000029 ffff880036a9a000 ffff88021f3c0f20 ffff88007744fe80 Call Trace: [<ffffffff811df969>] shrink_dcache_for_umount+0x49/0x60 [<ffffffff811c8fe1>] generic_shutdown_super+0x21/0xe0 [<ffffffff811c9282>] kill_anon_super+0x12/0x20 [<ffffffffa041827b>] nfs_kill_super+0x1b/0x30 [nfs] [<ffffffff811c962d>] deactivate_locked_super+0x3d/0x60 [<ffffffff811c9c36>] deactivate_super+0x46/0x60 [<ffffffff811e6ac5>] mntput_no_expire+0xc5/0x120 SELinux: initialized (dev 0:40, type nfs4), uses genfs_contexts [<ffffffff811e7bff>] SyS_umount+0x9f/0x3c0 [<ffffffff81614de9>] system_call_fastpath+0x16/0x1b Code: 00 00 48 8b 40 28 4c 8b 08 48 8b 43 30 48 85 c0 74 1b 48 8b 50 40 48 89 34 24 48 c7 c7 20 f1 83 81 48 89 de 31 c0 e8 f0 0a 42 00 <0f> 0b 31 d2 eb e5 0f 0b 66 66 66 2e 0f 1f 84 00 00 00 00 00 66 RIP [<ffffffff811dddcc>] shrink_dcache_for_umount_subtree+0x1ac/0x1c0 RSP <ffff88007744fe10> ---[ end trace ae487f589c43fd74 ]--- Kernel panic - not syncing: Fatal exception Thank you for you attention

1 0

bind chroot, bind mounts and selinux
by Tom Robinson 10 Sep '15

10 Sep '15

Hi All, I'm migrating a CentOS 6 bind instance (chrooted) to a CentOS 7 box and am curious of people's opinions on chrooting vs selinux as a way of securing bind. The bind-chroot on CentOS 7 also comes with a script (/usr/libexec/setup-named-chroot.sh) that sets up the much maligned systemd and, through bind mounts, creates and extra level of chroot hierarchy giving: /var/named/chroot/var/named/chroot/var/named which seems totally unnecessary. I'm sure that bind-chroot would be happy enough running without the bind mounts but would I be loosing anything in terms of security? Also, would I bother with chrooting at all if selinux can secure the environment for me? My own opinions aside what do others think and has anyone had experience with this? 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 2

Re: [CentOS] CentOS 7 + Dell Latitude E6420 laptop = thermalshutdown
by deoren 10 Sep '15

10 Sep '15

> On 6/23/2015 7:22 AM, johan.vermeulen7 at telenet.be wrote: > > Hello All, > > > > installing these laptops went ok, but indeed, they shutdown on logon. > > When coming back up, I get a bios warning about temperature. > > On my first attempt on installing Nvidia driver, I wrecked the laptop. > > To be continued. > > > > greetings, Johan > > > Hi, > > Thanks for your feedback. I can't say I'm "happy" that someone else is > having the same problem, but I'm relieved that it's not just something > odd with the setup I am using. > > Any luck? I'm hoping to have a chance to look more into this myself in > the next few weeks once some other projects calm down. Ironically my > next step was going to be going after an updated video card driver. > > Hello Deoren, > > adding elrepo and installing kmod-nvidia seems to have solved the issue. > I hope this works for you as wel. > > greetings, Johan Thanks for the feedback. I'm a little late getting around to it, but I got a chance yesterday to look at this again and followed the steps to enable the ELRepo repository and installed the `kmod-nvidia` package. Once I did so, I was given a warning that there was a conflict with libglamoregl and to see the wiki page for more details. I looked on the site and found this page: http://elrepo.org/tiki/kmod-nvidia which covered not only that issue (basically run `yum remove xorg-x11-glamor`) but also emphasized that 'kmod-nvidia' might not work for some older chipsets and that the 'nvidia-detect' package should be installed and run to check for compatibility. I did so and got this output: kmod-nvidia Optimus hardware detected: An Intel display controller was detected Either disable the Intel display controller in the BIOS or use the bumblebee driver to suport Optimus hardware Now that the 'kmod-nvidia' driver was installed I rebooted the laptop to load it upon boot. Since I had rebooted, I checked my BIOS settings and sure enough I had the 'Enable Optimus' box selected. Figuring myself clever (ha), I disabled the option and attempted to boot the laptop. I got a blinking cursor against a black background and the password prompt to decrypt the disk and finish booting was never given. Since Ctrl+Alt+Del didn't appear to work, I held the power button and forced the laptop off. I then re-enabled the option and when the laptop next booted I got the password prompt to decrypt the disk and the laptop got to the point where Gnome should have loaded, but the system went no further. My notes are unclear at this point whether I was referring to the login window not displaying or whether it did and just logging into the desktop environment didn't work. I then installed the 'bumblebee' package and I was able to login without locking up the system. I then wiped the laptop, disabled the Optimus support in BIOS and did a clean installation making sure to use the same settings for the new installation as the old. The system booted up and I logged into KDE with no issues and the laptop remained powered on. Presumably the Optimus option was the issue all along. In summary: * If I have the Optimus option enabled I need to enable the ELRepo repository and install the kmod-nvidia (presumably) and bumblebee packages. * If I have the Optimus option disabled it appears that I don't need to do anything else other than install CentOS 7 normally and use it. Thanks again for your help with this.

1 0

yum list-sec CVE
by Raymond Durand 09 Sep '15

09 Sep '15

Hi, Is the command #yum list-sec cves still compatible with Centos7? Or are there alternatives to list all CVE applicable to a CentOS without the Satellite? Thanks

3 3

Working with PEM content
by Alice Wonder 09 Sep '15

09 Sep '15

Hi, If I need to script some management of text files with PEM content, are there already some tools that exist that do this safely? e.g. somecert.pem that might contain -----BEGIN CERTIFICATE----- blah blah -----END CERTIFICATE----- -----BEGIN DH PARAMETERS----- more blah -----END DH PARAMETERS----- What I would like is a utility that can read that file, remove the DH parameters, write new file, validate new file is valid PEM contents, and give exit status 0 on success. Could be done with standard scripting methods but I'm guessing a perl or python tool already exists that won't have me hitting myself when I make a stupid scripting mistake. Google and Bing lately though seem to be getting harder and harder for me to use to find that kind of stuff. Suggestions?

2 2

← Newer
1
...
7
8
9
10
11
12
13
14
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss September 2015