Re: [CentOS] Samba setup
Hi, > Am 18.01.2021 um 20:08 schrieb Robert G. (Doc) Savage via CentOS > : > > I'm > following > https://www.linuxbabe.com/redhat/set-up-samba-server-on-centos-8-rhel-8-for-file-sharing > to set up Samba 4.12.3-12 on my Storinator fileserver running CentOS > 8.3. I am trying to share out /tank/Windows/ as a Samba share: > > # ls -al /tank > total 61 > drwxr-xr-x. 6 root root 7 Dec 26 10:43 Backups > drwxr-xr-x. 6 root root 6 Dec 4 22:47 Repos > drwxrwxrwx. 2 doc doc 4 Dec 28 14:01 VMs > drwxrwxrwx. 2 root root 2 Jan 17 17:04 Windows > > My /etc/samba/smb.conf file is set up as follows: > > # testparm > Load smb config files from /etc/samba/smb.conf > Loaded services file OK. > Server role: ROLE_STANDALONE > > Press enter to see a dump of your service definitions > > # Global parameters > [global] > printcap name = cups > security = USER > idmap config * : backend = tdb > cups options = raw > hosts allow = 192.168.0 > > ... > > [public] > comment = public share, no need to enter username and password > guest ok = Yes > path = /tank/Windows > read only = No > > When I try to map network drive from my Windows 10 PC using the > graphical File Explorer, it asks me for my username and password. It > doesn't accept my password. When I try to map it at the CMD cli, I get: > > C:\> net use S: \\192.168.1.20\public\ > System error 67 has occurred. > > The network name cannot be found. > > Could this be a network browsing problem in Samba? What have I missed? Anything in the samba logs? May be SELinux/Firewall issues? Regards . Götz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Restore pristine SELinux configuration ?
Hi, I have CentOS 7 running on a public server hosting all sorts of web applications, mail, XMPP, MPD, etc. How do I reset SELinux configuration to defaults? I know how to reset all my custom booleans to the initial state. # cat /etc/selinux/targeted/active/booleans.local # This file is auto-generated by libsemanage # Do not edit directly. httpd_unified=1 httpd_can_sendmail=1 spamd_enable_home_dirs=1 httpd_can_network_connect=1 ftpd_full_access=1 mpd_enable_homedirs=1 named_write_master_zones=1 Starting from there, I can manually reset them to 0 with setsebool. On the other hand, I don't know how I would do something similar with the SELinux modules. I vaguely remember having created some of these, for example for Fail2ban to work correctly. But I don't remember what I did here over the years, what modules I created, etc. How would I recreate the default SELinux configuration without having to wipe and reinstall the whole server? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Kickstart "Error setting up base repository"
I recently built my first CentOS kickstart config on a CentOS 7 system; it runs well, but the OS and its tools are old enough that it's causing pain with the apps I want to run on top of said system, so I'm trying to port it to CentOS 8. I've taken the anaconda-ks.cfg file created from a successful manual install (of both regular 8 and Stream), placed it on my DVD ISO, and wrapped things back up like I was doing with CentOS 7. I'm successfully beginning the installation, but running into "Error setting up base repository" - despite having not touched either the filesystem structure of the ISO, or the generated kickstart file that points at my repos. Here is the relevant config: #version=RHEL8 # Use graphical install graphical repo --name="AppStream" --baseurl=file:///run/install/sources/mount--cdrom/AppStream %packages @^minimal-environment @development kexec-tools %end # Keyboard layouts keyboard --xlayouts='us' # System language lang en_US.UTF-8 # Network information network --hostname=localhost.localdomain # Use CDROM installation media cdrom # Run the Setup Agent on first boot firstboot --enable ignoredisk --only-use=sda autopart # Partition clearing information clearpart --none --initlabel # System timezone timezone America/New_York --isUtc %addon com_redhat_kdump --enable --reserve-mb='auto' %end %anaconda pwpolicy root --minlen=6 --minquality=1 --notstrict --nochanges --notempty pwpolicy user --minlen=6 --minquality=1 --notstrict --nochanges --emptyok pwpolicy luks --minlen=6 --minquality=1 --notstrict --nochanges --notempty %end When I switched over to a console to try to troubleshoot this, I noticed that /run/install/sources/mount--cdrom/AppStream didn't exist (the "mount--cdrom" directory is empty), but /run/install/repo/AppStream does, and appears to have all the right information within it. I've tried specifying that directory as the baseurl instead, and get no difference in behavior. The only other file I've touched is isolinux/isolinux.cfg on the DVD, with the relevant line now being: append initrd=initrd.img inst.ks=cdrom:/ks.cfg inst.stage2=hd:LABEL=CentOS-Stream-8-x86_64-dvd quiet What am I doing wrong here? This seems like basic config, but obviously I've missed something... -- Alex Kirk Global Principal, Suricata 404-291-6588 ak...@corelight.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstart "Error setting up base repository"
On Tue, 19 Jan 2021 at 12:27, Alex Kirk wrote: > I recently built my first CentOS kickstart config on a CentOS 7 system; it > runs well, but the OS and its tools are old enough that it's causing pain > with the apps I want to run on top of said system, so I'm trying to port it > to CentOS 8. > > I've taken the anaconda-ks.cfg file created from a successful manual > install (of both regular 8 and Stream), placed it on my DVD ISO, and > wrapped things back up like I was doing with CentOS 7. I'm successfully > beginning the installation, but running into "Error setting up base > repository" - despite having not touched either the filesystem structure of > the ISO, or the generated kickstart file that points at my repos. > > Here is the relevant config: > > #version=RHEL8 > # Use graphical install > graphical > > repo --name="AppStream" > --baseurl=file:///run/install/sources/mount--cdrom/AppStream > > I think you need to have a repo for every repository used including the baseOS one.. like repo --name="BaseOS" --baseurl=file:///run/install/sources/mount--cdrom/BaseOS -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstart "Error setting up base repository"
Alex Kirk wrote: > I recently built my first CentOS kickstart config on a CentOS 7 system; it > I've taken the anaconda-ks.cfg file created from a successful manual > install (of both regular 8 and Stream), placed it on my DVD ISO, and > wrapped things back up like I was doing with CentOS 7. I'm successfully > beginning the installation, but running into "Error setting up base > repository" - despite having not touched either the filesystem structure of > the ISO, or the generated kickstart file that points at my repos. I don't know if it's connected, but I had a problem (with a similar errors) when installing 8.3.2011 over httpd using a copy of the contents of the 8.3.2011 iso My kickstart file contained: url --url="http://distro/CentOS/8.3.2011"; repo --name="AppStream" --baseurl=http://disto/CentOS/8.3.2011/AppStream This was a copy of what I has done with 8.1.1911 - which worked OK I couldn't get 8.3.2011 to install, until I hacked things so the kickstart contained: url --url="http://distro/CentOS/8.3.2011/BaseOS"; repo --name="AppStream" --baseurl=http://disto/CentOS/8.3.2011/AppStream but I also had to put a symlink in the BaseOS subdir of: images -> ../images i.e. it worked with 8.1.1911 but not 8.3.2011 (I never tried 8.2.2004) I don't know if this is a bug or I'm doing something wrong? James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Restore pristine SELinux configuration ?
Am 19.01.21 um 17:25 schrieb Nicolas Kovacs: Hi, I have CentOS 7 running on a public server hosting all sorts of web applications, mail, XMPP, MPD, etc. How do I reset SELinux configuration to defaults? I know how to reset all my custom booleans to the initial state. # cat /etc/selinux/targeted/active/booleans.local # This file is auto-generated by libsemanage # Do not edit directly. httpd_unified=1 httpd_can_sendmail=1 spamd_enable_home_dirs=1 httpd_can_network_connect=1 ftpd_full_access=1 mpd_enable_homedirs=1 named_write_master_zones=1 Starting from there, I can manually reset them to 0 with setsebool. On the other hand, I don't know how I would do something similar with the SELinux modules. I vaguely remember having created some of these, for example for Fail2ban to work correctly. But I don't remember what I did here over the years, what modules I created, etc. How would I recreate the default SELinux configuration without having to wipe and reinstall the whole server? list your modules with semodule -l and remove custom modules with semodule -r myfail2ban -- Leon ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba setup
On Tue, 2021-01-19 at 17:18 +0100, Götz Reinicke wrote: > Hi, > > > Am 18.01.2021 um 20:08 schrieb Robert G. (Doc) Savage via CentOS > > : > > > > I'm > > > following > https://www.linuxbabe.com/redhat/set-up-samba-server-on-centos-8-rhel-8-for-file-sharing > > to set up Samba 4.12.3-12 on my Storinator fileserver running > > CentOS > > 8.3. I am trying to share out /tank/Windows/ as a Samba share: ... > > > > When I try to map network drive from my Windows 10 PC using the > > graphical File Explorer, it asks me for my username and password. > > It > > doesn't accept my password. When I try to map it at the CMD cli, I > > get: > > > > C:\> net use S: \\192.168.1.20\public\ > > System error 67 has occurred. > > > > The network name cannot be found. > > > > Could this be a network browsing problem in Samba? What have I > > missed? > > Anything in the samba logs? May be SELinux/Firewall issues? Götz, Unfortunately, no. The nmbd log verifies that the fileserver's samba service is the local master browser for WORKGROUP on both eth0 and virbr0. [2021/01/17 19:02:22.190795, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) * Samba name server LIONSTORE is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.20 * [2021/01/17 19:02:22.191085, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) * Samba name server LIONSTORE is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 * The samba smbd log simply reports the connection denials: [2021/01/17 23:07:40.304626, 0] ../../lib/util/access.c:371(allow_access) Denied connection from 192.168.1.30 (192.168.1.30 There's nothing in the SELinux logs for that date. I checked firewall-config on the storage server and verified that the samba service is allowed (but not samba-client or samba-dc). --Doc ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstart "Error setting up base repository"
So adding on: repo --name="BaseOS" --baseurl=file:///run/install/sources/mount--cdrom/BaseOS ...didn't help at all. Neither did adding the symlink out of the BaseOS directory to the images subdirectory above it. I did notice this time, however, that when I click into the "Installation Source" button of the UI where the erorr is, if I click on the repos being read from my Kickstart file, there's a small error at the bottom of the page that says "Repository name conflicts with internal repository name". That seems weird, since again I'm basing this on a successful manual install - why would that write a conflicting repo name to the config? On Tue, Jan 19, 2021 at 12:52 PM James Pearson wrote: > Alex Kirk wrote: > > I recently built my first CentOS kickstart config on a CentOS 7 system; > it > > I've taken the anaconda-ks.cfg file created from a successful manual > > install (of both regular 8 and Stream), placed it on my DVD ISO, and > > wrapped things back up like I was doing with CentOS 7. I'm successfully > > beginning the installation, but running into "Error setting up base > > repository" - despite having not touched either the filesystem structure > of > > the ISO, or the generated kickstart file that points at my repos. > > I don't know if it's connected, but I had a problem (with a similar > errors) when installing 8.3.2011 over httpd using a copy of the contents of > the 8.3.2011 iso > > My kickstart file contained: > > url --url="http://distro/CentOS/8.3.2011"; > repo --name="AppStream" --baseurl=http://disto/CentOS/8.3.2011/AppStream > > This was a copy of what I has done with 8.1.1911 - which worked OK > > I couldn't get 8.3.2011 to install, until I hacked things so the kickstart > contained: > > url --url="http://distro/CentOS/8.3.2011/BaseOS"; > repo --name="AppStream" --baseurl=http://disto/CentOS/8.3.2011/AppStream > > but I also had to put a symlink in the BaseOS subdir of: > > images -> ../images > > i.e. it worked with 8.1.1911 but not 8.3.2011 (I never tried 8.2.2004) > > I don't know if this is a bug or I'm doing something wrong? > > James Pearson > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > -- Alex Kirk Global Principal, Suricata 404-291-6588 ak...@corelight.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstart "Error setting up base repository"
On Tue, 19 Jan 2021 at 15:54, Alex Kirk wrote: > So adding on: > > repo --name="BaseOS" > --baseurl=file:///run/install/sources/mount--cdrom/BaseOS > > ...didn't help at all. Neither did adding the symlink out of the BaseOS > directory to the images subdirectory above it. > > I did notice this time, however, that when I click into the "Installation > Source" button of the UI where the erorr is, if I click on the repos being > read from my Kickstart file, there's a small error at the bottom of the > page that says "Repository name conflicts with internal repository name". > That seems weird, since again I'm basing this on a successful manual > install - why would that write a conflicting repo name to the config? > > so I think the error (or warning) is because according to the repo command you can't name repositories the same as ones already defined in anaconda. However somehow our working kickstarts have # Use network install url --url=http://10.0.0.1/repo/rhel/RHEL/8.2/x86_64/ repo --name=epel --baseurl=http://10.0.0.1/pub/epel/8/Everything/x86_64/ repo --name="BaseOS" --baseurl= http://10.0.0.1/repo/rhel/rhel8/x86_64/rhel-8-for-x86_64-baseos-rpms/ repo --name="AppStream" --baseurl= http://10.0.0.1/repo/rhel/rhel8/x86_64/rhel-8-for-x86_64-appstream-rpms/ repo --name="PowerTools" --baseurl= http://10.0.0.1/repo/rhel/rhel8/x86_64/codeready-builder-for-rhel-8-x86_64-rpms/ are you able to get to a console when this box is 'failing'? control-b 2 or something to move to a shell? if you can there might be a way to see if the cdrom is even mounted and in the directory listed. If it isn't //run/install/sources/mount--cdrom then none of the repositories would work. I don't have any systems with cdroms anymore so I am not sure how to test to see myself. -- Stephen J Smoogen. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Restore pristine SELinux configuration ?
Le 19/01/2021 à 19:29, Leon Fauster via CentOS a écrit : > list your modules with > > semodule -l > > and remove custom modules with > > semodule -r myfail2ban Thank you very much ! Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] btrfs to ext4
Hello CentOS Gurus, I have just learned that our backup system natively supports restoring vmware VM individual files from a vmware based backup for ext3,ext4 file systems but not BTRFS and some of our VM's run BTRFS as the root file system. Does anyone know if it's possible to convert BTRFS partitions to ext4? Chris -- Christopher Wensink IS Administrator Five Star Plastics, Inc 1339 Continental Drive Eau Claire, WI 54701 Office: 715-831-1682 Mobile: 715-563-3112 Fax: 715-831-6075 cwens...@five-star-plastics.com www.five-star-plastics.com ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] btrfs to ext4
Does anyone know if it's possible to convert BTRFS partitions to > ext4? > I think that you can convert ext to btrfs , but not the opposite. The cleanest way is to reinstall . Best Regards, Strahil Nikolov ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] mcelog service error flagged in Cockpit
Whenever I log into Cockpit, it flags mcelog as a service failure-to- start failure. systemctl confirms this. # systemctl status mcelog * mcelog.service - Machine Check Exception Logging Daemon Loaded: loaded (/usr/lib/systemd/system/mcelog.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-01-10 18:06:36 CST; 1 weeks 2 days ago Main PID: 21959 (code=exited, status=1/FAILURE) Jan 10 18:06:36 lionstore.protogeek.org systemd[1]: Started Machine Check Exception Logging Daemon. Jan 10 18:06:36 lionstore.protogeek.org mcelog[21959]: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Jan 10 18:06:36 lionstore.protogeek.org mcelog[21959]: CPU is unsupported Jan 10 18:06:36 lionstore.protogeek.org systemd[1]: mcelog.service: Main process exited, code=exited, status=1/> Jan 10 18:06:36 lionstore.protogeek.org systemd[1]: mcelog.service: Failed with result 'exit-code'. A search through BZ indicates mcelog hasn't been supported on AMD processors s since family 21. How do I tell Cockpit to use this alternative module? Perhaps more importantly, why doesn't Cockpit automatically set up this module when it's installed on an AMD system? --Doc Savage Fairview Heights, IL ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
