Bug 1210266

Summary: chrony: log flooded with error messages
Product: [Fedora] Fedora Reporter: Felix Miata <mrmazda>
Component: chronyAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 22CC: anaconda-maint-list, awilliam, extras-qa, g.kaviyarasu, jonathan, mlichvar, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Unspecified   
Whiteboard:
Fixed In Version: chrony-2.0-1.fc22 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1194991 Environment:
Last Closed: 2015-06-26 13:57:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda logs .tgz none

Description Felix Miata 2015-04-09 10:07:40 UTC 
Created attachment 1012620 [details]
anaconda logs .tgz

+++ This bug was initially created as a clone of Bug #1194991 +++

Description of problem:
installation cannot proceed past Welcome/language selection screen

Version-Release number of selected component (if applicable):
anaconda-22.20.8-1

How reproducible:
start installation on 32 bit Socket A Sempron with NForce2 chipset & rv200 radeon (host m7ncd)

Steps to Reproduce:
1.start HTTP installation via boot.iso or Grub
2.click "Continue" on Welcome to screen

Actual results:
Installation summary wheel screen paints, then an empty popup appears, and nothing is possible on the screen except for moving the mouse pointer

Expected results:
Installation can proceed

Additional info:
1-I've been trying to get Xorg/KF5 to work on this host, in both F22 and Rawhide, off and on for several months without success, to follow-up in Rawhide to bug 1096487 , getting black screen from what should be sddm or kdm greeter, and plasma-workspace segfault from trying startx, with no clues given by Xorg.0.log. With same host, Cauldron and Tumbleweed, XOrg and K* are working as expected except for bug 1096487.
Comment 1 David Shea 2015-04-14 13:30:37 UTC 
Two things stand out in the logs:

1) there are an absurd number of partitions, and checking them is taking a while. There is nothing that can be done about this. The partition checks run in a separate thread, so if this is making the rest of the GUI unresponsive it's because your system does not have the capacity to run fsck and also run a GUI

2) chronyd is flooding the log with " ERR chronyd: Could not open IPv6 NTP socket : Address family not supported by protocol". Reassigning to chrony for that part of it.
Comment 2 Miroslav Lichvar 2015-04-14 14:04:56 UTC 
Fixed in upstream git:

http://git.tuxfamily.org/chrony/chrony.git/commit/?id=fdf9640349f1432ed2c2a0d343bca06fe9771e0d
Comment 3 Felix Miata 2015-04-15 05:25:04 UTC 
(In reply to David Shea from comment #1)
> 1) there are an absurd number of partitions, and checking them is taking a
> while. There is nothing that can be done about this. The partition checks
> run in a separate thread, so if this is making the rest of the GUI

But for bug 1202024 there shouldn't have been any significant time spent checking.

> unresponsive it's because your system does not have the capacity to run fsck
> and also run a GUI

Retrying with today's failed to reproduce the GUI hang. OTOH, I waited 20 minutes on tty2 watching top tell me e2fsck was busy and 100% of swap was available before proceeding with installation.