Re: [CentOS] smb protocol version

2020-06-15 Thread Michael Schumacher
Chris,

CW> I don't have any lines in my configuration file for any of the servers,
CW> how can I tell what the default protocols are?

you may want to add

log file = /var/log/samba/log.%m.%R

to the "global" part of your smb.conf.

The %R gives "the selected protocol level after protocol negotiation.
It can be one of CORE, COREPLUS, LANMAN1, LANMAN2, NT1, SMB2_02,
SMB2_10, SMB2_22, SMB2_24, SMB3_00, SMB3_02, SMB3_10, SMB3_11 or
SMB2_FF."

This will at least give you information about the actually used
protocol for every client. A bit "the other way around", but it might
help.

Michael
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Apache (httpd) fails to start at boot - Centos 8.1

2020-06-15 Thread Gordon Messmer

On 6/15/20 7:06 PM, Jay Hart wrote:

If I do 'systemctl start httpd', apache will start right up.  But during boot, 
it doesn't and I
get the resulting errors below.

Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address: 
AH00072: make_sock: could
not bind to address 10.20.30.11:80



httpd is starting before an interface has been configured with 10.20.30.11.

The default configuration starts httpd after "network.target" but you 
want to start it after "network-online.target".


IIRC: run "systemctl edit httpd.service" and insert:

[Unit]
After=network-online.target

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Apache (httpd) fails to start at boot - Centos 8.1

2020-06-15 Thread Kenneth Porter

On 6/15/2020 7:06 PM, Jay Hart wrote:

Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address: 
AH00072: make_sock: could
not bind to address 10.20.30.11:80


Could some transient service be holding port 80 at that time?

You could probably arrange to run a script that runs "lsof -i" and "ip 
addr show", dumping the output to a temp file, just before httpd runs to 
see what's not set up right.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Apache (httpd) fails to start at boot - Centos 8.1

2020-06-15 Thread Alan McRae via CentOS
I have always had exactly the same problem. I had to write a script and 
run it at boot time:


sleep 10
/usr/bin/systemctl start httpd

Must be some timing problem with the interface addresses not being set 
up in time.


Alan

On 16/06/2020 14:06, Jay Hart wrote:

If I do 'systemctl start httpd', apache will start right up.  But during boot, 
it doesn't and I
get the resulting errors below.

Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address: 
AH00072: make_sock: could
not bind to address 10.20.30.11:80
Jun 15 21:17:28 dream httpd[1534]: no listening sockets available, shutting down
Jun 15 21:17:28 dream httpd[1534]: AH00015: Unable to open logs
Jun 15 21:17:29 dream systemd[1]: httpd.service: Main process exited, 
code=exited, status=1/FAILURE
Jun 15 21:17:29 dream systemd[1]: httpd.service: Failed with result 'exit-code'.

the box's ip address is 10.20.30.11, and I am trying to get http (80), and 
https (443) going.

Firewall is turned on. The listen parameter in httpd.conf is 10.20.30.11:80  
The log files in
/var/log/httpd are all owned by root.  Httpd runs as user 'apache'.

Google searches have not returned anything that looks remotely promising.

Got any suggestions?

Thanks in advance,

Jay

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Apache (httpd) fails to start at boot - Centos 8.1

2020-06-15 Thread Jay Hart
If I do 'systemctl start httpd', apache will start right up.  But during boot, 
it doesn't and I
get the resulting errors below.

Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address: 
AH00072: make_sock: could
not bind to address 10.20.30.11:80
Jun 15 21:17:28 dream httpd[1534]: no listening sockets available, shutting down
Jun 15 21:17:28 dream httpd[1534]: AH00015: Unable to open logs
Jun 15 21:17:29 dream systemd[1]: httpd.service: Main process exited, 
code=exited, status=1/FAILURE
Jun 15 21:17:29 dream systemd[1]: httpd.service: Failed with result 'exit-code'.

the box's ip address is 10.20.30.11, and I am trying to get http (80), and 
https (443) going.

Firewall is turned on. The listen parameter in httpd.conf is 10.20.30.11:80  
The log files in
/var/log/httpd are all owned by root.  Httpd runs as user 'apache'.

Google searches have not returned anything that looks remotely promising.

Got any suggestions?

Thanks in advance,

Jay

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS runs on six cores.

2020-06-15 Thread Thomas Stephen Lee
On Sun, Jun 14, 2020 at 8:12 PM Alessandro Baggi 
wrote:

>
>
> Il 12/06/20 18:59, Gordon Messmer ha scritto:
> > On 6/12/20 2:16 AM, Thomas Stephen Lee wrote:
> >> Do we need an upgrade ?
> >
> >
> > Can you restate your question so that it's clear what version you are
> > running, what hardware you are running it on, what you expect to happen,
> > and what is happening instead?
> Hi,
> I think that Stephen is referring about the number of developer of the
> core team that is of 6 members (from this "Do we need an upgrade?").
>
> My first question for Stephen is: why do you think that the core team
> needs more dev?
>
>
>
Hi,

No upgrades needed.

Working fine 
-
Lee
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Simple scan in CentOS 7

2020-06-15 Thread Fred Smith
On Mon, Jun 15, 2020 at 04:28:17PM -0400, H wrote:
> I just installed C7 on a new computer and despite Simple Scan being installed 
> as part of C7, I have not been able to get it to recognize my Canon scanner 
> connected to a USB port. I did have it running on another computer with C7 so 
> there should not be any inherent issues.
> 
> On a lark I installed gscan2pdf and sane-backends-drivers-scanners and 
> sane-find-scanner found it:
> 
> found USB scanner (vendor=0x04a9 [Canon], product=0x1908 [CanoScan]) at 
> libusb:001:010
> 
> I perused my notes for the old computer but did not see I installed any 
> additional software to get it going but I might be wrong.
> 
> What have I missed?
> 

On my C7 box, simple-scan requires libsane. try: ldd simple-scan |grep -i sane.

# ldd /usr/bin/simple-scan | grep -i sane
libsane.so.1 => /lib64/libsane.so.1 (0x7f3668291000)


ldd doesn't show any other sane dependencies, but I'd sorta think
that simple-scan would also need sane-backends as well. Here's all
the sane things I have installed, FYI:

# ldd /usr/bin/simple-scan | grep -i sane
libsane.so.1 => /lib64/libsane.so.1 (0x7f3668291000)
[root@fcshome log]# yum list installed | grep -i sane
libsane-hpaio.x86_64  3.15.9-5.el7   @base  
sane-backends.x86_64  1.0.24-12.el7  @base  
sane-backends-devel.i686  1.0.24-12.el7  @base  
sane-backends-devel.x86_641.0.24-12.el7  @base  
sane-backends-doc.noarch  1.0.24-12.el7  @base  
sane-backends-drivers-cameras.i6861.0.24-12.el7  @base  
sane-backends-drivers-cameras.x86_64  1.0.24-12.el7  @base  
sane-backends-drivers-scanners.i686   1.0.24-12.el7  @base  
sane-backends-drivers-scanners.x86_64 1.0.24-12.el7  @base  
sane-backends-libs.i686   1.0.24-12.el7  @base  
sane-backends-libs.x86_64 1.0.24-12.el7  @base  
sane-frontends.x86_64 1.0.14-19.el7  @base  
xsane.x86_64  0.999-9.el7@base  
xsane-common.x86_64   0.999-9.el7@base  
xsane-gimp.x86_64 0.999-9.el7@base

also FYI, I'm using a Canon LiDE 210, which works fine for me.

Good luck!

Fred

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
   "For the word of God is living and active. Sharper than any double-edged 
   sword, it penetrates even to dividing soul and spirit, joints and marrow; 
  it judges the thoughts and attitudes of the heart."  
 Hebrews 4:12 (niv) --
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS-virt] very low performance of Xen guests

2020-06-15 Thread Adi Pircalabu via CentOS-virt

On 15-06-2020 23:42, Manuel Wolfshant wrote:

On 6/15/20 2:46 PM, Stephen John Smoogen wrote:


On Sun, 14 Jun 2020 at 14:49, Manuel Wolfshant
 wrote:


Hello

For the past months I've been testing upgrading my Xen hosts
to CentOS 7 and I face an issue for which I need your help to
solve.

The testing machines are IBM blades, model H21 and H21XM.
Initial tests were performed on the H21 with 16 GB RAM; during the
last 6=7 weeks I've been using the H21XM with 64 GB. In all cases
the guests were fully updated CentOS 7 -- initially 7.6 ( most
recent at the time of the initial tests ), and respectively 7.8
for the tests performed during the last 2 months.  As host I used
initially CentOS 6 with latest kernel available in the centos virt
repo at the time of the tests and CentOS 7 with the latest kernel
as well. As xen versions I tested 4.8 and 4.12 ( xl info included
below ). The storage for the last tests is a Crucial MX500 but
results were similar when using traditional HDD.

My problem, in short, is that the guests are extremely slow.
For instance , in the most recent tests, a yum install kernel
takes cca 1 min on the host and 12-15 (!!!) minutes in the guest,
all time being spent in dracut regenerating the initramfs images.
I've done rough tests with the storage  ( via dd if=/dev/zero
of=a_test_file size bs=10M count=1000 ) and the speed was
comparable between the hosts and the guests. The version of the
kernel in use inside the guest also did not seem to make any
difference . OTOH, sysbench (
https://github.com/akopytov/sysbench/ ) as well as p7zip benchmark
report for the guests a speed which is between 10% and 50% of the
host. Quite obviously, changing the elevator had no influence
either.

Here is the info which I think that should be relevant for the
software versions in use. Feel free to ask for any additional
info.


Is there a way to boot up a PV guest versus an HVM?


If I understood the docs correctly, newer xen does only PVHVM (
xen_platform_pci=1 activates that ) and HVM. But they say it's better
than PV. And I did verify, PVHVM is indeed enabled and active


You can also test running your Linux domUs as Xen PVH [1], which 
requires kernel 4.11 and Xen 4.10 as a minimum.


[1] https://wiki.xenproject.org/wiki/Linux_PVH

--
Adi Pircalabu
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt


[CentOS] Simple scan in CentOS 7

2020-06-15 Thread H
I just installed C7 on a new computer and despite Simple Scan being installed 
as part of C7, I have not been able to get it to recognize my Canon scanner 
connected to a USB port. I did have it running on another computer with C7 so 
there should not be any inherent issues.

On a lark I installed gscan2pdf and sane-backends-drivers-scanners and 
sane-find-scanner found it:

found USB scanner (vendor=0x04a9 [Canon], product=0x1908 [CanoScan]) at 
libusb:001:010

I perused my notes for the old computer but did not see I installed any 
additional software to get it going but I might be wrong.

What have I missed?

Thank you.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Updating microcode_ctl froze Centos7

2020-06-15 Thread Robin Lee
On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote:
> Today when I ran yum update two packages came up microcode_ctl
> and unbound-libs. The updating process went fine until it outputted 
> 
> Running transaction
>   Updating   : 2:microcode_ctl-2.1-61.6.el7_8.x86_64
> 
> then it just froze. I could no longer ssh to the machine and the
> console was just blank. I had to shut down it hard. It came back up
> seemingly fine. But yum update doesn't work anymore. It says "Error
> importing repomd.xml from base/7/x86_64: Damaged repomd.xml file"
> I looked at the logs, but journalctl only shows the latest boot on
> this
> machine. 
> 
> So I guess I have three questions
> - Any idea what happened with the update process?
> - How can I repair repomd.xml?

Now that yum is up and running again it tells me the following 

"There are unfinished transactions remaining. You might consider
running yum-complete-transaction, or "yum-complete-transaction --
cleanup-only" and "yum history redo last", first to finish them. If
those don't work you'll have to try removing/installing packages by
hand (maybe package-cleanup can help)."

Doing "yum-complete-transaction --cleanup-only" should be safe, right?
To clean up the botched microcode_ctl update and after that set it
among excluded packages.

/Robin

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] smb protocol version

2020-06-15 Thread Christopher Wensink
I don't have any lines in my configuration file for any of the servers,
how can I tell what the default protocols are?

Are the defaults controlled by samba or the kernel?

Chris

On 6/15/2020 2:13 PM, Fred Smith wrote:
> On Mon, Jun 15, 2020 at 11:23:54AM -0500, Christopher Wensink wrote:
>> I have a handful of Linux Servers, running Centos 6.10, and 6.8 with the
>> main host running openvz w/ Centos 6.10 as the main OS.  Two of the
>> guests are running samba, sharing directories out to windows clients.
>>
>> I'm in the process of migrating servers over to vmware, using Centos
>> 7.8.  How can I determine what smb protocol version is being used in the
>> shares for each server?  I don't see the protocol specified anywhere in
>> smb.conf?
>>
>> Chris
> in my Centos-7 box, /etc/samba/smb.conf contains:
>
> server min protocol = SMB3_11
> client max protocol = SMB3_11
> client min protocol = SMB3_11
>
>
> Some non-current windows versions don't support that version, you
> may need to try different values til you find one that works.
> Whatever you do, you don't want to use version 1.
>
> I'm forcing version 3.1.1 only because all the devices I have
> that support SMB also support 3.1.1, so if someone comes along with,
> e.g., an old laptop with XP, it won't be able to insecurely talk
> to my lan/wan. (and that's a feature, not a bug! ;=) )
>
> Also, you may wish to peruse this page:
>
> https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3
>

-- 
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] C8 install problems SOLVED

2020-06-15 Thread ejm
I burned a total of 7.55Gb from an ISO image to a dual-layer HP DVD+R disc.

I got a bootable USB stick containing 8.1 and it's 7.65 Gb so apparently my ISO 
image file
is messed up.

I was able to install C8 just fine from the USB stick, so marking this as 
solved.

Thanks,

--Ed
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] smb protocol version

2020-06-15 Thread Fred Smith
On Mon, Jun 15, 2020 at 11:23:54AM -0500, Christopher Wensink wrote:
> I have a handful of Linux Servers, running Centos 6.10, and 6.8 with the
> main host running openvz w/ Centos 6.10 as the main OS.  Two of the
> guests are running samba, sharing directories out to windows clients.
> 
> I'm in the process of migrating servers over to vmware, using Centos
> 7.8.  How can I determine what smb protocol version is being used in the
> shares for each server?  I don't see the protocol specified anywhere in
> smb.conf?
> 
> Chris

in my Centos-7 box, /etc/samba/smb.conf contains:

server min protocol = SMB3_11
client max protocol = SMB3_11
client min protocol = SMB3_11


Some non-current windows versions don't support that version, you
may need to try different values til you find one that works.
Whatever you do, you don't want to use version 1.

I'm forcing version 3.1.1 only because all the devices I have
that support SMB also support 3.1.1, so if someone comes along with,
e.g., an old laptop with XP, it won't be able to insecurely talk
to my lan/wan. (and that's a feature, not a bug! ;=) )

Also, you may wish to peruse this page:

https://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3

-- 
---
 .Fred Smith   /  
( /__  ,__.   __   __ /  __   : / 
 //  /   /__) /  /  /__) .+'   Home: fre...@fcshome.stoneham.ma.us 
//  (__ (___ (__(_ (___ / :__ 781-438-5471 
 Jude 1:24,25 -
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] /etc/networks file

2020-06-15 Thread John Pierce
On Mon, Jun 15, 2020 at 4:39 AM Stephen John Smoogen 
wrote:

>
> This is an archaic file which is equivalent to /etc/hosts and can be  used
> by various network tools instead of DNS.
> https://linux-audit.com/the-purpose-of-etc-networks/
>
> Other than getent, this file seems to be little use in a default EL7/EL8
> system as route and netstat were 'deprecated' and have to be installed
> outside of default installs.
>


IIRC, the names in /etc/networks would be used in places like ip.wrappers
and NFS exports.   The earliest Solaris networks I worked with made pretty
extensive use of that archaic kinda stuff.


-- 
-john r pierce
  recycling used bits in santa cruz
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS-announce] Release for CentOS Linux 8 (2004)

2020-06-15 Thread Brian Stinson
Release for CentOS Linux 8 (2004)

We are pleased to announce the general availability of CentOS Linux 8.
Effectively immediately, this is the current release for CentOS Linux 8
and is tagged as 2004, derived
from Red Hat Enterprise Linux 8.2 Source Code.

As always, read through the Release Notes at :
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2004  - these notes
contain important information about the release and details about some
of the content inside the release from the CentOS QA team. These notes
are updated constantly to include issues and incorporate feedback from
the users.

--
Updates, Sources, and DebugInfos

Updates released since the upstream release are all posted, across all
architectures. We strongly recommend every user apply all updates,
including the content released today, on your existing CentOS Linux 8
machine by just running 'dnf update'.

As with all CentOS Linux 8 components, this release was built from sources
hosted at git.centos.org. Sources will be available from vault.centos.org in
their own dedicated directories to match the corresponding binary RPMs.
Since
there is far less traffic to the CentOS source RPMs compared with the binary
RPMs, we are not putting this content on the main mirror network. If
users wish
to mirror this content they can do so using the reposync command
available in
the yum/dnf-utils package. All CentOS source RPMs are signed with the
same key
used to sign their binary counterparts. Developers and end users looking at
inspecting and contributing patches to the CentOS Linux distro will find
the
code hosted at git.centos.org far simpler to work against. Details on how to
best consume those are documented along with a quick start at :
http://wiki.centos.org/Sources

Debuginfo packages have been signed and pushed. Yum configs
shipped in the new release file will have all the context required for
debuginfo to be available on every CentOS Linux install.

This release supersedes all previously released content for CentOS
Linux 8, and therefore we highly encourage all users to upgrade their
machines. Information on different upgrade strategies and how to
handle stale content is included in the Release Notes.

Note that older content, obsoleted by newer versions of the same
applications are trim'd off from repos like extras/ and centosplus/

--
Download

We produced the following installer images for CentOS Linux 8
# CentOS-8.2.2004-x86_64-minimal.iso: 1718616064 bytes
SHA256 (CentOS-8.2.2004-x86_64-minimal.iso) =
47ab14778c823acae2ee6d365d76a9aed3f95bb8d0add23a06536b58bb5293c0
# CentOS-8.2.2004-x86_64-boot.iso: 654311424 bytes
SHA256 (CentOS-8.2.2004-x86_64-boot.iso) =
c67876a5602faa17f68b40ccf2628799b87454aa67700f0f57eec15c6ccdd98c
# CentOS-8.2.2004-x86_64-dvd1.iso: 8231321600 bytes
SHA256 (CentOS-8.2.2004-x86_64-dvd1.iso) =
c87a2d81d67bbaeaf646aea5bedd70990078ec252fc52f5a7d65ff609871e255

# CentOS-8.2.2004-aarch64-minimal.iso: 1410226176 bytes
SHA256 (CentOS-8.2.2004-aarch64-minimal.iso) =
621d08902bfd7ca8437cd536b86631c87ddc3e36a530abc77011d230401eb158
# CentOS-8.2.2004-aarch64-boot.iso: 579823616 bytes
SHA256 (CentOS-8.2.2004-aarch64-boot.iso) =
76a9a5f84ac9581fee079d7154bf68f72661c9d941e9ab3143bccc760c23eecc
# CentOS-8.2.2004-aarch64-dvd1.iso: 5988872192 bytes
SHA256 (CentOS-8.2.2004-aarch64-dvd1.iso) =
9d2f066edfc3820fc9e4c6d52f01489a3ed57515cf608773e2b8a04f1903c838

# CentOS-8.2.2004-ppc64le-minimal.iso: 1493422080 bytes
SHA256 (CentOS-8.2.2004-ppc64le-minimal.iso) =
1d6802ce5581bd6ae22d13e491dfad65b7a32166f1484e8d6c532cd4cd7e18db
# CentOS-8.2.2004-ppc64le-boot.iso: 628408320 bytes
SHA256 (CentOS-8.2.2004-ppc64le-boot.iso) =
a039bc592e416b97914b6c99cc8cb070d6b35742dbcb7b6eccff55291659c664
# CentOS-8.2.2004-ppc64le-dvd1.iso: 7080738816 bytes
SHA256 (CentOS-8.2.2004-ppc64le-dvd1.iso) =
1a94eff60fd016ea8efb1d592eda85f0b5edde2ff2ad4c77db546ab90392421e

Information for the torrent files and sums are available at
http://mirror.centos.org/centos/8/isos/


Additional Images

Vagrant and Generic Cloud images are available at:

http://cloud.centos.org/centos/8/

Amazon Machine Images for Amazon Web Services are published by ID into a
number
of regions. A table of AMI IDs can be found here:

https://wiki.centos.org/Cloud/AWS

--
Getting Help

The CentOS ecosystem is sustained by community driven help and
guidance. The best place to start for new users is at
http://wiki.centos.org/GettingHelp

We are also on social media, you can find the project:
on Twitter at  :http://twitter.com/CentOSProject
on Facebook at :https://www.facebook.com/groups/centosproject/
on LinkedIn at :https://www.linkedin.com/groups/22405

And you will find the core team and a majority of the contributors on
irc, on freenode.net in #centos ; talking about the finer points of
distribution engineering and platform enablement.

--
Contributors

This release was made possible due to the hard work of many people,
foremost on that list are the Red Hat 

Re: [CentOS] halt versus shutdown

2020-06-15 Thread J Martin Rushton via CentOS

On 15/06/2020 15:53, Valeri Galtsev wrote:



On 6/15/20 6:19 AM, Leon Fauster via CentOS wrote:

Am 15.06.20 um 05:38 schrieb Strahil Nikolov via CentOS:

Working with different Linux Distributions makes the life harder.
So far I have found out that 'poweroff' & 'reboot' has the same 
behaviour on  Linux/Unix/BSDs.




Yeah, poweroff seems the appropriate command instead of halt.

Thanks for all the "historical" input. Things make now sense :-)



Thanks for excurse in the past, whent the world made sense ;-)

Valeri


--
Leon


Hmm.  If the disks really were "on fire", my preferred means of shutdown 
was the big red button by the door as I exited, PDQ.


Actually I did once have to do this.  I was "minding the shop" at lunch 
time on a sunny day.  As I looked into the machine room from the 
operations office I saw a cloud of smoke arising from the floor through 
one of the AC vents.  Dead stop - building alarm and get out.  It turned 
out that one of the AC units had started its steam generator and the 
blast was picking up dist mites, which showed up in a shaft of sunshine 
looking light smoke.  Most machines were at the 
far end of the room and it was only occasionally that that particular 
unit came on.  The fire brigade confirmed that it was the right action, 
but some of the users were less happy!


--
J Martin Rushton MBCS
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] smb protocol version

2020-06-15 Thread Christopher Wensink
I have a handful of Linux Servers, running Centos 6.10, and 6.8 with the
main host running openvz w/ Centos 6.10 as the main OS.  Two of the
guests are running samba, sharing directories out to windows clients.

I'm in the process of migrating servers over to vmware, using Centos
7.8.  How can I determine what smb protocol version is being used in the
shares for each server?  I don't see the protocol specified anywhere in
smb.conf?

Chris
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS-docs] [centos/centos.org] branch master updated: Updated download link for 8.2.2004 release

2020-06-15 Thread git
This is an automated email from the git hooks/post-receive script.

arrfab pushed a commit to branch master
in repository centos/centos.org.

The following commit(s) were added to refs/heads/master by this push:
 new 1e28b50  Updated download link for 8.2.2004 release
1e28b50 is described below

commit 1e28b5028709fb8c47c920b5964e4f642b3d823e
Author: Fabian Arrotin 
AuthorDate: Mon Jun 15 17:33:12 2020 +0200

Updated download link for 8.2.2004 release

Signed-off-by: Fabian Arrotin 
---
 content/download.haml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/download.haml b/content/download.haml
index 90cff60..02dd5bf 100644
--- a/content/download.haml
+++ b/content/download.haml
@@ -17,7 +17,7 @@ title: Download CentOS
 .col-sm-12
   %p
 .downloadbutton
-  %a( 
href="http://isoredirect.centos.org/centos/8/isos/x86_64/CentOS-8.1.1911-x86_64-dvd1.iso;
 ) CentOS Linux DVD ISO
+  %a( 
href="http://isoredirect.centos.org/centos/8/isos/x86_64/CentOS-8.2.2004-x86_64-dvd1.iso;
 ) CentOS Linux DVD ISO
   %p
 .downloadbutton
   %a( 
href="http://isoredirect.centos.org/centos/8-stream/isos/x86_64/CentOS-Stream-8-x86_64-20191219-dvd1.iso;
 ) CentOS Stream DVD ISO
@@ -45,7 +45,7 @@ title: Download CentOS
   %hr
   %h2 Need a Cloud or Container Image?
   %p
-%a( 
href="https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde-8f34-1b0f377efe89;
 ) Amazon Web Services
+%a( 
href="https://wiki.centos.org/Cloud/AWS/#Official_CentOS_Linux_:_Public_Images; 
) Amazon Web Services
   %p
 %a( href="https://registry.hub.docker.com/_/centos/; ) Docker registry
   .row

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs


Re: [CentOS] halt versus shutdown

2020-06-15 Thread Valeri Galtsev



On 6/15/20 6:19 AM, Leon Fauster via CentOS wrote:

Am 15.06.20 um 05:38 schrieb Strahil Nikolov via CentOS:

Working with different Linux Distributions makes the life harder.
So far I have found out that 'poweroff' & 'reboot' has the same 
behaviour on  Linux/Unix/BSDs.




Yeah, poweroff seems the appropriate command instead of halt.

Thanks for all the "historical" input. Things make now sense :-)



Thanks for excurse in the past, whent the world made sense ;-)

Valeri


--
Leon
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


--

Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS-virt] very low performance of Xen guests

2020-06-15 Thread Manuel Wolfshant

On 6/15/20 2:46 PM, Stephen John Smoogen wrote:



On Sun, 14 Jun 2020 at 14:49, Manuel Wolfshant 
mailto:wo...@nobugconsulting.ro>> wrote:


Hello


    For the past months I've been testing upgrading my Xen hosts
to CentOS 7 and I face an issue for which I need your help to solve.

    The testing machines are IBM blades, model H21 and H21XM.
Initial tests were performed on the H21 with 16 GB RAM; during the
last 6=7 weeks I've been using the H21XM with 64 GB. In all cases
the guests were fully updated CentOS 7 -- initially 7.6 ( most
recent at the time of the initial tests ), and respectively 7.8
for the tests performed during the last 2 months.  As host I used
initially CentOS 6 with latest kernel available in the centos virt
repo at the time of the tests and CentOS 7 with the latest kernel
as well. As xen versions I tested 4.8 and 4.12 ( xl info included
below ). The storage for the last tests is a Crucial MX500 but
results were similar when using traditional HDD.

    My problem, in short, is that the guests are extremely slow.
For instance , in the most recent tests, a yum install kernel
takes cca 1 min on the host and 12-15 (!!!) minutes in the guest,
all time being spent in dracut regenerating the initramfs images.
I've done rough tests with the storage  ( via dd if=/dev/zero
of=a_test_file size bs=10M count=1000 ) and the speed was
comparable between the hosts and the guests. The version of the
kernel in use inside the guest also did not seem to make any
difference . OTOH, sysbench (
https://github.com/akopytov/sysbench/ ) as well as p7zip benchmark
report for the guests a speed which is between 10% and 50% of the
host. Quite obviously, changing the elevator had no influence either.

    Here is the info which I think that should be relevant for the
software versions in use. Feel free to ask for any additional info.


Is there a way to boot up a PV guest versus an HVM?


If I understood the docs correctly, newer xen does only PVHVM ( 
xen_platform_pci=1 activates that ) and HVM. But they say it's better 
than PV. And I did verify, PVHVM is indeed enabled and active





I could not find a H21XM but found an HS21XM on the iBM


My bad. The blades are indeed HS21 (Type 8853) and HS21 XM (Type 7995). 
The XM blades have 2*Xeon E5450@3GHz / 12GB L1 cache processors. The 
options I can fiddle with are https://imgur.com/a/DonXe5P


AFAICS the setttings are reasonable but please do let me know if there 
is anything there that should not be as it is



site and that seemed to be a 4 core 8 thread cpu which looks 'old' 
enough that the Spectre/etc fixes to improve performance after the 
initial hit were not done. (Basically I was told that if the CPU was 
older than 2012, just turn off hyperthreading altogether to try and 
get back some performance.. but don't expect much).


I can live with that. My problem is that DomU are much much slower that 
Dom0 so it seems xen virtualization affects ( heavily ) the performance.



As such I would also try turning off HT on the CPU to see if that 
improves anything.


I got inspired by Adi's earlier suggestion and after reading 
https://access.redhat.com/articles/3311301 I've tried today all variants 
of disabling the spectre mitigations. Whatever I do, immediately after a 
reboot, yum reinstall kernel does not take less than 5 minutes :( It 
goes down to 2 min if I repeat the operation afterwards so I guess some 
caching kicks in. I will try later today the kernels from elrepo and 
maybe even xen.crc.id.au ( I kind of hate the "disable selinux" 
recommendation from the install page so I postponed it in the hope of 
other solution ).


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt


Re: [CentOS-virt] very low performance of Xen guests

2020-06-15 Thread Stephen John Smoogen
On Sun, 14 Jun 2020 at 14:49, Manuel Wolfshant 
wrote:

> Hello
>
>
> For the past months I've been testing upgrading my Xen hosts to CentOS
> 7 and I face an issue for which I need your help to solve.
>
> The testing machines are IBM blades, model H21 and H21XM. Initial
> tests were performed on the H21 with 16 GB RAM; during the last 6=7 weeks
> I've been using the H21XM with 64 GB. In all cases the guests were fully
> updated CentOS 7 -- initially 7.6 ( most recent at the time of the initial
> tests ), and respectively 7.8 for the tests performed during the last 2
> months.  As host I used initially CentOS 6 with latest kernel available in
> the centos virt repo at the time of the tests and CentOS 7 with the latest
> kernel as well. As xen versions I tested 4.8 and 4.12 ( xl info included
> below ). The storage for the last tests is a Crucial MX500 but results were
> similar when using traditional HDD.
>
> My problem, in short, is that the guests are extremely slow. For
> instance , in the most recent tests, a yum install kernel takes cca 1 min
> on the host and 12-15 (!!!) minutes in the guest, all time being spent in
> dracut regenerating the initramfs images. I've done rough tests with the
> storage  ( via dd if=/dev/zero of=a_test_file size bs=10M count=1000 ) and
> the speed was comparable between the hosts and the guests. The version of
> the kernel in use inside the guest also did not seem to make any difference
> . OTOH, sysbench ( https://github.com/akopytov/sysbench/ ) as well as
> p7zip benchmark report for the guests a speed which is between 10% and 50%
> of the host. Quite obviously, changing the elevator had no influence
> either.
>
> Here is the info which I think that should be relevant for the
> software versions in use. Feel free to ask for any additional info.
>

Is there a way to boot up a PV guest versus an HVM? I could not find a
H21XM but found an HS21XM on the iBM site and that seemed to be a 4 core 8
thread cpu which looks 'old' enough that the Spectre/etc fixes to improve
performance after the initial hit were not done. (Basically I was told that
if the CPU was older than 2012, just turn off hyperthreading altogether to
try and get back some performance.. but don't expect much). As such I would
also try turning off HT on the CPU to see if that improves anything.


-- 
Stephen J Smoogen.
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt


Re: [CentOS] /etc/networks file

2020-06-15 Thread Stephen John Smoogen
On Sun, 14 Jun 2020 at 19:55, Jay Hart  wrote:

> I am having some network connectivity issues that manifest itself through
> ping, wget, dnf, etc.
> The symptoms are intermittent ability to ping, was wget, or connect to
> repositories.
>
> Where this inquiry is going is: If your internal network is using
> 192.168.1 or 10..50.10, what
> should be in /etc/networks.
>
> My current file contains:
>
> default 0.0.0.0
> loopback 127.0.0.0
> link-local 169.254.0.0
>
> And I'm pretty sure this is the default OS installed contents.
>
> I don't think this is related to my connectivity issue, just curious about
> what this file does.
>
> My old server (which is working just fine) has the same content in its
> /etc/networks file so not
> configuring this does not seem to matter one way or the other.
>
> If one were using 192.168.1.x network , assume 'default' should be
> 192.168.1.0.  'Link-local'
> should match???
>
>
This is an archaic file which is equivalent to /etc/hosts and can be  used
by various network tools instead of DNS.
https://linux-audit.com/the-purpose-of-etc-networks/

Other than getent, this file seems to be little use in a default EL7/EL8
system as route and netstat were 'deprecated' and have to be installed
outside of default installs.




> Thanks,
>
> Jay
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


-- 
Stephen J Smoogen.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] halt versus shutdown

2020-06-15 Thread Leon Fauster via CentOS

Am 15.06.20 um 05:38 schrieb Strahil Nikolov via CentOS:

Working with different Linux Distributions makes the life harder.
So far I have found out that 'poweroff' & 'reboot' has the same behaviour on  
Linux/Unix/BSDs.



Yeah, poweroff seems the appropriate command instead of halt.

Thanks for all the "historical" input. Things make now sense :-)

--
Leon
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos