Skip to contentSkip to conversation

do_rootfs fails while attempting to install hostapd package

DISCUSSION Morné Lamprecht 3 participants 8 messages Jun 1, 2019 – Jun 3, 2019

lore
Share & tools
lore
#0 lore raw

Hi

I created a new custom distribution and everything seems to work fine until the do_rootfs task is executed. It fails specifically when trying to install the hostapd package, with the error below (snippet from log.do_rootfs):

Quoted 9 lines

Running scriptlet: hostapd-2.6-r0.aarch64

usage: update-rc.d [-n] [-f] [-r <root>] <basename> remove update-rc.d [-n] [-r <root>] [-s] <basename> defaults [NN | sNN kNN] update-rc.d [-n] [-r <root>] [-s] <basename> start|stop NN runlvl [runlvl]

error: %prein(hostapd-2.6-r0.aarch64) scriptlet failed, exit status 1

error: hostapd-2.6-r0.aarch64: install failed

The hostapd package itself builds fine, it is just the installation to the rootfs that fails.

The hostapd package is specified in MACHINE_EXTRA_DEPENDS, if I remove it, then the build succeeds without any issues.

If I interpret the error correctly, it is the preinstall scriptlet that fails...but I am not sure where to start debugging this.

Any suggestions ?

- Morné

#1 lore raw

Hi,

Quoted 8 lines · Morné Lamprecht

Hi

I created a new custom distribution and everything seems to work fine until the do_rootfs task is executed. It fails specifically when trying to install the hostapd package, with the error below (snippet from log.do_rootfs):

I would check run.do_rootfs and check it maybe there will be some more info. Do you have some custom extension for hostapd? Thanks.

Quoted 22 lines
Quoted 10 lines

Running scriptlet: hostapd-2.6-r0.aarch64

usage: update-rc.d [-n] [-f] [-r <root>] <basename> remove update-rc.d [-n] [-r <root>] [-s] <basename> defaults [NN | sNN kNN] update-rc.d [-n] [-r <root>] [-s] <basename> start|stop NN runlvl [runlvl]

error: %prein(hostapd-2.6-r0.aarch64) scriptlet failed, exit status 1

error: hostapd-2.6-r0.aarch64: install failed

The hostapd package itself builds fine, it is just the installation to the rootfs that fails.

The hostapd package is specified in MACHINE_EXTRA_DEPENDS, if I remove it, then the build succeeds without any issues.

If I interpret the error correctly, it is the preinstall scriptlet that fails...but I am not sure where to start debugging this.

Quoted 8 lines

Any suggestions ?

- Morné
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

marek

#2 lore raw
Quoted 1 line

I would check run.do_rootfs and check it maybe there will be some more info.

I checked it based on your suggestion, unfortunately found no relevant info.

Quoted 1 line

Do you have some custom extension for hostapd?

No, just the standard package.

- Morné

#3 lore raw
Quoted 10 lines · Morné Lamprecht
Quoted 3 lines

I would check run.do_rootfs and check it maybe
there will be some more info.

I checked it based on your suggestion,
unfortunately found no relevant info.

Quoted 1 line

Do you have some custom extension for hostapd?

No, just the standard package.

Which startup system do you use (sysVinit or systemd)? You can take a look at poky/meta/classed/update-rc.d.bbclass which checks various parameters and try to debug it (by adding some printouts).
By my guess is that some misconfiguration between systemd/sysvinit must cause this issue. Thanks.

Quoted 2 lines

- Morné

BR,

marek

Signature · 10 lines
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
#4 lore raw
Quoted 1 line

Which startup system do you use (sysVinit or systemd)? You can take a look at poky/meta/classed/update-rc.d.bbclass which checks various parameters and try to debug it (by adding some printouts). By my guess is that some misconfiguration between systemd/sysvinit must cause this issue.

I'm using systemd. I think you may be right, I'll have a look at update-rc.d.bbclass and see if I can debug it.

Thanks for the advice !

- Morné

#5 lore raw
In reply to Belisko Marek
Quoted 1 line

Which startup system do you use (sysVinit or systemd)? You can take a look at poky/meta/classed/update-rc.d.bbclass which checks various parameters and try to debug it (by adding some printouts). By my guess is that some misconfiguration between systemd/sysvinit must cause this issue.

Adding DISTRO_FEATURES_remove += " sysvinit" to my distro conf file, solved the problem.

I also have DISTRO_FEATURES_BACKFULL_CONSIDERED = "sysvinit" in my config (also had it during the failed builds), I thought it would prevent sysvinit from being added/backfilled to the DISTRO features ? So I'm not sure why DISTRO_FEATURES_remove is also required in this case ?

- Morné

#6 lore raw
Quoted 7 lines · Morné Lamprecht

I also have DISTRO_FEATURES_BACKFULL_CONSIDERED = "sysvinit" in my config (also had it during the failed builds), I thought it would prevent sysvinit from being added/backfilled to the DISTRO features ? So I'm not sure why DISTRO_FEATURES_remove is also required in this case ?

The variable is DISTRO_FEATURES_BACKFILL_CONSIDERED, in case that wasn't a typo when writing the mail.

Ross

#7 lore raw
Quoted 1 line · Ross

The variable is DISTRO_FEATURES_BACKFILL_CONSIDERED, in case that wasn't a typo when writing the mail.

It wasn't a typo, and that was exactly the problem. Well spotted, everything in the world makes sense again :-)

- Morné