1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Broken database problem solved but not all well
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Broken%20database%20problem%20solved%20but%20not%20all%20well&In-Reply-To=%3C4F8D7A72.7020900%40kde.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="014369.html">
<LINK REL="Next" HREF="014371.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Broken database problem solved but not all well</H1>
<B>Anne Wilson</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Broken%20database%20problem%20solved%20but%20not%20all%20well&In-Reply-To=%3C4F8D7A72.7020900%40kde.org%3E"
TITLE="[Mageia-dev] Broken database problem solved but not all well">annew at kde.org
</A><BR>
<I>Tue Apr 17 16:13:06 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="014369.html">[Mageia-dev] Broken database problem solved but not all well
</A></li>
<LI>Next message: <A HREF="014371.html">[Mageia-dev] Broken database problem solved but not all well
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14370">[ date ]</a>
<a href="thread.html#14370">[ thread ]</a>
<a href="subject.html#14370">[ subject ]</a>
<a href="author.html#14370">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17/04/12 10:00, Colin Guthrie wrote:
><i> 'Twas brillig, and Anne Wilson at 17/04/12 07:24 did gyre and
</I>><i> gimble:
</I>>><i> On 16/04/12 16:58, Colin Guthrie wrote:
</I>>>><i> OK, so this is incorrect, (prefdm *is* started, but perhaps
</I>>>><i> some other jobs had to be cancelled instead.
</I>>>><i>
</I>>>><i> Can you do this:
</I>>>><i>
</I>>>><i>
</I>>>><i> 1. Add the following the to kernel command line when booting
</I>>>><i> normally: "systemd.log_level=debug systemd.log_target=kmsg"
</I>>>><i>
</I>>>><i> 2. When you boot and it gets stuck, simply go to tty2 copy
</I>>>><i> /var/log/dmesg to some file and then somehow give it to me :)
</I>>>><i>
</I>>><i> Hope this helps :-)
</I>><i>
</I>><i> OK so there are definitely ordering cycles here:
</I>><i>
</I>><i> [ 18.312187] systemd[1]: Activating default unit: default.target
</I>><i> [ 18.312219] systemd[1]: Trying to enqueue job
</I>><i> graphical.target/start/replace [ 18.312874] systemd[1]: Found
</I>><i> ordering cycle on basic.target/start [ 18.312891] systemd[1]:
</I>><i> Walked on cycle path to sockets.target/start [ 18.312905]
</I>><i> systemd[1]: Walked on cycle path to syslog.socket/start [
</I>><i> 18.312917] systemd[1]: Walked on cycle path to basic.target/start [
</I>><i> 18.312930] systemd[1]: Breaking ordering cycle by deleting job
</I>><i> syslog.socket/start
</I>><i>
</I>><i> And herein lies the problem probably. This might affect a few
</I>><i> other things that require to be after syslog.socket. (dbus itself
</I>><i> is after syslog.target so this could be affected here which would
</I>><i> explain why kdm failed to start properly as it couldn't connect to
</I>><i> dbus)
</I>><i>
</I>><i>
</I>><i> [ 18.313131] systemd[1]: Looking at job
</I>><i> plymouth-quit.service/stop conflicted_by=yes [ 18.313146]
</I>><i> systemd[1]: Looking at job plymouth-quit.service/start
</I>><i> conflicted_by=no [ 18.313160] systemd[1]: Fixing conflicting jobs
</I>><i> by deleting job plymouth-quit.service/start [ 18.313186]
</I>><i> systemd[1]: Looking at job prefdm.service/start conflicted_by=no [
</I>><i> 18.313199] systemd[1]: Looking at job prefdm.service/stop
</I>><i> conflicted_by=no [ 18.313212] systemd[1]: Fixing conflicting jobs
</I>><i> by deleting job prefdm.service/stop [ 18.313237] systemd[1]:
</I>><i> Looking at job <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">getty at tty1.service</A>/stop conflicted_by=yes [
</I>><i> 18.313250] systemd[1]: Looking at job <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">getty at tty1.service</A>/start
</I>><i> conflicted_by=no [ 18.313263] systemd[1]: Fixing conflicting jobs
</I>><i> by deleting job <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">getty at tty1.service</A>/start [ 18.313400] systemd[1]:
</I>><i> Installed new job graphical.target/start as 1
</I>><i>
</I>><i>
</I>><i> These are normal conflicting jobs and this bit is expected
</I>><i> behaviour.
</I>><i>
</I>><i>
</I>><i> All of this should be fixed when we update all the legacy
</I>><i> initscripts.
</I>><i>
</I>><i> In the mean time if you go into /etc/init.d/ and do:
</I>><i>
</I>><i> grep -c "INIT INFO" *| grep -vE
</I>><i> "(halt|killall|mandrake_.*|reboot|single|functions):" | grep :0$
</I>><i>
</I>><i>
</I>><i> This should show you what initscripts you have on your system that
</I>><i> do not have LSB header information.
</I>><i>
</I>><i> If you let me know the results of that command I'll look
</I>><i> specifically at this one so I can push a fix for you sooner rather
</I>><i> than latter (tho' all will get fixed before RC).
</I>><i>
</I>I've been over and over that command, and I'm certain I've typed it
right, but sending it to a text file always produced a 0byte file, so
I tried it without the redirect, and there was a hesitation - working
time - then the prompt returned - no output at all. Any idea what
could be wrong?
Anne
- --
Need KDE help? Try
<A HREF="http://userbase.kde.org">http://userbase.kde.org</A> or
<A HREF="http://forum.kde.org">http://forum.kde.org</A>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - <A HREF="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A>
iEYEARECAAYFAk+NemgACgkQj93fyh4cnBejxQCghKKdqF2kbWVRAVwKazKPIFNY
dAkAn2UtYyqQlfPhD3MCa9GmHNkhFyHH
=yYy/
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="014369.html">[Mageia-dev] Broken database problem solved but not all well
</A></li>
<LI>Next message: <A HREF="014371.html">[Mageia-dev] Broken database problem solved but not all well
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14370">[ date ]</a>
<a href="thread.html#14370">[ thread ]</a>
<a href="subject.html#14370">[ subject ]</a>
<a href="author.html#14370">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
