[SOLVED] Borked systemd setup -- dbus errors during boot; can't login

I have error messages very similar to this post. Unfortunately, as the author states, he never persisted in solving it but instead re-installed from scratch. I'd rather not do that.
For reference, I have a pure systemd setup -- no rc.conf file, no initscripts package, etc.
At boot I get the "Welcome to Arch!" messages followed by the various [OK] lines and then I get blindingly fast repeating lines about dbus not starting and attempting to restart it too quickly. If I walk away for about 1-2min, I finally see a login screen, but after entering my username/password, it just sits there and does nothing.
As for suspects... I had systemd working fine.
-- I updated some packages (not more than a few days worth and I'd have to check the list)
-- I also took care of manual updates to some .pacnew files I periodically check for. In this group were some biggies: group, shadow, and passwd. I did recall the odd bit about uuidd changing from uid 995 to 68, but in reading about that since then, it doesn't seem to be a big deal.
I've been booting in by appending
systemd.unit=emergency.target
to the kernel line, but my exploration hasn't been all that helpful. `journalctl since=date` reveals the errors, but I don't get much information about why dbus is having issues starting.
emergency.target also doesn't seem to be that helpful since I can't do anything with a read-only system. I'd love some suggestions about what, specifically, to check for before I reboot from Windows back into Arch and record more careful notes, probably by jotting notes onto a flash drive. Any places to start? For reference, I've done:
-- systemctl status dbus: lists as inactive (dead) and simply shows the errors I see at boot (failed to start)
-- systemctl list-units
-- systemctl list-unit-files
-- journalctl and looking around for instances of fail or failed or dbus
If I start systemd-logind.service or dbus.service, it displays a status message about running fsck and then takes me to a login prompt automatically. Then I can type in my username and password and then there's nothing after that. No prompt, just an apparent hang.
Thanks for any suggestions -- I'll take them and then collect more detailed results and report back.
Thanks!
Last edited by jwhendy (2012-11-08 16:07:33)

As I wondered, I think it's a problem with passwd. I don't have a dbus entry and must have missed it when I was copying things around between my version and the .pacnew. Downloading an install disc now since I can't seem to change it from the recovery console due to mounting root read-only.
I'd love to know of a way to boot that avoids starting dbus and other things that might break while still having read/write access to root. Will mark solved once I update /etc/passwd and reboot.

Similar Messages

3 unable to open '/etc/udev/rules.d/':m error during booting

After a recent upgrade to the kernel26-2.6.28.5-1-i686, I got the above error during booting in one of the laptop.
My search did not give any positive solution for this till now. I read that now udev gets its rules from /lib/udev/rules.d.
But still rules files in /etc/udev/rules.d and /lib/udev/rules.d are different. I know that any symllink work around will not work in this case, I tried but as expected the error message appears again.
So, I roll back to kernel26-2.6.28.4-1-i686 and everything back to normal.
Any Idea to resolve this? (package is not broken as I use the same mirror for another PC and in that I am not getting any error)
Last edited by kgas (2009-02-19 16:10:23)

This issue got resolved on its own with the latest kernel (kernel26-2.6.28.6-1-i686) update. I will leave this topic for some more time to see others response...

G580 Upgrade to Windows 10 failed in the SAFE_OS phase with an error during BOOT operation

0xC1900101-0x20017 I could not successfully upgrade from windows update, nor from the straight download site. The installation failed in the SAFE_OS phase with an error during BOOT operation. I see w10 bios updates for other models. Has anyone been successful in upgrading to W10 from W8?

2015-07-31 21:36:19, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:36:19, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:36:21, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >:uspend(1066): Result = 0xC18001042015-07-31 21:36:21, Error MOUPG CSetupManager::ExecuteInstallMode(656): Result = 0x800705BB
2015-07-31 21:36:21, Error MOUPG CSetupManager::ExecuteDownlevelMode(376): Result = 0x800705BB
2015-07-31 21:36:21, Error MOUPG CSetupManager::Execute(222): Result = 0x800705BB
2015-07-31 21:36:21, Error MOUPG CSetupHost::Execute(370): Result = 0x800705BB
2015-07-31 21:36:21, Error MOUPG CDlpManager::AsyncSerializeDisable(471): Result = 0x80070216
2015-07-31 21:36:36, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010101)
2015-07-31 21:36:40, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010101)
2015-07-31 21:37:02, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:37:03, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:37:04, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
2015-07-31 21:37:04, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
2015-07-31 21:37:11, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:39:15, Error CDiagnosticsHelper:etSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2015-07-31 21:39:18, Error CDiagnosticsHelper:etDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]

Error on boot: "Can not find script file "C:\ProgramData\Lenovo-20841.vbs".

Recently I'm getting an error dialog box on my T530 when I boot it into my OEM installation of Windows 8. The window title bar is "Windows Script Host", and the error message is:
Error on boot: "Can not find script file "C:\ProgramData\Lenovo-20841.vbs".
I pulled up an old backup, and I do have that file, along with a number of other ones that are missing from that directory. I'm attaching a screenshot of the files that are missing. Not sure why they would have been deleted (I know I didn't do it manually). Should I just restore the file? What about the other ones?
Thanks very much.

I am getting a different VBS script error than the one listed above.
Does anyone know how I can get this file? or recreate it?
I get a similar message saying that it can't find the file c:\programdata\Lenovo-11472.vbs
Also, my wireless just randomly resets - sometimes very few minutes - after I've been using the system for a while. It's brand new and I can't figure out what's going on. Could this be the issue?
When I restart, it stays stable for a while and then starts acting up again.
Thanks for your help!

[SOLVED] Error during boot, need help to identify

I've noticed recently that I'm getting an error during (taken from dmesg)
[ 7.982440] [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart module.
[ 7.982865] DRM: Fill_in_dev failed.
can anyone tell me where this is coming from and how to fix it maybe? I have a Intel i7-2600K (Ivy Bridge generation) with a Nvidia GTX 580 card using the propriatary driver.
Last edited by fettouhi (2014-11-20 21:28:04)

BTW, if your processor really is an i7-2600k, that would make it a Sandy Bridge (2nd gen) processor, not an Ivy Bridge (3rd gen and starts with a '3'). Unless this is just a typo, knowing this might help you debug things in the future, as there are unfortunately bugs that affect some 2nd but not 3rd gen procssors, and vice-versa.

VIA Raid 0: Red screen of Death - fatal error during boot sequence

I have been using two Maxtor 120GB SATA drives in a RAID 0 array on my Athlon 64 MSI MB. I have occasionally had messages saying "Hard disk error. Can't find drive 0". I've assumed that this has been a driver issue because if I power down, wait a while I can reboot and continue without issue (other than chkdsk running during boot up). However after the last such error, when I next tried to reboot I got an error message as the RAID was initialising. The error message was in a red box on a black screen and stated that there was a fatal error and that the raid relationship and all HHD would be destroyed if I continued. Naturally I switched off at this point, but on rebooting got exactly the same message. Eventually, as I have backups, I continued past this point and sure enough the RAID had gone. So I rebuilt the raid array and everything seems to be OK.
However, I'd forgotten that my MSI DVD burner was incapacitated due to a failed firmware update so had temporaril;y replace it with a DVD rom drive to get access to my backups. BUT the drive won't read all my backup discs, in particular it won't read the Drive C backups .
Has anyone else had this RAID erro. Is it a driver error or is it a dsik failing (even though they were new at Christmas).
I am using a Superflower power supply which has 22A on the 12V rail
1GB PC3200 ram by A-Data (CAS 2.5)
Elderly HP 9100 CDRW
MSI DR-8 DVD RW
Ethernet card
Radeon 9600 128MB
AMD64 3000 processor
Freeflow

Raids do not really help benchmarks unless you considure hard drive benchmarks. Most games and benchmark proggies load everything they need prior to running. So unless you have a low memory condition that forces the game or benchmark to use the swap file the only place that you would typically see any gain in speed is during the loading of the game or benchmark. That is hard to quantify other than through experience.
Where a raid shines is in file tranfer situations. When you create and save large files such as movies, Reading or copying large files, defragging, or any other massive file effort. Overall the gains can be very small compaired to the rest of what you do with your system. However that is not to belittle what a Raid does. It does give a finer sheen to the overall computers operations and will make sluggish file transfers seem much more bearable overall.

Microsoft Setup Bootstrapper Error during SharePoint 2013 install using Hyper-V on Windows 8.1

Client Machine
Windows Server 2008 R2 SP1
SQL Server 2012 (11.0.2100.60)
Hosted on Windows 8.1 Hyper-V
Doing a SharePoint Install and during the install (very near completion) I get:
Error log shows the ugly:
2014/01/07 13:36:12:444::[3648] MSI(INFO): 'Action start 13:36:12: ArpWrite.'
2014/01/07 13:36:12:444::[3648] MSI(INFO): 'CustomAction
ArpWrite returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)'
2014/01/07 13:36:12:444::[3648] MSI(INFO): 'Action ended 13:36:12: ArpWrite. Return value 3.'
2014/01/07 13:36:12:444::[3648] MSI(INFO): 'Action ended 13:36:12: INSTALL. Return value 3.'
...SharePoint\global\oserver.MSI ErrorCode: 1603(0x643).
A couple of posts seemed related:
http://www.bluedoglimited.com/SharePointThoughts/Lists/Posts/Post.aspx?ID=346
http://blogs.msdn.com/b/odabasi/archive/2012/12/28/failed-to-install-the-product-drive-name-global-oserver-msi-error-code-1603-0x643-error-when-istalling-sharepoint-2013.aspx
http://www.helpfuladm.in/sp2013-preview-install-error-microsoft-sharepoint-server-2013-preview-encountered-an-error-during-setup/
I have had a few virtual machines that built fine... one I’ve been using to test with works about 33% of the time and fails with the same error other times.
I have tweaked the RAM and the # of Virtual Procs and nothing seems to consistently fix it. Specifically I've disabled dynamic memory, set the RAM to 8GB and the number of procs to
4. I've also downloaded the SharePoint ISO from multiple sources (MSDN/TechNet/Trial) thinking the installer was possibly corrupt - same issue.
At this point I'm thinking it is either an issue with Hyper-V on Windows 8.1 + SharePoint or else something specific to my hardware but it is terribly hard to troubleshoot an error that
is intermittent. Any thoughts or suggestions would be appreciated!

@Trevor, I'm new to MSI debugging... now that I have a verbose log, what should I be doing with it? :)
The area of the error appears to be:
Action ended 13:13:06: Set_ArpWrite. Return value 1.
MSI (s) (2C:E0) [13:13:06:201]: Creating MSIHANDLE (15358) of type 790542 for thread 4064
MSI (s) (2C:BC) [13:13:06:201]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIE1F4.tmp, Entrypoint: OcaArpWrite
MSI (s) (2C!44) [13:13:06:216]: Creating MSIHANDLE (15359) of type 790541 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Creating MSIHANDLE (15360) of type 790540 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Creating MSIHANDLE (15361) of type 790531 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Creating MSIHANDLE (15362) of type 790531 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Closing MSIHANDLE (15362) of type 790531 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Note: 1: 2259 2: 3: 4:
MSI (s) (2C!44) [13:13:06:216]: Creating MSIHANDLE (15363) of type 790531 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Closing MSIHANDLE (15363) of type 790531 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Closing MSIHANDLE (15361) of type 790531 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Closing MSIHANDLE (15360) of type 790540 for thread 3908
MSI (s) (2C!44) [13:13:06:216]: Note: 1: 2205 2: 3: Error
MSI (s) (2C!44) [13:13:06:216]: Note: 1: 2228 2: 3: Error 4: SELECT `Error`,`Message` FROM `Error`
MSI (s) (2C!44) [13:13:06:216]: Closing MSIHANDLE (15359) of type 790541 for thread 3908
Action start 13:13:06: ArpWrite.
MSI (s) (2C:BC) [13:13:06:216]: Closing MSIHANDLE (15358) of type 790542 for thread 4064
CustomAction ArpWrite returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 13:13:06: ArpWrite. Return value 3.
Action ended 13:13:06: INSTALL. Return value 3.
Any thoughts on what else I should look for in the MSI Log?

Memory Allocation Error during Boot

Hi,
I am posting this on a different computer than the one on which I istalled Java because I can no longer get it to boot.
Here's the history:
I am working in Windows 98
I added a line to the autoexec.bat so that the PATH lines looked like this:
SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
PATH=%PATH%;"C:Program Files\Mts";"C:j2sdk1.4.0_02\bin
I then rebooted and tried the javac and java commands in different folders and everything worked fine. I shut down the computer and tried to reboot a day later. The following are pieces of the message I received (I don't usually go near the autoexec.bat or system settings so I have no idea how to get past these errors, nor fix them):
SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
PATH=C:WINDOWS;C:WINDOWS\COMMAND;C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1;"C:Program Files\Mts";"C:j2sdk1.4.0_02\bin
General Protection Fault in C:WINDOWS\SCANDISK.ALT at 0090:1921
Memory Allocation Error
Cannot load COMMAND, system halted
Please help!
Thanks,
Julie

SET PATH=C:PROGRA~1\UTILIT~1\SYMATEC\PCANYW~1
PATH=C:WINDOWS;C:WINDOWS\COMMAND;C:PROGRA~1\UTILIT~1\SY
ATEC\PCANYW~1;"C:Program
Files\Mts";"C:j2sdk1.4.0_02\bin
General Protection Fault in C:WINDOWS\SCANDISK.ALT at
0090:1921This shouldn't have been caused by the Java installation. As I understand the situation, at load time scandisk has been called. This is usually due to the computer not having been shut down properly, or a sign of real problems. However, scandisk is unable to run.
You should try a forum/newsgroup for Windows for more help. My own suggestion would be to load to the command prompt (or try safe mode). (Press F8 during boot to get a menu.) And then run scandisk manually. If it works, try renaming the C:\WINDOWS\SCANDISK.ALT file and rebooting.
Regards,
Bhaveet

Errors during boot OEL 5.5 starting a 11.2 instance

Hello,
I've installed Oracle 11GR2 on OEL 5.5 and a I created a db instance. How I can see why my db instance is not up? More precisely , how I can get errors messages thrown by procedure that start oracle instance during boot process (I am sure that kind of messages is thrown but I can't see them).
Many thanks,
Aurel

Hi;
I've installed Oracle 11GR2 on OEL 5.5 and a I created a db instance. How I can see why my db instance is not up? More precisely , how I can get errors messages thrown by procedure that start oracle instance during boot process (I am sure that kind of messages is thrown but I can't see them).For can see your db up or not u can run :
ps -ef|grep lg
oracle 6750316 1 0 Feb 28 - 0:03 asm_lgwr_+ASM
oracle 9437238 14418146 0 16:06:56 pts/3 0:00 grep lg
oracle 14745644 1 0 15:50:41 - 0:00 ora_lgwr_orcl
So my asm instance and db instance is up
For alert or error message you need to create one sh which is cheking alert.log,if you hit ORA error than it can send u email
Regard
Helios

Error during boot

When doing tmboot, I have obtained the following error:
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22319 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22320 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22321 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
That it means? So that one takes place? The documentation on the error indicates
that any action is not necessary. And that the servants can have published or
no. I have verified with tmadmin that the servants estan DEAD. He can be a problem
of allocation of resources, can be that ipc does not have sufficient resources
associate? Somebody podria to give an idea me on like acting? Thank you very much

This error message is normaly printed if the server is directly going down again
during boot. Don't know what your servers are, but you will see this error message
e.g. if the server is not able to allocate its resources like database access,
open config/logfiles, etc.. As the server is not booting you have a problem you
should investigate. Taking a look to your ULOG and stdout/stderr files may give
more details.
"lucia vilar" <[email protected]> wrote:
>
>
When doing tmboot, I have obtained the following error:
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22319 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22320 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
CMDTUX_CAT:819: INFO: Process id=22321 Assume started (pipe).
exec siscafrn -A -- -d -l 09 :
That it means? So that one takes place? The documentation on the error
indicates
that any action is not necessary. And that the servants can have published
or
no. I have verified with tmadmin that the servants estan DEAD. He can
be a problem
of allocation of resources, can be that ipc does not have sufficient
resources
associate? Somebody podria to give an idea me on like acting? Thank you
very much

[solved] Hard disk security parameters freeze during boot

Hi fellow archers!
Currently I am trying to pin point a problem I have. I have an old PC of mine setup as some kind of experimental playground. My problem is that the security options of my driver become frozen during powering up this PC. It is a fresh and empty Arch installation with just sshd running and no services has been installed that should set the drive security-freeze. I am trying to figure out who is locking it, my current suspicion is the mainboard/BIOS itself, but I need to be sure, that there is no script during executing Arch boot setting the freeze parameter. -- Oh if someone one if the ASUS A8N32-SLI is doing such nasty stuff, it would be great to know.
Thanks in advance for your feedback
Last edited by jpk (2011-10-15 13:19:20)

Hi, it's not really a fix for the problem, but I now know what happens. It is really the mainboard BIOS who freezes the security state of my hdds. So what I did was to build a power switch for my hdd. During boot I switch the power and linux will detect the sata drive (haven't tested it with IDE drives) and I can work with it.

[SOLVED] Two Archlinux logos show up during boot

Hi! I recently installed Archlinux on my HP Mini 110 netbook via a usb core image. I can see an Archlinux logo at the top of the screen during boot using the usb stick, but this is not the case in my installation. When booting up my netbook, I can see two Archlinux logos side by side. As far as I can remember, this does not happen at the first time I boot my machine with a fresh install. At that time, I was using vga=773 kernel boot option at my menu.lst, but my laptop monitor does not support this and grub asks me for a new parameter instead. I'm sorry but I really don't remember clearly how it happened, as it did not bother me at first, but it's getting quite annoying that you see something wrong everytime I boot up.
The right way:
A
boot messages
scrolling on
the
screen
What shows up in my case:
AA
boot messages
scrolling on
the
screen
I have already corrected the vga option to suit my laptop monitor's specification (1024x576 is vga=866) but the problem still persists. I have also tried other vga options, both supported and unsupported by my laptop monitor, to no avail. Does this have something to do with intramfs, or do I have to recreate the logo? As far as I can remember, I mkinicpio a couple of times: once during installation, and once during post-installation configuration.
Last edited by avendael (2010-04-13 03:26:34)

dcc24 wrote:
skottish wrote:Intel's hyperthreaded CPUs sometimes report 'cores' that are not physical. It varies from model to model.
That would explain the difference between 2 and 4, but 3?
Do your physical cores seem like they are working properly? I really don't understand much about how it works, but this is the first that I've heard of an odd number of cores on a multi-core system being reported.

I keep getting the error that I can't login into the itunes store...

I've been trying to purchase a movie through my appletv, but whenever I put in my itunes username and password it is giving me the error that they can't access the itunes store right now and to check back later...help!

This is an Apple issue, tested mine from FiOS and Comast, same errors, iPad, phone, AppleTV

[SOLVED] Imapd does not start (only during boot process)

I'm running a courier-imap server.
A few days ago I noticed I did not receive any mails anymore. Then I found my imapd daemon was not running anymore.
I then stopped the daemon process together with the xinetd daemon (which lets me connect to my imap server via my local network).
I restart from a terminal both daemons (imapd an xinetd) and ... everything is up and running ! Note that I have to stop xinetd too because only stopping imapd and restarting doesn't help.
I reboot my PC ... again no imapd anymore. During the boot process I do not get any error message though ...
I'm completely puzzled
The problem started when I upgraded to the linux 3.0.1 kernel ...
Last edited by Strider (2011-08-14 07:59:41)

I managed to get the problem solved by removing and re-installing the courier-imap package. Don't know why that solved it though ...
Last edited by Strider (2011-08-14 07:59:05)

[solved] udev = systemd-tools: system no longer boots completely

Hi guys. Today I updated my system, and now it won't boot past the boot messages. It appears that my ttys aren't being "made" (?). The actual errors appear to be
[ TIME ] Timed out waiting for device dev-tty2.device
[ TIME ] Timed out waiting for device dev-tty3.device
Booting into rescue.target doesn't complete either.
Downgrading systemd-184-2 => systemd-44-7, and replacing systemd-tools with udev allows me to boot successfully again.
Additional info:
cpu: Intel Core i5-3570K
kernel: linux-3.3.7-1-x86_64
graphics card: GeForce GTX 560 Ti
graphics driver: xf86-video-nouveau 0.0.16_git20120512-1 (relevant, maybe? 0.0.16_git20120512-2 makes X give up with a "No screens found" error
system init: systemd (via systemd-sysvcompat)
Advice please.
EDIT: boot screen images
EDIT EDIT: I can connect via SSH to the affected machine. Here's the journal: http://codepad.org/76aB2DnD
EDIT EDIT EDIT: That apparently got snipped. Here's part 2, starting from line 806: http://codepad.org/5UGdsuwE
Last edited by WorMzy (2012-06-02 00:15:21)

Huh. I guess the problem was a couple of stale and crusty {,f}getty .service files, and an obsolete slim.service file I created a while back.
Removing them fixed my problem, although tty1 still shows boot messages (not a problem, and may not even be "new" behaviour)
Cheers Tomegun.

[SOLVED] Borked systemd setup -- dbus errors during boot; can't login

Similar Messages

Maybe you are looking for