Update rc d error no runlevel symlinks to modify aborting

I’m running Raspbian Wheezy, on a freshly installed SD card:

pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l GNU/Linux

I wanted to make my Raspberry Pi a Wifi access point, so I followed the instructions in this tutorial.

All was good until I got to the «Finishing up…» section. It says to avoid having to start hostapd and dhcp each time I boot the pi, I should run these commands:

sudo update-rc.d hostapd enable 
sudo update-rc.d isc-dhcp-server enable

When I run them, I get this:

pi@raspberrypi ~ $ sudo update-rc.d hostapd enable
update-rc.d: using dependency based boot sequencing
update-rc.d: error: no runlevel symlinks to modify, aborting!
pi@raspberrypi ~ $ sudo update-rc.d isc-dhcp-server enable
update-rc.d: using dependency based boot sequencing
pi@raspberrypi ~ $

So, the second command (for isc-dhcp-server) was successful, but the first command (for hostapd) was not. I have no idea what it’s talking about, and don’t know what to do next.

I had followed the instructions on the above-mentioned site exactly, including his instructions for building hostapd from source:

wget https://github.com/jenssegers/RTL8188-hostapd/archive/v1.1.tar.gz
tar -zxvf v1.1.tar.gz
cd RTL8188-hostapd-1.1/hostapd
sudo make
sudo make install

(So, I’m wondering if that’s why isc-dhcp-server succeeded, and hostapd failed; because I installed isc-dhcp-server from apt and hostapd from source.)

I searched for the error message no runlevel symlinks to modify, aborting! and found this page. It seemed fairly specific to bluetooth, though, and I wasn’t sure how to apply it to my situation with hostapd. The main thing I gleaned from that page was the tone of «If you removed the symlinks in rc?.d manually, you will have to recreate them manually,» and «What went wrong is that you were doing things in there without a sufficient understanding of what should be done.»

Well, I most definitely didn’t remove any symlinks manually. And although the esoteric details of runlevels is definitely above my head, I haven’t messed with anything except exactly what the tutorial told me to do.

Any thoughts on how I can fix this problem?

CrunchBang Linux

SEARCH

You are not logged in.

#1 2011-10-07 10:39:37

[SOLVED] update-rc.d not working

I wanted bluetooth to be enabled from startup, but I somehow can’t add it by using rcconf or update-rc.d. Both used as root.
When enabling it in rcconf and quitting, it is unmarked as soon as I check rcconf again.
update-rc.g gives following failure:

After boot bluetooth-applet is started by autostart.sh, but I can’t access or enable my device.
Starting the service manually by /etc/init.d/bluetooth start works fine and I can use it through bluetooth-applet.

Can I add runevel symlinks in rc2.d .. rc5.d manually? I don’t want to mess up with the numbering.

I’m on statler and a thinkpad r61, by the way.

Last edited by Criminal (2011-10-08 14:24:45)

#2 2011-10-07 12:00:08

Re: [SOLVED] update-rc.d not working

Post the result of

please
If you removed the symlinks in rc?.d manually, you will have to recreate them manually. Debian considers this to be the sysadmins responsability.

Edit: If you have deleted the links manually, I guess the easiest way to restore them is to uninstall bluez and then reinstall

Last edited by xaos52 (2011-10-07 12:10:00)

#3 2011-10-07 12:03:49

Re: [SOLVED] update-rc.d not working

I wanted bluetooth to be enabled from startup, but I somehow can’t add it by using rcconf or update-rc.d. Both used as root.
.
update-rc.g gives following failure:

Can I add runevel symlinks in rc2.d .. rc5.d manually? I don’t want to mess up with the numbering.

In my Statler install Bluetooth is already symlinked to those runlevels as S03bluetooth. Here is an excerpt from the header of the file :

### BEGIN INIT INFO
# Provides: bluetooth
# Required-Start: $local_fs $syslog $remote_fs dbus
# Required-Stop: $local_fs $syslog $remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start bluetooth daemons
### END INIT INFO

#4 2011-10-07 14:41:50

Re: [SOLVED] update-rc.d not working

Please give us the output of

after you start up the machine (i.e. without any tinkering).

Check out Musik — an easy-to-use text-to-music converter!
Join SpiderOak using this link and get an extra 1 GB free: https://spideroak.com/download/referral … 660e787ff1

#5 2011-10-07 14:44:31

Re: [SOLVED] update-rc.d not working

Seems like I did already mess things up.

sudo find /etc/rc?.d| grep blue

doesn’t give a result, so I tried reinstalling bluez as you said using purge.
I got following error message (I marked repeating lines with . ):

Same error while trying to install bluez afterwards, since it couldn’t be uninstalled.

@Thorny:
The same header is found in my /etc/init.d/bluetooth script, which should be the target your symlink is pointing to.

Any Ideas what went wronge?

#6 2011-10-07 14:56:04

Re: [SOLVED] update-rc.d not working

Output of /etc/init.d/bluetooth status is:

Did that right after boot.

Edit1:
I noticed that in rc2..5.d I got K01vpnagentd_init and S85vpnagentd_init. That seems to cause the problems in my prior post. Can someone please confirm this is correct? Why killing a service at the beginning and then restarting it in the end?

Edit2:
I just tried creating the symlinks by hand and got the same result. update-rc.d still gives the error message and bluetooth status also returns the quote above.

Hope someone’s got some ideas .

Last edited by Criminal (2011-10-07 15:26:33)

#7 2011-10-07 15:16:43

Re: [SOLVED] update-rc.d not working

We know now that bluetooth is *definitely* not being started (just wanted to make sure of that). Side note: I don’t have the vpn thing (but then again, I don’t use vpn).

Check out Musik — an easy-to-use text-to-music converter!
Join SpiderOak using this link and get an extra 1 GB free: https://spideroak.com/download/referral … 660e787ff1

#8 2011-10-07 15:32:48

Re: [SOLVED] update-rc.d not working

I remeber some time ago (my very beginning noob days, now I consider myself as regular noob ) I didn’t want bluetooth to start. So I disabled it in bios.
But I’m not sure whether I did anything else before disabling it in bios or not.

Is there a way to disable a service in that way, that all symlinks in rc?.d are removed? Some kind of blacklist? Maybe I did that long ago and don’t remember .
Or other way round: Is there a config file listing all services to be used in rc?.d? Maybe I added or removed bluetooth from one of theese files? Just a guess. I really don’t remember what I did or if I did anything at all.

#9 2011-10-07 16:13:34

Re: [SOLVED] update-rc.d not working

@Thorny:
The same header is found in my /etc/init.d/bluetooth script, which should be the target your symlink is pointing to.

Any Ideas what went wronge?

Of course they are the same, it’s the standard Debian script. What I wanted you to observe was that the links should already have been made for the runlevels.

What went wrong is that you were doing things in there without a sufficient understanding of what should be done. However, you’re learning stuff now.

Edit1:
I noticed that in rc2..5.d I got K01vpnagentd_init and S85vpnagentd_init. That seems to cause the problems in my prior post. Can someone please confirm this is correct? Why killing a service at the beginning and then restarting it in the end?

Well, it isn’t on my system either. It’s likely something that you tried.

Edit2:
I just tried creating the symlinks by hand and got the same result. update-rc.d still gives the error message and bluetooth status also returns the quote above.

Hope someone’s got some ideas .

I don’t think you understand the process, «update-rc.d» exists to create the required symlinks in the runlevels detailed in the script in /etc/init.d. If you created them manually there would be nothing for the update to do.

Judging by what you wrote it sounds like you didn’t record all the things you tried to do and don’t remember what they all were. It could be hard to try and figure out remotely what you «might» have done. It might be useful for you to boot up a live session and compare the run levels of a working system with your system.

#10 2011-10-07 16:17:25

Re: [SOLVED] update-rc.d not working

Hi,
Sorry I got you into this mess.
What happened is:
while trying to remove bluez, apt-get triggers insserv to rearrange the order in which services are started automatically. It uses the headers of the init files to determine the order. This process went into a loop, which certainly can be considered a bug, unless header files were changed manually or services were added with incorrect header files. (vpnagent services?)

Killing and restarting a service in a runlevel does make sense. On entering the runlevel the service is first killed, and later restarted because it depends on other services that need to be running for this service to be able to do whatever it has to do.

insserv: warning: script ‘S85vpnagentd_init’ missing LSB tags and overrides
insserv: warning: script ‘vpnagentd_init’ missing LSB tags and overrides

means that the headers of this service do NOT contain the necessary tags so that insserv (or update-rc.d) can determine where this service has to be inserted in the startup sequence.

I can not find a package that contains the string vpnagent (debian testing), so probably this service was added manually.

Try to adapt the headers in vpnagentd-init by adding tags so that insserv does not go into a loop.
Edit:
can you post the script
etc/init.d/vpnagentd_init
I will try to help you insert valid tags in the headers.

hope this helps a bit

Last edited by xaos52 (2011-10-07 16:24:51)

#11 2011-10-07 18:40:09

Re: [SOLVED] update-rc.d not working

While you are in /etc/init.d, have a look at the readme in there, it will explain a few things and give you a skeleton of the format of a script for inclusion in this directory. It might help you to understand what xaos52 is writing about.

I can not find a package that contains the string vpnagent (debian testing), so probably this service was added manually.

[Edit] Just to verify, I do not find it in Debian stable either.

Last edited by Thorny (2011-10-07 18:43:35)

#12 2011-10-08 14:24:22

Re: [SOLVED] update-rc.d not working

Thanks for your support!

Got it now. xaos52 was absolutely right:
I had to install the vpn_client (from Cisco I think) to connect to my university network from home. They recommended / forced this client, so I didn’t want to mess with anything else. Anyway.

After the hint of a missing header in vpnagentd_init I took a look.

It seems they relied on chkconfig which I don’t have installed. Somehow they missed giving a error message during installation, so I didn’t notice. That way the symlinks in rc?.d haven’t been setup correctly.

I read the README, but didn’t know what to insert.
Google helped: After changing the header the way someone else did it here, update-rc.d worked fine for vpnagentd_init and afterwards for bluetooth. Note the last comment in the thread. timblaktu came to the same conclusion.

After reboot bleutooth was running as desired.

@ thorny:
I think that’s the problem every noob has.
On the one hand people are annoyed when there are the same simple questions on and on (like «how do I disable bluetooth forever?»), so one starts googling and trying different solutions. Lacking of experience one also does lot’s of stupid things (like using wronge programs or deleting things manually). I agree that I propably should have made backups a year ago, when I did that, but that’s what I’ve learned up to now.

On the other hand people are often annoyed when noobs do stuff for themselves and run into selfmade problems they caused during trial and error.

So either way one chooses, every time someone is annoyed.

Once again: Thank you both for pointing me into the right direction.

Last edited by Criminal (2011-10-08 14:27:42)

Источник

Error update-rc.d proftpd

I come to you because I do not find the solution to a small problem.

Since the admin (via internet), I wanted to change settings, but once you register, I get this error:

I tried several things, but none work.

Thanking you in advance

Looks like the daemon is disabled. You can enable with cli with the command.

update-rc.d proftpd enable

Then go back to the webUI, enable again the ftp

This command ‘update-rc.d proftpd enable’ return :

Edited 2 times, last by subzero79 ( Oct 28th 2014 ).

Can you try update-rc.d proftpd defaults

In system information, the support info tab. You can press send, that will upload a log file. Post the ID here so I can take a look please.

I don’t button send :

Are you on OMV 1.0? BTW what where your last modifications to the system? any extra software package installed?

if you’re in 1.0, then you don’t have the omv-extras plugin, you have to install it first to upload the log file. Check my signature in the post to install omv-extras.
Once installed

My version a OMV is 0.5.60 (Sardaukar)

This ‘apt-get update‘ command shows me :

And, ‘apt-get install openmediavault-omvextrasorg‘ shows me :

Источник

unixforum.org

Форум для пользователей UNIX-подобных систем

• Темы без ответов
• Активные темы
• Поиск
• Статус форума

Автозапуск Screen

Модератор: Bizdelnick

Автозапуск Screen

Сообщение Bookkc » 03.08.2015 10:57

Очень простой вопрос, но я толком ничего найти не могу. Как закинуть в автозапуск такой скрипт ?

в rc.local кидал, не запускается Прошу Вашей помощи!

amd64) Контактная информация:

Re: Автозапуск Screen

Сообщение devilr » 03.08.2015 11:04

Re: Автозапуск Screen

Сообщение s.xbatob » 03.08.2015 11:53

— не во всех дистрибутивах rc.local исполняется.
— очень сильно подозреваю, что screen-у требуется управляющий терминал и TERM в окружении. А для вашего скрипта ещё и USER с HOME и правильный рабочий каталог. Насчёт tty — не знаю, но в environment ничего этого нет.

И вообще вы затеяли какую-то авантюру с непонятной целью.

Re: Автозапуск Screen

Сообщение Hephaestus » 03.08.2015 11:54

Re: Автозапуск Screen

Сообщение yars » 03.08.2015 12:00

Re: Автозапуск Screen

Сообщение Bookkc » 03.08.2015 18:15

старенький Дебиан стоит 6.0.0

Права стоят 777 на всю директорию.

Re: Автозапуск Screen

Сообщение Rootlexx » 03.08.2015 20:17

Re: Автозапуск Screen

Сообщение Bookkc » 03.08.2015 20:56

Я говорю за каталог, в котором лежит скрипт запуска.

А подробней про init-скрипт

Re: Автозапуск Screen

Сообщение Rootlexx » 03.08.2015 22:19

Re: Автозапуск Screen

Сообщение Bookkc » 04.08.2015 14:09

Re: Автозапуск Screen

Сообщение Bookkc » 04.08.2015 14:25

В итоге все равно не запускается. Вот содержание файла

Re: Автозапуск Screen

Сообщение s.xbatob » 04.08.2015 14:34

Re: Автозапуск Screen

Сообщение Goodvin » 04.08.2015 17:07

В итоге все равно не запускается. Вот содержание файла

Что именно Вы сделали по мануалу?
Содержимое какого именно файла Вы нам показываете?
По ссылке нет ни слова про screen, зато там простым и понятным языком показывают как написать init-скрипт, а Вы вместо него написали снова странный однострочник.

Кроме того, по ссылке в примерах в качестве интерпретататора указан #!/bin/sh
Вам действительно нужен #!/bin/bash?
Это в данном случае вряд ли причина Вашей проблемы, но Вы явно делаете не по мануалу, а что-то своё самобытное.

Источник

I’m running Raspbian Wheezy, on a freshly installed SD card:

pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l GNU/Linux

I wanted to make my Raspberry Pi a Wifi access point, so I followed the instructions in this tutorial.

All was good until I got to the «Finishing up…» section. It says to avoid having to start hostapd and dhcp each time I boot the pi, I should run these commands:

sudo update-rc.d hostapd enable 
sudo update-rc.d isc-dhcp-server enable

When I run them, I get this:

pi@raspberrypi ~ $ sudo update-rc.d hostapd enable
update-rc.d: using dependency based boot sequencing
update-rc.d: error: no runlevel symlinks to modify, aborting!
pi@raspberrypi ~ $ sudo update-rc.d isc-dhcp-server enable
update-rc.d: using dependency based boot sequencing
pi@raspberrypi ~ $

So, the second command (for isc-dhcp-server) was successful, but the first command (for hostapd) was not. I have no idea what it’s talking about, and don’t know what to do next.

I had followed the instructions on the above-mentioned site exactly, including his instructions for building hostapd from source:

wget https://github.com/jenssegers/RTL8188-hostapd/archive/v1.1.tar.gz
tar -zxvf v1.1.tar.gz
cd RTL8188-hostapd-1.1/hostapd
sudo make
sudo make install

(So, I’m wondering if that’s why isc-dhcp-server succeeded, and hostapd failed; because I installed isc-dhcp-server from apt and hostapd from source.)

I searched for the error message no runlevel symlinks to modify, aborting! and found this page. It seemed fairly specific to bluetooth, though, and I wasn’t sure how to apply it to my situation with hostapd. The main thing I gleaned from that page was the tone of «If you removed the symlinks in rc?.d manually, you will have to recreate them manually,» and «What went wrong is that you were doing things in there without a sufficient understanding of what should be done.»

Well, I most definitely didn’t remove any symlinks manually. And although the esoteric details of runlevels is definitely above my head, I haven’t messed with anything except exactly what the tutorial told me to do.

Any thoughts on how I can fix this problem?