Discuss

discuss@lists.centos.org

11 participants
34747 discussions

Centos 7 Samba - all shares read only
by Gary Stainburn 08 May '17

08 May '17

I few weeks back my server started having a problem where all shares are now readonly. AFAIK nothing has changed except a 'yum update' which was probably around the same time. Everyone still has the shares on their Win7 PC's and can see the contents. However, if they try to open a file it opens read only. If the try to create a new file (e.g. right click -> New -> Text Document) it says that they don't have permission. I am not seeing anything meaningful in the log files. Can anyone give me a clue how to fix this, or at least how to collect getting debug info? SELinux has been disabled to eliminate that. Gary Global parameters [global] netbios name = ZEPPO2 server string = Ringways Doncaster Showroom Server workgroup = MOTORPARK os level = 33 preferred master = Yes log file = /var/log/samba/log.%m max log size = 50 guest account = gary security = USER username map = /etc/samba/smbusers wins proxy = Yes wins server = 10.1.1.101 idmap config * : backend = tdb cups options = raw hosts allow = 127. 10. [printers] comment = All Printers path = /var/spool/samba browseable = No printable = Yes guest ok = Yes [tmp] comment = Temporary work area path = /user/remote/tmp guest ok = Yes read only = No [goodwill] comment = Good will documents path = /user/remote/goodwill force user = gary guest ok = Yes read only = No valid users = gary [service] comment = Temporary work area path = /user/remote/service force user = gary read only = No valid users = gary write list = gary [sales_doc] comment = Sales D.O.C. spreadsheets path = /user/remote/sales_doc force user = gary guest ok = Yes read only = No valid users = gary [root@zeppo ~]# smbstatus Samba version 4.4.4 PID Username Group Machine Protocol Version Encryption Signing ---------------------------------------------------------------------------------------------------------------------------------------- 2552 gary gary 10.6.103.236 (ipv4:10.6.103.236:50445) SMB2_10 - - Service pid Machine Connected at Encryption Signing --------------------------------------------------------------------------------------------- tmp 2552 10.6.103.236 Thu May 4 14:05:23 2017 BST - - Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------------------------------------------------------------- 2552 1000 DENY_ALL 0x100080 RDONLY NONE /user/remote/tmp . Thu May 4 14:05:23 2017 2552 1000 DENY_NONE 0x100081 RDONLY NONE /user/remote/tmp . Thu May 4 14:05:39 2017 [root@zeppo ~]# ls -ld / /user /user/remote/ /user/remote/tmp/ /user/remote/service/ dr-xr-xr-x. 18 root root 4096 May 4 13:59 / drwxr-xr-x. 4 root root 34 Nov 7 2013 /user drwxr-xr-x. 22 gary gary 4096 Jun 2 2016 /user/remote/ drwxr-xr-x. 6 gary gary 4096 Apr 19 08:32 /user/remote/service/ drwxr-xr-x. 8 gary gary 4096 Feb 23 17:26 /user/remote/tmp/ [root@zeppo ~]#

4 7

where to find stable thread pool?
by qw 08 May '17

08 May '17

Hi, I have one question. Where to find source code of statble thread pool for CentOS? Thanks! Regards Andrew

1 0

Squirrelmail/PHP issue
by Jay Hart 08 May '17

08 May '17

Been using Centos and Squirrelmail since early in Centos 6 cycle. IIRC, I used to be able to attach more than 4 pictures to an email. Now I can't, four seems to be the limit. Picture file size doesn't seem to matter, they can be 50k or 5 meg each. I upped the limits in php.ini for the following parameters to see if this would have any bearing on the issue: post_max_size = 20M upload_max_filesize = 15M The way I see this is that I should be able to attach [more than] four pics of say, size 100K, to an email. I can't. Within Squirrelmail I go to 'Compose', put in a recipient, subject title, and in the body of text lets just say I add "test case" (as an example). Then I go to 'browse', select a [pic] file, click 'add' (which attaches the pic to the email), and repeat this for a total of four files. When I try to attach the fifth pic, the 'email' frame goes blank, nothing shown. To recover the text I can select 'Compose' again and squirrelamil will state I have an email in 'draft' and do I want to open it. If I click 'ok' I get my email back minus all attached pics. Cycle repeats itself if I try to attach pic #5. I've googled the web looking to see if others have had this issue, and a buddy helped me a bit, but nothing definite shown to resolve. I've got to figure its a PHP issue. I'm currently patched to Centos 6.9. Any help appreciated as to what to look for... J

1 0

systemd missing something?
by ken 07 May '17

07 May '17

"Note that traditional init scripts continue to function on a systemd system. An init script /etc/rc.d/init.d/foobar is implicitly mapped into a service unit foobar.service during system initialization." That's what it says in /etc/init.d/README. However, what it implies doesn't seem to work out. In the same directory as that README is a file called "network" which is symlinked into the various /etc/rc.d/rc?.d/ directories, i.e.: # ls -l $(find /etc/rc.d/ -name S*network) lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc2.d/S56network -> ../init.d/network lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc3.d/S56network -> ../init.d/network lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc4.d/S56network -> ../init.d/network lrwxrwxrwx. 1 root root 17 Jan 26 15:22 /etc/rc.d/rc5.d/S56network -> ../init.d/network But "network" isn't executed on boot. However, it does work when I run this: # /etc/init.d/network restart So is this a bug, or is there something else that needs to be done?

4 3

CentOS 7 cloned VM cannot boot
by Nikolaos Milas 06 May '17

06 May '17

Hello, I'm struggling to make a cloned CentOS 7 VM (under KVM) to work. The VM was cloned using mondorestore. Restore appears successful but the VM won't boot; see: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-04.png I booted with CentOS 7 disk in troubleshooting mode (where the virtual disk was automatically mounted without issues) and I tried to repair: http://iweb.noa.gr/files/centos7/el7-rescue-scratchvm-20170502-01.png Also: # grub2-mkconfig -o /boot/grub2/grub.cfg ... /usr/sbin/grub2-probe: error: unknown filesystem. I then tried to repair using: https://sourceforge.net/p/boot-repair-cd/home/Home/ but it didn't manage to solve the problem. (It reported success but the VM still won't boot.) More interesting was the effort with the supergrub2 disk: http://www.supergrubdisk.org/super-grub2-disk/ This managed to identify the available "boot methods" and allowed me to boot correctly. See screenshots: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-00.png http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-01.png http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-02.png Once I logged in, I checked /etc/fstab and /boot/grub2/grub.cfg but I didn't see any obvious problem. The are here as well: http://iweb.noa.gr/files/centos7/fstab http://iweb.noa.gr/files/centos7/grub.cfg However, I also followed these directions: https://www.techbrown.com/reinstall-grub2-boot-loader-centos-7-rhel-7.shtml to rebuild grub2.conf. The commands were completed successfully. Unfortunately, the OS still won't boot: same issue, see: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-04.png I again tried to boot using the supergrub2 disk; this time the boot method detection produced the (slightly different) list you see in image: http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-05.png Using the supergrub2 disk I can boot and login successfully. Otherwise (i.e. directly) the box won't boot. As I know little about grub2 (and low-level linux) to troubleshoot the issue, can you please help identify and correct the problem? Why the VM always refuses to boot? Which is the reported device (on image -04) that remains unrecognized? I looked into /boot/grub/grub2.cfg but I didn't see any such UUID there. Where may it be referenced to be used during the boot process? Note: I never have such issues when restoring (using mondorestore) CentOS 5 or CentOS 6 mondoarchive backups (even on dissimilar virtual hardware). Can you please help me identify the problem, based on the above info, and make the VM normally bootable? Many thanks, Nick

6 29

tabs ignored in here document
by Robert Moskowitz 05 May '17

05 May '17

I thought this worked. Many web pages tell you it works. But bash is ignoring tabs in my here docs. Worst, where there are two tabs, it is functioning as a command expand in bash, where all files in the current directory are listed to complete the command. The following is the here doc I am using. Most likely the tabs will be converted to spaces in this email. But the bottom line is, that while processing all the double tables, all the files in the current directory get listed, and the resultant file is all flush left, as if I had used the +EOF option: Thing is, I thought I tested this previously, so it is possible that there is now something wrong in my environment causing the problem? cat <<EOF>00-init.conf || exit 1 ServerAdmin $admin_email ServerName $your_host_tld <VirtualHost *:80> <Directory "/var/www/html"> Options Indexes FollowSymLinks AllowOverride None Require all granted </Directory> </VirtualHost> <VirtualHost *:443> SSLEngine On SSLCertificateFile /etc/pki/tls/certs/$your_host_tld.crt SSLCertificateKeyFile /etc/pki/tls/private/$your_host_tld.key <Directory "/var/www/html"> Options Indexes FollowSymLinks AllowOverride None Require all granted </Directory> </VirtualHost> EOF thanks

5 10

Re: [CentOS] CentOS 7 cloned VM cannot boot
by Gianluca Cecchi 05 May '17

05 May '17

Il 05 Mag 2017 19:30, "Nikolaos Milas" <nmilas(a)noa.gr> ha scritto: On 5/5/2017 3:45 μμ, Gianluca Cecchi wrote: BTW: see also this paragraph in the provided RH EL link: > 24.7.3. Resetting and Reinstalling GRUB 2 > > But i think is not your problem.... > Yes, I have done that, without change in behavior. Also, after changing partitions flag does your fdisk command reflect the > change? > Yes. Is the error during boot the same as the one provided in your first e-mail? > Yes. One final thing. When I had to change boot settings, I made different steps > in choot environment in respect of the indication inside the image you > sent. > > Specifically > > Verify if your boot partition is already mounted under /mnt/sysimage/boot > in your current environment > Yes, it is: sh-4.2# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/live-rw 2.0G 1.1G 930M 54% / devtmpfs 979M 0 979M 0% /dev tmpfs 1001M 4.0K 1001M 1% /dev/shm tmpfs 1001M 8.3M 993M 1% /run tmpfs 1001M 0 1001M 0% /sys/fs/cgroup /dev/sr0 680M 680M 0 100% /run/install/repo tmpfs 1001M 300K 1001M 1% /tmp /dev/mapper/centos-root 18G 1.5G 16G 9% /mnt/sysimage /dev/vdal 497M 192M 306M 39% /mnt/sysimage/boot /tmpfs 1001M 0 1001M 0% /mnt/sysimage/dev/shm If it is mounted on another mount point in your live env go and umount it > and run > mount /dev/vda1 /mnt/sysimage/boot > Didn't need to. then > chroot /mnt/sysimage > OK, I did so: sh-4.2# chroot /mnt/sysimage bash-4.2# when you are in chrooted environment, probably you don't have special files > for vda and vda1 because they are dinamically created; > verify with > > ls -l /dev/vda* > It seems I do have such files: bash-4.2# ls -la /dev/vda* brw-rw----. 1 root disk 252, 0 May 5 16:49 vda brw-rw----. 1 root disk 252, 1 May 5 16:49 vdal brw-rw----. 1 root disk 252, 2 May 5 16:49 vda2 If this is the case, go and create them > > mknod -m 660 /dev/vda b 253 0 > mknod -m 660 /dev/vda1 b 253 1 > Didn't need to. at this point > > grub2-install /dev/vda > and let see the output of the command and its exit code > As usual: bash-4.2# grub2-install /dev/vda Installing for i386-pc platform. grub2-install: error: unknown filesystem. at this point exit chrooted environment (exit) > umount /mnt/sysimage/boot > > reboot and see if anything changes > Didn't do it, because grub2-install above failed, so nothing changed. I am very puzzled with "unknown filesystem". Thanks for your time and help! I am looking forward to reaching a solution! All the best, Nick _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos Your /mnt/sysimage/boot is under tmpfs not real disk... Try to unmount it and mount the vda1 device instead and then follow the other steps...

2 2

CentOS-announce Digest, Vol 147, Issue 1
by centos-announce-request＠centos.org 05 May '17

05 May '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEEA-2017:1194 CentOS 7 kmod-redhat-ixgbevf Enhancement Update (Johnny Hughes) 2. CEEA-2017:1194 CentOS 7 kmod-redhat-ixgbe Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 4 May 2017 15:23:48 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:1194 CentOS 7 kmod-redhat-ixgbevf Enhancement Update Message-ID: <20170504152348.GA43540(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:1194 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-1194.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ead8dfcb3828518aed74380b77d990bb193ee63417354c20c4b91b2ef95a720f kmod-redhat-ixgbevf-3.2.2_k_rh7.4_z-1.el7_3.x86_64.rpm Source: dccc0b49f0cdf5751526307d6572aec90d0b28cad6c0137898affeb6ed6cdf2b kmod-redhat-ixgbevf-3.2.2_k_rh7.4_z-1.el7_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 4 May 2017 15:24:10 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:1194 CentOS 7 kmod-redhat-ixgbe Enhancement Update Message-ID: <20170504152410.GA43598(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:1194 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-1194.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: cd47bdab22ce9c387beaf066c0e36d63633b07bfcbcad4bda1dac53c74a095e2 kmod-redhat-ixgbe-4.4.0_k_rh7.4_z-2.el7_3.x86_64.rpm Source: 6566b60dd49a2156360e3c60e819acf37c652c931d5d52f995c8dd7d225486e4 kmod-redhat-ixgbe-4.4.0_k_rh7.4_z-2.el7_3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 147, Issue 1 ***********************************************

1 0

running tomcat as non-root user.. (/var/run pidfile issue)
by Jason Welsh 04 May '17

04 May '17

hey folks, we are migrating our tomcat setup over to centos 7. Im converting init-scripts over to systemd services and whatnot.. One thing that Ive noticed is that my systemd startup script cant seem to write to /var/run as a non-root user to drop a pidfile.. If I create a directory in /var/run owned by my user, it gets wiped out on reboot. Ive searched and found this https://blog.hqcodeshop.fi/archives/93-Handling-varrun-with-systemd.html which says to use ExecStartPre to fudge creating directories in /var/run so what non-root users can write there.. Is that the suggested way to do this? It seems awful kludgey. Jason

3 3

External drive, BackupPC service, and booting
by Kenneth Porter 03 May '17

03 May '17

I'm using an external drive with BackupPC on CentOS 7. I currently have a mount entry like this in fstab: /dev/disk/by-label/backuppc4 /var/lib/BackupPC ext4 noauto,rw 0 0 This means I must manually mount the drive and then start the backuppc service. Is there a way to set up hotplugging so that the drive is mounted if present at boot time but doesn't stop the boot if it's not present or otherwise fails? I see the fstab nofail option. Will that do what I want? Is there a way to set up the backuppc service (through systemd) so that it starts if and only if the drive is present, or starts if the drive is plugged in later? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

1 0

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