Fedora :: Slow Boot Time / "Starting System Message Bus"?
Dec 14, 2009
My fedora 11 (2.6.30-102) spends a long time while initializing services on
"Starting system message bus:"
---------- Post added at 08:47 PM CST ---------- Previous post was at 06:33 PM CST ----------
Auth is LDAP.
There's a 3.5 years old bug in redhat bugs database, that's still not resolved,regarding dbus trying to use ldap auth, before ldap service is started.Workaround is to change ldap config to soft binding.
3.5 years for a bug that affect enterprise users - are you there redhat?
When booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
i'm heaving the following message at boot time: "Starting udev: udevd[114]: unknown key 'DEVTYPE' in /etc/udev/rules.d/70-cups-libusb.rules:6", i guess it's something about usb printing support but i am not sure, and i don't know how to fix it, does any of you guys know what this exactly means and how to fix it
I am running my Ubuntu 32 bit server on top of Windows 7 64 bit with VirualBox. It's a 2 core Atom. It's been working good for about half a year. But the last about 6 weeks the system time only in Ubuntu is going slow. About -8 per 24 hours! I can only guess because I have more things running in my Windows 7 and Ubuntu.
I can set it right by coping the hareware time to system time with this command:
Code: hwclock --hctosys
I want to run a crontab to have that command run every minute. But it don't seem to run.
I'm using Fedora 12 since 2 years lately, I really enjoy this S.O., it's quite robust and wonderful, but a couple of months ago it is really slow to boot up when startup the computer, I've checked everything, but seems to be ok, I had a partition lost arround that date, but recover successfully, it happens when I run gparted that It cannot see partition on my 500 GB disk, but still boots up. When running Mandriva live cd, it can see (?) all partitions on that disk, even with Fedora Dolphin I can access this partitions. What could it be?
I am having dual boot system(windows 7 and Fedora 12).When i switch on my system.It show the the timer 3 sec in order to get boot selection window(means window which asks that what to start fedora 12 or windows 7).I want to increase this time from 3 to 10 sec.
I've been a long time Windows user, but I've started a small firm and because of lack of funds, I've decided to install Ubuntu on my company's PCs.I have 8 PCs in total - 6 of them with Intel CPUs, and the last two with AMD CPUs. I bought the extra two computers because I've managed to find an extra two people to work at my company, and AMD-based PCs are cheaper so I've decided to buy them instead of Intel.Long-story short, I've installed Ubuntu 9.10 and boot time takes about half-an-hour. After the computers finally boot, USB hardware doesn't work at all. I was forced to buy PS/2 keyboards & mice and they both work fine after the PCs boot.I don't know what's causing this delay.I've enabled Cool 'n Quiet from BIOS.I've tried several instructions like editing the /etc/modules file.I've installed cpufreqd, tried to configure it, but it didn't work.I've check the CPU stats and my CPUs are running at 800MHz. I can't believe nobody managed to fix the 800MHz problem as I've noticed it's quite common among AMD Ubuntu users. I think I've tried almost anything that I've found on this forum.I can't keep asking my employees not to reboot their PCs. Both Chrome/Firefox crash a lot on Ubuntu so they're forced to restart their computers.The computer specs are: AMD Athlon II X2 240 dual-core @ 2.800MHz, 2GB RAM, 500GB HDD, etc.
I've got two laptops running Ubuntu. Both have had Lucid installed from the live cd. I have upgraded one of them to Maverick. Both distributions are running great after they boot up, but I haven't experienced any faster boot times with either distibution. Both boot to Bios and then the screen goes black with a blinking cursor in upper left corner of the screen. The black screen remains for 30 to 45 seconds and then I get the Ubuntu splash screen for maybe 5 seconds, and then desktop. Why am I not seeing faster boot times? I realize 45 to 60 seconds is good compared to other os's, but I anticipated much faster boot times. Shut down on the other hand is quite fast at maybe 5 to 10 seconds. Does anyone else get this black screen on boot? Seems like wasted time cause I can't tell what's going on during the time there is a black screen. This is not a real big deal breaker, as I don't reboot very often, but I just wonder why bootup isn't faster.
i wanted to know how can I make my programs or script automatically start at boot time ,for example if I restart my server at any time they start at boot time automatically with no need to any body to start them.
I have a SSH box which is command line only and no X, this will be used remote and i'm trying to get the wireless network configured to start at boot. I'm using wpa_supplicant as the access point is secure with WPA2 At present if I send the following commands the machine will connect to the wifi and be reachable via ssh
This does not start at boot but requires manual input of the above commands. I've just come to a complete blank on geting this to start at boot time. Also I would like to set a fixed IP for this box.
After a new Fedora 12 installation, i cannot automount my Windows partition. My system is setup originally at windows XP ,partitioned, then change to Fedora 10. Change to Fedora 11 through update.System very slow.
I decided to upgrade to fedora 12 by DVD installer, then i have to mount manually to access my back-up, when typing su -c '/sbin/fdisk -l' at terminal, this is the code:
why, after booting to windows for any length of time that upon rebooting to Fedora the system time is 3 or 4 or 6 hours off? Sure, it is easily fixed with ntpdate but is there a more permanent fix?
I installed and configured privoxy - everything worked nicely when I run it manually by
Quote: /etc/init.d/privoxy start
After restarting the computer privoxy wasn't start automatically. I checked the links in /etc/rcX.d - are o.k. I installed sysv-rc-conf - shows that for runlevel 2 - 5 privoxy is running. I changed /etc/rc2.d/S20privoxy to /etc/rc2.d/S99privoxy - to start that process at the end. I installed Boot-Up Manager. Privoxy is marked for start automatically. I added in /etc/rc.local line: /etc/init.d/privoxy start
Privoxy still doesn't turn on at boot time and every time I must start it manually. Could you tell me how could I repair this ?
Probing EDD (edd=off to disable) .... then the boot hang up for a few minutes with a flashing cursor immediately after the message and finally it booted the default OpenSuse 11.1 in the usual way. I tried to search LQ, Wikipedia, Google... but even if the message has been reported by many people, nobody gave the answer to the question running in my mind:
Code:
What is EDD? Should I start to think about the funeral for my beloved notebook? Should I consider to do an additional backup copy of the backup of my disk, just for sure?
How do I speed up the Macbook Pro boot time? In OSX when I boot it goes directly to the mac logo. In Ubuntu there seems to be a 10 second or more hesitation before it access my hard drive. Is there anyway to change some settings in the BIOS / EFI?
I'm using OpenSUSE 11.2 with all the released updates are installed. I've got an Windows Xp SP3 on the same hard drive and it's works fine. S.M.A.R.T. says the hdd is 100%. A few days ago I realized that the boot time increased and the hard drive operations takes way too much time. So currently the boot sequence takes 11-14 minutes.
I've already tried to solve this problem but no effect: 1.) cleaned up the root directory to create more free space 2.) plugged the sata cable to another port 3.) changed from AHCI to IDE and reverse in BIOS settings 4.) added ahci, sata_nv into the /etc/sysconfig/kernel file and created a new initrd 5.) searched for problems in the syslog Just to imagine how slow is currently the system/hdd:
I installed OS11.4 on my old laptop, Compaq Armada E500., 512MB RAM, ATI Rage Mobility. During installation I chose "minimal server" and added some development packages, lxde and a little more. I chose to start in runlevel 3 which is full networking without X. Still, when computer is booted it tries to start Xorg which doesn't work because of some problem w driver. The start-up seems to stop there, it never loads completely - seems most things in runlevel 3 are not started (see below) I can manually login on laptop and fix it - but never permanently, same thing again after reboot.
I have checked /etc/inittab & yast - both states default runlevel is 3. I have checked services to be started both directly, browsing directory /etc/rc.d/rc3.d/, and with YaST, it is very clear X should not load during boot. But, as said, it does.. I don't really care about the driver problem right now, I can fix that later when I have more time. So how do I stop X from getting started automatically?
More info, if needed: The installation also stopped with message on tty1 "Starting YaST2" and tty8 showing errors with graphics driver (mach64). The system seemed to be installed though, so I simply rebooted (issuing "reboot" from tty2).
[Code]....
I'm not completely sure where it stops, network is configured but keyboard is wrong and mysql & everything after is not started, so somewhere between S02network and S06kbd. I'm going to use it as a server for testing purposes so no X is actually needed - however I do want to have X & lxde installed just in case, my Internet connection at home is terribly slow so I need most things I might need in the future installed today.
My laptop boot up time increased considerably (10 seconds) after allocating a virtual drive for virtualbox guest. The guest installation did not work so i removed it along with the virtual disk. Now everytime when i boot to ubuntu, after inputting my password in the login screen, it takes much longer to load the system. And during the loading time the disk activity indicator light blinks indicating the harddisk is actually busy loading the system.
I decided to search around for a possible answer and force reprofiling ureadahead does the trick Now boot time is back to what it used to be
When booting the system ,"starting system logger : Failed" after that i login to the system as usual but the system logger cannot start,even i use the service syslog restart command,how can i solve such problem ,thanks a lot
I have linux in my system with windows (dual boot). Now when I start my PC. It shows me only Linux, in splash screen. but when i press ENTER key on this. It starts in windows not in linux. And I completely unable to boot my system in linux.
We have 2 applications set as S96 and S98 at rc3.d and rc5.d simultaneously. Both applications create a system V shared memory segment by calling shmget.If the system boot at runlevel 5, both applications can obtain their shared memory segment id correctly, i.e. 98305 and 131074 individually. While there is a root owned segment id 32768 takes first seat on the list. This is the id list:
I've been having a problem on my AMD based machine, 4cpu, gigabyte ga-ma78gm-s2h Mobo, 8GB mem, two 2 terabyte Sata HDs.One thing I've found is that any kernel after 2.6.32-17 has a randomness at boot time whether the system will completely boot or not.
For instance just today I downloaded and installed 2.6.32-24
It fails to boot (I've tried cold boot, warm boot).Running its repair also fails to completely boot.My experience is that if I keep trying it "may" eventually boot but I believe there was some change after 2.6.32-17-generic that's causing the problem.Because as with 2.6.32.23... which also fails to complete bootup many times... eventually my guess is that 2.6.32.24 will also boot "sometimes".But why does 2.6.32.17 always boot for me? Something changed and its not my setup.
I got a message today telling me that there where 78 updates available. One of them was Kernel 2.6.29.6-213.fc11.i586 and when I installed all the updates and rebooted, my startup time was very slow. And when I checked the boot.log I noticed this:
I have installed fedora 13 in my system. httpd server is also installed. when I tried to start the service of httpd, following error message displayed: Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
