> Any symlinks for /home or /root or anything weird? This looks like > systemd and your specific setup being weird.
No, though I have seen weird things in OpenVZ-land before. I recently tried to use a Debian image that was so sketchy it utterly failed to upgrade between Debian versions from a minimal install state. Another time I saw something that might be quite pertinent: after an upgrade to the pre-release Stretch, systemd was pretty much hosed. The machine would still boot, but there was no networking, none of the services would autostart. There were lots of cgroup type of errors in the logs. I managed to talk the tech support into upgrading the kernel on the OpenVZ host to a more recent patch level and after that systemd worked. (Did not try Tor on that machine though.) I see that the kernel here, while appearing to be close to the same vintage, is clearly different from OpenVZ machines I run with other providers, and in fact every provider I am using seems to have a slightly different kernel version. If you are pretty sure it isn't a problem with this package, I would be tempted to point a finger at the OpenVZ kernel. But, sadly, tech support with this provider seems to be somewhat hostile and I am not in a position to engage with them any further. > If you google for 'systemd Failed at step NAMESPACE spawning Too > many levels' you can find a few more examples of where things may go > wrong. > > I don't think this is a bug in the Debian package, but I'd still like > to learn what is causing this on your system, exactly. I see you have a PGP key. If you are interested and would like root on the machine to poke around for a while to satisfy your curiosity, you are welcome. It is still at a fairly early stage of installation, and as a heavy OpenVZ user I too would like to see Tor work properly here as well. Clayton
