When rpcbind is terminated it emits (in src/rpcbind.c::terminate())
syslog(LOG_ERR, ...). As $syslog is shut down before rpcbind, the message
appears on all virtual terminals.

I tried to add $syslog to rpcbind's Required-Stop or Should-Stop, but then I
get

insserv: There is a loop between service rsyslog and rpcbind if stopped
insserv:  loop involving service rpcbind at depth 5
insserv:  loop involving service umountnfs at depth 4
insserv: There is a loop between service rpcbind and umountnfs if stopped
insserv:  loop involving service rsyslog at depth 6
insserv:  loop involving service networking at depth 9
insserv:  loop involving service nfs-common at depth 8

So it appears rpcbind cannot be stopped before $syslog (I'm also confused why
Should-Stop acts like Required-Stop but if it was ignored instead, this bug
would persist so it's not my concern now). I don't want to find out if some
deps can be changed to allow that, but at least the message level can be
lowered as I don't see reasons for it to be LOG_ERR.