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