My system is also affected. Running debian 10.2, with greenbone-security-assistant 7.0.3+dfsg.1-1.
 
I get the following error, with enable or disable actions:
% sudo systemctl disable greenbone-security-assistant
Synchronizing state of greenbone-security-assistant.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable greenbone-security-assistant
update-rc.d: error: greenbone-security-assistant Default-Start contains no runlevels, aborting.
 
If I manually edit /etc/init.d/greenbone-security-assistant, to replace this line:
# Default-Start:    
 
...with this one:
# Default-Start:     2 3 4 5
 
...then I get the following error instead:
% sudo systemctl disable greenbone-security-assistant
Synchronizing state of greenbone-security-assistant.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable greenbone-security-assistant
update-rc.d: error: no runlevel symlinks to modify, aborting!
 
My current work-around is to manually stop the GSA service and its dependencies, after they get restarted each time. A more severe workaround is to use systemctl masking:
% sudo systemctl mask greenbone-security-assistant
 
However, this prevents the service from being started manually. To start manually:
% sudo systemctl unmask greenbone-security-assistant
% sudo systemctl start greenbone-security-assistant
 
Then, of course, it has to be re-masked when done being used, to prevent it from being auto-started again.
 
To improve on this, I'm trying to disable the dependency. Not being an expert at systemd, I'm not sure if this will have the intended effect, or possibly adverse effects:
% sudo rm /etc/systemd/system/multi-user.target.wants/greenbone-security-assistant.service

Reply via email to