`update-rc.d: error: no runlevel symlinks to modify, aborting!` on Ubuntu 16.04 #1193

2E0PGS · 2017-04-25T15:38:19Z

Lintian Output:

E: fahclient: embedded-library usr/bin/FAHClient: expat
E: fahclient: embedded-library usr/bin/FAHClient: openssl
E: fahclient: embedded-library usr/bin/FAHClient: sqlite
W: fahclient: hardening-no-relro usr/bin/FAHClient
W: fahclient: hardening-no-relro usr/bin/FAHCoreWrapper
W: fahclient: package-contains-timestamped-gzip usr/share/doc/fahclient/changelog.Debian.gz
W: fahclient: package-contains-timestamped-gzip usr/share/doc/fahclient/changelog.gz
E: fahclient: duplicate-updaterc.d-calls-in-postinst FAHClient
W: fahclient: binary-without-manpage usr/bin/FAHClient
W: fahclient: binary-without-manpage usr/bin/FAHCoreWrapper
E: fahclient: maintainer-script-should-not-use-adduser-system-without-home preinst:24 'adduser --quiet --system --no-create-home --disabled-password                 $CLIENT_USER 2>/dev/null; then'
W: fahclient: init.d-script-does-not-source-init-functions etc/init.d/FAHClient

Lintian finished with exit status 1

APT-GET Output:

Setting up fahclient (7.4.4) ...
update-rc.d: error: no runlevel symlinks to modify, aborting!
dpkg: error processing package fahclient (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 fahclient
E: Sub-process /usr/bin/dpkg returned an error code (1)

The text was updated successfully, but these errors were encountered:

jcoffland · 2017-04-25T21:10:22Z

I was aware of most of those lintian warnings. duplicate-updaterc.d-calls-in-postinst is concerning and may be related. This might be relevant: http://comments.gmane.org/gmane.linux.debian.devel.mentors/52381

Which version of Ubuntu?

2E0PGS · 2017-04-25T21:11:36Z

Ubuntu 16.04.2
Unity 7.4.0

BurntRouter · 2017-10-26T19:53:20Z

I realize this is an old issue but it is still open and I am now experiencing this problem. Ubuntu 16.04.03 Server x64

jcoffland · 2017-10-27T17:57:50Z

I need more information. What is the situation that causes this error? Is this a new install or an upgrade? What is the install command?

jcoffland · 2017-10-31T19:08:03Z

Does running the following command and then trying to install again work?:

sudo update-rc.d FAHClient defaults

kkoyung · 2017-11-06T05:07:13Z

I got the same problem when I installed fahclient on Ubuntu 16.04.

$ sudo dpkg -i fahclient_7.4.4_amd64.deb
Selecting previously unselected package fahclient.
(Reading database ... 306306 files and directories currently installed.)
Preparing to unpack fahclient_7.4.4_amd64.deb ...
Adding system user fahclient...done
Unpacking fahclient (7.4.4) ...
Setting up fahclient (7.4.4) ...
update-rc.d: error: no runlevel symlinks to modify, aborting!
dpkg: error processing package fahclient (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for systemd (229-4ubuntu21) ...
Processing triggers for ureadahead (0.100.0-19) ...
Errors were encountered while processing:
fahclient

jcoffland · 2017-11-10T18:35:50Z

@koyung Please try running the command I suggested above and report back.

martinvonwittich · 2017-11-30T11:29:34Z

Yes, that command resolved the issue on my computer:

martin@dogmeat ~/Downloads % sudo dpkg --configure -a
fahclient (7.4.4) wird eingerichtet ...
update-rc.d: error: no runlevel symlinks to modify, aborting!
dpkg: Fehler beim Bearbeiten des Paketes fahclient (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 fahclient
martin@dogmeat ~/Downloads % sudo update-rc.d FAHClient defaults
martin@dogmeat ~/Downloads % sudo dpkg --configure -a           
fahclient (7.4.4) wird eingerichtet ...

The Folding@home client is now installed

You can access the Web interface by going to:

  http://folding.stanford.edu/client/

in a browser on this computer.

For information about configuring the Folding@home client for
remote access please see the comments in:

  /etc/fahclient/config.xml

martin@dogmeat ~/Downloads % lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 17.04
Release:        17.04
Codename:       zesty

jcoffland · 2017-11-30T22:08:41Z

Thanks. One more question. When you initially encountered this problem where you doing a fresh install or an upgrade?

martinvonwittich · 2017-12-01T10:20:46Z

Thanks. One more question. When you initially encountered this problem where you doing a fresh install or an upgrade?

A fresh install.

informatorius · 2018-05-27T18:35:09Z

Got this error with FAH 7.5.1 beta on latest Linux Mint 18 with latest updates and the workaround
sudo update-rc.d FAHClient defaults
worked and FAHClient is running

jcoffland · 2018-05-29T17:59:04Z

Ok, I figured out what's going on here. This only happens if you tell FAHClient not to start automatically.

informatorius · 2018-05-29T18:10:14Z

Yes, I did say not to start automatically.

2E0PGS · 2018-05-29T18:12:13Z

I think I also selected that option to not start automatically since it was installed on my main desktop. Nice work to narrow that issue down. ⁣Peter Stevenson (2E0PGS) http://www.m3pgs.co.uk

…

On 29 May 2018, 19:10, at 19:10, informatorius ***@***.***> wrote: Yes, I did say not to start automatically. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #1193 (comment)

kaefert · 2018-11-19T14:07:12Z

Ran into this issue on a fresh Linux Mint 19 desktop. Manually running sudo update-rc.d FAHClient defaults solved the issue, but it would be nice if you could fix the deb package to "just work".

Battleman · 2018-12-26T12:33:08Z

Same as others: fresh install on a Debian 10 Buster, kernel 4.18.10-2.
Got a similar error

>sudo dpkg -i fahclient_7.5.1_amd64.deb 
Selecting previously unselected package fahclient.
(Reading database ... 337291 files and directories currently installed.)
Preparing to unpack fahclient_7.5.1_amd64.deb ...
usermod: no changes
Unpacking fahclient (7.5.1) ...
Setting up fahclient (7.5.1) ...
update-rc.d: error: no runlevel symlinks to modify, aborting!
dpkg: error processing package fahclient (--install):
 installed fahclient package post-installation script subprocess returned error exit status 1
Processing triggers for systemd (239-15) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for gnome-menus (3.13.3-11) ...
Processing triggers for mime-support (3.61) ...
Errors were encountered while processing:
 fahclient

But the aformentionned command sudo update-rc.d FAHClient defaults fixed it. Thanks for that

Edit: Also configured for not starting up automatically

bb30994 · 2019-01-20T20:26:00Z

Also configured for not starting up automatically.

Why? FAHClient is a service which is easily managed by settings using FAHControl. If you've restarted your system with data that can be processed, it should start doing that. If you specifically configure a slot to PAUSE, it will; Also it won't download more work if you set it to FINISH.

Would you configure your system to avoid starting the printer daemon forcing you to start it manually when nothing happens when you issue a PRINT function in some program... or do you expect any incompletely printed file to resume processing after a restart?

Sanaki · 2019-01-20T23:23:08Z

This isn't the place to question why people don't want a service to start automatically. Everyone has different use cases for their systems. Some people don't want it. End of story. If the option is provided for the service not to start automatically, that option should work.

ck-kc · 2019-04-22T14:10:22Z

Got his error. I don't want to touch my rc.d files. What should I do?

martinvonwittich · 2019-04-22T16:04:21Z

Got his error. I don't want to touch my rc.d files. What should I do?

Run these commands, as stated above:

sudo update-rc.d FAHClient defaults
sudo dpkg --configure -a

hasezoey · 2019-08-17T05:18:47Z

ran into the same issue, the command fixed it
system:
Linux Mint 19.2
Kernel Linux 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
fahclient fahclient_7.5.1_amd64.deb

fresh install, trying to not start it automatically

transplier · 2019-11-25T01:14:33Z

Same issue and fix on kubuntu 19.04.

orjanv · 2020-03-15T07:48:34Z

Same issue with Ubuntu 19.10 x86_64 - Solved with $ sudo update-rc.d FAHClient defaults
Cannot install fahcontrol : Depends: python-gnome2 but it is not installable

Doomsdayrs · 2020-03-22T19:59:42Z

Confirming same issues
python-support && python-gnome2 are not found

sturfee-petrl · 2020-03-26T23:58:17Z

Ubuntu 19.10 x86_64
I was almost going to abandon the idea to connect to the FoldingAtHome when I found this solution.
I was installing it via Ubuntu Software and I saw the initial window settings. Then it suddenly crushed. I tried couple of times to reinstall it but always without success. It didn't show the initial window at following tries.
Only when I tried install via dpkg -i I could see source of the problem.

peterjasko · 2020-04-07T09:46:51Z

Had the same issue on Linux Mint 19.3 Tricia, whilst doing a fresh install. The workaround (sudo update-rc.d FAHClient defaults) before installation solves the problem

pcolaianni · 2020-04-08T10:57:33Z

What does the workaround do? Will it run the service at boot, no matter what I select during the installation of fahclient?

rsimac · 2020-04-13T14:28:19Z

Same problem on ubuntu 18.04. I wanted to remain in control as whether to start fahclient at boot, and opted for no. That apparently caused the above bug.
Suggested solution of: sudo update-rc.d FAHClient defaults works, and it fixes ubuntu packaging system.

While still wanting to be in control of what is starting on my system, my best guess, without testing would be to modify the /etc/init.d/FAHClient file, line 27:

ENABLE=true

into

ENABLE=false

From the contents of the script, it is my semi-educated guess, such modified script will NOT launch fahclient at system startup.

ipkh · 2020-04-15T23:35:57Z

You can add the pause-on-start true to the client under Fahcontrol, config, expert.
In my case I don't want it starting auto as I frequently use the finish command before shutting down or switching to another dual boot OS.

MichaIng · 2020-05-19T14:12:01Z

From what I see this issue has been resolved with the current version. update-rc.d FAHClient defaults has been added to the package pre/post install/config scripts and neither a reinstall now a fresh install with debconf-set-selections <<< 'fahclient fahclient/autostart boolean false' causes any failure during my tests.

Tested with https://download.foldingathome.org/releases/public/release/fahclient/debian-stable-64bit/v7.6/latest.deb, probably users of other platforms can verify and in case this issue can be closed.

lalala548 · 2021-05-29T13:32:26Z

update-rc.d: error: unable to read /etc/init.d/FAHClient

MichaIng · 2021-05-29T17:01:37Z

That file should exist, what does the following show?

ls -l /etc/init.d/FAHClient

jcoffland changed the title ~~fahclient ubuntu .deb~~ Lintian warnings on .deb Apr 25, 2017

jcoffland added the 3.Component - FAHClient Reported issue relates to FAHClient. label Apr 25, 2017

jcoffland changed the title ~~Lintian warnings on .deb~~ update-rc.d: error: no runlevel symlinks to modify, aborting! on Ubuntu Apr 25, 2017

jcoffland changed the title ~~update-rc.d: error: no runlevel symlinks to modify, aborting! on Ubuntu~~ update-rc.d: error: no runlevel symlinks to modify, aborting! on Ubuntu 16.04 Apr 25, 2017

jcoffland added 1.Type - Defect Reported issue is a defect. Linux 3.Component - Installer Reported issue relates to the installer. and removed 1.Type - Defect Reported issue is a defect. labels Oct 31, 2017

Fourdee mentioned this issue Aug 8, 2018

Folding@Home MichaIng/DietPi#1985

Closed

MichaIng mentioned this issue Aug 9, 2018

[Question] FAHClient automated (and testing) install #1255

Closed

patvdleer mentioned this issue Mar 19, 2020

Failed to install on Ubuntu 18.04+ #1327

Closed

PantherX added 4.OS - Debian Reported issue occurs on Debian based OS (Debian, Mint, Ubuntu). and removed Linux labels May 22, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`update-rc.d: error: no runlevel symlinks to modify, aborting!` on Ubuntu 16.04 #1193

`update-rc.d: error: no runlevel symlinks to modify, aborting!` on Ubuntu 16.04 #1193

2E0PGS commented Apr 25, 2017

jcoffland commented Apr 25, 2017 •

edited

Loading

2E0PGS commented Apr 25, 2017

BurntRouter commented Oct 26, 2017

jcoffland commented Oct 27, 2017

jcoffland commented Oct 31, 2017 •

edited

Loading

kkoyung commented Nov 6, 2017

jcoffland commented Nov 10, 2017

martinvonwittich commented Nov 30, 2017

jcoffland commented Nov 30, 2017

martinvonwittich commented Dec 1, 2017

informatorius commented May 27, 2018 •

edited

Loading

jcoffland commented May 29, 2018

informatorius commented May 29, 2018

2E0PGS commented May 29, 2018 via email

kaefert commented Nov 19, 2018

Battleman commented Dec 26, 2018 •

edited

Loading

bb30994 commented Jan 20, 2019 •

edited

Loading

Sanaki commented Jan 20, 2019

ck-kc commented Apr 22, 2019

martinvonwittich commented Apr 22, 2019

hasezoey commented Aug 17, 2019 •

edited

Loading

transplier commented Nov 25, 2019

orjanv commented Mar 15, 2020

Doomsdayrs commented Mar 22, 2020

sturfee-petrl commented Mar 26, 2020

peterjasko commented Apr 7, 2020

pcolaianni commented Apr 8, 2020

rsimac commented Apr 13, 2020

ipkh commented Apr 15, 2020

MichaIng commented May 19, 2020

lalala548 commented May 29, 2021

MichaIng commented May 29, 2021

update-rc.d: error: no runlevel symlinks to modify, aborting! on Ubuntu 16.04 #1193

update-rc.d: error: no runlevel symlinks to modify, aborting! on Ubuntu 16.04 #1193

Comments

2E0PGS commented Apr 25, 2017

jcoffland commented Apr 25, 2017 • edited Loading

2E0PGS commented Apr 25, 2017

BurntRouter commented Oct 26, 2017

jcoffland commented Oct 27, 2017

jcoffland commented Oct 31, 2017 • edited Loading

kkoyung commented Nov 6, 2017

jcoffland commented Nov 10, 2017

martinvonwittich commented Nov 30, 2017

jcoffland commented Nov 30, 2017

martinvonwittich commented Dec 1, 2017

informatorius commented May 27, 2018 • edited Loading

jcoffland commented May 29, 2018

informatorius commented May 29, 2018

2E0PGS commented May 29, 2018 via email

kaefert commented Nov 19, 2018

Battleman commented Dec 26, 2018 • edited Loading

bb30994 commented Jan 20, 2019 • edited Loading

Sanaki commented Jan 20, 2019

ck-kc commented Apr 22, 2019

martinvonwittich commented Apr 22, 2019

hasezoey commented Aug 17, 2019 • edited Loading

transplier commented Nov 25, 2019

orjanv commented Mar 15, 2020

Doomsdayrs commented Mar 22, 2020

sturfee-petrl commented Mar 26, 2020

peterjasko commented Apr 7, 2020

pcolaianni commented Apr 8, 2020

rsimac commented Apr 13, 2020

ipkh commented Apr 15, 2020

MichaIng commented May 19, 2020

lalala548 commented May 29, 2021

MichaIng commented May 29, 2021

`update-rc.d: error: no runlevel symlinks to modify, aborting!` on Ubuntu 16.04 #1193

`update-rc.d: error: no runlevel symlinks to modify, aborting!` on Ubuntu 16.04 #1193

jcoffland commented Apr 25, 2017 •

edited

Loading

jcoffland commented Oct 31, 2017 •

edited

Loading

informatorius commented May 27, 2018 •

edited

Loading

Battleman commented Dec 26, 2018 •

edited

Loading

bb30994 commented Jan 20, 2019 •

edited

Loading

hasezoey commented Aug 17, 2019 •

edited

Loading