updates broke system, no x, try level 3 but cannot even log in (f20)

Michael D. Setzer II mikes at kuentos.guam.net
Wed May 20 16:30:37 UTC 2015


On 20 May 2015 at 7:55, Antonio Olivares wrote:

Date sent:      	Wed, 20 May 2015 07:55:33 -0800
From:           	Antonio Olivares <wingators at inbox.com>
Subject:        	updates broke system, no x, try level 3 but cannot even 
log in (f20)
To:             	Community support for Fedora users 
<users at lists.fedoraproject.org>
Send reply to:  	Community support for Fedora users 
<users at lists.fedoraproject.org>
	
> Dear folks,
> 
> the title says it all.  running fedora 20 updates I installed are:
> 
>   Verifying  : firefox-38.0-4.fc20.x86_64                                  1/26 
>   Verifying  : 1:perl-Socket-2.019-1.fc20.x86_64                           2/26 
>   Verifying  : glusterfs-fuse-3.5.3-2.fc20.x86_64                          3/26 
>   Verifying  : ibus-libs-1.5.10-4.fc20.x86_64                              4/26 
>   Verifying  : ibus-gtk3-1.5.10-4.fc20.x86_64                              5/26 
>   Verifying  : glusterfs-libs-3.5.3-2.fc20.x86_64                          6/26 
>   Verifying  : ibus-wayland-1.5.10-4.fc20.x86_64                           7/26 
>   Verifying  : glusterfs-3.5.3-2.fc20.x86_64                               8/26 
>   Verifying  : glusterfs-api-3.5.3-2.fc20.x86_64                           9/26 
>   Verifying  : ibus-1.5.10-4.fc20.x86_64                                  10/26 
>   Verifying  : fedora-release-20-4.noarch                                 11/26 
>   Verifying  : ibus-gtk2-1.5.10-4.fc20.x86_64                             12/26 
>   Verifying  : ibus-setup-1.5.10-4.fc20.noarch                            13/26 
>   Verifying  : ibus-setup-1.5.10-1.fc20.noarch                            14/26 
>   Verifying  : glusterfs-api-3.5.3-1.fc20.x86_64                          15/26 
>   Verifying  : ibus-libs-1.5.10-1.fc20.x86_64                             16/26 
>   Verifying  : firefox-37.0.2-1.fc20.x86_64                               17/26 
>   Verifying  : fedora-release-20-3.noarch                                 18/26 
>   Verifying  : ibus-1.5.10-1.fc20.x86_64                                  19/26 
>   Verifying  : 1:perl-Socket-2.018-1.fc20.x86_64                          20/26 
>   Verifying  : ibus-gtk2-1.5.10-1.fc20.x86_64                             21/26 
>   Verifying  : glusterfs-3.5.3-1.fc20.x86_64                              22/26 
>   Verifying  : glusterfs-fuse-3.5.3-1.fc20.x86_64                         23/26 
>   Verifying  : glusterfs-libs-3.5.3-1.fc20.x86_64                         24/26 
>   Verifying  : ibus-gtk3-1.5.10-1.fc20.x86_64                             25/26 
>   Verifying  : ibus-wayland-1.5.10-1.fc20.x86_64                          26/26 

> Updated:
>   fedora-release.noarch 0:20-4           firefox.x86_64 0:38.0-4.fc20          
>   glusterfs.x86_64 0:3.5.3-2.fc20        glusterfs-api.x86_64 0:3.5.3-2.fc20   
>   glusterfs-fuse.x86_64 0:3.5.3-2.fc20   glusterfs-libs.x86_64 0:3.5.3-2.fc20  
>   ibus.x86_64 0:1.5.10-4.fc20            ibus-gtk2.x86_64 0:1.5.10-4.fc20      
>   ibus-gtk3.x86_64 0:1.5.10-4.fc20       ibus-libs.x86_64 0:1.5.10-4.fc20      
>   ibus-setup.noarch 0:1.5.10-4.fc20      ibus-wayland.x86_64 0:1.5.10-4.fc20   
>   perl-Socket.x86_64 1:2.019-1.fc20     
> 
> Complete!
> 
> Systemd shows some failed services; if I leave graphical screen I get Oh
> no something has gone wrong and it dies off does not go to login screen. 
> When I start by adding a 3 and removing rhgb and quiet I see that some new
> jobs get started and restarting some failed services and ..., then I get
> the login prompt and I type username and it stays there no progress.  What
> happened?  What was wrong with these updates?  anybody else have this
> problem? 
> 
> Thanks!
> 
> 
> Antonio A. Olivares

Haven't seen that problem, but I've seen some issue with systemd and 
services.

What does 

systemctl --state=failed 

report?

I just had a system that I updated from Fedora 20 to Fedora 21, and thought 
everything went without a problem. Then someone tried to print, and cupsd 
wasn't working along with a couple of other services. After doing a lot of 
searching. It was nothing wrong with cupsd service, but the colord service 
was failing since it couldn't upgrade the db files since they were owned by 
root and not colord?? Once I changed the ownership, and restarted colord 
and cupsd it started working again. 

For some reason, also seeing the dnf cache service fails from time to time on 
many systems??

I created a script to test can try to fix issues, and just seeing the dnf cache 
issue, and another service that I can't recall the fail from time to time.

In /etc/cron.hourly fixsystemctl

chksystemctl=`systemctl --state=failed | grep failed | cut -f 2 -d\  `
if [ -n "$chksystemctl" ] ; then
	date >>/var/log/chksystemctl
        echo $chksystemctl >>/var/log/chksystemctl
	systemctl restart $chksystemctl
fi

So, failed services can cause issues. 
Had to use systemctl status (service) -i 
and look at message log file to get info.


> 
> ____________________________________________________________
> FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop!
> Check it out at http://www.inbox.com/marineaquarium
> 
> 
> -- 
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org


+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:mikes at kuentos.guam.net                            
  mailto:msetzerii at gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC at HOME CREDITS
ROSETTA     29616971.088964   |   SETI        52324657.991736
ABC         16613838.513356   |   EINSTEIN    61291230.682700



More information about the users mailing list