Discuss November 2017

discuss@lists.centos.org

105 participants
103 discussions

File access in Apache 2.4 (clarification)
by david 21 Nov '17

21 Nov '17

Folks I'm having file-access problems in Apache 2.4 under Centos 7. In particular: - I have a file that's readable to every user and every application, (writeable by only one user), but my CGI scripts cannot read it. - Some of my CGI scripts need temporary storage for some files. They are, for example, some internal log files, tnat get cleaned up over time, but I want to be able to look at them (as root). Where would you suggest they be placed? I've tried /tmp/my_private_files/, and /var/tmp/my_private_files/, but Apache fails to find even the directory. Here's some extra information SELINUX is disabled. I modified my CGI script to report where in the path to /tmp/my_private_files/temp_log.log the process failed. The Perl code I ran is: my $x = ""; print STDERR "Trying to read /tmp/ramdisk/keys.txt\n"; for (split /\//, "/tmp/ramdisk/keys.txt") { next unless $_; $x .= "/$_"; print STDERR "Test $x, " , (-e $x?"exists":"does not exist"), "\n"; } And the output in the http error log for this virtual user, (timestamp and other error log data stripped) was: AH01215: Trying to read /tmp/ramdisk/keys.txt AH01215: Test /tmp, exists AH01215: Test /tmp/ramdisk, does not exist AH01215: Test /tmp/ramdisk/keys.txt, does not exist Using the "dir -l" command as root, I discover: dir -l / | grep tmp drwxrwxrwt. 16 root root 4096 Nov 21 08:35 tmp dir -l /tmp | grep ramdisk drwxrwxrwt 2 root root 140 Nov 21 08:35 ramdisk dir -l /tmp/ramdisk | grep keys.txt -rw-r--r-- 1 user1 user1 11829 Nov 21 08:29 keys.txt Any suggestions? PS: Centos 6 had no such problems, and the file locations worked just fine. David

4 5

Grub2 utilities missing from Rescue environment in build 1708
by arjones85 21 Nov '17

21 Nov '17

grub2-install and a majority of the other grub2-* utilities are no longer present in the Rescue environment. These were there in 1611. Anyone know if this was a purposefully-made decision (and why?), or an oversight? I've checked both the DVD and Everything iso. Not there. -- Sent from: http://centos.1050465.n5.nabble.com/

1 0

grub To grub2 Migration
by Eugene Poole 21 Nov '17

21 Nov '17

I'm trying to move to CentOS 7. One of my concerns is how to make the changes to grub that supports booting from either of the disk partitions that make up /dev/md0 (/dev/sda1 and /dev/sdb1) or whatever it would be under CentOS 7. Is there some document or tutorial available on making the move from CentOS 6 to CentOS 7? -- Eugene Poole Woodstock, Georgia

2 1

CentOS Atomic and OpsWorks?
by Dave Johansen 20 Nov '17

20 Nov '17

Has anyone used CentOS Atomic with OpsWorks? My searches on the internet haven't turned anything up, so I wanted to see if there was any experience/advice on here. Thanks, Dave

1 0

Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4
by Kretschmer, Jens 20 Nov '17

20 Nov '17

Hi Mark, did you manage to sort out messages from Dracut and /sbin/weak-modules you received while installing kmod-nvidia? We get the same messages while installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4 with the kernel 3.10.0-693.5.2.el7.x86_64. Kr, Jens

3 2

gnome boot problem
by dominic adair-jones 20 Nov '17

20 Nov '17

greetings all. running centos 7. i recently performed an upgrade and the server rebooted later in the night. now everytime i start my server its sits at the grey gnome background. i can hit ctl+atl+f2 to get to another console and the error message states "a start job is running for wait for plymouth boot screen to quit". i can ssh into the server but i dont see any obvious issues. this is the brain of my network and houses all my vms and documents. any help would be greatly appreciated.

6 15

Intel Bluetooth problems - "Invalid request code (56)" - on CentOS 6.9
by Toralf Lund 20 Nov '17

20 Nov '17

Hi, I have Lenovo laptop with an Intel wireless and Bluetooth adapter, running CentOS 6.9. The wireless works just fine, but I can't seem to get Bluetooth to work. When I try to force it up from the command line I get # hciconfig hci0 up Can't init device hci0: Invalid request code (56) There is also a similar message message in /var/log/messages from start-up on boot. The device info from "hciconfig" also seems a bit suspicious to me - notice how the address has all 0s: # hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:48 acl:0 sco:0 events:8 errors:0 TX bytes:24 acl:0 sco:0 commands:12 errors:4 /var/log/messages indicates that firmware is loaded correctly # egrep "iwlwifi.*firmware" /var/log/messages Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: firmware: requesting iwlwifi-8000C-17.ucode Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: firmware: requesting iwlwifi-8000C-16.ucode Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm and I think the following shows that the device is actually there # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 17ef:1010 Lenovo Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 005: ID 5986:0706 Acer, Inc Bus 002 Device 002: ID 17ef:1010 Lenovo Bus 001 Device 006: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 007: ID 17ef:100f Lenovo Bus 002 Device 003: ID 2109:8110 VIA Labs, Inc. Hub Bus 001 Device 008: ID 05e3:0610 Genesys Logic, Inc. 4-port hub # lsusb -s 001:004 -v | grep bInterface bInterfaceNumber 0 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth The bluetooth kernel modules should be loaded, too (but perhaps I need some extra driver or whatever?) # lsmod | grep bluetooth bluetooth 97799 6 sco,bnep,l2cap,btusb rfkill 19255 5 cfg80211,bluetooth,thinkpad_acpi Does anyone have any idea what's wrong here? Is there any way at all I can enable Bluetooth on this system? Thanks, - Toralf

2 1

Possible to have EthX acting like the ipaddress of the attached device (aka bridge) having no ipaddress?
by Jobst Schmalenbach 20 Nov '17

20 Nov '17

Hi I have a Centos 6.X router/firewall/gateway for a /29 network all connected to one ETHX that has a switch behind it. This setup works very well but does NOT allow me to QOS one of the devices (a VOIP phone, many lines) as for "tc" to work I need a device, not ipaddress. I thought to connect the VOIP phone directly to the router, but in doing so I need that interface to ACT like the IPADDRESS of the VOIP box, meaning the ethernet interface has no ipaddress acting like a bridge: Internet | --------------------------- | router ip | | BRIDGE base of /29 --------------------------- | | | ------------- | | | | _____________ | | | | | | ---------------- | phone system | ---------------- That way I can use "tc" to prioritize the traffic for the phone system If there are other ways to do this, please suggest. thanks Jobst -- Sometimes, the sharpest sword is not enough, but usually...it is. | |0| | Jobst Schmalenbach | | |0| +61 3 9533 0000, POBox 277, Caulfield South, 3162, Australia |0|0|0|

1 0

CentOS 7: unable to mount
by wwp 18 Nov '17

18 Nov '17

Hello, when I plug an external disk (USB3) of mine, I get this 'Unable to mount /mnt/storage10' alert: Error mounting system-managed device /dev/sda1: Command-line `mount "/mnt/storage10"' exited with non-zero exit status 32: mount: /dev/sda1 is already mounted or /mnt/storage10 busy /dev/sda1 is already mounted on /mnt/storage10 And it's right, /mnt/storage10 has just been mounted (by root): # mount /dev/sda1 on /mnt/storage10 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered) as it's defined in /etc/fstab: /dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20140807009490F-0:0-part1 /mnt/storage10 auto nosuid,nodev,nofail,x-gvfs-show 0 0 Question is: why are there 2 concurrent mount attempts? The user one fails. I will need the root password to unmount. I'd prefer the user mount to proceed, BTW. Other USB disks behave the same here. For every single USB disk I need, once I've mounted it the first time, I've edited the mount options in the gnome-disk-utility and set it to be automatically mounted and "Mount at startup" and "Show in user interface" to true. Any hint, there? Regards, -- wwp

1 0

semi-OT:apcupsd
by m.roth＠5-cent.us 18 Nov '17

18 Nov '17

I can't seem to find apcupsd for C 6. Just went to epel's website, and not visible. Anyone have a clue? mark

9 14

← Newer
1
2
3
4
5
6
7
...
11
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2017