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