1 |
Canek Peláez Valdés <caneko@×××××.com> wrote: |
2 |
|
3 |
> On Fri, May 16, 2014 at 12:17 PM, <covici@××××××××××.com> wrote: |
4 |
> [snip] |
5 |
> >> I don't understand the current situation .So now you get ALL your |
6 |
> >> volumes activated, or not? |
7 |
> > |
8 |
> > Yep, they are all activated and they all get mounted. |
9 |
> |
10 |
> Cool, one problem less. |
11 |
> |
12 |
> >> > Now for some systemd problems. The root file system was read only when |
13 |
> >> > I logged in, but I could remount it rw -- not sure why this was |
14 |
> >> > happening. |
15 |
> >> |
16 |
> >> Set systemd.log_level=debug in your command line, and post the exit |
17 |
> >> from journalctl -b. |
18 |
> > |
19 |
> > I had debug in the command line by itself, would that make the correct |
20 |
> > log_level? The file is quite large, should I send it to you privately? |
21 |
> |
22 |
> I don't think is necessary, I may have found the real problem (see below). |
23 |
> |
24 |
> >> > Some units did start, but most did not. Whenever I tried to |
25 |
> >> > start one manually, I got a message like the following: |
26 |
> [snip] |
27 |
> >> > No matter what unit I tried to start I would get such a message about |
28 |
> >> > the service.mount. |
29 |
> >> |
30 |
> >> That sounds like a problem with the cgroups hierarchy (which uses a |
31 |
> >> virtual filesystem). I don't remember seeing a problem like that |
32 |
> >> before. |
33 |
> >> |
34 |
> >> > Also, even though my network names were correct, they did not come up, |
35 |
> >> > but I will try to look in the logs to see why not. |
36 |
> > I wrote a service file to start my network adaptors, here it is: |
37 |
> > network@.service |
38 |
> > |
39 |
> > |
40 |
> > [Unit] |
41 |
> > Description=Network Connectivity for %i |
42 |
> > Wants=network.target |
43 |
> > Before=network.target |
44 |
> > BindsTo=sys-subsystem-net-devices-%i.device |
45 |
> > After=sys-subsystem-net-devices-%i.device |
46 |
> > [Service] |
47 |
> > Type=oneshot |
48 |
> > RemainAfterExit=yes |
49 |
> > EnvironmentFile=/etc/conf.d/network@%i |
50 |
> > ExecStart=/usr/bin/ip link set dev %i up |
51 |
> > ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i |
52 |
> > ExecStart=/bin/bash -c 'test -n ${gateway} && /usr/bin/ip route add default via |
53 |
> > ${gateway}' |
54 |
> > ExecStart=/bin/bash -c 'test -f /etc/conf.d/postup@%i.sh&&/bin/bash /etc/conf.d/postup@%i.sh |
55 |
> > ExecStop=/usr/bin/ip addr flush dev %i |
56 |
> > ExecStop=/usr/bin/ip link set dev %i down |
57 |
> > [Install] |
58 |
> > WantedBy=network.target |
59 |
> |
60 |
> Did you enabled network@×××××.service? Also, WantedBy=network.target |
61 |
> doesn't do what you probably think it does (check [1]... and BTW, I |
62 |
> forgot my last footnote, is now on [2]). |
63 |
> |
64 |
> I would use WantedBy=multi-user.target. |
65 |
> |
66 |
> >> systemd will not (AFAIK) start your network, and before the 209 or 210 |
67 |
> >> version it needed helper program (NetwokrManager, connman, ip, |
68 |
> >> ifconfig, etc.) to do it. Now it includes networkd, but you need to |
69 |
> >> set up .network files (like .service files) to configure it. See [1]. |
70 |
> >> |
71 |
> >> > So we have made some progress, but still a long way to go yet. Note |
72 |
> >> > also, that I am not booting into a display manager, just a regular |
73 |
> >> > console. |
74 |
> >> > |
75 |
> >> > |
76 |
> >> > What a lot of work just to get the system booted! |
77 |
> >> |
78 |
> >> Well, you have a setup that is not, by any means, simple. Also, in my |
79 |
> >> experience old LVM configurations seem to cause a lot of troubles to |
80 |
> >> bring to what systemd expects. |
81 |
> >> |
82 |
> >> John, could you also post here your kernel config? Those cgroups |
83 |
> >> errors *may* be related to some missing functionality from the kernel. |
84 |
> |
85 |
> [snip kernel config] |
86 |
> |
87 |
> John, your kernel is incorrectly configured to be used by systemd. |
88 |
> When you installed systemd, a warning should have appeared about some |
89 |
> missing configure options; you either didn't saw or ignored those |
90 |
> warnings. Install systemd again so you can see them. |
91 |
> |
92 |
> From what I can tell, you are missing *AT LEAST* the following options: |
93 |
> |
94 |
> CONFIG_AUTOFS4_FS |
95 |
configured as a module. |
96 |
|
97 |
> CONFIG_DMIID |
98 |
|
99 |
set to Y |
100 |
|
101 |
> CONFIG_FANOTIFY |
102 |
set to y |
103 |
|
104 |
> CONFIG_INOTIFY_USER |
105 |
set to y |
106 |
|
107 |
|
108 |
> CONFIG_PROC_FS |
109 |
set to y |
110 |
|
111 |
> CONFIG_SYSFS |
112 |
set to y |
113 |
|
114 |
> |
115 |
> John, if you don't set them, systemd *CANNOT WORK PROPERLY*. They are |
116 |
> mandatory. I'm surprised you are able to boot to a semi-working state. |
117 |
> |
118 |
> Yes, migrating to systemd is a lot of work. But if you don't see (or |
119 |
> ignore) your system messages, that work gets multiplied several times. |
120 |
> |
121 |
> Reconfigure, recompile, and reinstall your kernel (don't forget to |
122 |
> reinstall the modules!), regenerate your initramfs, update lilo (if I |
123 |
> remember correctly, you need to run lilo -something-or-another every |
124 |
> time you change kernel and/or initramfs), and try again. |
125 |
> |
126 |
> Regards |
127 |
> |
128 |
> [1] http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ |
129 |
> [2] http://www.freedesktop.org/software/systemd/man/systemd.network.html |
130 |
> -- |
131 |
> Canek Peláez Valdés |
132 |
> Profesor de asignatura, Facultad de Ciencias |
133 |
> Universidad Nacional Autónoma de México |
134 |
> |
135 |
|
136 |
-- |
137 |
Your life is like a penny. You're going to lose it. The question is: |
138 |
How do |
139 |
you spend it? |
140 |
|
141 |
John Covici |
142 |
covici@××××××××××.com |