Radvd will not start on about 200 VLANs

Hallo,

I am using radvd on about 200 VLANs. But when I load the config, I can not commit it, because radvd does not start. I think there is a restart limit for radvd:

● radvd.service - LSB: Router Advertising Daemon
   Loaded: loaded (/etc/init.d/radvd)
   Active: failed (Result: start-limit) since Mon 2020-01-13 07:39:54 UTC; 2min 2s ago
  Process: 30044 ExecStop=/etc/init.d/radvd stop (code=exited, status=0/SUCCESS)
  Process: 30020 ExecStart=/etc/init.d/radvd start (code=exited, status=0/SUCCESS)

Jan 13 07:40:01 router3 systemd[1]: Failed to start LSB: Router Advertising Daemon.
Jan 13 07:40:01 router3 systemd[1]: Starting LSB: Router Advertising Daemon...
Jan 13 07:40:01 router3 systemd[1]: radvd.service start request repeated too quickly, refusing to start.
Jan 13 07:40:01 router3 systemd[1]: Failed to start LSB: Router Advertising Daemon.
Jan 13 07:40:01 router3 systemd[1]: Starting LSB: Router Advertising Daemon...
Jan 13 07:40:01 router3 systemd[1]: radvd.service start request repeated too quickly, refusing to start.
Jan 13 07:40:01 router3 systemd[1]: Failed to start LSB: Router Advertising Daemon.
Jan 13 07:40:01 router3 systemd[1]: Starting LSB: Router Advertising Daemon...
Jan 13 07:40:01 router3 systemd[1]: radvd.service start request repeated too quickly, refusing to start.
Jan 13 07:40:01 router3 systemd[1]: Failed to start LSB: Router Advertising Daemon.

It will also remove the radvd configuration lines of the last ~ 10 interfaces from the configuration when I save it.

Is this a bug as I suspect?

Thanks

Mebus

Is it possible to overwrite the restart limit in systemd?

Mebus

I cannot overwrite anything /run/systemd/generator.late/radvd.service , because it gets overwritten automatically. Does somebody know how to do this?

# Automatically generated by systemd-sysv-generator

[Unit]
SourcePath=/etc/init.d/radvd
Description=LSB: Router Advertising Daemon
Before=shutdown.target
After=systemd-journald-dev-log.socket remote-fs.target network-online.target
Wants=network-online.target
Conflicts=shutdown.target

[Service]
Type=forking
Restart=no
TimeoutSec=5min
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
ExecStart=/etc/init.d/radvd start
ExecStop=/etc/init.d/radvd stop
ExecReload=/etc/init.d/radvd reload
~                        

Mebus

This was reported and should be fixed in later rolling versions. See https://phabricator.vyos.net/T1891

What version are you running?

Ah, nice. Currently I am running:

"Version: VyOS 1.2.0
Built by: […]
Built on: Sun 12 Jan 2020 10:22 UTC
Build UUID: 13aa9ef5-837f-482b-b1f5-2c1c7a86b94d
Build Commit ID: f17ce666249dab

Architecture: x86_64
Boot via: installed image
System type: bare metal"

Maybe I can backport the fix to this release.

Mebus

Is this:

a Debian package, which I can edit, compile and install on crux?

Mebus

Hello @Mebus, yes, I think it will be solution. Do you need help with building package?

Some advice would be nice. I am using the Docker container to build the iso, but I couldn’t find the sources for the package in there.

Mebus

I think you can clone from git and build from docker container.

  1. Enter to docker container

docker run --rm -it --privileged -v $(pwd):/vyos -w /vyos vyos/vyos-build bash

  1. Get necessary source code

git clone https://github.com/vyos/vyatta-ipv6-rtradv.git

  1. Need choice commit and patch files
cd vyatta-ipv6-rtradv
git checkout crux
# add patch or make changes manually
  1. Build package
dpkg-buildpackage -us -uc -b
  1. Upload this deb file to your router and install it
sudo dpkg -i package_name.deb
1 Like

Hallo,

I was able to build and install my patched Debian package.

I couldn’t use this line:

docker run --rm -it --privileged -v $(pwd):/vyos -w /vyos vyos-builder bash

I had to use

docker run --rm -it --privileged -v $(pwd):/vyos -w /vyos vyos/vyos-build bash

Seems that VyOS now reloads radvd instead of restarting it. Thanks!

Mebus

1 Like

it was typo, fixed it in original post
Thanks for reporting back!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.