Re: SL 7.8 x86_64 is now available

[Bill Maidment]

On 22/04/2020 1:39 pm, Bill Maidment wrote:



Thank you for your hard work.

Just one issue I have at the moment, my laptop connects to my network
via a wireless connection, and after doing
yum clean all
yum update
I can no longer connect to my network via wireless, only via ethernet 
cable.

Can you give me some pointers to check.
All I get in /var/log/wpa_supplicant.log is:
  Successfully initialized wpa_supplicant
Normally there would be a swag of other messages showing the progress,
but nothing now.

(This message send via wired connection on the laptop.)


Problem worked around.
It appears that SL7.8 installed a new firmware interface
/lib/firmware/ath10k/QCA9377/hw1.0/firmware-6.bin
which is incompatible with kmod-ath10k_pci.rpm from epel (correction 
that should be elrepo), <<<=
so I just renamed that file for the time being and rebooted and it used 
the previous firmware-5.bin file OK.


--
Cheers
Bill

SL7.7 systemd-journald killed by SIGABRT

[Bill Maidment]

Hi
I have just received a couple of emails from my main server with 
systemd-journald errors (see following example). Is this anything for me 
to be concerned about? I really don't understand much of what is in it! 
Can anyone advise me further?


Cheers
Bill

 Original Message 
Subject: [abrt] systemd: systemd-journald killed by SIGABRT
Date: 25/11/2019 1:29 pm
From: u...@localhost.maidment.me
To: r...@localhost.maidment.me

reason: systemd-journald killed by SIGABRT
cmdline:/usr/lib/systemd/systemd-journald
executable: /usr/lib/systemd/systemd-journald
package:systemd-219-67.el7_7.2
component:  systemd
pid:20360
pwd:/
hostname:   ferguson.maidment.me
count:  1
abrt_version:   2.1.11
analyzer:   CCpp
architecture:   x86_64
event_log:
global_pid: 20360
kernel: 3.10.0-1062.4.3.el7.x86_64
last_occurrence: 1574648913
os_release: Scientific Linux release 7.7 (Nitrogen)
pkg_arch:   x86_64
pkg_epoch:  0
pkg_fingerprint: B0B4 183F 192A 7D7D
pkg_name:   systemd
pkg_release:67.el7_7.2
pkg_vendor: Scientific Linux
pkg_version:219
runlevel:   N 3
time:   Mon 25 Nov 2019 13:28:33 AEDT
type:   CCpp
uid:0
username:   root
uuid:   08123cd98757724da38faab67126155961c598f1

core_backtrace:
:{   "signal": 6
:,   "executable": "/usr/lib/systemd/systemd-journald"
:,   "stacktrace":
:  [ {   "crash_thread": true
:,   "frames":
:  [ {   "address": 94768875716065
:,   "build_id": 
"877e8b8ffb24bf1a371e55967ba4208fb4f758a9"

:,   "build_id_offset": 159201
:,   "function_name": "cg_path_get_session"
:,   "file_name": "/usr/lib/systemd/systemd-journald"
:}
:  , {   "address": 94768875604493
:,   "build_id": 
"877e8b8ffb24bf1a371e55967ba4208fb4f758a9"

:,   "build_id_offset": 47629
:,   "function_name": "dispatch_message_real"
:,   "file_name": "/usr/lib/systemd/systemd-journald"
:}
:  , {   "address": 94768875611692
:,   "build_id": 
"877e8b8ffb24bf1a371e55967ba4208fb4f758a9"

:,   "build_id_offset": 54828
:,   "function_name": "server_driver_message"
:,   "file_name": "/usr/lib/systemd/systemd-journald"
:}
:  , {   "address": 94768875587225
:,   "build_id": 
"877e8b8ffb24bf1a371e55967ba4208fb4f758a9"

:,   "build_id_offset": 30361
:,   "function_name": "server_read_dev_kmsg"
:,   "file_name": "/usr/lib/systemd/systemd-journald"
:}
:  , {   "address": 94768875707552
:,   "build_id": 
"877e8b8ffb24bf1a371e55967ba4208fb4f758a9"

:,   "build_id_offset": 150688
:,   "function_name": "source_dispatch"
:,   "file_name": "/usr/lib/systemd/systemd-journald"
:}
:  , {   "address": 94768875711082
:,   "build_id": 
"877e8b8ffb24bf1a371e55967ba4208fb4f758a9"

:,   "build_id_offset": 154218
:,   "function_name": "sd_event_dispatch"
:,   "file_name": "/usr/lib/systemd/systemd-journald"
:}
:  , {   "address": 94768875584637
:,   "build_id": 
"877e8b8ffb24bf1a371e55967ba4208fb4f758a9"

:,   "build_id_offset": 27773
:,   "function_name": "main"
:,   "file_name": "/usr/lib/systemd/systemd-journald"
:} ]
:} ]
:}
cgroup:
:11:cpuset:/
:10:pids:/system.slice/systemd-journald.service
:9:blkio:/system.slice
:8:freezer:/
:7:hugetlb:/
:6:net_prio,net_cls:/
:5:cpuacct,cpu:/system.slice
:4:memory:/system.slice
:3:devices:/system.slice/systemd-journald.service
:2:perf_event:/
:1:name=systemd:/system.slice/systemd-journald.service
dso_list:
:/usr/lib64/libgcc_s-4.8.5-20150702.so.1 libgcc-4.8.5-39.el7.x86_64 
(Scientific Linux) 1566888321
:/usr/lib64/liblzma.so.5.2.2 xz-libs-5.2.2-1.el7.x86_64 (Scientific 
Linux) 1487738905
:/usr/lib64/libc-2.17.so glibc-2.17-292.el7.x86_64 (Scientific Linux) 
1566888348
:/usr/lib64/libattr.so.1.1.0 libattr-2.4.46-13.el7.x86_64 (Scientific 
Linux) 1526007663
:/usr/lib/systemd/systemd-journald systemd-219-67.el7_7.2.x86_64 
(Scientific Linux) 1571788102
:/usr/lib64/ld-2.17.so glibc-2.17-292.el7.x86_64 (Scientific Linux) 
1566888348
:/usr/lib64/liblz4.so.1.7.5 lz4-1.7.5-3.el7.x86_64 (Scientific Linux) 
1566888391
:/usr/lib64/libpcre.so.1.2.0 pcre-8.32-17.el7.x86_64 (Scientific Linux) 
1507013975
:/usr/lib64/libacl.so.1.1.0 libacl-2.2.51-14.el7.x86_64 (Scientific 
Linux) 1526007670
:/usr/lib64/libgcrypt.so.11.8.2 libgcrypt-1.5.3-14.el7.x86_64 
(Scientific Linux) 1507013966
:/usr/lib64/librt-2.17.so 

Re: centOS 8 ... Gnome 3, Mate

[Bill Maidment]

On 10/10/2019 5:15 am, Keith Lofstrom wrote:

On Wed, Oct 09, 2019 at 12:10:50PM +, Teh, Kenneth M. wrote:

One thing that annoys me is the hot top left corner but I have that 
disabled.


That is nice to know, I'll find out how.  I presume Mate and
Gnome3 can coexist on the same machine, perhaps with different
logins to access them, so I can make the transition as Gnome3
is adapted to my needs.



For a while I missed the icons on the desktop but I don't anymore.


Is there a way around that with Gnome3, to keep user-generated
icons on the desktop, and few or NO system-mandatory icons?

I keep about two dozen icons and folders on my desktop,
changing them frequently with my workflow, different patterns
for differently tasked machines.

Sadly, it is true that some people let icons accumulate and
make a mess (resembling their physical desktops), and that
slows down the machine.  I once helped a colleague move 800
overlapped icons on her desktop to folders, and mostly to
the trash.

For me, visual organization of my work using my own icons
and classifications is vital, and saves mental effort for
more important needs.  Also important is to avoid externally
imposed change for change's sake; I'm quite capable of
introducting more changes in my own life than I can manage.

Keith

What about using gnome  3clasic
--
Cheers
Bill

Re: ImageMagick convert no longer works

[Bill Maidment]

On 10/09/2019 2:15 pm, Bill Maidment wrote:

After the updates from SL7.6 to SL7.7 I found that the convert
function in ImageMagick no longer works with the error:

convert: unable to read font
`/usr/share/ghostscript/fonts/n019003l.pfb' @
error/annotate.c/RenderFreetype/1124.

It seems there is some mismatch between ImageMagick and ghostcript.
Anyone else seen this and/or have a solution? Googling only muddies
the issue for me.


I've found a work around as follows:

yum install urw-base35-fonts-legacy
ln -s /usr/share/X11/fonts/urw-fonts /usr/share/ghostscript/fonts

--
Cheers
Bill

ImageMagick convert no longer works

[Bill Maidment]

After the updates from SL7.6 to SL7.7 I found that the convert function 
in ImageMagick no longer works with the error:


convert: unable to read font `/usr/share/ghostscript/fonts/n019003l.pfb' 
@ error/annotate.c/RenderFreetype/1124.


It seems there is some mismatch between ImageMagick and ghostcript.
Anyone else seen this and/or have a solution? Googling only muddies the 
issue for me.


--
Cheers
Bill

RedHat spamming???

[Bill Maidment]

Hi
After applying today's SL7.7 updates I have now received a pile of 
emails from RedHat, see following example.

What has happened?


The following Red Hat Bug Fix Advisory has been published which may 
affect

subscriptions which you have purchased.


RHBA-2019:2640 Red Hat Enterprise Linux Atomic 7.7.1 openscap Container 
Image Update



Summary:

An updated Red Hat Enterprise Linux Atomic openscap container image is 
now

available for Red Hat Enterprise Linux 7 Extras.

The Red Hat Enterprise Linux Atomic openscap container image contains 
the
OpenSCAP-daemon, a service that performs SCAP scans of bare-metal 
machines,

virtual machines and containers. Running the openscap container enables
container vulnerability scanning with the "atomic scan" command.

All users who require the Red Hat Enterprise Linux Atomic openscap
container are advised to update this container image.

Full details and references:

https://urldefense.proofpoint.com/v2/url?u=https-3A__access.redhat.com_errata_RHBA-2D2019-3A2640-3Fsc-5Fcid-3D70160006NHXAA2=DwICAg=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=0XE3e7SLfcT12pgil39KQn0rel7Ar1A7A0ykpCn5tNQ=7B5H1hYvuolzCWJZNS3Ic66PI8uR0vcKcJ9nsSgTVfk= 


Revision History:

Issue Date: 2019-09-03
Updated:2019-09-03


--
Manage Errata Notifications
--

You are receiving this email because you have elected to receive errata 
notifications

from Red Hat. This message is being sent to:
Red Hat login: WMaidment
Email address on file: 

Update your preferences at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_wapps_ugc_protected_notif.html=DwICAg=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=0XE3e7SLfcT12pgil39KQn0rel7Ar1A7A0ykpCn5tNQ=mwl7exZsFSf5VQCKLdFlQjV8NIjzmL3oAOLtvp25SIA= 



--
Contact
--

This is an automated message. Please do not reply. If you have further 
questions or concerns,
please contact Red Hat Technical Support 
https://urldefense.proofpoint.com/v2/url?u=https-3A__access.redhat.com_support_contact_technicalSupport_=DwICAg=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=0XE3e7SLfcT12pgil39KQn0rel7Ar1A7A0ykpCn5tNQ=AzyC580ovOgM0FMTgrCruFggObpSM1zXV_pk3hewZ9w= 
or open a support case via the Red Hat Customer Portal 
https://urldefense.proofpoint.com/v2/url?u=https-3A__access.redhat.com_support_cases_-23_case_new_=DwICAg=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=0XE3e7SLfcT12pgil39KQn0rel7Ar1A7A0ykpCn5tNQ=ctxL069e5XvJHJ48UkT4gR204lpYnJe9qydxz8EiTQI= 



Copyright 2019 Red Hat, Inc.

--
Cheers
Bill

Kernel 3.10.0-1062.1.1.el7.x86_64 noise

[Bill Maidment]

Hi
I've just installed the security and fastbugs updates for SL7.7 and when 
booting the new kernel I get the following message on screen twice, but 
nothing is shown in the logs.


ERROR: No symbol table
Press any key to continue

The boot process continues OK whether I press a key or not, so I guess 
this is just noise.

Any idea where this comes from?

--
Cheers
Bill

Re: SL 7.7 update

[Bill Maidment]

On 27/08/2019 9:49 pm, John Pilkington wrote:

I have 7.7 running.  Part of the update went ahead with --skip-broken,
but qt5-webkit (epel) and libreport-rhel-anaconda-bugzilla still
caused problems.

qt5-webkit from epel-testing pulled in others of the family, and I
don't see the libreport-rhel-anaconda-bugzilla package in the repos I
use, so I erased it.

HTH,

John P


One of my servers had the libreport error, but I did yum remove 
libreport-rhel-anaconda-bugzilla to resolve it.

I think the new version did not have rhel in the name.

--
Cheers
Bill

Re: SL 7.7 wireless issue

[Bill Maidment]

On 27/08/2019 1:58 pm, Bill Maidment wrote:

Hi
It's time to start testing SL 7.7 updates and the first thing I found
was that my laptop wireless (using ath10k_pci) does not work:

Aug 27 12:52:51 [localhost] kernel: ath10k_pci :03:00.0: pci irq
msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Aug 27 12:52:51 [localhost] kernel: ath10k_pci :03:00.0: qca9377
hw1.1 target 0x05020001 chip_id 0x003821ff sub 11ad:08a6
Aug 27 12:52:51 [localhost] kernel: ath10k_pci :03:00.0: kconfig
debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Aug 27 12:52:51 [localhost] kernel: ath10k_pci :03:00.0: firmware
ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp
crc32 42e41877
Aug 27 12:52:54 [localhost] kernel: ath10k_pci :03:00.0: unable to
read from the device
Aug 27 12:52:54 [localhost] kernel: ath10k_pci :03:00.0: could not
execute otp for board id check: -110
Aug 27 12:52:54 [localhost] kernel: ath10k_pci :03:00.0: failed to
get board id from otp: -110
Aug 27 12:52:54 [localhost] kernel: ath10k_pci :03:00.0: could not
probe fw (-110)

I tried using the previous 7.6 kernel but no luck there.

I plugged in a USB dongle and that worked OK for wireless.

Are we missing an update for the ath10k driver or is something else 
interfering?


No. It seems we have a new version that doesn't match the kernel. I 
found the following on the Manjaro site:



This is a firmware issue. The firmware needs to be downgraded to 
version 5 or you need to upgrade to kernel 4.19 and use the version 6 
firmware.


Firmware Version Incompatibilities:

The QCA9377 adapter will work on kernel 4.19 if the ath10k 
“firmware-6.bin” file is within the firmware folder.


The QCA9377 adapter will work on kernel 4.14 if the ath10k 
“firmware-6.bin” is removed from the firmware folder.


The firmware is located in:

/lib/firmware/ath10k/QCA9377

Delete the version 6 firmware and reboot if you have no internet 
connection (or need to remain on kernel 4.14). Otherwise upgrade to 
kernel 4.19.



The location on SL7.7 is /lib/firmware/ath10k/QCA9377/hw1.0/ and 
removing firmware-6.bin worked for me.


--
Cheers
Bill

SL 7.7 - mount issue

[Bill Maidment]

Another problem during boot

[1.312875] tmpfs: Bad mount option huge
[1.317515] [drm] Unable to create a private tmpfs mount, hugepage 
support will be disabled(-22).
[1.317841] checking generic (c000 7e9000) vs hw (c000 
1000)
[1.317843] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - 
removing generic driver

[1.317855] Console: switching to colour dummy device 80x25


Is this something to do with /etc/mtab ?


cgroup /sys/fs/cgroup/hugetlb cgroup 
rw,nosuid,nodev,noexec,relatime,hugetlb 0 0

hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0

--
Cheers
Bill

SL 7.7 wireless issue

[Bill Maidment]

Hi
It's time to start testing SL 7.7 updates and the first thing I found 
was that my laptop wireless (using ath10k_pci) does not work:


Aug 27 12:52:51 [localhost] kernel: ath10k_pci :03:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
Aug 27 12:52:51 [localhost] kernel: ath10k_pci :03:00.0: qca9377 
hw1.1 target 0x05020001 chip_id 0x003821ff sub 11ad:08a6
Aug 27 12:52:51 [localhost] kernel: ath10k_pci :03:00.0: kconfig 
debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Aug 27 12:52:51 [localhost] kernel: ath10k_pci :03:00.0: firmware 
ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 
42e41877
Aug 27 12:52:54 [localhost] kernel: ath10k_pci :03:00.0: unable to 
read from the device
Aug 27 12:52:54 [localhost] kernel: ath10k_pci :03:00.0: could not 
execute otp for board id check: -110
Aug 27 12:52:54 [localhost] kernel: ath10k_pci :03:00.0: failed to 
get board id from otp: -110
Aug 27 12:52:54 [localhost] kernel: ath10k_pci :03:00.0: could not 
probe fw (-110)


I tried using the previous 7.6 kernel but no luck there.

I plugged in a USB dongle and that worked OK for wireless.

Are we missing an update for the ath10k driver or is something else 
interfering?


--
Cheers
Bill

Re: [SCIENTIFIC-LINUX-USERS] XFS memory allocation deadlock

[Bill Maidment]

On 22/08/2019 11:20 pm, Pat Riehecky wrote:

I believe the solution is two fold:

- The SL 7.7 kernel will help prevent the problem from reoccurring
(currently in sl-testing, scheduled for release Monday)
- Existing fragmentation should probably be cleaned up via xfs_fsr[1]



Thanks Pat and others. I will await the updates and make some space 
available for de-fraging.


--
Cheers
Bill

XFS memory allocation deadlock

[Bill Maidment]

Hi
During copying a large file (about 200GB) to a backup hard drive, I am 
getting a multitude of XFS possible memory allocation deadlock messages.

RedHat Portal shows the following:

XFS issues "possible memory allocation deadlock in kmem_alloc" messages
Solution Verified - Updated August 9 2019 at 2:51 AM - English
Issue

Seeing file system access issues on XFS based file systems.
dmesg shows continuous entries with:

XFS: possible memory allocation deadlock in kmem_alloc (mode:0x250)

Does anyone know what the solution is? And if SL7 will get this solution 
soon?


--
Cheers
Bill

Re: Security ERRATA Low: curl on SL7.x x86_64

[Bill Maidment]

On 30/07/2019 7:34 am, Scott Reid wrote:




SL7
  x86_64
curl-7.29.0-51.el7_6.3.x86_64.rpm
curl-debuginfo-7.29.0-51.el7_6.3.i686.rpm
curl-debuginfo-7.29.0-51.el7_6.3.x86_64.rpm
libcurl-7.29.0-51.el7_6.3.i686.rpm
libcurl-7.29.0-51.el7_6.3.x86_64.rpm
libcurl-devel-7.29.0-51.el7_6.3.i686.rpm
libcurl-devel-7.29.0-51.el7_6.3.x86_64.rpm

- Scientific Linux Development Team


It looks like the i686 rpms didn't make it to the rsync repository.

Protected multilib versions: libcurl-7.29.0-51.el7_6.3.x86_64 != 
libcurl-7.29.0-51.el7.i686



--
Cheers
Bill

Re: XFS memory allocation deadlock

[Bill Maidment]

On 27/06/2019 1:06 am, Denice Deatrich wrote:

On Wed, 26 Jun 2019, Bill Maidment wrote:


Hi friends
I have run into a problem in SL7.6 copying a large KVM guest lvm 
snapshot

file using cp --sparse=always
I get flooded with the following message:

XFS: cp(12985) possible memory allocation deadlock size 131088 in
kmem_realloc (mode:0x250)

The copy ends eventually, but it takes much longer than I expected.
Has anyone else come across this? Googling doesn't throw much light on 
this.


Did you come across this article in your searches:

https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.codecentric.de_en_2017_04_xfs-2Dpossible-2Dmemory-2Dallocation-2Ddeadlock-2Dkmem-5Falloc_=DwICAg=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=4GjGRmmnQ9-vd6f8scya52mViTCGS_ZqoGYkx8Kolag=eD7uFM_WBarNpN9bJqTk3mUuyJRlCWrpHAFr_t2CoAo= 


However their deadlock is in kmem_alloc instead, and there is no
mention of LVM.  It's a nice analysis - it might shed some light on
the problem.

cheers, etc.


Hi Denice
Thank you very much. This explains a lot. This guest server has never 
been reorganised in recent years. A defrag is definitely in order.


--
Cheers
Bill

XFS memory allocation deadlock

[Bill Maidment]

Hi friends
I have run into a problem in SL7.6 copying a large KVM guest lvm 
snapshot file using cp --sparse=always

I get flooded with the following message:

XFS: cp(12985) possible memory allocation deadlock size 131088 in 
kmem_realloc (mode:0x250)


The copy ends eventually, but it takes much longer than I expected.
Has anyone else come across this? Googling doesn't throw much light on 
this.


--
Cheers
Bill

Re: Problem with volume groups after latest updates

[Bill Maidment]

On 17/05/2019 5:59 pm, Bill Maidment wrote:

Hi
After updating kernel qemu-kvm and libvirt from 7x I have found that
one of my volume groups is not found with pvdisplay or vgdisplay. The
/dev and /dev/mapper files are still there and the virtual servers are
running fine.
How do I fix this without destroying my virtual servers?



Well, no replies, so I bit the bullet and tried a hard reboot. This 
restored the missing volume group, etc.
This is the second server I've experienced having issues doing a soft 
reboot after a kernel update.

Something to watch out for ..

--
Cheers
Bill

Problem with volume groups after latest updates

[Bill Maidment]

Hi
After updating kernel qemu-kvm and libvirt from 7x I have found that one of my 
volume groups is not found with pvdisplay or vgdisplay. The /dev and 
/dev/mapper files are still there and the virtual servers are running fine.
How do I fix this without destroying my virtual servers?

Cheers
Bill Maidment

RE: Can't reboot after latest updates (maybe solved)

[Bill Maidment]

Well the hard reboot has got the server running OK.
The logs show that a backup drive was at 100% full halfway through a backup in 
April. This went unnoticed until the reboot.
Somehow the drive seemed to remain in an unstable state, which the hard reboot 
cleared.

Cheers
Bill
 
-Original message-
> From:Bill Maidment 
> Sent: Saturday 4th May 2019 18:47
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: RE: Can't reboot after latest updates
> 
> Correction. Every 2 minutes, not every 2 seconds.
> I've advised my colleague to try a hard reboot to see if that gets us out of 
> trouble.
> 
>  
> -Original message-
> > From:Bill Maidment 
> > Sent: Saturday 4th May 2019 18:16
> > To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> > Subject: Can't reboot after latest updates
> > 
> > Hi
> > Today, a colleague ran yum update on our SL7.6 server and after reboot the 
> > server refuses to start with the following message every 2 seconds:
> > 
> > System Journal ID 20156 – failed to send WATCHDOG=1 notification message.  
> > Transport endpoint is not connected.
> > 
> > Any ideas how to fix this. Google shows this as an occasional issue, but 
> > with no specific help.
> > .
> > 
> > Cheers
> > Bill Maidment

RE: Can't reboot after latest updates

[Bill Maidment]

Correction. Every 2 minutes, not every 2 seconds.
I've advised my colleague to try a hard reboot to see if that gets us out of 
trouble.

 
-Original message-
> From:Bill Maidment 
> Sent: Saturday 4th May 2019 18:16
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: Can't reboot after latest updates
> 
> Hi
> Today, a colleague ran yum update on our SL7.6 server and after reboot the 
> server refuses to start with the following message every 2 seconds:
> 
> System Journal ID 20156 – failed to send WATCHDOG=1 notification message.  
> Transport endpoint is not connected.
> 
> Any ideas how to fix this. Google shows this as an occasional issue, but with 
> no specific help.
> .
> 
> Cheers
> Bill Maidment

Can't reboot after latest updates

[Bill Maidment]

Hi
Today, a colleague ran yum update on our SL7.6 server and after reboot the 
server refuses to start with the following message every 2 seconds:

System Journal ID 20156 – failed to send WATCHDOG=1 notification message.  
Transport endpoint is not connected.

Any ideas how to fix this. Google shows this as an occasional issue, but with 
no specific help.
.

Cheers
Bill Maidment

RE: Re[2]: question regarding the future

[Bill Maidment]

Oh! Dear!
Not only is "redhat" two words, but so is "alot".
Does that matter in computing? Well if you can slip up there, you will have 
real trouble with programming syntax ;-)

Cheers (and only joking)
Bill
 
-Original message-
> From:Maarten 
> Sent: Thursday 2nd May 2019 21:48
> To: David Sommerseth 
> Cc: scientific-linux-us...@listserv.fnal.gov
> Subject: Re[2]: question regarding the future
> 
> I know it's two words, it has become muscle memory for some reason 
> to type redhat instead of Red Hat or maybe because of seeing seeing 
> the domain redhat.com come across my screen alot :) 
> 

RE: question regarding the future

[Bill Maidment]

Hi
I moved from CentOS 5 to SL6 when I urgently needed version 6 for some of its 
new features, and CentOS didn't get their act together for a few months.
I stayed with SL because of the extremely helpful, caring people who made up 
the team as well as those on the mailing lists.
It seemed a logical move for Fermilab to move to CentOS after CERN did that a 
while back. CentOS has matured since then and I do not see RedHat or IBM as 
threats, especially since Fermilab, CERN, et. al. will be helping to improve 
the product.
If anything does go awry in the future, I do not see major science institutions 
sitting back and doing nothing about it. Maybe even SL would then arise again? 
Call it Phoenix?
Anyway, I am now looking forward to CentOS 8. Are we there yet?
Cheers from an old-timer, with less than 2 cents left to contribute.
Bill
 
 
-Original message-
> From:Maarten 
> Sent: Sunday 28th April 2019 3:55
> To: scientific-linux-us...@listserv.fnal.gov
> Subject: Re: question regarding the future
> 
> I still find it uncertain of what might happen in the future, changes 
> can take more then a couple of years to develop.
> Also with IBM having bought Redhat the future can still be uncertain, 
> IBM is not known for their opensource projects.
> Yes with Fermilab, CERN and other labs deciding to go with CentOS 
> chances are increased of CentOS staying the way
> it us, but Redhat and IBM remains a companies and companies are driven 
> by increasing their profit. Just my two cents ;)
> 
> On 4/27/19 7:18 PM, Steven Haigh wrote:
> > I think this misses the point.
> >
> > SL was a major 'security blanket' for the uncertainty that was 
> > happening with RedHat essentially taking control of CentOS. People 
> > were not sure which way things were going to go, so SL filled the gap.
> >
> > As time has passed, RedHat has done the right thing so far with CentOS 
> > - and a lot of people are less nervous as a result.
> >
> > I understand the decision not to do an SL8 - as the environment is 
> > pretty settled again and it is much clearer how this will run. It's 
> > better to utilise those resources on a more internal focus.
> >
> > The threat of CentOS disappearing is gone, so most people will 
> > probably pick up CentOS 8 when it comes around to it.
> > Steven Haigh
> >
> >  net...@crc.id.au     
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.crc.id.au=DwIFaQ=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=bxSPoSV3klZdWvNSRY1MzfipTnfuVcJ-eFb3mV2ht3A=z13E-77e2i9E3Fd3_dgZfCfqJPga60K5Jdz9WOj_qIA=
> >  +61 (3) 9001 6090     0412 935 897
> >
> > On Sun, Apr 28, 2019 at 1:08 AM, John Holmes  
> > wrote:
> >> Try Springdale Linux (formerly PUIAS), it was started long before 
> >> CentOS.
> >> PU-IAS = Princeton University - Institute for Advanced Study
> >> https://urldefense.proofpoint.com/v2/url?u=http-3A__springdale.math.ias.edu_=DwIDaQ=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=wP65fR-SDNTSPXnXaiYwSUdkmZtorgLfyxLkJX73d1U=GCfR5v9kjH_NGH0--yMHNpy_l708MANUmXBGhyDJIBw=
> >>  
> >>
> >>
> >> On 27/04/2019 14:15, Maarten wrote:
> >>>  Hello fellow SL users,
> >>>
> >>>  I having been using SL for a while now, after the CentOS project 
> >>> became
> >>>  part of Redhat
> >>>  I was glad that I was using SL because I would think that CentOS would
> >>>  become a middle
> >>>  testing ground for Redhat to test new things, getting the idea SL 
> >>> would
> >>>  stay closer to the
> >>>  source since it just being another clone. Now that it has been 
> >>> announced
> >>>  that there will
> >>>  be no SL8, what's the best clone to switch to after EOL of SL6 and 
> >>> SL7.
> >>>  Even  though
> >>>  Redhat says that  CentOS will never be used as a testing ground or
> >>>  switch how they are
> >>>  doing things, I do not believe what they say now will be the same 
> >>> in the
> >>>  future.
> >
> >
> 
> 

RE: [SCIENTIFIC-LINUX-USERS] Rsync issue with SL7 repository

[Bill Maidment]

Hi Pat
I was still getting the same error, so I deleted the iso file in question and 
the next rsync downloaded it OK.
Maybe it was a corrupt iso at my end, anyway it's all OK now.
Cheers
Bill
 
-Original message-
> From:Pat Riehecky 
> Sent: Friday 4th January 2019 1:57
> To: Bill Maidment ; scientific-linux-us...@listserv.fnal.gov
> Subject: Re: [SCIENTIFIC-LINUX-USERS] Rsync issue with SL7 repository
> 
> Hello,
> 
> I'm not showing anything weird going on with rsync today.
> 
> I'll see about kicking the daemon just to be safe
> 
> Pat
> 
> On 1/2/19 10:04 PM, Bill Maidment wrote:
> > Hi
> > If anyone is not on holiday, is there a problem with the rsync server?
> > I've received the following errors twice today.
> >
> >  Getting SL7x/x86_64/iso   at: Thu Jan  3 13:16:27 AEDT 2019
> > receiving incremental file list
> >
> > sent 43 bytes  received 119 bytes  46.29 bytes/sec
> > total size is 3,030  speedup is 18.70
> > receiving incremental file list
> > Scientific-7.6-Everything-DVD-x86_64.iso
> > rsync: connection unexpectedly closed (4845638 bytes received so far) 
> > [receiver]
> > rsync error: error in rsync protocol data stream (code 12) at io.c(226) 
> > [receiver=3.1.2]
> > rsync: connection unexpectedly closed (62 bytes received so far) [generator]
> > rsync error: error in rsync protocol data stream (code 12) at io.c(226) 
> > [generator=3.1.2]
> >
> >
> > Cheers
> > Bill Maidment
> 
> -- 
> Pat Riehecky
> 
> Fermi National Accelerator Laboratory
> http://www.fnal.gov
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.scientificlinux.org=DwIFaQ=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=oDenoeTtUJIP87sO2obXHes6pYXEGpaSF44Ddf_6Wo4=D1bmzKEqpjP1lqks89ufRO-ONxdZmIFykA_uXXm4ch0=
> 
> 

Rsync issue with SL7 repository

[Bill Maidment]

Hi
If anyone is not on holiday, is there a problem with the rsync server?
I've received the following errors twice today.

 Getting SL7x/x86_64/iso   at: Thu Jan  3 13:16:27 AEDT 2019
receiving incremental file list

sent 43 bytes  received 119 bytes  46.29 bytes/sec
total size is 3,030  speedup is 18.70
receiving incremental file list
Scientific-7.6-Everything-DVD-x86_64.iso
rsync: connection unexpectedly closed (4845638 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) 
[receiver=3.1.2]
rsync: connection unexpectedly closed (62 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) 
[generator=3.1.2]


Cheers
Bill Maidment

RE: SL7 updates cause issues with eclipse 4.7.3a (FIXED)

[Bill Maidment]

Well it seemed that all the editors in eclipse had disappeared.
I deleted /opt/eclipse and installed eclipse 4.9.0.
This converted my workspace metadata and all was back to normal exactly as I 
had left it.
I've no idea what caused the issue in the first place.
Cheers
Bill
 
-Original message-
> From:Bill Maidment 
> Sent: Wednesday 28th November 2018 19:38
> To: scientific-linux-us...@listserv.fnal.gov
> Subject: SL7 updates cause issues with eclipse 4.7.3a
> 
> Hi
> Is it possible that the git updates has caused my eclipse IDE to stop working 
> properly, or is it something else?
> I cannot edit any file in my projects and running eclipse with -clean doesn't 
> help.
> I get a pop-up error with:
> 
> An error has occurred. See error log for more details.
> org/eclipse/jdt/core/IJavaElement
> 
> Has anyone else come across this?
> 
> Cheers
> Bill
>  
> The logs show:
> 
> eclipse.buildId=4.7.3.M20180330-0640
> java.version=1.8.0_191
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_AU
> Framework arguments:  -product org.eclipse.epp.package.php.product
> Command-line arguments:  -os linux -ws gtk -arch x86_64 -product 
> org.eclipse.epp.package.php.product -clean
> 
> org.eclipse.jface
> Error
> Wed Nov 28 19:26:07 AEDT 2018
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> 
> java.lang.NoClassDefFoundError: org/eclipse/jdt/core/IJavaElement 
> at 
> org.jetbrains.kotlin.aspects.navigation.KotlinOpenEditorAspect.ajc$around$org_jetbrains_kotlin_aspects_navigation_KotlinOpenEditorAspect$1$d64491c4(KotlinOpenEditorAspect.aj:17)
>  
> at 
> org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:164)
>  
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:279) 
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:244) 
> at 
> org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:271)
>  
> at 
> org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:249)
>  
> at 
> org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50)
>  
> at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:216) 
> at 
> org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
>  
> at 
> org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:46)
>  
> at 
> org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:851) 
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) 
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) 
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) 
> at 
> org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:848)
>  
> at 
> org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1163)
>  
> at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:451) 
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:273) 
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:268) 
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:308) 
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) 
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348) 
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348) 
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4602) 
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4183) 
> at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
>  
> at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) 
> at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
>  
> at 
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
>  
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) 
> at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) 
> at 
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) 
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) 
> at 
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
>  
> at 
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>  
> at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
>  
> at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
>  
> at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) 
> at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) 
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at 
> 

SL7 updates cause issues with eclipse 4.7.3a

[Bill Maidment]

Hi
Is it possible that the git updates has caused my eclipse IDE to stop working 
properly, or is it something else?
I cannot edit any file in my projects and running eclipse with -clean doesn't 
help.
I get a pop-up error with:

An error has occurred. See error log for more details.
org/eclipse/jdt/core/IJavaElement

Has anyone else come across this?

Cheers
Bill
 
The logs show:

eclipse.buildId=4.7.3.M20180330-0640
java.version=1.8.0_191
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_AU
Framework arguments:  -product org.eclipse.epp.package.php.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product 
org.eclipse.epp.package.php.product -clean

org.eclipse.jface
Error
Wed Nov 28 19:26:07 AEDT 2018
Problems occurred when invoking code from plug-in: "org.eclipse.jface".

java.lang.NoClassDefFoundError: org/eclipse/jdt/core/IJavaElement 
at 
org.jetbrains.kotlin.aspects.navigation.KotlinOpenEditorAspect.ajc$around$org_jetbrains_kotlin_aspects_navigation_KotlinOpenEditorAspect$1$d64491c4(KotlinOpenEditorAspect.aj:17)
 
at 
org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:164)
 
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:279) 
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:244) 
at 
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:271)
 
at 
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:249)
 
at 
org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50) 
at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:216) 
at 
org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
 
at 
org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:46)
 
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:851) 
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) 
at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44) 
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) 
at 
org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:848) 
at 
org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1163)
 
at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:451) 
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:273) 
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:268) 
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:308) 
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) 
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348) 
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348) 
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4602) 
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4183) 
at 
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
 
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) 
at 
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
 
at 
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
 
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680) 
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) 
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594) 
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) 
at 
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
 
at 
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
 
at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
 
at 
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
 
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) 
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:498) 
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) 
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) 
at org.eclipse.equinox.launcher.Main.run(Main.java:1499) 
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
 

RE: update causes problems

[Bill Maidment]

updating udisks2 from sl-rolling fixed it.
Cheers
Bill 
 
-Original message-
> From:Bill Maidment 
> Sent: Tuesday 27th November 2018 15:54
> To: Bill Maidment ; Adam Jensen ; 
> Mailling list for Scientific Linux users worldwide 
> 
> Subject: RE: update causes problems
> 
> Gentoo had a similar problem about a year ago and it was solved with:
> Fixed after upgrading udisks to sys-fs/udisks-2.7.5 and sys-libs/libblockdev 
> as static, and other "helper" fs programs that libblockdev might need. The 
> latter steps probably not necessary. Anyway all functional now.
> 
> Maybe there are some missing updates for similar files.
> Cheers
> Bill
>  
> -Original message-
> > From:Bill Maidment 
> > Sent: Tuesday 27th November 2018 15:36
> > To: Adam Jensen ; Mailling list for Scientific Linux 
> > users worldwide 
> > Subject: RE: update causes problems
> > 
> > Hi again
> > I just tested mounting an SD card from my camera and I get the same error
> > Error mounting /dev/mmcblk0p1 at /run/media/bill/disk: The function 
> > 'bd_fs_mount' called, but not implemented!
> > This worked OK immediately before the update.
> > Cheers
> > Bill 
> >  
> > -Original message-
> > > From:Adam Jensen 
> > > Sent: Tuesday 27th November 2018 10:49
> > > To: Mailling list for Scientific Linux users worldwide 
> > > 
> > > Subject: Re: update causes problems
> > > 
> > > On 11/26/18 6:05 PM, Adam Jensen wrote:
> > > > On 11/26/18 2:48 PM, Akemi Yagi wrote:
> > > >> You need to enable epel-testing like so:
> > > >>
> > > >> yum --enablerepo=epel-testing update
> > > > 
> > > > Thanks!
> > > > 
> > > 
> > > Today's update caused malfunction in the system. Attaching a FAT
> > > formatted USB drive fails with:
> > > 
> > > Error mounting /dev/sdc4 at /run/media/hanzer/MEDIA:
> > > The function 'bd_fs_mount' called, but not implemented!
> > > 
> > > This happens on both updated machines. The USB drive worked yesterday
> > > before the update and it currently still works fine with Ubuntu.
> > > 
> > > 
> > 
> > 
> 
> 

RE: update causes problems

[Bill Maidment]

Gentoo had a similar problem about a year ago and it was solved with:
Fixed after upgrading udisks to sys-fs/udisks-2.7.5 and sys-libs/libblockdev as 
static, and other "helper" fs programs that libblockdev might need. The latter 
steps probably not necessary. Anyway all functional now.

Maybe there are some missing updates for similar files.
Cheers
Bill
 
-Original message-
> From:Bill Maidment 
> Sent: Tuesday 27th November 2018 15:36
> To: Adam Jensen ; Mailling list for Scientific Linux users 
> worldwide 
> Subject: RE: update causes problems
> 
> Hi again
> I just tested mounting an SD card from my camera and I get the same error
> Error mounting /dev/mmcblk0p1 at /run/media/bill/disk: The function 
> 'bd_fs_mount' called, but not implemented!
> This worked OK immediately before the update.
> Cheers
> Bill 
>  
> -Original message-
> > From:Adam Jensen 
> > Sent: Tuesday 27th November 2018 10:49
> > To: Mailling list for Scientific Linux users worldwide 
> > 
> > Subject: Re: update causes problems
> > 
> > On 11/26/18 6:05 PM, Adam Jensen wrote:
> > > On 11/26/18 2:48 PM, Akemi Yagi wrote:
> > >> You need to enable epel-testing like so:
> > >>
> > >> yum --enablerepo=epel-testing update
> > > 
> > > Thanks!
> > > 
> > 
> > Today's update caused malfunction in the system. Attaching a FAT
> > formatted USB drive fails with:
> > 
> > Error mounting /dev/sdc4 at /run/media/hanzer/MEDIA:
> > The function 'bd_fs_mount' called, but not implemented!
> > 
> > This happens on both updated machines. The USB drive worked yesterday
> > before the update and it currently still works fine with Ubuntu.
> > 
> > 
> 
> 

RE: update causes problems

[Bill Maidment]

Hi again
I just tested mounting an SD card from my camera and I get the same error
Error mounting /dev/mmcblk0p1 at /run/media/bill/disk: The function 
'bd_fs_mount' called, but not implemented!
This worked OK immediately before the update.
Cheers
Bill 
 
-Original message-
> From:Adam Jensen 
> Sent: Tuesday 27th November 2018 10:49
> To: Mailling list for Scientific Linux users worldwide 
> 
> Subject: Re: update causes problems
> 
> On 11/26/18 6:05 PM, Adam Jensen wrote:
> > On 11/26/18 2:48 PM, Akemi Yagi wrote:
> >> You need to enable epel-testing like so:
> >>
> >> yum --enablerepo=epel-testing update
> > 
> > Thanks!
> > 
> 
> Today's update caused malfunction in the system. Attaching a FAT
> formatted USB drive fails with:
> 
> Error mounting /dev/sdc4 at /run/media/hanzer/MEDIA:
> The function 'bd_fs_mount' called, but not implemented!
> 
> This happens on both updated machines. The USB drive worked yesterday
> before the update and it currently still works fine with Ubuntu.
> 
> 

RE: update problem with MATE desktop

[Bill Maidment]

Yep it also fixed the multilib issues.
Thanks
Bill
 
 
-Original message-
> From:Gilbert E. Detillieux 
> Sent: Tuesday 27th November 2018 9:47
> To: Orion Poplawski ; Adam Jensen ; 
> scientific-linux-us...@listserv.fnal.gov
> Subject: Re: update problem with MATE desktop
> 
> Enabling epel-testing seemed to do the job on my test system.  All 
> updates are now in.
> 
> Thanks,
> Gilbert
> 
> On 26/11/2018 3:30 p.m., Orion Poplawski wrote:
> > On 11/26/18 12:15 PM, Adam Jensen wrote:
> >> Both of my SL-7.5 systems use the MATE desktop. Today, `yum update`
> >> gives some errors (below). Is there a good way to deal with this that
> >> won't result long-term maintenance problems?
> ...
> > 
> > Looks like there is an update in epel-testing:
> > 
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__bodhi.fedoraproject.org_updates_FEDORA-2DEPEL-2D2018-2D417249babc=DwICaQ=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=Qp7ishAEDrqiuFk0qQxf6M7fqcIAbyh5lzk7RfOcOzM=765FE2sV443sbx3LvfXKbzC1UomkVrDBsd-V8sHbBzo=
> > 
> > so --enablerepo=epel-testing
> 
> -- 
> Gilbert E. Detillieux E-mail: 
> Dept. of Computer Science Web:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cs.umanitoba.ca_-7Egedetil_=DwICaQ=gRgGjJ3BkIsb5y6s49QqsA=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A=H0ybc8YjSEE5HYkDOVSqSE8S9t8uteGlY4EKiCMvry8=9P5qWf2YuB4vEYxvtBId1viPb22Z1xA7P4xRUpnXZdg=
> University of ManitobaPhone:  (204)474-8161
> Winnipeg MB CANADA  R3T 2N2   Fax:(204)474-7609
> 
> 

RE: update problem with MATE desktop

[Bill Maidment]

Hi
I also have this problem and when I tried --skip-broken I got multilib issues


   Protected multilib versions: libblkid-2.23.2-52.el7.i686 != 
libblkid-2.23.2-52.el7_5.1.x86_64
Error: Protected multilib versions: libuuid-2.23.2-52.el7.i686 != 
libuuid-2.23.2-52.el7_5.1.x86_64
Error: Protected multilib versions: libmount-2.23.2-52.el7.i686 != 
libmount-2.23.2-52.el7_5.1.x86_64

 
 
-Original message-
> From:Adam Jensen 
> Sent: Tuesday 27th November 2018 6:15
> To: scientific-linux-us...@listserv.fnal.gov
> Subject: update problem with MATE desktop
> 
> Both of my SL-7.5 systems use the MATE desktop. Today, `yum update`
> gives some errors (below). Is there a good way to deal with this that
> won't result long-term maintenance problems?
> 
> 
> ---> Package libgtop2.x86_64 0:2.34.2-2.el7 will be updated
> --> Processing Dependency: libgtop-2.0.so.10()(64bit) for package:
> mate-system-monitor-1.16.0-1.el7.x86_64
> --> Processing Dependency: libgtop-2.0.so.10()(64bit) for package:
> mate-applets-1.16.0-1.el7.x86_64
> --> Processing Dependency: libgtop-2.0.so.10()(64bit) for package:
> marco-1.16.1-3.el7.x86_64
> --> Processing Dependency: libgtop-2.0.so.10()(64bit) for package:
> mate-disk-usage-analyzer-1.16.1-1.el7.x86_64
> --> Finished Dependency Resolution
> Error: Package: mate-system-monitor-1.16.0-1.el7.x86_64 (@epel)
>Requires: libgtop-2.0.so.10()(64bit)
>Removing: libgtop2-2.34.2-2.el7.x86_64 (@sl)
>libgtop-2.0.so.10()(64bit)
>Updated By: libgtop2-2.38.0-3.el7.x86_64 (sl-security)
>   ~libgtop-2.0.so.11()(64bit)
> Error: Package: marco-1.16.1-3.el7.x86_64 (@epel)
>Requires: libgtop-2.0.so.10()(64bit)
>Removing: libgtop2-2.34.2-2.el7.x86_64 (@sl)
>libgtop-2.0.so.10()(64bit)
>Updated By: libgtop2-2.38.0-3.el7.x86_64 (sl-security)
>   ~libgtop-2.0.so.11()(64bit)
> Error: Package: mate-applets-1.16.0-1.el7.x86_64 (@epel)
>Requires: libgtop-2.0.so.10()(64bit)
>Removing: libgtop2-2.34.2-2.el7.x86_64 (@sl)
>libgtop-2.0.so.10()(64bit)
>Updated By: libgtop2-2.38.0-3.el7.x86_64 (sl-security)
>   ~libgtop-2.0.so.11()(64bit)
> Error: Package: mate-disk-usage-analyzer-1.16.1-1.el7.x86_64 (@epel)
>Requires: libgtop-2.0.so.10()(64bit)
>Removing: libgtop2-2.34.2-2.el7.x86_64 (@sl)
>libgtop-2.0.so.10()(64bit)
>Updated By: libgtop2-2.38.0-3.el7.x86_64 (sl-security)
>   ~libgtop-2.0.so.11()(64bit)
>  You could try using --skip-broken to work around the problem
>  You could try running: rpm -Va --nofiles --nodigest
> 
> 

RE: Security ERRATA Important: kernel on SL6.x i386/x86_64

[Bill Maidment]

Thanks Akemi (and Johnny)
Changing the SL6 CPU to Opteron-G3 worked like a charm.
Cheers
Bill
 
-Original message-
> From:Akemi Yagi 
> Sent: Tuesday 12th June 2018 8:43
> To: Bill Maidment 
> Cc: scientific-linux-us...@listserv.fnal.gov 
> ; 
> scientific-linux-err...@listserv.fnal.gov 
> 
> Subject: Re: Security ERRATA Important: kernel on SL6.x i386/x86_64
> 
> On Tue, May 22, 2018 at 7:20 PM, Bill Maidment  wrote:
> > Hi
> > The new kernel caused
> > PANIC early exception 0d 10 . error 0 rc2
> > on a KVM SL 6.9 x86_64 guest
> > AMD server and all other guests running SL7.5 are all runn ing OK on their 
> > new kernel
> >
> > Reverting to the previous SL 6.9 kernel gave me back my guest machine
> > Cheers
> > Bill
> 
> This is a known bug. There is a workaround. For more details, see this
> post from Johnny Hughes:
> 
> https://lists.centos.org/pipermail/centos/2018-June/169058.html
> 
> Akemi
> 
> 

RE: Python-urllib3 package is corrupt on rsync

[Bill Maidment]

But first.
I found a pile of directories from the attempts to install python-urllib3. I 
deleted them all
rm -fr /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname*
(dangerous, I know)
and the rpm then installed OK.

Hopefully, that is the end of that problem. Now for the other one.
Cheers
Bill
 
-Original message-
> From:Bill Maidment <b...@maidment.me>
> Sent: Saturday 26th May 2018 16:52
> To: Akemi Yagi <amy...@gmail.com>; SCIENTIFIC-LINUX-USERS@FNAL.GOV 
> <SCIENTIFIC-LINUX-USERS@fnal.gov>
> Subject: RE: Python-urllib3 package is corrupt on rsync
> 
> Thanks Akemi
> I am getting the same hash value as you, so it doesn't appear to be the rpm 
> that is at fault.
> I have tried yum reinstall of yum* and rpm* without solving the issue.
> As this is on another KVM guest on the machine on which I had an unrelated 
> unsolved error, I think I may have a hardware problem.
> Time for the memory test.
> Cheers
> Bill
>  
> -Original message-
> > From:Akemi Yagi <amy...@gmail.com>
> > Sent: Saturday 26th May 2018 15:03
> > To: SCIENTIFIC-LINUX-USERS@FNAL.GOV <SCIENTIFIC-LINUX-USERS@fnal.gov>
> > Subject: Re: Python-urllib3 package is corrupt on rsync
> > 
> > On Fri, May 25, 2018 at 8:53 PM, Bill Maidment <b...@maidment.me> wrote:
> > > In SL7x I tried to install python-urllib3 and got this error, even after 
> > > deleting it from my repository and rsyncing again.
> > >
> > >   Installing : python-urllib3-1.10.2-5.el7.noarch 
> > >  1/1
> > > Error unpacking rpm package python-urllib3-1.10.2-5.el7.noarch
> > > error: unpacking of archive failed on file 
> > > /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname: 
> > > cpio: rename
> > >   Verifying  : python-urllib3-1.10.2-5.el7.noarch 
> > >  1/1
> > >
> > > Failed:
> > >   python-urllib3.noarch 0:1.10.2-5.el7
> > >
> > > Cheers
> > > Bill Maidment
> > 
> > I just tried and was able to install
> > python-urllib3-1.10.2-5.el7.noarch without any issue.
> > 
> > You may want to check the file you have rsynced by comparing it
> > against the original file. For example:
> > 
> > $ sha256sum python-urllib3-1.10.2-5.el7.noarch.rpm
> > ef4067425a59ec50a9a201a94e408f13dc7b021ca8950249eaf047f084b1e606
> > python-urllib3-1.10.2-5.el7.noarch.rpm
> > 
> > Checking the hash value is one way to verify the file's integrity.
> > 
> > Akemi
> > 
> > 
> 
> 

RE: Python-urllib3 package is corrupt on rsync

[Bill Maidment]

Thanks Akemi
I am getting the same hash value as you, so it doesn't appear to be the rpm 
that is at fault.
I have tried yum reinstall of yum* and rpm* without solving the issue.
As this is on another KVM guest on the machine on which I had an unrelated 
unsolved error, I think I may have a hardware problem.
Time for the memory test.
Cheers
Bill
 
-Original message-
> From:Akemi Yagi <amy...@gmail.com>
> Sent: Saturday 26th May 2018 15:03
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV <SCIENTIFIC-LINUX-USERS@fnal.gov>
> Subject: Re: Python-urllib3 package is corrupt on rsync
> 
> On Fri, May 25, 2018 at 8:53 PM, Bill Maidment <b...@maidment.me> wrote:
> > In SL7x I tried to install python-urllib3 and got this error, even after 
> > deleting it from my repository and rsyncing again.
> >
> >   Installing : python-urllib3-1.10.2-5.el7.noarch   
> >1/1
> > Error unpacking rpm package python-urllib3-1.10.2-5.el7.noarch
> > error: unpacking of archive failed on file 
> > /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname: cpio: 
> > rename
> >   Verifying  : python-urllib3-1.10.2-5.el7.noarch   
> >1/1
> >
> > Failed:
> >   python-urllib3.noarch 0:1.10.2-5.el7
> >
> > Cheers
> > Bill Maidment
> 
> I just tried and was able to install
> python-urllib3-1.10.2-5.el7.noarch without any issue.
> 
> You may want to check the file you have rsynced by comparing it
> against the original file. For example:
> 
> $ sha256sum python-urllib3-1.10.2-5.el7.noarch.rpm
> ef4067425a59ec50a9a201a94e408f13dc7b021ca8950249eaf047f084b1e606
> python-urllib3-1.10.2-5.el7.noarch.rpm
> 
> Checking the hash value is one way to verify the file's integrity.
> 
> Akemi
> 
> 

Python-urllib3 package is corrupt on rsync

[Bill Maidment]

In SL7x I tried to install python-urllib3 and got this error, even after 
deleting it from my repository and rsyncing again.

  Installing : python-urllib3-1.10.2-5.el7.noarch   1/1 
Error unpacking rpm package python-urllib3-1.10.2-5.el7.noarch
error: unpacking of archive failed on file 
/usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname: cpio: 
rename
  Verifying  : python-urllib3-1.10.2-5.el7.noarch   1/1 

Failed:
  python-urllib3.noarch 0:1.10.2-5.el7  

Cheers
Bill Maidment

RE: [SCIENTIFIC-LINUX-USERS] Security ERRATA Important: kernel on SL6.x i386/x86_64

[Bill Maidment]

Hi Pat
Thanks for your suggestions.

confirmed memory is 2048MB
tried numa=off
confirmed virtio and qxl
confirmed BIOS is F8

I'll try resetting BIOS and doing a memory test over the weekend.

I have an SL7.5 guest which I am setting up with Kolab, so I will probably 
switch to that soon and ditch SL6.9

Thanks again for spending time on this.
Cheers
Bill
 
-Original message-
> From:Pat Riehecky <riehe...@fnal.gov>
> Sent: Friday 25th May 2018 6:11
> To: Bill Maidment <b...@maidment.me>; scientific-linux-us...@listserv.fnal.gov
> Subject: Re: [SCIENTIFIC-LINUX-USERS] Security ERRATA Important: kernel on 
> SL6.x i386/x86_64
> 
> H this error seems to point to a memory/instruction mapping 
> issue.
> 
>   Do you have a base8 amount of RAM in the VMs?
>   Can I have you try adding 'numa=off' to the boot line?
>   Are things using virtio/qxl/etc?
> 
> 
> While I doubt this is it, you may want to be sure you've got the F8 
> bios[1].  If you can I'd consider setting the values back to defaults 
> and then re-activating the hardware VM acceleration after that.
> 
> Pat
> 
> [1] https://www.gigabyte.com/Motherboard/GA-990FXA-D3-rev-1x#support-dl-bios
> 
> On 05/24/2018 12:40 AM, Bill Maidment wrote:
> > Hi Pat
> > The full error message is:
> > PANIC: early exception 0d rip 10:810462b6 error 0 cr2 0
> >
> > These are my specs:
> >
> > Mobo GA-990FXA-D3
> > CPU AMD FX-8120
> > Host 8 CPU 16GB RAM running SL 7.5 with kernel 3.10.0-862.3.2
> > Guest 2 CPU 2GB RAM running SL 6.9 with kernel 2.6.32.30.1
> > 5 other guests running SL 7.5 with kernel 3.10.0-862.3.2 run OK
> >
> > SL 6.9 kernel re-installed but still the same error
> > previous kernel 2.6.32-696.28.1 runs OK
> >
> > The SL 6.9 machine is my internal mail server running zarafa and mysql
> >
> > Is there anything else you need to know?
> >
> > Cheers
> > Bill
> >
> >   
> >   
> > -Original message-
> >> From:Pat Riehecky <riehe...@fnal.gov>
> >> Sent: Wednesday 23rd May 2018 23:25
> >> To: Bill Maidment <b...@maidment.me>; 
> >> scientific-linux-us...@listserv.fnal.gov
> >> Subject: Re: [SCIENTIFIC-LINUX-USERS] Security ERRATA Important: kernel on 
> >> SL6.x i386/x86_64
> >>
> >> Hi Bill,
> >>
> >> Our internal test VMs are KVM guests on SL 6.9 with an AMD server. I'm
> >> not seeing this problem there.
> >>
> >> Are there any more details you can share?
> >>
> >> Pat
> >>
> >> On 05/22/2018 09:20 PM, Bill Maidment wrote:
> >>> Hi
> >>> The new kernel caused
> >>> PANIC early exception 0d 10 . error 0 rc2
> >>> on a KVM SL 6.9 x86_64 guest
> >>> AMD server and all other guests running SL7.5 are all runn ing OK on 
> >>> their new kernel
> >>>
> >>> Reverting to the previous SL 6.9 kernel gave me back my guest machine
> >>> Cheers
> >>> Bill
> >>> 
> >>> 
> >>> -Original message-
> >>>> From:Scott Reid <svr...@fnal.gov>
> >>>> Sent: Wednesday 23rd May 2018 4:33
> >>>> To: scientific-linux-err...@listserv.fnal.gov
> >>>> Subject: Security ERRATA Important: kernel on SL6.x i386/x86_64
> >>>>
> >>>> Synopsis:  Important: kernel security and bug fix update
> >>>> Advisory ID:   SLSA-2018:1651-1
> >>>> Issue Date:    2018-05-22
> >>>> CVE Numbers:   CVE-2018-3639
> >>>> --
> >>>>
> >>>> Security Fix(es):
> >>>>
> >>>> * An industry-wide issue was found in the way many modern microprocessor
> >>>> designs have implemented speculative execution of Load & Store
> >>>> instructions (a commonly used performance optimization). It relies on the
> >>>> presence of a precisely-defined instruction sequence in the privileged
> >>>> code as well as the fact that memory read from address to which a recent
> >>>> memory write has occurred may see an older value and subsequently cause 
> >>>> an
> >>>> update into the microprocessor's data cache even for speculatively
> >>>> executed instructions that never actually commit (retire). As a result, 
> >>>> an
> >>>> unprivileged attacker could use this flaw to read privileged memory by
> >>>> conducting targeted cache side-channe

RE: [SCIENTIFIC-LINUX-USERS] Security ERRATA Important: kernel on SL6.x i386/x86_64

[Bill Maidment]

Hi Pat
The full error message is:
PANIC: early exception 0d rip 10:810462b6 error 0 cr2 0

These are my specs:

Mobo GA-990FXA-D3
CPU AMD FX-8120
Host 8 CPU 16GB RAM running SL 7.5 with kernel 3.10.0-862.3.2
Guest 2 CPU 2GB RAM running SL 6.9 with kernel 2.6.32.30.1
5 other guests running SL 7.5 with kernel 3.10.0-862.3.2 run OK

SL 6.9 kernel re-installed but still the same error
previous kernel 2.6.32-696.28.1 runs OK

The SL 6.9 machine is my internal mail server running zarafa and mysql

Is there anything else you need to know?

Cheers
Bill

 
 
-Original message-
> From:Pat Riehecky <riehe...@fnal.gov>
> Sent: Wednesday 23rd May 2018 23:25
> To: Bill Maidment <b...@maidment.me>; scientific-linux-us...@listserv.fnal.gov
> Subject: Re: [SCIENTIFIC-LINUX-USERS] Security ERRATA Important: kernel on 
> SL6.x i386/x86_64
> 
> Hi Bill,
> 
> Our internal test VMs are KVM guests on SL 6.9 with an AMD server. I'm 
> not seeing this problem there.
> 
> Are there any more details you can share?
> 
> Pat
> 
> On 05/22/2018 09:20 PM, Bill Maidment wrote:
> > Hi
> > The new kernel caused
> > PANIC early exception 0d 10 . error 0 rc2
> > on a KVM SL 6.9 x86_64 guest
> > AMD server and all other guests running SL7.5 are all runn ing OK on their 
> > new kernel
> >
> > Reverting to the previous SL 6.9 kernel gave me back my guest machine
> > Cheers
> > Bill
> >   
> >   
> > -Original message-
> >> From:Scott Reid <svr...@fnal.gov>
> >> Sent: Wednesday 23rd May 2018 4:33
> >> To: scientific-linux-err...@listserv.fnal.gov
> >> Subject: Security ERRATA Important: kernel on SL6.x i386/x86_64
> >>
> >> Synopsis:  Important: kernel security and bug fix update
> >> Advisory ID:   SLSA-2018:1651-1
> >> Issue Date:    2018-05-22
> >> CVE Numbers:   CVE-2018-3639
> >> --
> >>
> >> Security Fix(es):
> >>
> >> * An industry-wide issue was found in the way many modern microprocessor
> >> designs have implemented speculative execution of Load & Store
> >> instructions (a commonly used performance optimization). It relies on the
> >> presence of a precisely-defined instruction sequence in the privileged
> >> code as well as the fact that memory read from address to which a recent
> >> memory write has occurred may see an older value and subsequently cause an
> >> update into the microprocessor's data cache even for speculatively
> >> executed instructions that never actually commit (retire). As a result, an
> >> unprivileged attacker could use this flaw to read privileged memory by
> >> conducting targeted cache side-channel attacks. (CVE-2018-3639)
> >>
> >> Note: This issue is present in hardware and cannot be fully fixed via
> >> software update. The updated kernel packages provide software side of the
> >> mitigation for this hardware issue. To be fully functional, up-to-date CPU
> >> microcode applied on the system is required.
> >>
> >> In this update mitigations for x86 (both 32 and 64 bit) architecture are
> >> provided.
> >>
> >> Bug Fix(es):
> >>
> >> * Previously, an erroneous code in the x86 kexec system call path caused a
> >> memory corruption. As a consequence, the system became unresponsive with
> >> the following kernel stack trace:
> >>
> >> 'WARNING: CPU: 13 PID: 36409 at lib/list_debug.c:59
> >> __list_del_entry+0xa1/0xd0 list_del corruption. prev->next should be
> >> dd03fddeeca0, but was (null)'
> >>
> >> This update ensures that the code does not corrupt memory. As a result,
> >> the operating system no longer hangs.
> >> --
> >>
> >> SL6
> >>    x86_64
> >>      kernel-2.6.32-696.30.1.el6.x86_64.rpm
> >>      kernel-debug-2.6.32-696.30.1.el6.x86_64.rpm
> >>      kernel-debug-debuginfo-2.6.32-696.30.1.el6.i686.rpm
> >>      kernel-debug-debuginfo-2.6.32-696.30.1.el6.x86_64.rpm
> >>      kernel-debug-devel-2.6.32-696.30.1.el6.i686.rpm
> >>      kernel-debug-devel-2.6.32-696.30.1.el6.x86_64.rpm
> >>      kernel-debuginfo-2.6.32-696.30.1.el6.i686.rpm
> >>      kernel-debuginfo-2.6.32-696.30.1.el6.x86_64.rpm
> >>      kernel-debuginfo-common-i686-2.6.32-696.30.1.el6.i686.rpm
> >>      kernel-debuginfo-common-x86_64-2.6.32-696.30.1.el6.x86_64.rpm
> >>      kernel-devel-2.6.32-696.30.1.el6.x86_64.rpm
> >>      kernel-headers-2.6.32-696.30.1.el6.x86_64.rpm
> >>      perf-2.

RE: Security ERRATA Important: kernel on SL6.x i386/x86_64

[Bill Maidment]

Hi
The new kernel caused
PANIC early exception 0d 10 . error 0 rc2
on a KVM SL 6.9 x86_64 guest
AMD server and all other guests running SL7.5 are all runn ing OK on their new 
kernel

Reverting to the previous SL 6.9 kernel gave me back my guest machine
Cheers
Bill
 
 
-Original message-
> From:Scott Reid 
> Sent: Wednesday 23rd May 2018 4:33
> To: scientific-linux-err...@listserv.fnal.gov
> Subject: Security ERRATA Important: kernel on SL6.x i386/x86_64
> 
> Synopsis:  Important: kernel security and bug fix update
> Advisory ID:   SLSA-2018:1651-1
> Issue Date:    2018-05-22
> CVE Numbers:   CVE-2018-3639
> --
> 
> Security Fix(es):
> 
> * An industry-wide issue was found in the way many modern microprocessor
> designs have implemented speculative execution of Load & Store
> instructions (a commonly used performance optimization). It relies on the
> presence of a precisely-defined instruction sequence in the privileged
> code as well as the fact that memory read from address to which a recent
> memory write has occurred may see an older value and subsequently cause an
> update into the microprocessor's data cache even for speculatively
> executed instructions that never actually commit (retire). As a result, an
> unprivileged attacker could use this flaw to read privileged memory by
> conducting targeted cache side-channel attacks. (CVE-2018-3639)
> 
> Note: This issue is present in hardware and cannot be fully fixed via
> software update. The updated kernel packages provide software side of the
> mitigation for this hardware issue. To be fully functional, up-to-date CPU
> microcode applied on the system is required.
> 
> In this update mitigations for x86 (both 32 and 64 bit) architecture are
> provided.
> 
> Bug Fix(es):
> 
> * Previously, an erroneous code in the x86 kexec system call path caused a
> memory corruption. As a consequence, the system became unresponsive with
> the following kernel stack trace:
> 
> 'WARNING: CPU: 13 PID: 36409 at lib/list_debug.c:59
> __list_del_entry+0xa1/0xd0 list_del corruption. prev->next should be
> dd03fddeeca0, but was (null)'
> 
> This update ensures that the code does not corrupt memory. As a result,
> the operating system no longer hangs.
> --
> 
> SL6
>   x86_64
>     kernel-2.6.32-696.30.1.el6.x86_64.rpm
>     kernel-debug-2.6.32-696.30.1.el6.x86_64.rpm
>     kernel-debug-debuginfo-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debug-debuginfo-2.6.32-696.30.1.el6.x86_64.rpm
>     kernel-debug-devel-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debug-devel-2.6.32-696.30.1.el6.x86_64.rpm
>     kernel-debuginfo-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debuginfo-2.6.32-696.30.1.el6.x86_64.rpm
>     kernel-debuginfo-common-i686-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debuginfo-common-x86_64-2.6.32-696.30.1.el6.x86_64.rpm
>     kernel-devel-2.6.32-696.30.1.el6.x86_64.rpm
>     kernel-headers-2.6.32-696.30.1.el6.x86_64.rpm
>     perf-2.6.32-696.30.1.el6.x86_64.rpm
>     perf-debuginfo-2.6.32-696.30.1.el6.i686.rpm
>     perf-debuginfo-2.6.32-696.30.1.el6.x86_64.rpm
>     python-perf-debuginfo-2.6.32-696.30.1.el6.i686.rpm
>     python-perf-debuginfo-2.6.32-696.30.1.el6.x86_64.rpm
>     python-perf-2.6.32-696.30.1.el6.x86_64.rpm
>   i386
>     kernel-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debug-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debug-debuginfo-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debug-devel-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debuginfo-2.6.32-696.30.1.el6.i686.rpm
>     kernel-debuginfo-common-i686-2.6.32-696.30.1.el6.i686.rpm
>     kernel-devel-2.6.32-696.30.1.el6.i686.rpm
>     kernel-headers-2.6.32-696.30.1.el6.i686.rpm
>     perf-2.6.32-696.30.1.el6.i686.rpm
>     perf-debuginfo-2.6.32-696.30.1.el6.i686.rpm
>     python-perf-debuginfo-2.6.32-696.30.1.el6.i686.rpm
>     python-perf-2.6.32-696.30.1.el6.i686.rpm
>   noarch
>     kernel-abi-whitelists-2.6.32-696.30.1.el6.noarch.rpm
>     kernel-doc-2.6.32-696.30.1.el6.noarch.rpm
>     kernel-firmware-2.6.32-696.30.1.el6.noarch.rpm
> 
> - Scientific Linux Development Team
> 
> 

Problem with yum daily cron

[Bill Maidment]

All my servers are showing this today:

/etc/cron.daily/0yum-daily.cron:

Update notice SLEA-2017:1977-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
You should report this problem to the owner of the sl-security repository.
If you are the owner, consider re-running the same command with --verbose to 
see the exact data that caused the conflict.


Cheers
Bill Maidment

RE: Multiple Vulnerabilities in PHP Could Allow for Arbitrary Code Execution

[Bill Maidment]

SL7.5 has a newer version 5.4.16-45.el7 which may have the fixes backported.
Cheers
Bill
 
 
-Original message-
> From:Jon Brinkmann 
> Sent: Saturday 28th April 2018 12:19
> To: scientific-linux-us...@listserv.fnal.gov
> Subject: Multiple Vulnerabilities in PHP Could Allow for Arbitrary Code 
> Execution
> 
> See 
> https://www.cisecurity.org/advisory/multiple-vulnerabilities-in-php-could-allow-for-arbitrary-code-execution_2018-046/
> 
> This is the second warning in as many months.  The current version of PHP
> distributed with SL 7.4 is "PHP 5.4.16 (cli) (built: Mar  7 2018 12:48:25)"
> which is vulnerable.  Are there plans to distribute version 5.6.36 or
> newer anytime soon?
> 
> Jon
> 
> 

RE: Problem recreating grub2 menu in SL7 dual boot with Win10

[Bill Maidment]

> From:Nico Kadel-Garcia <nka...@gmail.com>
> Sent: Wednesday 24th January 2018 23:55
> To: Bill Maidment <b...@maidment.me>
> Cc: R P Herrold <herr...@owlriver.com>; SCIENTIFIC-LINUX-USERS@FNAL.GOV 
> <SCIENTIFIC-LINUX-USERS@fnal.gov>
> Subject: Re: Problem recreating grub2 menu in SL7 dual boot with Win10
> 
> On Wed, Jan 24, 2018 at 4:22 AM, Bill Maidment <b...@maidment.me> wrote:
> > All sorted.
> > The second USB stick worked OK before doing the chroot.
> 
> Good. I was wondering why the first stick didn't have network enabled
> when it booted. Not all drivers work perfectly from some USB sticks
> and the minimal kernel present on them, but I've certainly used them
> myself to do recovery work.

The first USB stick was used to boot, but wireless network didn't work. I 
didn't try wired network. It could have been I was trying to use the network 
within chroot.
The second USB stick was used in addition to the first, to convey the fastbugs 
rpm files I needed. That was successful, but then I found the boot partition 
had been corrupted, so I reinstalled SL7 again and recovered my data from 
backuppc.
An interesting learning experience.

> 
> I'm trying to figure out why you're doing dual boot. Does the Windows
> box not have enough resources to run VirtualBox, and run your working
> Linux in a VM ? I've found that very useful for development work,
> since Steam doesn't work as well on Linux boxes to give access to
> games I might like to play with all resources available.
> 

I'm using dual boot rather than VirtualBox because I find the idea of running 
Linux under Windows abhorrent.
I may eventually rebuild the laptop as SL7 only.

Anyway, thanks for your suggestions Nico.

RE: Problem recreating grub2 menu in SL7 dual boot with Win10

[Bill Maidment]

All sorted.
The second USB stick worked OK before doing the chroot.
 
-Original message-
> From:Bill Maidment 
> Sent: Wednesday 24th January 2018 17:17
> To: R P Herrold 
> Cc: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: RE: Problem recreating grub2 menu in SL7 dual boot with Win10
> 
> Thanks for your response
> 
> > Packages are partitioned into a main and sub-packages, so that 
> > the bloat of un-needed matter is avoided.  UEFI is relatively 
> > new, and until Windows 10, not really mandated by Microsoft 
> > installations.  Also the needed hardware (a TPM chip) was not 
> > universally present, and so that sub-package would seem to be 
> > bloat to most people
> 
> Understood.
> 
> > As to how to get a copy, using an second machine to retrieve 
> > the needed package, and placing it on a data stick comes to  
> > mind.
> 
> But how to get it into the system that can only be booted in rescue mode from 
> my USB stick?
> I will try using a second USB stick
> 
> Cheers
> Bill
> 
> 

Problem recreating grub2 menu in SL7 dual boot with Win10

[Bill Maidment]

Hi
In fear and trepidation I ran a BIOS update on my Acer Aspire A515-51G from the 
Win10 part of my dual boot (only Win10 can update the BIOS). On reboot, all I 
get is Win10 (Surprise! Surprise!).
So I booted into an SL7.4 USB recovery mode with chroot /mnt/sysimage and tried 
grub2-install /dev/sda only to be told /usr/lib/grub/x86_64-efi/modinfo.sh 
doesn't exist.
It appears that I need to do yum install grub2-efi-modules (why wasn't this 
done before? I ask).
Anyway, how do I install this while in rescue mode, which doesn't seem to have 
network access? Or is there a network enabling option for rescue mode (like 
there was in SystemRescueCD)?
Am I being dense in my old age?

Cheers
Bill Maidment

RE: EFI installation of SL 7.4

[Bill Maidment]

A bit more Googling provided the answer.
There is a magic touch in Acer laptops. You have to set an administrator 
password in the bios before you are allowed to disable secure boot.
I can now dual boot (using the windows boot manager). The rest should be plain 
sailing now.
Cheers
Bill
 
-Original message-
> From:Eero Volotinen <eero.voloti...@iki.fi>
> Sent: Tuesday 2nd January 2018 15:21
> To: Bill Maidment <b...@maidment.me>
> Cc: SCIENTIFIC-LINUX-USERS@FNAL.GOV <SCIENTIFIC-LINUX-USERS@fnal.gov>
> Subject: RE: EFI installation of SL 7.4
> 
> I have never seen hardware without possibility to disable secureboot.   
> 
> UBuntu works with secureboot. try it first?
> 
> Eero 
> 
> 2.1.2018 5.20 "Bill Maidment" <b...@maidment.me <mailto:b...@maidment.me>> 
> kirjoitti:Thanks. I thought that might be the answer.
 
> Unfortunately, the bios (version 1.10) will not let me disable secure boot.
 
> Maybe an older bios will?
 
> 
 
> 
 
> -Original message-
 
> > From:Eero Volotinen <eero.voloti...@iki.fi <mailto:eero.voloti...@iki.fi>>
 
> > Sent: Tuesday 2nd January 2018 13:33
 
> > To: Bill Maidment <b...@maidment.me <mailto:b...@maidment.me>>
 
> > Cc: SCIENTIFIC-LINUX-USERS@FNAL.GOV 
> > <mailto:SCIENTIFIC-LINUX-USERS@FNAL.GOV> <SCIENTIFIC-LINUX-USERS@fnal.gov 
> > <mailto:SCIENTIFIC-LINUX-USERS@fnal.gov>>
 
> > Subject: Re: EFI installation of SL 7.4
 
> >
 
> > enable uefi on bios and disable secure boot.
 
> >
 
> > Eero
 
> >
 
> > 2.1.2018 4.25 "Bill Maidment" <b...@maidment.me <mailto:b...@maidment.me> 
> > <mailto:b...@maidment.me <mailto:b...@maidment.me>>> kirjoitti: > type="attribution" />Happy New Year everyone.
 
> 
 
> > I am now an owner of an Acer A515-51G laptop and Im trying to install SL 
> > 7.4 in EFI mode dual boot with Win 10.
 
> 
 
> > After lots of experiments I was only able to install in legacy mode, but 
> > that locked me out of Win 10.
 
> 
 
> > I am trying to run mokutil, but I get an error as follows:
 
> 
 
> > mokutil --import 
> > /etc/pki/secure-boot/SECURE-BOOT-KEY-fnal-sl7-exp-2020-08-26
 
> 
 
> > EFI variables are not supported on this system
 
> 
 
> > Elsewhere, it was suggested to do modprobe efivars, but efivars does not 
> > appear to be available.
 
> 
 
> > Any suggestions as to what to do next?
 
> 
 
> >
 
> 
 
> > Cheers
 
> 
 
> > Bill Maidment
 
> 
 
> 

EFI installation of SL 7.4

[Bill Maidment]

Happy New Year everyone.
I am now an owner of an Acer A515-51G laptop and I'm trying to install SL 7.4 
in EFI mode dual boot with Win 10.
After lots of experiments I was only able to install in legacy mode, but that 
locked me out of Win 10.
I am trying to run mokutil, but I get an error as follows:
mokutil --import /etc/pki/secure-boot/SECURE-BOOT-KEY-fnal-sl7-exp-2020-08-26
EFI variables are not supported on this system
Elsewhere, it was suggested to do modprobe efivars, but efivars does not appear 
to be available.
Any suggestions as to what to do next?

Cheers
Bill Maidment

RE: Rage against the EL Machine

[Bill Maidment]

Can we stop this dumb thread. It's so boring and unhelpful.
Or at least take it private.

Cheers
Bill
 
-Original message-
> From:ToddAndMargo 
> Sent: Thursday 9th November 2017 12:07
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV 
> Subject: Re: Rage against the EL Machine
> 
> On 11/08/2017 03:52 PM, O'Neal, Miles wrote:
> > I'm not real sure what this discussion has to do with Scientific Linux, 
> > but I'll give this a shot.
> > 
> > On 11/08/2017 05:25 PM, ToddAndMargo wrote:
> >>
> >> I can't afford to have my Contacts and Tasks wiped out
> >> by the OS being too out of date to accept fixes and
> >> an OS vendor that won't fix it.  So it works both ways.
> > RedHat is quite up front about the point of RHEL, which is long term 
> > stability and support. EL is NOT about being anywhere even close to 
> > leading edge, much less bleeding edge. If you buy a heavy duty pickup 
> > truck, you do not get (and should not expect) sports car performance.
> > 
> > We use EL for both servers and workstations in hardware design[1] (and 
> > we are not alone in this). That's because that's what the third party 
> > tools support. There is no way those vendors can validate complex tool 
> > chains against a new build every six months. Yes, we are frustrated that 
> > we can't use the latest email client, web browser, or aardvarkial 
> > sanitization discomboobulator, but it comes with the turf. Conversely, 
> > many software groups prefer something that is very up to date, such as 
> > Fedora, Ubuntu, etc. They need a sports car, and recognize they can't 
> > haul a half ton microscope in it.
> > 
> > And you know what? For the job they really need to do (all sorts of 
> > things around hardware design and basic business and communication 
> > functions), the EL-based workstations work great.
> >>
>  And you know the Cxxx series of chipsets have been around
>  for a while now.  Just not long enough to be out of
>  production at which point it will appear on Red Hat
>  compatibility list.
> >>>
> >>> Nonsense. Our friends over at Red Hat are continuously supporting
> >>> leading edge *server* hardware. 
> >>
> >> Niko!  The C236 chipset *IS* a server grade chipset!
> >> And it has been around for a long time.  No doubt Red Hat
> >> will eventually support it in about five years, which is
> >> typical of them and useless to me.
> >>
> > Actually, it was meant to be a consumer and workstation chipset. While 
> > it is based on a server chipset, it's been somewhat gutted. But either 
> > way, unless the hardware vendor partners with RedHat, the latter is 
> > unlikely to support it. Should vendor be yelling at you if your employer 
> > got caught in a Congressional budget crunch and couldn't pay for massive 
> > magnets? No, because that's not how it works.
> 
> Intel does classify it as a "server grade" chipset.  It is
> meant low end model meant for small business servers and
> top reliability workstations.
> 
> > ...
> >>
> >> My problem is that I have been trying to pound a square peg
> >> into a round hole.  RHEL is a really poor choice for a system
> >> that has a lot of innovation going on on it.
> > 
> > It does sound like you're trying to pound a square peg into a round 
> > hole, but it's not the peg's fault. One must pick the right peg for the 
> > hole that needs to be filled.
> > 
> > -Miles
> 
> RHEL and Clones is best not used as a workstation, unless the
> software yo are going to run on it expressly support out-of-date
> operating system or software that currently work and your intention
> is to freeze it.  And can do such with any OS by turning of
> the updates.
> 
> In my case, the software I run requires the OS to keep on top
> of things.  Having my business' Tasks and Contacts deleted
> and the OS not supporting the patch is a *total annoyance*.
> 
> And it is my fault for choosing an OS that is out-of-date
> by design.  Square peg, round hole.
> 
> 

RE: EPEL Download

[Bill Maidment]

I've found a new directory in x86_64 called Packages which seems to be a 
duplicate of the x86_64 directory
So it now takes up twice  the space.
 
-Original message-
> From:Steven C Timm <t...@fnal.gov>
> Sent: Monday 30th October 2017 13:06
> To: Bill Maidment <b...@maidment.me>; ~Stack~ <i.am.st...@gmail.com>; 
> scientific-linux-users <scientific-linux-users@fnal.gov>
> Subject: Re: EPEL Download
> 
> I see the a/b/c/ and so forth in the 7 directories but not in the 6 
> directories.
 
> Can't tell you if the 7 directories always were that way or not. 
> 
 
> Steve Timm 
> --- 
> From: owner-scientific-linux-us...@listserv.fnal.gov 
> <owner-scientific-linux-us...@listserv.fnal.gov> on behalf of Bill Maidment 
> <b...@maidment.me>
 
> Sent: Sunday, October 29, 2017 8:24:07 PM
 
> To: ~Stack~; scientific-linux-users
 
> Subject: RE: EPEL Download
 
> It looks like they deleted everything and added an extra level 2 3 4 a b c 
> etc or has it always been like that?
 
> I only mirror 6/7 x64
 
> Cheers
 
> Bill
 
>  
 
>  
 
> -Original message-
 
> > From:~Stack~ <i.am.st...@gmail.com>
 
> > Sent: Monday 30th October 2017 12:08
 
> > To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
 
> > Subject: Re: EPEL Download
 
> > 
 
> > On 10/29/2017 07:49 PM, Bill Maidment wrote:
 
> > > Hi
 
> > > Today I found out that EPEL had reorganized their repository structure 
> > > without warning.
 
> > > A 26 GB download ensued. Ouch. That's a quarter of my monthly quota.
 
> > 
 
> > I too mirror for my site, but I only mirror x86_64 for 6/7. I haven't
 
> > checked yet my mirror yet...what changed? I don't see anything obvious
 
> > looking at my upstream mirror.
 
> > 
 
> > ~Stack~
 
> > 
 
> > 
 

RE: EPEL Download

[Bill Maidment]

It looks like they deleted everything and added an extra level 2 3 4 a b c etc 
or has it always been like that?
I only mirror 6/7 x64
Cheers
Bill
 
 
-Original message-
> From:~Stack~ <i.am.st...@gmail.com>
> Sent: Monday 30th October 2017 12:08
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: Re: EPEL Download
> 
> On 10/29/2017 07:49 PM, Bill Maidment wrote:
> > Hi
> > Today I found out that EPEL had reorganized their repository structure 
> > without warning.
> > A 26 GB download ensued. Ouch. That's a quarter of my monthly quota.
> 
> I too mirror for my site, but I only mirror x86_64 for 6/7. I haven't
> checked yet my mirror yet...what changed? I don't see anything obvious
> looking at my upstream mirror.
> 
> ~Stack~
> 
> 

EPEL Download

[Bill Maidment]

Hi
Today I found out that EPEL had reorganized their repository structure without 
warning.
A 26 GB download ensued. Ouch. That's a quarter of my monthly quota.

Cheers
Bill Maidment

RE: emacs on SL6 - was Re: Security ERRATA Important: emacs on SL7.x x86_64

[Bill Maidment]

Hi Andrew
So much for security issue support for 10 years. Probably best to assume only 7 
years in real life.
This is why I'm switching all our users over to SL7 MATE, now that SL6 is in 
its final phase.
Cheers
Bill
 
 
-Original message-
> From:Andrew C Aitchison 
> Sent: Wednesday 20th September 2017 16:32
> To: scientific-linux-us...@listserv.fnal.gov
> Subject: emacs on SL6 - was Re: Security ERRATA Important: emacs on SL7.x 
> x86_64
> 
> On Tue, 19 Sep 2017, Pat Riehecky wrote:
> 
> > Synopsis:  Important: emacs security update
> > Advisory ID:   SLSA-2017:2771-1
> > Issue Date:2017-09-19
> > CVE Numbers:   CVE-2017-14482
> > --
> >
> > Security Fix(es):
> >
> > * A command injection flaw within the Emacs "enriched mode" handling has
> > been discovered. By tricking an unsuspecting user into opening a specially
> > crafted file using Emacs, a remote attacker could exploit this flaw to
> > execute arbitrary commands with the privileges of the Emacs user.
> > (CVE-2017-14482)
> 
> I see from https://access.redhat.com/security/cve/CVE-2017-14482
> that RedHat have marked this "wont fix" on RHEL6 and "investigating"
> on RHEL5, which seems odd - I'd have expected the other way around
> (unless a RHEL5 customer is paying for it).
> 
> Yes, there is a workaround, but I imagine that emacs is commonly used
> on RHEL6 and SL6 servers and it only takes one careless mistake...
> 
> How do other SL6 users feel about this "wont fix" ?
> 
> I'm trying to write my own patch, but seem to be struggling to patch
> a file near a ctrl-L character ...
> 
> -- 
> Andrew C. Aitchison   Cambridge, UK
>   and...@aitchison.me.uk
> 
> 

RE: Security ERRATA Important: kernel on SL6.x i386/x86_64

[Bill Maidment]

Aha.
Thanks for that. How many mailing lists do we need???
I got confused (not difficult at my age) as the response came on the User list.

Anyway, I echo the response. The team always seems to be on top of security 
issues.
Thank you (and the community) for being so friendly and helpful.

Cheers
Bill 
 
-Original message-
> From:Hans Kristian Rosbach <ha...@raskesider.no>
> Sent: Wednesday 21st June 2017 17:30
> To: Bill Maidment <b...@maidment.me>; scientific-linux-us...@listserv.fnal.gov
> Subject: Re: Security ERRATA Important: kernel on SL6.x i386/x86_64
> 
> I think that mail came from the 
> scientific-linux-err...@listserv.fnal.gov list, so you might
> have been removed from that list for some reason, but not from the users 
> list for example.
> 
> -- 
>   Hans Kristian Rosbach
>   Servebolt.com / Raske Sider
> 
> On 06/21/2017 12:41 AM, Bill Maidment wrote:
> > Hi. Is there something wrong with this mailing list? I received this 
> > response, but I never received the original message. This is not the first 
> > time I have noticed this.
> > Cheers
> > Bill
> >   
> >   
> > -Original message-
> >> From:Stephan Wiesand <stephan.wies...@desy.de>
> >> Sent: Wednesday 21st June 2017 2:58
> >> To: scientific-linux-us...@listserv.fnal.gov
> >> Subject: Re: Security ERRATA Important: kernel on SL6.x i386/x86_64
> >>
> >> Kudos to the SL team at FNAL for once again getting the updates for a 
> >> really nasty issue out incredibly quickly. Impressive.
> >>
> >> -- 
> >> Stephan Wiesand
> >> DESY -DV-
> >> Platanenenallee 6
> >> 15738 Zeuthen, Germany
> >>
> >>
> 
> 

RE: Security ERRATA Important: kernel on SL6.x i386/x86_64

[Bill Maidment]

Yeah I got that message on 17th, so I guess it may depend on who is sending the 
messages from SL
Cheers
Bill
 
 
-Original message-
> From:O'Neal, Miles <miles.on...@cirrus.com>
> Sent: Wednesday 21st June 2017 9:13
> To: Steven J. Yellin <yel...@slac.stanford.edu>; Bill Maidment 
> <b...@maidment.me>
> Cc: scientific-linux-us...@listserv.fnal.gov
> Subject: Re: Security ERRATA Important: kernel on SL6.x i386/x86_64
> 
> The SL email system was also broken for
 
>   a while. A message came through about that within the last couple
 
>   of days.
 
>   
 
>   On 06/20/2017 06:04 PM, Steven J. Yellin wrote:
 
>     Last November I was "automatically removed from
 
>   the SCIENTIFIC-LINUX-USERS list (Mailing list for Scientific Linux
 
>   users worldwide)  as a result of repeated delivery error reports
 
>   from your mail system."  So one possibility is that your mail
 
>   system is occasionally failing to deliver mail to you from this
 
>   list, but you haven't yet been removed.  In my case, the reason
 
>   was that the listserver sometimes sends email with a header longer
 
>   than 32768 bytes, which the SLAC mail system couldn't handle. 
 
>   FermiLab said such long headers are becoming necessary because
 
>   "cloud systems that everyone has and will be moving to, add
 
>   additional diagnostic info in the headers so if people report any
 
>   errors, they can more easily be diagnosed."  The solution was to
 
>   convince the managers of SLAC's mail system to increase their
 
>   incoming header size parameter.
 
>   
 
>   
 
>   Steven Yellin
 
>   
 
>   
 
>   On Wed, 21 Jun 2017, Bill Maidment wrote:
 
>   
 
>   
 
>   Hi. Is there something wrong with this
 
> mailing list? I received this response, but I never received the
 
> original message. This is not the first time I have noticed
 
> this.
 
> 
 
>   
 
>   Cheers
 
> 
 
> Bill
 
> 
 
> 
 
> 
 
> -Original message-
 
> 
 
> From:Stephan Wiesand
 
>   <stephan.wies...@desy.de> <mailto:stephan.wies...@desy.de>
 
>   
 
>   Sent: Wednesday 21st June 2017 2:58
 
>   
 
>   To: scientific-linux-us...@listserv.fnal.gov 
><mailto:scientific-linux-us...@listserv.fnal.gov>
 
>   
 
>   Subject: Re: Security ERRATA Important: kernel on SL6.x
 
>   i386/x86_64
 
>   
 
>   
 
>   Kudos to the SL team at FNAL for once again getting the
 
>   updates for a really nasty issue out incredibly quickly.
 
>   Impressive.
 
>   
 
>   
 
>   --
 
>   
 
>   Stephan Wiesand
 
>   
 
>   DESY -DV-
 
>   
 
>   Platanenenallee 6
 
>   
 
>   15738 Zeuthen, Germany
 
>   
 
>   
 
>   
 
> 
 
> 
 
> 
 
> -- 
 
>   Miles O'Neal
 
>   CAD Systems Engineer
 
>   Cirrus Logic | cirrus.com | 1.512.851.4659
 

RE: Security ERRATA Important: kernel on SL6.x i386/x86_64

[Bill Maidment]

Well, I'm running postfix with the default header_size_limit of 102,400, so I 
don't think that's the issue and there are no reject messages in the mail logs 
to indicate any problem. It seems that the mailing list is not always sending 
me the emails.
Another mystery from the bowels of technology!
Cheers
Bill 
 
-Original message-
> From:Steven J. Yellin <yel...@slac.stanford.edu>
> Sent: Wednesday 21st June 2017 9:04
> To: Bill Maidment <b...@maidment.me>
> Cc: scientific-linux-us...@listserv.fnal.gov
> Subject: RE: Security ERRATA Important: kernel on SL6.x i386/x86_64
> 
>  Last November I was "automatically removed from the 
> SCIENTIFIC-LINUX-USERS list (Mailing list for Scientific Linux users 
> worldwide)  as a result of repeated delivery error reports from your mail 
> system."  So one possibility is that your mail system is occasionally 
> failing to deliver mail to you from this list, but you haven't yet been 
> removed.  In my case, the reason was that the listserver sometimes sends 
> email with a header longer than 32768 bytes, which the SLAC mail system 
> couldn't handle.  FermiLab said such long headers are becoming necessary 
> because "cloud systems that everyone has and will be moving to, add 
> additional diagnostic info in the headers so if people report any errors, 
> they can more easily be diagnosed."  The solution was to convince the 
> managers of SLAC's mail system to increase their incoming header size 
> parameter.
> 
> Steven Yellin
> 
> On Wed, 21 Jun 2017, Bill Maidment wrote:
> 
> > Hi. Is there something wrong with this mailing list? I received this 
> > response, but I never received the original message. This is not the 
> > first time I have noticed this.
> 
> > Cheers
> > Bill
> >
> >
> > -Original message-
> >> From:Stephan Wiesand <stephan.wies...@desy.de>
> >> Sent: Wednesday 21st June 2017 2:58
> >> To: scientific-linux-us...@listserv.fnal.gov
> >> Subject: Re: Security ERRATA Important: kernel on SL6.x i386/x86_64
> >>
> >> Kudos to the SL team at FNAL for once again getting the updates for a 
> >> really nasty issue out incredibly quickly. Impressive.
> >>
> >> --
> >> Stephan Wiesand
> >> DESY -DV-
> >> Platanenenallee 6
> >> 15738 Zeuthen, Germany
> >>
> >>
> >
> 
> 

RE: Security ERRATA Important: kernel on SL6.x i386/x86_64

[Bill Maidment]

Hi. Is there something wrong with this mailing list? I received this response, 
but I never received the original message. This is not the first time I have 
noticed this.
Cheers
Bill
 
 
-Original message-
> From:Stephan Wiesand 
> Sent: Wednesday 21st June 2017 2:58
> To: scientific-linux-us...@listserv.fnal.gov
> Subject: Re: Security ERRATA Important: kernel on SL6.x i386/x86_64
> 
> Kudos to the SL team at FNAL for once again getting the updates for a really 
> nasty issue out incredibly quickly. Impressive.
> 
> -- 
> Stephan Wiesand
> DESY -DV-
> Platanenenallee 6
> 15738 Zeuthen, Germany
> 
> 

kernel error in SL 6.9

[Bill Maidment]

Hi
I am getting kernel errors in several SL 6 machines after yum update:
kernel: gam_server[2941]: segfault at 58f5f7aa ip 0040a2b9 sp 
7ffe56238e80 error 4 in gam_server[40+16000]
What is a gam_server? Should I be worried by this?

Cheers
Bill Maidment

RE: Strange network device name chages on reboot of SL7 kvm guests

[Bill Maidment]

Thanks everyone for your comments and advice.
It seemed I had commented out the HWADDR and UUID for some strange reason. I 
have now added them back in and all is back to normal.
Now I know the importance of those values.
Cheers
Bill
 
-Original message-
> From:~Stack~ <i.am.st...@gmail.com>
> Sent: Monday 27th February 2017 1:58
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: Re: Strange network device name chages on reboot of SL7 kvm guests
> 
> On 02/25/2017 10:18 PM, Bill Maidment wrote:
> > Hi again
> Greetings!
> 
> > I have recently rebooted KVM guests with two virtual NICs (e.g. /dev/ens4 
> > and /dev/eth0) only to find that the device name of the eth0 changes to 
> > eth1 and so the ifcfg-eth0 doesn't match.
> > So I fix the ifcfg file and restart network - all OK.
> > On a later reboot eth1 changes back to eth0.
> > What is going on? Anyone else observe this phenomena?
> 
> Yes. It is part of the goofy new naming structure. It's nice when it
> works, but it seems to not-work more often then it does-work. Then it is
> infuriating.
> 
> 
> Anyway...
> 
> Here's the short version.
> en: ethernet prefix
> o: onboard
> s: slot
> p: physical location of connector.
> 
> If the device is "unknown" then it gets "eth". And of course the numbers
> increment for each new device.
> 
> So what your device names tell me is that you have one card in slot 4
> and a second card that the OS can't figure out where it goes.
> 
> There are two ways of "fixing" this.
> 1)
> *If* you have your HWADDR= assigned in your
> /etc/sysconfig/network-scripts/ifcfg-eth0 then it *should* always get
> that interface regardless of what the OS detects it to be on boot. I
> have found this isn't always the case with some specialty cards that
> take FOREVER to initialize. I tend to throw in the UUID as well and that
> seems to resolve the problems for those cards.
> 
> 2)
> Now, here is the odd part because this next problem is also on my big
> KVM host. None of the above worked. I never found a good answer to why
> and I am wondering if it is related to KVM...but at this point my sample
> size is two so probably not something to make a solid educated guess on...
> 
> Anyway..
> 
> Read this:
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html
> 
> There are some good tips throughout chapter 8 on how to tweak and/or
> disable udev from scanning devices. I had to rewrite the udev rules on
> my KVM box right after 7.1 released because *every* *single* reboot
> broke my networking. However, after I adjusted the udev rules based on
> the RH documentation I haven't had a problem with reboots since.
> 
> I _really_ hope that #1 fixes your issues as it is by far the easiest to
> do and manage. If not, the udev rules should do the trick.
> 
> One last thought. In that documentation there is something called
> "biosdevname"; I'm pretty sure that wasn't in the docs when I was having
> a problem with 7.1 as I don't recall seeing it before, but it looks
> interesting. You might just want to go through that chapter and give
> those suggestions a go.
> 
> Hope that helps!
> 
> ~Stack~
> 
> 

Strange network device name chages on reboot of SL7 kvm guests

[Bill Maidment]

Hi again
I have recently rebooted KVM guests with two virtual NICs (e.g. /dev/ens4 and 
/dev/eth0) only to find that the device name of the eth0 changes to eth1 and so 
the ifcfg-eth0 doesn't match.
So I fix the ifcfg file and restart network - all OK.
On a later reboot eth1 changes back to eth0.
What is going on? Anyone else observe this phenomena?

Cheers
Bill Maidment

RE: PHP issue with Firefox-45.7.0-1.el7_3.x86_64

[Bill Maidment]

Thanks David.
That tidied it up nicely.
 
-Original message-
> From:David Sommerseth <sl+us...@lists.topphemmelig.net>
> Sent: Friday 3rd February 2017 7:04
> To: Bill Maidment <b...@maidment.me>
> Subject: Re: PHP issue with Firefox-45.7.0-1.el7_3.x86_64
> 
> You might need this line as well:
> 
> header('Content-Disposition: inline; filename="the.pdf"');
> 
> 

RE: PHP issue with Firefox-45.7.0-1.el7_3.x86_64 - Solved

[Bill Maidment]

How embarrassing!
When checking the Application defaults for Firefox I failed to notice that 
there are TWO PDF entries:
PDF Document -- which was set to Use (default)
Portable Document Format (PDF) -- which was set to Save File

Why are there two entries?

Anyway it's all working now I have set the second entry to Use Document Viewer 
(default) 
 
-Original message-
> From:Bill Maidment <b...@maidment.me>
> Sent: Wednesday 1st February 2017 12:51
> To: Bill Maidment <b...@maidment.me>; SCIENTIFIC-LINUX-USERS@FNAL.GOV 
> <SCIENTIFIC-LINUX-USERS@fnal.gov>
> Subject: RE: PHP issue with Firefox-45.7.0-1.el7_3.x86_64
> 
> Further information:
> 
> The PHP script creates a PDF temporary file (which succeeds) and passes that 
> file to the browser to display it as follows.
> 
> header('Content-Type: application/pdf');
> readfile($sTempFile);
> 
> But all I get is a Save popup for the PHP script.
> 
>  
>  
> -Original message-
> > From:Bill Maidment <b...@maidment.me>
> > Sent: Wednesday 1st February 2017 12:38
> > To: SCIENTIFIC-LINUX-USERS@FNAL.GOV <SCIENTIFIC-LINUX-USERS@fnal.gov>
> > Subject: PHP issue with Firefox-45.7.0-1.el7_3.x86_64
> > 
> > Hi gang
> > I am having trouble running an onclick PHP script on an internal web site 
> > using the latest Firefox browser. The site was running OK prior to 
> > upgrading to 7.3.
> > I see lots of errors in the Browser Console like:
> > NS_ERROR_FAILURE: Component returned failure code: 0x80004005 
> > (NS_ERROR_FAILURE) [nsIURI.host]
> > and pointing to contentPolicy.js line 182 (see attached image of that part 
> > of the js)
> > 
> > Is this some new security check? Has anyone else seen something similar?
> > 
> > Cheers
> > Bill Maidment
> 
> 

RE: PHP issue with Firefox-45.7.0-1.el7_3.x86_64

[Bill Maidment]

Further information:

The PHP script creates a PDF temporary file (which succeeds) and passes that 
file to the browser to display it as follows.

header('Content-Type: application/pdf');
readfile($sTempFile);

But all I get is a Save popup for the PHP script.

 
 
-Original message-
> From:Bill Maidment <b...@maidment.me>
> Sent: Wednesday 1st February 2017 12:38
> To: SCIENTIFIC-LINUX-USERS@FNAL.GOV <SCIENTIFIC-LINUX-USERS@fnal.gov>
> Subject: PHP issue with Firefox-45.7.0-1.el7_3.x86_64
> 
> Hi gang
> I am having trouble running an onclick PHP script on an internal web site 
> using the latest Firefox browser. The site was running OK prior to upgrading 
> to 7.3.
> I see lots of errors in the Browser Console like:
> NS_ERROR_FAILURE: Component returned failure code: 0x80004005 
> (NS_ERROR_FAILURE) [nsIURI.host]
> and pointing to contentPolicy.js line 182 (see attached image of that part of 
> the js)
> 
> Is this some new security check? Has anyone else seen something similar?
> 
> Cheers
> Bill Maidment

PHP issue with Firefox-45.7.0-1.el7_3.x86_64

[Bill Maidment]

Hi gang
I am having trouble running an onclick PHP script on an internal web site using 
the latest Firefox browser. The site was running OK prior to upgrading to 7.3.
I see lots of errors in the Browser Console like:
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 
(NS_ERROR_FAILURE) [nsIURI.host]
and pointing to contentPolicy.js line 182 (see attached image of that part of 
the js)

Is this some new security check? Has anyone else seen something similar?

Cheers
Bill Maidment

RE: Anacron has an upset tummy over sl-security

[Bill Maidment]

I trust that you mean "yum clean all". 
 
 
-Original message-
> From:jdow <j...@earthlink.net>
> Sent: Monday 30th January 2017 11:34
> To: scientific-linux-users@fnal.gov
> Subject: Re: Anacron has an upset tummy over sl-security
> 
> I am not using a local repo. I'm trying a "repo clean all" and then an update.
> 
> {^_^}
> 
> On 2017-01-29 16:15, Bill Maidment wrote:
> > Hi
> > I got the same issue, but when I deleted repodata from my local repo and 
> > resynced from the rsync master, it sorted itself out.
> > I believe this may have been caused by the firefox update which was 
> > released about the same time as 7.3
> > Anyway, I no longer have the problem (for now).
> >
> > Cheers
> > Bill
> >
> >
> > -Original message-
> >> From:jdow <j...@earthlink.net>
> >> Sent: Monday 30th January 2017 10:30
> >> To: scientific-linux-users@fnal.gov
> >> Subject: Anacron has an upset tummy over sl-security
> >>
> >> /etc/cron.daily/0yum-daily.cron:
> >>
> >> Not using downloaded repomd.xml because it is older than what we have:
> >>Current   : Wed Jan 25 11:54:42 2017
> >>Downloaded: Wed Jan 25 11:54:25 2017
> >> Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad 
> >> duplicate,
> >> skipping.
> >> You should report this problem to the owner of the sl-security repository.
> >> Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad 
> >> duplicate,
> >> skipping.
> >> Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad 
> >> duplicate,
> >> skipping.
> >> ... many more
> >>
> >>
> >>
> >> I thought this was supposed to be fixed. This suggests there still is some 
> >> form
> >> of problem with the sl-security repo.
> >>
> >> {^_^}   Joanne
> >>
> >>
> >
> 
> 

RE: Anacron has an upset tummy over sl-security

[Bill Maidment]

Hi
I got the same issue, but when I deleted repodata from my local repo and 
resynced from the rsync master, it sorted itself out.
I believe this may have been caused by the firefox update which was released 
about the same time as 7.3
Anyway, I no longer have the problem (for now).

Cheers
Bill
 
 
-Original message-
> From:jdow 
> Sent: Monday 30th January 2017 10:30
> To: scientific-linux-users@fnal.gov
> Subject: Anacron has an upset tummy over sl-security
> 
> /etc/cron.daily/0yum-daily.cron:
> 
> Not using downloaded repomd.xml because it is older than what we have:
>Current   : Wed Jan 25 11:54:42 2017
>Downloaded: Wed Jan 25 11:54:25 2017
> Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad 
> duplicate, 
> skipping.
> You should report this problem to the owner of the sl-security repository.
> Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad 
> duplicate, 
> skipping.
> Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad 
> duplicate, 
> skipping.
> ... many more
> 
> 
> 
> I thought this was supposed to be fixed. This suggests there still is some 
> form 
> of problem with the sl-security repo.
> 
> {^_^}   Joanne
> 
> 

RE: SL73 GeoIP in named issue

[Bill Maidment]

Yeah I found that and set it all up and still it "vomits" the messages preceded 
by
using "/usr/share/GeoIP" as GeoIP directory
However the geoiplookup command works from the command line, so I reckon named 
startup has a bug.
 
-Original message-
> From:Denice <deatr...@triumf.ca>
> Sent: Friday 16th December 2016 13:13
> To: Bill Maidment <b...@maidment.me>
> Cc: SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: Re: SL73 GeoIP in named issue
> 
> On Fri, 16 Dec 2016, Bill Maidment wrote:
> 
> > Here's another issue
> >
> > named now has GeoIP switched on and I get the following errors at start up
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Country (IPv4) (type 1) DB 
> > not available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Country (IPv6) (type 12) DB 
> > not available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP City (IPv4) (type 2) DB not 
> > available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP City (IPv4) (type 6) DB not 
> > available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP City (IPv6) (type 30) DB not 
> > available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP City (IPv6) (type 31) DB not 
> > available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Region (type 3) DB not 
> > available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Region (type 7) DB not 
> > available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP ISP (type 4) DB not available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Org (type 5) DB not available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP AS (type 9) DB not available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Domain (type 11) DB not 
> > available
> > Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP NetSpeed (type 10) DB not 
> > available
> >
> > Is there a way of switching this off? Or should there be a pile of DBs with 
> > the RPM ?
> 
> It is annoying that it vomits out those messages. AFAICT, there is no
> option to disable it.  The named.conf option to specify the directory
> containing the geoip DBs is:
>   geoip-directory
> 
> There is a thread about it in the bind-users mailing list:
>https://lists.isc.org/pipermail/bind-users/2015-November/thread.html#95971
> 
> Presumably, if you want to use GeoIP you need to install the GeoIP and
> GeoIP-update packages, and enable the cron job to update the database.
> 
> cheers, etc.
> -- 
> deatrich @ triumf.ca, Science/ATLAS PH: +1 604-222-7665
> <*> This moment's fortune cookie:
> There must be more to life than having everything.
>   -- Maurice Sendak
> 
> 

SL73 GeoIP in named issue

[Bill Maidment]

Here's another issue

named now has GeoIP switched on and I get the following errors at start up
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Country (IPv4) (type 1) DB not 
available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Country (IPv6) (type 12) DB not 
available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP City (IPv4) (type 2) DB not 
available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP City (IPv4) (type 6) DB not 
available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP City (IPv6) (type 30) DB not 
available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP City (IPv6) (type 31) DB not 
available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Region (type 3) DB not available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Region (type 7) DB not available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP ISP (type 4) DB not available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Org (type 5) DB not available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP AS (type 9) DB not available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP Domain (type 11) DB not available
Dec 16 10:20:47 ferdinand2 named[1425]: GeoIP NetSpeed (type 10) DB not 
available

Is there a way of switching this off? Or should there be a pile of DBs with the 
RPM ?

Cheers
Bill Maidment

RE: ACL Problem in SL7.2

[Bill Maidment]

Wow. Thanks everyone for your insights and suggestions.
After more thinking and tests, it could be that RedHat are closing in on a 
solution with https://access.redhat.com/solutions/447803 (I'm not a subscriber 
either).

For me the current situation is not ideal but usable.
Adding directories through Nautilus gives the correct permissions inherited 
down from the top directory, but adding a file adds a gratuitous read on Other.
As the share is restricted to a particular group of users, it is no real issue 
for me.

Thanks again everyone. I'll await any further developments from RedHat.
Bill
 
-Original message-
> From:Karel Lang AFD <l...@afd.cz>
> Sent: Tuesday 8th November 2016 21:22
> To: Bill Maidment <b...@maidment.me>; SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: Re: ACL Problem in SL7.2
> 
> Hi Bill,
> 
> problem indeed.
> Just suggestion/question - the NFS client running on SL 6.x is 
> configured to use also NFSv4 protocol? Eg.
> 
> mount -t nfs -o vers=4 server:/data /tmp
> 
> btw i think Red Hat been solving something similar here:
> 
> 'NFS client using NFSv4 ACLs loses the correct mask of a newly created 
> file in subdirectories'
> 
> https://access.redhat.com/solutions/447803
> 
> unfortunately 'subscriber content' which i'm not, maybe you? :-)
> 
> 
> On 11/08/2016 06:19 AM, Bill Maidment wrote:
> > Hi again
> > My research has revealed that nfs in SL 7.2 is translating the POSIX ACL to 
> > NFSv4 ACL (a completely different format).
> > vi appears to recognise NFSv4 ACL, but Nautilus, ls and probably other 
> > programs, only seem to recognise POSIX ACL.
> >
> > So I have the following alternatives:
> > 1. Stop nfs translating to NFSv4 ACL
> > 2. Change the guest mount to translate NFSv4 ACL back to POSIX ACL
> > 3. Change Nautilus, etc to recognise NFSv4 ACL
> > 4. Use Samba instead of nfs
> >
> > I'm not sure if 1. or 2. are possible and 3. may happen one day. Does 
> > anyone know of a practical solution/workaround?
> > Cheers
> > Bill
> >
> > -Original message-
> >> From:Bill Maidment <b...@maidment.me>
> >> Sent: Sunday 6th November 2016 19:56
> >> To: Karel Lang AFD <l...@afd.cz>; SCIENTIFIC-LINUX-USERS@FNAL.GOV
> >> Subject: RE: ACL Problem in SL7.2
> >>
> >> Thanks for the response Karel.
> >> umask is the standard 0022 and this is a top level directory on the host 
> >> machine.
> >> I am using SL 6.8 to access the directory via nfs share.
> >> It looks like there is no problem if the file is created with vi
> >> But if I use Nautilus then that's when I get the issue.
> >> So Nautilus on SL 6.8 seems to be the culprit (or is it caused by nfs?)
> >> Cheers
> >> Bill
> >>
> >> -Original message-
> >>> From:Karel Lang AFD <l...@afd.cz>
> >>> Sent: Sunday 6th November 2016 16:16
> >>> To: Bill Maidment <b...@maidment.me>; SCIENTIFIC-LINUX-USERS@FNAL.GOV
> >>> Subject: Re: ACL Problem in SL7.2
> >>>
> >>> Hi Bill
> >>> just pasted your work here to CLI and works OK on SL 6.7 and SL 7.2 
> >>> here...
> >>> It has to be something else .. umask? or inherited from directory higher 
> >>> up?
> >>> Maybe strace would help to see whats happening exactly?
> >>>
> >>> cheers
> >>>
> >>> On 11/06/2016 03:58 AM, Bill Maidment wrote:
> >>>> Hi
> >>>> I am trying to set up ACL on a directory such that any new file created 
> >>>> in the directory has permissions of 0660.
> >>>> However, when I create a new file, the permissions are set as 0664 (see 
> >>>> test.txt file below)
> >>>> Is this a bug or am I doing something wrong?
> >>>>
> >>>> These are the commands I used:
> >>>>
> >>>> chmod -R u+rwX,g+rwXs,o-rwx /pictures
> >>>>
> >>>> setfacl -d -m u::rwx,g::rwx,o::--- /pictures
> >>>>
> >>>> getfacl /pictures
> >>>> getfacl: Removing leading '/' from absolute path names
> >>>> # file: pictures
> >>>> # owner: nfs01
> >>>> # group: nfs01
> >>>> # flags: -s-
> >>>> user::rwx
> >>>> group::rwx
> >>>> other::---
> >>>> default:user::rwx
> >>>> default:group::rwx
> >>>> default:other::---
> >>>>
> >>>> ls -latrh /pictures
> >>>> total 4.0K
> >>>> dr-xr-xr-x. 22 root  root  4.0K Nov  6 12:41 ..
> >>>> drwxrws---+  2 nfs01 nfs01   21 Nov  6 13:10 Testing
> >>>> -rw-rw-r--   1 nfs01 nfs01    0 Nov  6 13:44 test.txt
> >>>> drwxrws---+  3 nfs01 nfs01   35 Nov  6 13:44 .
> >>>>
> >>>> Cheers
> >>>> Bill Maidment
> >>>>
> >>>
> >>>
> >>
> >>
> >
> 
> -- 
> *Karel Lang*
> *Unix/Linux Administration*
> l...@afd.cz | +420 731 13 40 40
> AUFEER DESIGN, s.r.o. | www.aufeerdesign.cz
> 
> 

RE: ACL Problem in SL7.2

[Bill Maidment]

Hi again
My research has revealed that nfs in SL 7.2 is translating the POSIX ACL to 
NFSv4 ACL (a completely different format).
vi appears to recognise NFSv4 ACL, but Nautilus, ls and probably other 
programs, only seem to recognise POSIX ACL.

So I have the following alternatives:
1. Stop nfs translating to NFSv4 ACL
2. Change the guest mount to translate NFSv4 ACL back to POSIX ACL
3. Change Nautilus, etc to recognise NFSv4 ACL
4. Use Samba instead of nfs

I'm not sure if 1. or 2. are possible and 3. may happen one day. Does anyone 
know of a practical solution/workaround?
Cheers
Bill
 
-Original message-
> From:Bill Maidment <b...@maidment.me>
> Sent: Sunday 6th November 2016 19:56
> To: Karel Lang AFD <l...@afd.cz>; SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: RE: ACL Problem in SL7.2
> 
> Thanks for the response Karel.
> umask is the standard 0022 and this is a top level directory on the host 
> machine.
> I am using SL 6.8 to access the directory via nfs share.
> It looks like there is no problem if the file is created with vi
> But if I use Nautilus then that's when I get the issue.
> So Nautilus on SL 6.8 seems to be the culprit (or is it caused by nfs?)
> Cheers
> Bill
> 
> -Original message-
> > From:Karel Lang AFD <l...@afd.cz>
> > Sent: Sunday 6th November 2016 16:16
> > To: Bill Maidment <b...@maidment.me>; SCIENTIFIC-LINUX-USERS@FNAL.GOV
> > Subject: Re: ACL Problem in SL7.2
> > 
> > Hi Bill
> > just pasted your work here to CLI and works OK on SL 6.7 and SL 7.2 here...
> > It has to be something else .. umask? or inherited from directory higher up?
> > Maybe strace would help to see whats happening exactly?
> > 
> > cheers
> > 
> > On 11/06/2016 03:58 AM, Bill Maidment wrote:
> > > Hi
> > > I am trying to set up ACL on a directory such that any new file created 
> > > in the directory has permissions of 0660.
> > > However, when I create a new file, the permissions are set as 0664 (see 
> > > test.txt file below)
> > > Is this a bug or am I doing something wrong?
> > >
> > > These are the commands I used:
> > >
> > > chmod -R u+rwX,g+rwXs,o-rwx /pictures
> > >
> > > setfacl -d -m u::rwx,g::rwx,o::--- /pictures
> > >
> > > getfacl /pictures
> > > getfacl: Removing leading '/' from absolute path names
> > > # file: pictures
> > > # owner: nfs01
> > > # group: nfs01
> > > # flags: -s-
> > > user::rwx
> > > group::rwx
> > > other::---
> > > default:user::rwx
> > > default:group::rwx
> > > default:other::---
> > >
> > > ls -latrh /pictures
> > > total 4.0K
> > > dr-xr-xr-x. 22 root  root  4.0K Nov  6 12:41 ..
> > > drwxrws---+  2 nfs01 nfs01   21 Nov  6 13:10 Testing
> > > -rw-rw-r--   1 nfs01 nfs010 Nov  6 13:44 test.txt
> > > drwxrws---+  3 nfs01 nfs01   35 Nov  6 13:44 .
> > >
> > > Cheers
> > > Bill Maidment
> > >
> > 
> > 
> 
> 

RE: ACL Problem in SL7.2

[Bill Maidment]

Thanks for the response Karel.
umask is the standard 0022 and this is a top level directory on the host 
machine.
I am using SL 6.8 to access the directory via nfs share.
It looks like there is no problem if the file is created with vi
But if I use Nautilus then that's when I get the issue.
So Nautilus on SL 6.8 seems to be the culprit (or is it caused by nfs?)
Cheers
Bill

-Original message-
> From:Karel Lang AFD <l...@afd.cz>
> Sent: Sunday 6th November 2016 16:16
> To: Bill Maidment <b...@maidment.me>; SCIENTIFIC-LINUX-USERS@FNAL.GOV
> Subject: Re: ACL Problem in SL7.2
> 
> Hi Bill
> just pasted your work here to CLI and works OK on SL 6.7 and SL 7.2 here...
> It has to be something else .. umask? or inherited from directory higher up?
> Maybe strace would help to see whats happening exactly?
> 
> cheers
> 
> On 11/06/2016 03:58 AM, Bill Maidment wrote:
> > Hi
> > I am trying to set up ACL on a directory such that any new file created in 
> > the directory has permissions of 0660.
> > However, when I create a new file, the permissions are set as 0664 (see 
> > test.txt file below)
> > Is this a bug or am I doing something wrong?
> >
> > These are the commands I used:
> >
> > chmod -R u+rwX,g+rwXs,o-rwx /pictures
> >
> > setfacl -d -m u::rwx,g::rwx,o::--- /pictures
> >
> > getfacl /pictures
> > getfacl: Removing leading '/' from absolute path names
> > # file: pictures
> > # owner: nfs01
> > # group: nfs01
> > # flags: -s-
> > user::rwx
> > group::rwx
> > other::---
> > default:user::rwx
> > default:group::rwx
> > default:other::---
> >
> > ls -latrh /pictures
> > total 4.0K
> > dr-xr-xr-x. 22 root  root  4.0K Nov  6 12:41 ..
> > drwxrws---+  2 nfs01 nfs01   21 Nov  6 13:10 Testing
> > -rw-rw-r--   1 nfs01 nfs010 Nov  6 13:44 test.txt
> > drwxrws---+  3 nfs01 nfs01   35 Nov  6 13:44 .
> >
> > Cheers
> > Bill Maidment
> >
> 
> 

ACL Problem in SL7.2

[Bill Maidment]

Hi
I am trying to set up ACL on a directory such that any new file created in the 
directory has permissions of 0660.
However, when I create a new file, the permissions are set as 0664 (see 
test.txt file below)
Is this a bug or am I doing something wrong?

These are the commands I used:

chmod -R u+rwX,g+rwXs,o-rwx /pictures

setfacl -d -m u::rwx,g::rwx,o::--- /pictures

getfacl /pictures
getfacl: Removing leading '/' from absolute path names
# file: pictures
# owner: nfs01
# group: nfs01
# flags: -s-
user::rwx
group::rwx
other::---
default:user::rwx
default:group::rwx
default:other::---

ls -latrh /pictures
total 4.0K
dr-xr-xr-x. 22 root  root  4.0K Nov  6 12:41 ..
drwxrws---+  2 nfs01 nfs01   21 Nov  6 13:10 Testing
-rw-rw-r--   1 nfs01 nfs01    0 Nov  6 13:44 test.txt
drwxrws---+  3 nfs01 nfs01   35 Nov  6 13:44 .

Cheers
Bill Maidment

RE: Amusing/Sad Gnome3/Wayland story

[Bill Maidment]

Keith
With Linux there is always another way.
At our museum we run SL7 for the servers and SL6 for the desktops.
EXCEPT, I sneaked in a SL7 Mate Desktop and no one noticed the difference (they 
are just users).
I notice the difference, but then I have weird requirements.

BTW At least you were saved from "Death by PowerPoint/Impress" ;-)
Cheers
Bill
 
-Original message-
> From:Keith Lofstrom 
> Sent: Tuesday 11th October 2016 18:43
> To: scientific-linux-us...@listserv.fnal.gov
> Subject: Amusing/Sad Gnome3/Wayland story
> 
> Last week, a leader of the Gnome project spoke to our 
> local Linux user's group.  He had a new Lenovo laptop
> running Gnome 3 with the Wayland replacement for X.  He
> could NOT get his HDMI port working with our projector;
> that's the first time we've had that problem in years.
> 
> I offered my ancient SL6/Gnome2 laptop, but he demurred
> and went without slides.  It seems that the Gnomesters
> are building another incompatible tool, this one to
> replace LibreOffice Impress.
> 
> 
> 
> Harrumph.  If and when support for SL6 ends, and I must
> upgrade my laptop to SL7, I will use MATE.  The Gnome
> project has lost touch with reality.
> 
> Keith
> 
> -
> Keith Lofstrom  kei...@keithl.com
> -
> Don't waste your vote in 2016!  Give it to the Republicans
> and Democrats, and they will gladly waste it for you!
> 
> 

RE: SL7 CUPS/SELinux problem trying to install Brother HL-3150CDN printer driver

[Bill Maidment]

Hey guys
It's an interesting discussion

> >
> > Refusing to to use, accept and learn SELinux will serve you no good in
> > the long run.
> 
> See above. Security is a trade-off between trouble saved by having
> security, and caused by the security itself.

Today, We had the local council workers digging up our road and blocking us in, 
claiming it was because a sink-hole had developed and had to be fixed for 
safety reasons.
So they scraped off the top surface, and relaid tarmac over it. Sink hole 
neatly hidden.

Security box ticked, inconvenience box ticked, safety - we wait and see.

BTW Today is the last day of our financial year and the the remaining road 
works fund had to be spent. If you've watched "Yes, Minister" you will know 
what that means.
Anyway, I digress.

Some of my servers are now SELinux enforcing, others await testing.

Cheers
Bill

RE: SL7 CUPS/SELinux problem trying to install Brother HL-3150CDN printer driver

[Bill Maidment]

Well I've heard back from Brother and they suggest that my SElinux set up has a 
problem. They recommended that I do
semodule -vR
This gave me exactly the same error messages. Then I did semodule -vB which 
worked OK, but repeating semodule -vR still gives

[root@ferguson src]# semodule -vB
Committing changes:
Ok: transaction number 0.
[root@ferguson src]# semodule -vR
SELinux:  Could not downgrade policy file 
/etc/selinux/targeted/policy/policy.29, searching for an older version.
SELinux:  Could not open policy file <= /etc/selinux/targeted/policy/policy.29: 
 No such file or directory
/sbin/load_policy:  Can't load policy:  No such file or directory
libsemanage.semanage_reload_policy: load_policy returned error code 2. (No such 
file or directory).
[root@ferguson src]# 

This is happening on two different SL 7.2 machines with SElinux installed but 
disabled.

I even tried uninstalling selinux* but that got me into deeper trouble.

[root@ferguson src]# rpm -qv selinux-policy
selinux-policy-3.13.1-60.el7_2.7.noarch

Is there an issue with this version of selinux???

Cheers
Bill

-Original message-
> From:Bill Maidment <b...@maidment.me>
> Sent: Saturday 25th June 2016 17:26
> To: Akemi Yagi <amy...@gmail.com>; SL Users <scientific-linux-users@fnal.gov>
> Subject: RE: SL7 CUPS/SELinux problem trying to install Brother HL-3150CDN 
> printer driver
> 
> Thanks for the suggestion Akemi.
> Unfortunately, it made no difference.
> I'm awaiting comment from Brother, but I suspect they will say change to 
> Ubuntu :-(
> Cheers
> Bill 
>  
> -Original message-
> > From:Akemi Yagi <amy...@gmail.com>
> > Sent: Saturday 25th June 2016 1:10
> > To: SL Users <scientific-linux-users@fnal.gov>
> > Subject: Re: SL7 CUPS/SELinux problem trying to install Brother HL-3150CDN 
> > printer driver
> > 
> > On Fri, Jun 24, 2016 at 2:33 AM, Bill Maidment <b...@maidment.me> wrote:
> > > Has anyone any suggestions how to get a Brother HL-3150CDN printer driver 
> > > installed on SL7.
> > > I have been trying to install using the Brother supplied installation 
> > > script, which worked OK on SL6.
> > >
> > > With SL7 I get error messages such as:
> > > SELinux:  Could not downgrade policy file 
> > > /etc/selinux/targeted/policy/policy.29, searching for an older version.
> > > SELinux:  Could not open policy file <= 
> > > /etc/selinux/targeted/policy/policy.29:  No such file or directory 
> > > /sbin/load_policy:  Can't load policy:  No such file or directory
> > >
> > > The file in question does exist, but I have selinux disabled anyway.
> > >
> > > SL7 is using cups version 1.6 whereas SL6 uses cups version 1.4. Is that 
> > > an issue?
> > > I guess the Brother script is a bit out of date as it was created in 2012.
> > >
> > > Any help would be appreciated.
> > >
> > > Cheers
> > > Bill Maidment
> > 
> > Can you try reinstalling selinux-policy packages and see if that fixes
> > the issue?
> > 
> > yum reinstall selinux-policy\*
> > 
> > Akemi
> > 
> > 

RE: SL7 CUPS/SELinux problem trying to install Brother HL-3150CDN printer driver

[Bill Maidment]

Thanks for the suggestion Akemi.
Unfortunately, it made no difference.
I'm awaiting comment from Brother, but I suspect they will say change to Ubuntu 
:-(
Cheers
Bill 
 
-Original message-
> From:Akemi Yagi <amy...@gmail.com>
> Sent: Saturday 25th June 2016 1:10
> To: SL Users <scientific-linux-users@fnal.gov>
> Subject: Re: SL7 CUPS/SELinux problem trying to install Brother HL-3150CDN 
> printer driver
> 
> On Fri, Jun 24, 2016 at 2:33 AM, Bill Maidment <b...@maidment.me> wrote:
> > Has anyone any suggestions how to get a Brother HL-3150CDN printer driver 
> > installed on SL7.
> > I have been trying to install using the Brother supplied installation 
> > script, which worked OK on SL6.
> >
> > With SL7 I get error messages such as:
> > SELinux:  Could not downgrade policy file 
> > /etc/selinux/targeted/policy/policy.29, searching for an older version.
> > SELinux:  Could not open policy file <= 
> > /etc/selinux/targeted/policy/policy.29:  No such file or directory 
> > /sbin/load_policy:  Can't load policy:  No such file or directory
> >
> > The file in question does exist, but I have selinux disabled anyway.
> >
> > SL7 is using cups version 1.6 whereas SL6 uses cups version 1.4. Is that an 
> > issue?
> > I guess the Brother script is a bit out of date as it was created in 2012.
> >
> > Any help would be appreciated.
> >
> > Cheers
> > Bill Maidment
> 
> Can you try reinstalling selinux-policy packages and see if that fixes
> the issue?
> 
> yum reinstall selinux-policy\*
> 
> Akemi
> 
> 

SL7.0 yum update error

[Bill Maidment]

It looks like libguestfs needs to be updated to use libkadm5srv_mit.so.9

Error: Package: 1:libguestfs-1.22.6-22.el7.x86_64 (@anaconda)
   Requires: libkadm5srv_mit.so.8()(64bit)
   Removing: krb5-libs-1.11.3-49.el7.x86_64 (@anaconda)
   libkadm5srv_mit.so.8()(64bit)
   Updated By: krb5-libs-1.12.2-14.el7.x86_64 (sl-security)
  ~libkadm5srv_mit.so.9()(64bit)

RE: Installing Zarafa on SL7

[Bill Maidment]

 From:Phil Wyett philwyett.vende...@gmail.com
 Sent: Friday 6th February 2015 21:20
 To: Scientific Linux scientific-linux-users@fnal.gov
 Subject: Re: Installing Zarafa on SL7
 
 On Fri, 2015-02-06 at 20:46 +1100, Bill Maidment wrote:
  Hi guys
  
  
  When I try to install zarafa on SL7 from EPEL I get the following
  error:
  
  
  Error: Package: zarafa-search-7.1.11-2.el7.x86_64 (epel) Requires:
  catdoc
  
  
  
  Does anyone know where to get catdoc? Or how to get round this issue
  other than skip-broken ?
  
  
  
  Cheers
  
  
  Bill
  
  
 
 Hi,
 
 I can confirm this issue on SL 7. The package 'catdoc' does not yet
 exist in EPEL 7. I would suggest you file a bug against 'zarafa' on Red
 Hats bugzilla or you may wish to contact the 'catdoc' contact and ask
 for it building for EPEL 7. The contact according to the Fedora project
 is:
 
 Name: Adel Gadllah
 Nick: drago01
 Email: adel.gadl...@gmail.com
 
 Regards
 
 Phil
 
 

Thanks Phil
I have sent a request to Adel and noticed that there is also an outstanding 
RedHat Bugzilla for this issue.
In the meantime I have simply rebuild the rpm for SL7 as suggested in the 
bugzilla.
Now to test it all..

Cheers
Bill

Installing Zarafa on SL7

[Bill Maidment]

Hi guys

When I try to install zarafa on SL7 from EPEL I get the following error:

Error: Package: zarafa-search-7.1.11-2.el7.x86_64 (epel) Requires: catdoc



Does anyone know where to get catdoc? Or how to get round this issue other than 
skip-broken ?



Cheers

Bill

RE: SL7 - crond starting before chronyd causing problem with mrtg {solved - I think}

[Bill Maidment]

Hmm

It seems that I forgot that kvm by default only suspends the guests when you 
reboot the host. This explains the delay in resyncronising the clock, etc.

I've now fixed up the /etc/sysconfig/libvirt-guests on the host to ensure a 
reboot of guests.

I'm now awaiting the next reboot (a scheduled power outage on Tuesday) to prove 
the point.

Sorry all for the noise; at age 68 the little grey cells aren't what they used 
to be.

Cheers

Bill





-Original message-
From: Bill Maidment b...@maidment.me
Sent: Thursday 22nd January 2015 18:26
To: scientific-linux-users@fnal.gov
Subject: RE: SL7 - crond starting before chronyd causing problem with mrtg


Thanks David.
However, even using After= chronyd.service the chronyd still takes too long to 
correct the time for the time-zone.

After some investigation, it seems that the KVM system is at fault when the 
host is rebooted, but not when the guest is rebooted.
On reboot of the host KVM adds the timezone shift to the hardware clock for the 
guests and then the guest adds the timezone shift again.
This extra addition of the timzone shift did not happen on SL6.

After running hwclock --systohc on the guest, I get the following setup.

[root@giggs2 ˜]# timedatectl 
  Local time: Thu 2015-01-22 17:55:26 AEDT
  Universal time: Thu 2015-01-22 06:55:26 UTC
    RTC time: Thu 2015-01-22 06:55:26
    Timezone: Australia/Sydney (AEDT, +1100)
 NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
  DST active: yes
 Last DST change: DST began at
  Sun 2014-10-05 01:59:59 AEST
  Sun 2014-10-05 03:00:00 AEDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
  Sun 2015-04-05 02:59:59 AEDT
  Sun 2015-04-05 02:00:00 AEST
[root@giggs2 ˜]# 

On reboot of just the guest, I get the following, the RTC looks OK:

[root@giggs2 ˜]# timedatectl 
  Local time: Thu 2015-01-22 18:05:09 AEDT
  Universal time: Thu 2015-01-22 07:05:09 UTC
    RTC time: Thu 2015-01-22 07:05:09
    Timezone: Australia/Sydney (AEDT, +1100)
 NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
  DST active: yes
 Last DST change: DST began at
  Sun 2014-10-05 01:59:59 AEST
  Sun 2014-10-05 03:00:00 AEDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
  Sun 2015-04-05 02:59:59 AEDT
  Sun 2015-04-05 02:00:00 AEST
[root@giggs2 ˜]#

On reboot of the host, I get the following on the guest, the RTC looks wrong:

[root@giggs2 ˜]# timedatectl 
  Local time: Fri 2015-01-23 05:15:41 AEDT
  Universal time: Thu 2015-01-22 18:15:41 UTC
    RTC time: Thu 2015-01-22 18:15:42
    Timezone: Australia/Sydney (AEDT, +1100)
 NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
  DST active: yes
 Last DST change: DST began at
  Sun 2014-10-05 01:59:59 AEST
  Sun 2014-10-05 03:00:00 AEDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
  Sun 2015-04-05 02:59:59 AEDT
  Sun 2015-04-05 02:00:00 AEST
[root@giggs2 ˜]#

Regards
Bill Maidment 
 
-Original message-
 From:David Sommerseth sl+us...@lists.topphemmelig.net
 Sent: Wednesday 21st January 2015 23:33
 To: Bill Maidment b...@maidment.me; SCIENTIFIC-LINUX-USERS@FNAL.GOV 
 SCIENTIFIC-LINUX-USERS@fnal.gov
 Subject: Re: SL7 - crond starting before chronyd causing problem with mrtg
 
 On 21/01/15 12:18, Bill Maidment wrote:
  Hi guys
  MRTG is having problems with timeshift because crond starts before chronyd 
  on SL7.
  I have added chrond.service as a dependancy to the crond.service. Is that 
  the right approach to solving the problem?
 
 This sounds like the right approach.  But systemd have different levels of
 dependencies.  I recommend you to check the dependency you used against man
 systemd.unit.  Check out After=, Requires= and Requisite=.
 
 --
 kind regards,
 
 David Sommerseth
 
 

RE: SL7 - crond starting before chronyd causing problem with mrtg

[Bill Maidment]

Thanks David.
However, even using After= chronyd.service the chronyd still takes too long to 
correct the time for the time-zone.

After some investigation, it seems that the KVM system is at fault when the 
host is rebooted, but not when the guest is rebooted.
On reboot of the host KVM adds the timezone shift to the hardware clock for the 
guests and then the guest adds the timezone shift again.
This extra addition of the timzone shift did not happen on SL6.

After running hwclock --systohc on the guest, I get the following setup.

[root@giggs2 ~]# timedatectl 
  Local time: Thu 2015-01-22 17:55:26 AEDT
  Universal time: Thu 2015-01-22 06:55:26 UTC
RTC time: Thu 2015-01-22 06:55:26
Timezone: Australia/Sydney (AEDT, +1100)
 NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
  DST active: yes
 Last DST change: DST began at
  Sun 2014-10-05 01:59:59 AEST
  Sun 2014-10-05 03:00:00 AEDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
  Sun 2015-04-05 02:59:59 AEDT
  Sun 2015-04-05 02:00:00 AEST
[root@giggs2 ~]# 

On reboot of just the guest, I get the following, the RTC looks OK:

[root@giggs2 ~]# timedatectl 
  Local time: Thu 2015-01-22 18:05:09 AEDT
  Universal time: Thu 2015-01-22 07:05:09 UTC
RTC time: Thu 2015-01-22 07:05:09
Timezone: Australia/Sydney (AEDT, +1100)
 NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
  DST active: yes
 Last DST change: DST began at
  Sun 2014-10-05 01:59:59 AEST
  Sun 2014-10-05 03:00:00 AEDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
  Sun 2015-04-05 02:59:59 AEDT
  Sun 2015-04-05 02:00:00 AEST
[root@giggs2 ~]#

On reboot of the host, I get the following on the guest, the RTC looks wrong:

[root@giggs2 ~]# timedatectl 
  Local time: Fri 2015-01-23 05:15:41 AEDT
  Universal time: Thu 2015-01-22 18:15:41 UTC
RTC time: Thu 2015-01-22 18:15:42
Timezone: Australia/Sydney (AEDT, +1100)
 NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
  DST active: yes
 Last DST change: DST began at
  Sun 2014-10-05 01:59:59 AEST
  Sun 2014-10-05 03:00:00 AEDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
  Sun 2015-04-05 02:59:59 AEDT
  Sun 2015-04-05 02:00:00 AEST
[root@giggs2 ~]#

Regards
Bill Maidment 
 
-Original message-
 From:David Sommerseth sl+us...@lists.topphemmelig.net
 Sent: Wednesday 21st January 2015 23:33
 To: Bill Maidment b...@maidment.me; SCIENTIFIC-LINUX-USERS@FNAL.GOV 
 SCIENTIFIC-LINUX-USERS@fnal.gov
 Subject: Re: SL7 - crond starting before chronyd causing problem with mrtg
 
 On 21/01/15 12:18, Bill Maidment wrote:
  Hi guys
  MRTG is having problems with timeshift because crond starts before chronyd 
  on SL7.
  I have added chrond.service as a dependancy to the crond.service. Is that 
  the right approach to solving the problem?
 
 This sounds like the right approach.  But systemd have different levels of
 dependencies.  I recommend you to check the dependency you used against man
 systemd.unit.  Check out After=, Requires= and Requisite=.
 
 --
 kind regards,
 
 David Sommerseth
 
 

SL7 - crond starting before chronyd causing problem with mrtg

[Bill Maidment]

Hi guys
MRTG is having problems with timeshift because crond starts before chronyd on 
SL7.
I have added chrond.service as a dependancy to the crond.service. Is that the 
right approach to solving the problem?

Regards
Bill Maidment
Landline: +61 2 4472 9374
Mobile: +61 418 682 993
Web: www.maidment.me

RE: Printer driver for Samsung CLP-415-NW on SL7

[Bill Maidment]

Thanks everyone for the suggestions. I didn't try copying anything from SL6 to 
SL7; maybe I had in the past installed the Samsung Unified Linux Driver.
Anyway the newer SULD seems to have done the trick.
Two small problem with the installation was that I had to stop firewalld and 
CUPS failed to restart (probably because of the systemd changes).

Regards
Bill Maidment 
 
-Original message-
 From:Karel Lang AFD l...@afd.cz
 Sent: Friday 14th November 2014 20:52
 To: Bill Maidment b...@maidment.me; SCIENTIFIC-LINUX-USERS@FNAL.GOV
 Subject: Re: Printer driver for Samsung CLP-415-NW on SL7
 
 Hi Bill,
 did you just try to copy the ppd file you're using on the 6 to 7 and 
 test result?
 
 cheers,
 -- 
 *Karel Lang*
 *Unix/Linux Administration*
 l...@afd.cz | +420 731 13 40 40
 AUFEER DESIGN, s.r.o. | www.aufeerdesign.cz
 
 On 11/14/2014 05:10 AM, Bill Maidment wrote:
  Hi
  I have been using a Samsung colour printer CLP-415-NW on SL6 using the 
  recommended CLP-310 series driver with good results.
  On SL7, the driver recommended (the only one shown) is CLP-410 series, but 
  this only prints in black and white.
  Has anyone found a colour version that will work on SL7?
 
  Regards
  Bill Maidment
  Landline: +61 2 4472 9374
  Mobile: +61 418 682 993
  Web: www.maidment.me
 
 
 
 
 
 

RE: Printer driver for Samsung CLP-415-NW on SL7 (solved)

[Bill Maidment]

That should have read now i CAN print in colour.
Sorry for the confusion!!

Regards
Bill Maidment 
 
-Original message-
 From:Bill Maidment b...@maidment.me
 Sent: Friday 14th November 2014 17:39
 To: Bill Maidment b...@maidment.me; SCIENTIFIC-LINUX-USERS@FNAL.GOV
 Subject: RE: Printer driver for Samsung CLP-415-NW on SL7 (solved)
 
 Well I found UnifiedLinuxDriver-4.00.39.tar.gz and installed it with 
 compat-libtiff3.
 Now I can't print in colour.

Printer driver for Samsung CLP-415-NW on SL7

[Bill Maidment]

Hi
I have been using a Samsung colour printer CLP-415-NW on SL6 using the 
recommended CLP-310 series driver with good results.
On SL7, the driver recommended (the only one shown) is CLP-410 series, but this 
only prints in black and white.
Has anyone found a colour version that will work on SL7?

Regards
Bill Maidment
Landline: +61 2 4472 9374
Mobile: +61 418 682 993
Web: www.maidment.me

RE: Printer driver for Samsung CLP-415-NW on SL7

[Bill Maidment]

Further investigation shows that the driver installed is a generic postscript 
driver and the Samsung list does not contain any CLP drivers.

Regards
Bill Maidment 
 
-Original message-
 From:Bill Maidment b...@maidment.me
 Sent: Friday 14th November 2014 15:13
 To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
 Subject: Printer driver for Samsung CLP-415-NW on SL7
 
 Hi
 I have been using a Samsung colour printer CLP-415-NW on SL6 using the 
 recommended CLP-310 series driver with good results.
 On SL7, the driver recommended (the only one shown) is CLP-410 series, but 
 this only prints in black and white.
 Has anyone found a colour version that will work on SL7?
 
 Regards
 Bill Maidment
 Landline: +61 2 4472 9374
 Mobile: +61 418 682 993
 Web: www.maidment.me
 
 

RE: Printer driver for Samsung CLP-415-NW on SL7 (solved)

[Bill Maidment]

Well I found UnifiedLinuxDriver-4.00.39.tar.gz and installed it with 
compat-libtiff3.
Now I can't print in colour.

Regards
Bill Maidment 
 
-Original message-
 From:Bill Maidment b...@maidment.me
 Sent: Friday 14th November 2014 15:33
 To: Bill Maidment b...@maidment.me; SCIENTIFIC-LINUX-USERS@FNAL.GOV
 Subject: RE: Printer driver for Samsung CLP-415-NW on SL7
 
 Further investigation shows that the driver installed is a generic postscript 
 driver and the Samsung list does not contain any CLP drivers.
 
 Regards
 Bill Maidment 
  
 -Original message-
  From:Bill Maidment b...@maidment.me
  Sent: Friday 14th November 2014 15:13
  To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
  Subject: Printer driver for Samsung CLP-415-NW on SL7
  
  Hi
  I have been using a Samsung colour printer CLP-415-NW on SL6 using the 
  recommended CLP-310 series driver with good results.
  On SL7, the driver recommended (the only one shown) is CLP-410 series, but 
  this only prints in black and white.
  Has anyone found a colour version that will work on SL7?
  
  Regards
  Bill Maidment
  Landline: +61 2 4472 9374
  Mobile: +61 418 682 993
  Web: www.maidment.me
  
  
 
 

Missing dependancy for gnucash

[Bill Maidment]

Hi
The latest security update on SL6.5 to gnucash is missing the dependancy 
libwebkitgtk-1.0.so.0

Regards
Bill Maidment
Landline: +61 2 4472 9374
Mobile: +61 418 682 993
Web: www.maidment.me

Wireshark broken os SL6x

[Bill Maidment]

After the latest yum update, wireshark fails with:
wireshark: symbol lookup error: wireshark: undefined symbol: 
gtk_combo_box_text_new_with_entry
wireshark-1.8.10-8.el6_6.x86_64

Regards
Bill Maidment
Landline: +61 2 4472 9374
Mobile: +61 418 682 993
Web: www.maidment.me

RE: Wireshark broken os SL6x

[Bill Maidment]

It looks like we need a new version of gtk2
Current version is gtk2-2.20.1-4.el6.x86_64
gtk2-2.24 is required for gtk_combo_box_text_new_with_entry


Regards
Bill Maidment 
 
-Original message-
 From:Bill Maidment b...@maidment.me
 Sent: Friday 24th October 2014 18:01
 To: SCIENTIFIC-LINUX-USERS@FNAL.GOV
 Subject: Wireshark broken os SL6x
 
 After the latest yum update, wireshark fails with:
 wireshark: symbol lookup error: wireshark: undefined symbol: 
 gtk_combo_box_text_new_with_entry
 wireshark-1.8.10-8.el6_6.x86_64
 
 Regards
 Bill Maidment
 Landline: +61 2 4472 9374
 Mobile: +61 418 682 993
 Web: www.maidment.me
 
 

RE: libvirt guests graceful shutdown upon hosts powerdown/reboot

[Bill Maidment]

Hi
In SL6 /etc/sysconfig/libvirt-guets defaulted to suspend the guests, so I 
changed it to shutdown guets with:
ON_BOOT=ignore
ON_SHUTDOWN=shutdown
PARALLEL_SHUTDOWN=6
SHUTDOWN_TIMEOUT=90

It looks like SL7 has the same settings, but I haven't tried them yet.

Regards
Bill Maidment 
 
-Original message-
 From:Karel Lang AFD l...@afd.cz
 Sent: Wednesday 22nd October 2014 21:11
 To: lejeczek pelj...@yahoo.co.uk; scientific-linux-users@fnal.gov
 Subject: Re: libvirt guests graceful shutdown upon hosts powerdown/reboot
 
 Hi,
 IMHO, the libvirt-guests init script which is part of libvirt-client rpm 
 package should take care of suspending the guests upon shutdown procedure?
 
 
 -- 
 *Karel Lang*
 
 On 10/22/2014 11:58 AM, lejeczek wrote:
  hi everybody
 
  by an assumption I expected VM guests to be shut down/off gracefully
  when the host is being powered down or rebooted, but this does not seem
  to be the case so I wonder..
  Am I missing some libvirt components/packages ?
  Or my assumption is incorrect and guests have to be shutdown manually?
  it's all SL 7 and guest are M$
 
  regards
  P.
 
 
 
 -- 
 *Karel Lang*
 
 

No public key on bash and NetworkManager updates for SL7

[Bill Maidment]

Hi
When running yum update on SL7rc2 i got the following warnings:

warning: 
/misc/yum/7x/x86_64/updates/fastbugs/NetworkManager-0.9.9.1-26.git20140326.4dba720.el7_0.x86_64.rpm:
 Header V4 DSA/SHA1 Signature, key ID 192a7d7d: NOKEY
Public key for NetworkManager-0.9.9.1-26.git20140326.4dba720.el7_0.x86_64.rpm 
is not installed
Public key for bash-4.2.45-5.el7_0.4.x86_64.rpm is not installed

Regards
Bill Maidment

RE: Final Solution to Chinese Break in

[Bill Maidment]

There used to be an organisation called Interpol to deal with international 
crime. I haven't heard anything recent about them; do they still exist?

Regards
Bill Maidment
 
 
-Original message-
 From:Paul Robert Marino prmari...@gmail.com
 Sent: Sunday 5th October 2014 9:14
 To: Nico Kadel-Garcia nka...@gmail.com; Larry Linder 
 larry.lin...@micro-controls.com
 Cc: SCIENTIFIC-LINUX-USERS@FNAL.GOV scientific-linux-users@fnal.gov
 Subject: Re: Final Solution to Chinese Break in
 
 
 One other problem is the FBI can only investigate criminals operating within 
 the united states they really can't do any thing if the criminal is operating 
 out of an other country due to their mandated scope of enforcement. 
 In fact internet crimes are really difficult for any law enforcement because 
 they are usually international and there for exceed their jurisdiction. The 
 laws that limit jurisdiction are ment to protect our rights and prevent any 
 one law enforcement agency from having enough power to threaten the 
 government; however this makes it nearly impossible for any one of them to 
 truly investigate internet crimes. What is needed is a new agency who's 
 jurisdiction is international internet crimes; however that also presents its 
 own risks because if you think the NSA is bad about respecting our rights 
 just wait to see what an international agency tasked with tracking internet 
 crimes would do.
 
 -- Sent from my HP Pre3

Missing images in SL7-rc1 iso ?

[Bill Maidment]

Hi
I created a virtual server from SL7-rc1 Everything iso using PXE.
On the PXE server i got these error messages:
[Thu Oct 02 17:18:52 2014] [error] [client 192.168.2.166] File does not exist: 
/var/www/html/iso/SL-7/images/updates.img
[Thu Oct 02 17:18:52 2014] [error] [client 192.168.2.166] File does not exist: 
/var/www/html/iso/SL-7/images/product.img

Should these images be present within the iso?

Regards
Bill Maidment

RE: gnome-disk-utility

[Bill Maidment]

Try right-click on top bar (panel) and then Add to Panel

Cheers
Bill
 
 
-Original message-
 From:Vladimir Mosgalin mosga...@vm10124.spb.edu
 Sent: Monday 25th August 2014 19:03
 To: scientific-linux-users@fnal.gov
 Subject: Re: gnome-disk-utility
 
 Hi ToddAndMargo!
 
  On 2014.08.24 at 16:45:50 -0700, ToddAndMargo wrote next:
 
  Yup.  That is it.  Thank you!
  
  Also, it has no man or info page.
  
  How do I get it up in my task bar, as does the Live CD?
 
 I'm not sure, depends on desktop environment you use o.o
 I believe in gnome2 you could right-click panel and pick add
 application or something. Isn't it in normal application menu? It
 should be, as it has proper .desktop file (somewhere in System
 category).
 
 I don't use gnome desktop on any EL6 system so I can't help with precise
 instructions sorry.
 
 -- 
 
 Vladimir
 
 

RE: TFTP boot

[Bill Maidment]

 
That should be:

   hardware ethernet 08:00:2b:4c:a3:82;

 
-Original message-
 From:Patrick Mahan ma...@mahan.org
 Sent: Monday 28th July 2014 15:00
 To: Mahmood Naderan nt_mahm...@yahoo.com
 Cc: scientific-linux-users@fnal.gov
 Subject: Re: TFTP boot
 
 
 
 On Jul 27, 2014, at 1:01 PM, Mahmood Naderan nt_mahm...@yahoo.com 
 mailto:nt_mahm...@yahoo.com wrote:
 
 Hello,
 
 I want to setup a diskless node and it should boot from a server. The guide 
 in http://wiki.centos.org/HowTos/PXE/PXE_Setup 
 http://wiki.centos.org/HowTos/PXE/PXE_Setup explains DHCP setup. However I 
 want to assign static IP to the node. As a result, I have to add the node's 
 MAC address somewhere in the server's configuration file.
 
 Where should I do that?
 
 Try googling static dhcp lease linux.
 
 For example on a RH/CentOS/Fedora platform acting as your DHCP server, in 
 /etc/dhcpd.conf:
 
 #
 
 # assign a static lease to our printer
 
 #
 
 host lj4100 {
 
         hardware 08:00:2b:4c:a3:82;
 
         fixed-address 192.168.1.125;
 
 }
 
 Patrick
 
 Coming to you from deep inside Fortress Mahan
 
 

No emails reaching me

[Bill Maidment]

Hi
Is the list suddenly quiet? I have not received any emails for a few days. Was 
the SL7 Beta-1 announced?
Or do I have a problem at my end?

Regards
Bill Maidment

RE: No emails reaching me

[Bill Maidment]

Hmm. I found a few mis-filtered emails about rpm-problem but I never got the 
Beta announcement.
Anyway my auto rsync picked up all the new stuff.
Cheers
 
 
-Original message-
 From:Andras Horvath m...@log69.com
 Sent: Saturday 26th July 2014 18:21
 To: Bill Maidment b...@maidment.com.au
 Cc: scientific-linux-users@fnal.gov. scientific-linux-users@fnal.gov
 Subject: Re: No emails reaching me
 
 SL7 Beta 1 was the last email for me too (arrived 12 hours ago).
 
 
 On Sat, 26 Jul 2014 17:26:34 +1000
 Bill Maidment b...@maidment.com.au wrote:
 
  Hi
  Is the list suddenly quiet? I have not received any emails for a few days. 
  Was the SL7 Beta-1 announced?
  Or do I have a problem at my end?
  
  Regards
  Bill Maidment
 
 

Feedback on SL7 alpha 2

[Bill Maidment]

Hi again
After installing SL7 alpha 2, right at the end of the install, there is a 
warning message at the bottom of the screen referring to a redhat EULA. 
Should this text be amended?

Regards
Bill Maidment

Dependency Issue in fastbugs

[Bill Maidment]

Hi
There seems to be a dependency is the latest fastbugs for syslinux

-- Processing Dependency: syslinux-extlinux-nonlinux for package: 
syslinux-extlinux-4.02-16.el6_5.x86_64
-- Finished Dependency Resolution
Error: Package: syslinux-4.02-16.el6_5.x86_64 (sl6x-fastbugs)
   Requires: syslinux-nonlinux
Error: Package: syslinux-extlinux-4.02-16.el6_5.x86_64 (sl6x-fastbugs)
   Requires: syslinux-extlinux-nonlinux

Regards
Bill Maidment

RE: Exchange server alternative?

[Bill Maidment]

Have you looked at zarafa?
Cheers
Bill
 
 
-Original message-
 From:Steven Haigh net...@crc.id.au
 Sent: Saturday 8th February 2014 13:45
 To: scientific-linux-users@fnal.gov
 Subject: Re: Exchange server alternative?
 
 On 08/02/14 13:08, ToddAndMargo wrote:
  So I was wondering what you all thought would be a good
  SL6.x substitute for Exchange server?
 
 I'd actually be interested in this too... I wrote a howto[1] on getting
 virtual mail hosting using mysql + postfix + dovecot - however the big
 thing that is missing is contacts / calendar integration.
 
 Thunderbird can use caldav for calendar data, but the integration
 doesn't really seem to be there. As for contacts, this has the similar
 problem.
 
 I'd also be very interested in a method to sync calendar + contacts that
 can be easily tied into Thunderbird / Android
 
 -- 
 Steven Haigh
 
 Email: net...@crc.id.au
 Web: https://www.crc.id.au
 Phone: (03) 9001 6090 - 0412 935 897
 Fax: (03) 8338 0299
 
 1 - https://www.crc.id.au/virtual-mail-hosting-on-el6/
 
 

Problem loading iwldvm.ko with kernel-2.6.32-431

[Bill Maidment]

Hi
I tried out the new kernel due in SL6.5 and I couldn't get wifi to work as the 
iwldvm module fails to load.

modprobe iwldvm gives me:
WARNING: Error inserting iwlwifi 
(/lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko):
 Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting iwldvm 
(/lib/modules/2.6.32-431.el6.x86_64/kernel/drivers/net/wireless/iwlwifi/dvm/iwldvm.ko):
 Unknown symbol in module, or unknown parameter (see dmesg)

dmesg shows:
mac80211: Unknown symbol unregister_inet6addr_notifier
mac80211: Unknown symbol register_inet6addr_notifier

Anyone know what is the problem?

Regards
Bill Maidment