Fedora Linux Support Community & Resources Center
  #1  
Old 4th April 2017, 07:42 AM
nobody Offline
Registered User
 
Join Date: Mar 2012
Location: München, Deutschland
Posts: 661
windows_98_nt_2000chrome
Question Policy kit daemon fails to start due to Timeout

I had very strange error after I upgraded my Fedora 27 (rawhide). After upgrading, and rebooting, login stalls forever. This seems to happen when polkitd could not be started by systemd.

It appeared similar to this:
Code:
polkit.service operation timed out. Terminating.
systemd[1]: Failed to start Authorization Manager.
Job for polkit.service failed. See 'systemctl status polkit.service' and 'journalctl -xn' for details.
So, what I did (since nothing good happened while entering init=/bin/bash in kernel command line in GRUB2 menu), I de-installed polkit package. Because of dependencies, it de-installed most of gnome and some "other" packages.

After rebooting, I was able to get to normal run level 3 (and I have all 6 terminals), but network would not work. It'll show ONLY IPV6 on ETH (ens33 I/F), no sign of Wireless at all. And even giving IPV4 address manually to ETH/ens33, it would not ping wireless router (address which of I know).

ifconfig command shows something like this:

Code:
ens33  Link encap:Ethernet  HWaddr e8:03:9a:97:61:b1  
          inet6 addr: fe80::ea03:9aff:fe97:61b1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets: 0 errors:0 dropped:1 overruns:0 frame:0
          TX packets: 0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:  TX bytes:

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:1289 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1289 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:114509 (114.5 KB)  TX bytes:114509 (114.5 KB)
I tried many things, but not able to connect with the host (since my Fedora rawhide is, after all, VM).

Any suggestions?

Thank you,
_nobody_
__________________
I am nobody, and nobody is perfect, therefore I am perfect!
Reply With Quote
  #2  
Old 4th April 2017, 08:20 PM
dd_wizard Offline
Registered User
 
Join Date: Sep 2009
Posts: 1,995
linuxfedorafirefox
Re: Policy kit daemon fails to start due to Timeout

This early in the rawhide cycle, I leave the display manager disabled, and boot to multi-user instead of target.
Code:
# systemctl set-default multi-user

# systemctl disable lightdm

# reboot
When you get the terminal after booting, login as your normal user and run startx. When there fatal errors, like a broken polkit, you usually come back to a terminal. In the current situation, I'm logging in as root and running dnf upgrade until I see a new polkit being installed. There's not much point in trying to run x, or wayland, until that is fixed.

dd_wizard
Reply With Quote
  #3  
Old 15th May 2017, 09:14 PM
nobody Offline
Registered User
 
Join Date: Mar 2012
Location: München, Deutschland
Posts: 661
windows_98_nt_2000chrome
Question Re: Policy kit daemon fails to start due to Timeout

Hello Wizard of Oz,

Sorry for the long delay. I (after beginning of April, after this thread) got stuck on some completely different jobs/activities, and as well, I travelled a lot.

I am finally back...

And yes, before disappearing, I tried what you suggested to me. But it is not GFX, neither front end Desktop, neither X11 as back-end. It is something very ugly which happened with the IPV4 and WiFi Drivers/SW. I tried desperately to recover F27 VM, which I have for a year (as rawhide) destroyed 3x, and all 3x was able to save/fix/patch and recover it... NOT this time?!

So, in order to save data, I was able to copy data to two large USBs, and to capture several thousands installed package names using rpm -qa command.

Whole day today I spent time to un-rust my C skills, and I was able to create C parser which from installed list of packages (captured as file) is able to create several thousand lines of dnf install <package name SANS version> script, which I am now executing on my Fedora 26 VM.

I'll publish this C script on GitHub as public code, with GPL2 licence, but this must wait till tomorrow (I am tired as a dingo/AUStralian wild dog).

_nobody_
__________________
I am nobody, and nobody is perfect, therefore I am perfect!
Reply With Quote
  #4  
Old 16th May 2017, 08:35 AM
nobody Offline
Registered User
 
Join Date: Mar 2012
Location: München, Deutschland
Posts: 661
windows_98_nt_2000chrome
Talking Re: Policy kit daemon fails to start due to Timeout

Quote:
Originally Posted by nobody View Post
I'll publish this C script on GitHub as public code, with GPL2 licence, but this must wait till tomorrow (I am tired as a dingo/AUStralian wild dog).
Here we go: rpm -qa "C" parser
http://www.forums.fedoraforum.org/sh...d.php?t=314276

_nobody_
__________________
I am nobody, and nobody is perfect, therefore I am perfect!
Reply With Quote
Reply

Tags
daemon, fails, kit, policy, start, timeout

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Hal Daemon Fails to Start shduff Using Fedora 8 25th November 2013 08:48 PM
Hal daemon fails to start mukiwa Using Fedora 3 9th December 2006 06:49 PM
Timeout error occurred trying to start MySQL Daemon Mat Servers & Networking 1 15th December 2004 12:48 PM
Timeout error occurred trying to start MySQL Daemon Mat Using Fedora 0 21st November 2004 11:33 PM


Current GMT-time: 16:26 (Thursday, 25-05-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat