The systemd service is not working anymore on Debian 8

[Rikkit888]

The systemd starter tb@.service is not working anymore.
Tested on Debian 8

Error:
systemd[1]: Failed to load environment files: No such file or directory
systemd[1]: tb@xxxx.service failed to run 'start' task: No such file or directory
systemd[1]: Failed to start User Space Tunnel Broker.
systemd[1]: Unit tb@xxxx.service entered failed state.
systemd[1]: tb@xxxx.service holdoff time over, scheduling restart.
systemd[1]: Stopping User Space Tunnel Broker...

For sure i have a config file set up here:
/etc/tb-userspace/tbxxxx.conf
so this file is on my system.

[Blaok]

If the unit name is tb@xxxx.service, the config file should be /etc/tb-userspace/xxxx.conf. Based your error message, I think you have some inconsistency between the unit name and the config file name.

[Rikkit888]

Sadly the solution was not that easy.
I changed the name of the tbxxxx.conf to xxxx.conf, but same error, when i execute this:
systemctl start tb@xxxx
Perhaps something changed in debian.
I see the service file is using variables.
EnvironmentFile=/etc/tb-userspace/%I.conf
I also tried to change %I.conf to my exact config.
EnvironmentFile=/etc/tb-userspace/xxxx.conf
but still not working.

I am really unsure what could cause the problem.
I am unsure if the error message really belongs to this line:
EnvironmentFile=/etc/tb-userspace/%I.conf

[Blaok]

systemd[1]: Failed to load environment files: No such file or directory

This message indicates that the error is caused by systemd not being able to find the EnvironmentFile. Can you try sudo systemctl daemon-reload && sudo systemctl restart tb@xxxx?

[Rikkit888]

No change with this.
Yes seems so and this error output doesn`t deliver much information.
These steps were already suggested from systemd to me.
The logoutput is from journalctl. Systemd delivers nearly no information about the problem.

I think i try to put the commands from the systemd service file to an extra script and just call the extra script from the systemd service to keep it as simple as possible.
Any of the commands in the service file must cause a problem in the systemd environment.

[Blaok]

OK. That is very unusual because I just pulled a Debian 8 image and it seems to working fine.

[Rikkit888]

You used OpenVZ virtualisation?

My system is debian 8 in OpenVZ environment.
Tun kernel module is available.
There is already running a tunnel tun0 on this machine.

I think i have to examine the script to find out which command is causing trouble.
Is the script made for tun0 static or does it choose a free tun device?
I need it to work on tun1

[Blaok]

I don't have any OpenVZ instance now and used LXC yesterday.

The interface name is specified in the config file. If you want to use tun1, you can modify the first line of the config file:

INT=tun1

My suggestion is to inspect the log and identify the problem first. If the config file is recognized properly, sudo systemctl status tb@xxxx should show you the exit code for each of the command in addition to any error message.

[Rikkit888]

I stripped it down and put the commands in a simple script and removed the variables and set the real values.
Seems tb-userspace is starting then, but on my openvz instance it is not opening a tunnel.
I think my openvz is too much restricted. I thought it would be enough to have the tun kernel module loaded, but it seems there is more necessary.

Sadly i am not able to get it working in an openvz instance.