From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A56971386EF for ; Sun, 27 Jan 2013 22:14:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 75C0321C0D2; Sun, 27 Jan 2013 22:14:26 +0000 (UTC) Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E3BE321C003 for ; Sun, 27 Jan 2013 22:14:24 +0000 (UTC) Received: by mail-ia0-f172.google.com with SMTP id u8so3376505iag.3 for ; Sun, 27 Jan 2013 14:14:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=VaqcYm55EHS/mO1I4tR/b3US4S18PxlteQhTShAH4PU=; b=aMwA1Jolad3lbVSimM7pBqpgMkewlbVIE8b1XOg8W7FBx41023GKw7pEQOJcG2iAFR WkvCYJW8vfCQ93b2iiyQT4njlW+N+ATKfHN0+qfL1AEDW58c5uPWIkab18o0142fl6mO bBZUINX2yoaJp1Y4sFEJLfhdy9IohCuKZVyWCVVGyhPEceq/9iZkpMIbeWbeHnbNQZhJ R2Lk8ZS/F56y5OwBBoXu6Ikp2ZTI4rmb1wqJXO4ez4isS0zExpgJp8l43YZX/Kvo3lpU YJTjtvuDR5VvTg0fEjWpf1sxngbpUUzCR6aSU50JXSs4UC4q41GuDED0d3DU1zQdkrqL BfiQ== X-Received: by 10.50.163.35 with SMTP id yf3mr3649670igb.60.1359324863991; Sun, 27 Jan 2013 14:14:23 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.42.216.210 with HTTP; Sun, 27 Jan 2013 14:14:03 -0800 (PST) In-Reply-To: References: From: =?ISO-8859-1?Q?Jo=E3o_Matos?= Date: Sun, 27 Jan 2013 19:14:03 -0300 Message-ID: Subject: Re: [gentoo-user] Systemd reaches "target Emergency Mode" every boot To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=e89a8f839029a7116a04d44c7ba8 X-Archives-Salt: 31357839-050f-4d95-9265-208c2c596ed7 X-Archives-Hash: 95e06f609f32a471831f003f2de4edd9 --e89a8f839029a7116a04d44c7ba8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Is there any way it is not in the "default mode"? when it stoped, instead of hitting Ctrl D, I taped my password and "systemctl default", so it could try to start again the default boot process. And it worked. I'll not try the downgrade right now bcz, after a emerge --sync, my portage started do complain about compiling net-misc/networkmanager with support for both systemd and consolekit, but I'm not able to disable consolekit support. So I'll wait them to fix it. 2013/1/27 Jo=E3o Matos > > > > 2013/1/27 Canek Pel=E1ez Vald=E9s > >> On Sun, Jan 27, 2013 at 12:31 PM, Jo=E3o Matos wrote= : >> > >> > >> > >> > 2013/1/26 Canek Pel=E1ez Vald=E9s >> >> >> >> On Sat, Jan 26, 2013 at 7:08 PM, Jo=E3o Matos wro= te: >> >> > Hi list, >> >> > >> >> > I'm having this problem for a while, but I've decided to solve it >> know. >> >> > Every time I boot my system (couple times a day), I have to hid Ctr= l >> + D >> >> > when the boot process is interrupted by the "emergency mode". >> >> > >> >> > I think it started when I was compiling the kernel myself, and >> removing >> >> > lot >> >> > of stuff. Although, I checked and the mandatory options for systemd >> are >> >> > ok. >> >> > >> >> > When I run "journalctl -b -p err" the only information I get is: >> >> > >> >> > Jan 26 20:29:20 KONOHA NetworkManager[1497]: claim_connection: >> assertion >> >> > `nm_connection_get_path (NM_CONNECTION (connection)) =3D=3D NULL' f= ailed >> >> > Jan 26 20:29:24 localhost dhcpcd[1557]: wlan0: sendmsg: Cannot assi= gn >> >> > requested address >> >> > Jan 26 20:30:42 localhost pulseaudio[2073]: [pulseaudio] pid.c: >> Daemon >> >> > already running. >> >> > Jan 26 20:30:42 localhost pulseaudio[2080]: [pulseaudio] pid.c: >> Daemon >> >> > already running. >> >> > >> >> > It give me no clue. >> >> > >> >> > Attached the .conf from my gentoo-3.7.1 >> >> > >> >> > After I hit Ctrl + D, the system works normally. >> >> > >> >> > Any help will be appreciated :) >> >> >> >> Are you using udev-197 with systemd-197? mgorny masked it, and said >> >> this in package.mask: >> > >> > >> > I'm using them. Last time I updated my system there weren't any warnin= g. >> > Anyway, this problem is happening since the previous version. >> > >> >> >> >> # Does not boot. Something with udev is probably broken. Feel free >> >> # to unmask, debug and provide me with a patch. >> >> >> >> You need to be using the same version for udev and systemd (they are >> >> the same package). If you are using the same version for udev and >> >> systemd, are you using an initramfs? When was the last time you built >> >> it, if you do? >> > >> > >> > I don't have initramfs. Just the kernel. But it used to work normaly. >> >> >> >> >> >> Could you boot with "systemd.log_target=3Dkmsg" and >> >> "systemd.log_level=3Ddebug", and post the whole output of "journalctl >> >> -b"? It prints only the logs from the last boot. >> >> >> > >> > journalctl -b attached. >> >> From your logs: >> >> Jan 27 15:16:27 KONOHA systemd[1]: Activating default unit: >> emergency.target >> >> You have emergency.target as default unit. The default.target can be >> set in different ways: >> >> - Check /usr/lib64/systemd/system/default.target >> > > Nothing found here. The file is: > > [Unit] > Description=3DGraphical Interface > Documentation=3Dman:systemd.special(7) > Requires=3Dmulti-user.target > After=3Dmulti-user.target > Conflicts=3Drescue.target > Wants=3Ddisplay-manager.service > AllowIsolate=3Dyes > > [Install] > Alias=3Ddefault.target > > > - Check /etc/systemd/system/default.target >> > > doesn't exist. > > >> - Check if you use --unit=3Demergency.target in your grub config >> - Check if you pass the "emergency" kernel parametr in your grub config >> > > Nothing wrong with grub. > > >> udev-197 in the tree installs everything to /; systemd-197 installs to >> /usr. I'm pretty sure that is not going to end well; I haven't >> upgraded to 197 in neither package. >> >> Check your default.target; for some reason is set to emergency. >> >> Regards. >> -- >> Canek Pel=E1ez Vald=E9s >> Posgrado en Ciencia e Ingenier=EDa de la Computaci=F3n >> Universidad Nacional Aut=F3noma de M=E9xico >> >> > I've also tryed "systemctl disable emergency.service" and "systemctl > disable emergency.target" before but got nothing. > > Anyway, thank you for your help :). I'll try to downgrade. But I still > think it is about kernel config. > > -- > Jo=E3o de Matos > Linux User #461527 > Graduando em Engenharia de Computa=E7=E3o 2005.1 > UEFS - Universidade Estadual de Feira de Santana > --=20 Jo=E3o de Matos Linux User #461527 Graduando em Engenharia de Computa=E7=E3o 2005.1 UEFS - Universidade Estadual de Feira de Santana --e89a8f839029a7116a04d44c7ba8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Is there any way it is not in the "default = mode"?

when it stoped, instead of hitting Ctrl D, I taped= my password and "systemctl default", so it could try to start ag= ain the default boot process. And it worked.

I'll not try the downgrade right now bcz, after a emerge --sy= nc, my portage started do complain about compiling net-misc/networkmanager = with support for both systemd and consolekit, but I'm not able to disab= le consolekit support. So I'll wait them to fix it.


2013/1/= 27 Jo=E3o Matos <jaoneto@gmail.com>



2013/1/27 Canek Pel=E1ez Vald=E9s <caneko@g= mail.com>
On Sun, Jan 27, 2013 at 12:31 PM, Jo=E3o Matos <jaoneto@gmail.com> wrote: >
>
>
> 2013/1/26 Canek Pel=E1ez Vald=E9s <caneko@gmail.com>
>>
>> On Sat, Jan 26, 2013 at 7:08 PM, Jo=E3o Matos <jaoneto@gmail.com> wrote:
>> > Hi list,
>> >
>> > I'm having this problem for a while, but I've decided= to solve it know.
>> > Every time I boot my system (couple times a day), I have to h= id Ctrl + D
>> > when the boot process is interrupted by the "emergency m= ode".
>> >
>> > I think it started when I was compiling the kernel myself, an= d removing
>> > lot
>> > of stuff. Although, I checked and the mandatory options for s= ystemd are
>> > ok.
>> >
>> > When I run "journalctl -b -p err" the only informat= ion I get is:
>> >
>> > Jan 26 20:29:20 KONOHA NetworkManager[1497]: claim_connection= : assertion
>> > `nm_connection_get_path (NM_CONNECTION (connection)) =3D=3D N= ULL' failed
>> > Jan 26 20:29:24 localhost dhcpcd[1557]: wlan0: sendmsg: Canno= t assign
>> > requested address
>> > Jan 26 20:30:42 localhost pulseaudio[2073]: [pulseaudio] pid.= c: Daemon
>> > already running.
>> > Jan 26 20:30:42 localhost pulseaudio[2080]: [pulseaudio] pid.= c: Daemon
>> > already running.
>> >
>> > =A0It give me no clue.
>> >
>> > Attached the .conf from my gentoo-3.7.1
>> >
>> > After I hit Ctrl + D, the system works normally.
>> >
>> > Any help will be appreciated :)
>>
>> Are you using udev-197 with systemd-197? mgorny masked it, and sai= d
>> this in package.mask:
>
>
> I'm using them. Last time I updated my system there weren't an= y warning.
> Anyway, this problem is happening since the previous version.
>
>>
>> # Does not boot. Something with udev is probably broken. Feel free=
>> # to unmask, debug and provide me with a patch.
>>
>> You need to be using the same version for udev and systemd (they a= re
>> the same package). If you are using the same version for udev and<= br> >> systemd, are you using an initramfs? When was the last time you bu= ilt
>> it, if you do?
>
>
> I don't have initramfs. Just the kernel. But it used to work norma= ly.
>>
>>
>> Could you boot with "systemd.log_target=3Dkmsg" and
>> "systemd.log_level=3Ddebug", and post the whole output o= f "journalctl
>> -b"? It prints only the logs from the last boot.
>>
>
> journalctl -b attached.

From your logs:

Jan 27 15:16:27 KONOHA systemd[1]: Activating default unit: emergency.targe= t

You have emergency.target as default unit. The default.target can be
set in different ways:

- Check /usr/lib64/systemd/system/default.target

<= /div>
Nothing found here. The file is:

[Unit]
Description=3DGraphical Interface
Docu= mentation=3Dman:systemd.special(7)
Requires=3Dmulti-user.target
After=3Dmulti-user.target
Conflicts=3Dre= scue.target
Wants=3Ddisplay-manager.service
AllowIsolate=3Dyes
[Install]
Alias=3Ddefault.target


- Check /etc/systemd/system/default.target

<= div>doesn't exist.
=A0
- Check if you use --unit=3Demergency.target in your grub config
- Check if you pass the "emergency" kernel parametr in your grub = config

Nothing wrong with grub.
=A0
udev-197 in the tree installs everything to /; systemd-197 installs to
/usr. I'm pretty sure that is not going to end well; I haven't
upgraded to 197 in neither package.

Check your default.target; for some reason is set to emergency.

Regards.
--
Canek Pel=E1ez Vald=E9s
Posgrado en Ciencia e Ingenier=EDa de la Computaci=F3n
Universidad Nacional Aut=F3noma de M=E9xico


I= 've also tryed "systemctl disable emergency.service" and &quo= t;systemctl disable emergency.target" before but got nothing.

Anyway, thank you for your help :). I'll try= to downgrade. But I still think it is about kernel config.

--
Jo=E3o de M= atos
Linux User #461527
Graduando em Engenharia de Computa=E7=E3o 2005.1
UEFS - Universidade Est= adual de Feira de Santana



--
Jo=E3o de Matos
Linu= x User #461527
Graduando em Engenharia de Computa=E7=E3o 2005.1
UEFS = - Universidade Estadual de Feira de Santana
--e89a8f839029a7116a04d44c7ba8--