5:06 p.m.
Hello,
I created a livecd disk using a kickstart file which I modified from
the LXDE spin and got these error messages (at different points of the
ISO creation):
I wonder if any of these messages are serious. In any case, is there an
easy way to get rid of them?
Many thanks,
Ranjan
....
No '/dev/log' or 'logger' included for syslog logging (3 times)
....
....
Opening default zone 'public'
No changes to default zone needed.
Note: Forwarding request to 'systemctl enable NetworkManager.service'.
Note: Forwarding request to 'systemctl disable sshd.service'.
rm '/etc/systemd/system/multi-user.target.wants/sshd.service'
mkfs.fat 3.0.24 (2013-11-23)
Loop device does not match a floppy size, using default hd params
Initialized /dev/loop1 as a 20 MB HFS Plus volume
ERROR:program:umount: /tmp/lorax.imgutils.OtNm0z: target is busy
umount: /tmp/lorax.imgutils.OtNm0z: target is busy
ERROR:program: (In some cases useful info about processes that
(In some cases useful info about processes that
ERROR:program: use the device is found by lsof(8) or fuser(1).)
use the device is found by lsof(8) or fuser(1).)
WARNING:pylorax.imgutils:failed to unmount /tmp/lorax.imgutils.OtNm0z.
retrying (1/3)... ERROR:program:umount: /tmp/lorax.imgutils.LTGEmM:
target is busy umount: /tmp/lorax.imgutils.LTGEmM: target is busy
ERROR:program: (In some cases useful info about processes that
(In some cases useful info about processes that
ERROR:program: use the device is found by lsof(8) or fuser(1).)
use the device is found by lsof(8) or fuser(1).)
WARNING:pylorax.imgutils:failed to unmount /tmp/lorax.imgutils.LTGEmM.
retrying (1/3)... The unit files have no [Install] section. They are
not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another
unit's .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which
has a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path,
timer, D-Bus, udev, scripted systemctl call, ...).
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora: import read failed(2).
Packages within this LiveCD
....
....
....
Updating index cache for path `/usr/share/man/nl/man1'.
Wait.../usr/bin/mandb: warning: /usr/share/man/nl/man1/dos2unix.1.gz:
whatis parse for dos2unix(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2dos
(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2mac
(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for mac2unix
(1) failed
....
....
cp: cannot stat
'/home/maitra/remix/tmp/imgcreate-mHq7up/install_root/usr/share/doc/*-release-*/GPL':
No such file or directory
____________________________________________________________
FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop!
Check it out at http://www.inbox.com/marineaquarium
9:01 a.m.
On Fri, Jan 17, 2014 at 05:06:01PM -0600, Ranjan Maitra wrote:
Hello,
I created a livecd disk using a kickstart file which I modified from
the LXDE spin and got these error messages (at different points of the
ISO creation):
I wonder if any of these messages are serious. In any case, is there an
easy way to get rid of them?
Most of them are normal, there isn't any easy way to get rid of them
without also masking real errors. The unmount error is the one that may
cause problems. Sometimes it happens, some people seem to see it more
than others (eg. I don't see it myself). My suspicion is that some
desktop related thing is grabbing the mount when it shows up but I
haven't been able to confirm that.
Many thanks,
Ranjan
....
No '/dev/log' or 'logger' included for syslog logging (3 times)
Those come from dracut while making the initrd.
....
....
Opening default zone 'public'
No changes to default zone needed.
Note: Forwarding request to 'systemctl enable NetworkManager.service'.
Note: Forwarding request to 'systemctl disable sshd.service'.
rm '/etc/systemd/system/multi-user.target.wants/sshd.service'
These are firewall and service setup related.
mkfs.fat 3.0.24 (2013-11-23)
Loop device does not match a floppy size, using default hd params
Initialized /dev/loop1 as a 20 MB HFS Plus volume
That is from mkefiboot, it decides on the options to use based on the
filesystem size.
ERROR:program:umount: /tmp/lorax.imgutils.OtNm0z: target is busy
umount: /tmp/lorax.imgutils.OtNm0z: target is busy
ERROR:program: (In some cases useful info about processes that
(In some cases useful info about processes that
ERROR:program: use the device is found by lsof(8) or fuser(1).)
use the device is found by lsof(8) or fuser(1).)
WARNING:pylorax.imgutils:failed to unmount /tmp/lorax.imgutils.OtNm0z.
retrying (1/3)... ERROR:program:umount: /tmp/lorax.imgutils.LTGEmM:
target is busy umount: /tmp/lorax.imgutils.LTGEmM: target is busy
ERROR:program: (In some cases useful info about processes that
(In some cases useful info about processes that
ERROR:program: use the device is found by lsof(8) or fuser(1).)
use the device is found by lsof(8) or fuser(1).)
WARNING:pylorax.imgutils:failed to unmount /tmp/lorax.imgutils.LTGEmM.
retrying (1/3)... The unit files have no [Install] section. They are
not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another
unit's .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which
has a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path,
timer, D-Bus, udev, scripted systemctl call, ...).
This is the only part that bugs me -- something prevented it from
umounting the image, and the retry counter seems to be broken.
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora: import read failed(2).
Packages within this LiveCD
....
....
....
Updating index cache for path `/usr/share/man/nl/man1'.
Wait.../usr/bin/mandb: warning: /usr/share/man/nl/man1/dos2unix.1.gz:
whatis parse for dos2unix(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2dos
(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2mac
(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for mac2unix
(1) failed
....
....
cp: cannot stat
'/home/maitra/remix/tmp/imgcreate-mHq7up/install_root/usr/share/doc/*-release-*/GPL':
No such file or directory
These are all from the %post scripts
--
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)
9:26 a.m.
Thanks very much! Is there a place I can post my .ks files so that
someone can take a look and pin-point the errors? Or can I include as
an attachment here (many mailing lists do not allow for attachments to
be included)?
Many thanks,
Ranjan
On Mon, 20 Jan 2014 07:01:36 -0800 "Brian C. Lane" <bcl(a)redhat.com>
wrote:
On Fri, Jan 17, 2014 at 05:06:01PM -0600, Ranjan Maitra wrote:
> Hello,
>
> I created a livecd disk using a kickstart file which I modified from
> the LXDE spin and got these error messages (at different points of the
> ISO creation):
>
> I wonder if any of these messages are serious. In any case, is there an
> easy way to get rid of them?
Most of them are normal, there isn't any easy way to get rid of them
without also masking real errors. The unmount error is the one that may
cause problems. Sometimes it happens, some people seem to see it more
than others (eg. I don't see it myself). My suspicion is that some
desktop related thing is grabbing the mount when it shows up but I
haven't been able to confirm that.
>
> Many thanks,
> Ranjan
>
> ....
> No '/dev/log' or 'logger' included for syslog logging (3 times)
Those come from dracut while making the initrd.
> ....
> ....
> Opening default zone 'public'
> No changes to default zone needed.
> Note: Forwarding request to 'systemctl enable NetworkManager.service'.
> Note: Forwarding request to 'systemctl disable sshd.service'.
> rm '/etc/systemd/system/multi-user.target.wants/sshd.service'
These are firewall and service setup related.
> mkfs.fat 3.0.24 (2013-11-23)
> Loop device does not match a floppy size, using default hd params
> Initialized /dev/loop1 as a 20 MB HFS Plus volume
That is from mkefiboot, it decides on the options to use based on the
filesystem size.
> ERROR:program:umount: /tmp/lorax.imgutils.OtNm0z: target is busy
> umount: /tmp/lorax.imgutils.OtNm0z: target is busy
> ERROR:program: (In some cases useful info about processes that
> (In some cases useful info about processes that
> ERROR:program: use the device is found by lsof(8) or fuser(1).)
> use the device is found by lsof(8) or fuser(1).)
> WARNING:pylorax.imgutils:failed to unmount /tmp/lorax.imgutils.OtNm0z.
> retrying (1/3)... ERROR:program:umount: /tmp/lorax.imgutils.LTGEmM:
> target is busy umount: /tmp/lorax.imgutils.LTGEmM: target is busy
> ERROR:program: (In some cases useful info about processes that
> (In some cases useful info about processes that
> ERROR:program: use the device is found by lsof(8) or fuser(1).)
> use the device is found by lsof(8) or fuser(1).)
> WARNING:pylorax.imgutils:failed to unmount /tmp/lorax.imgutils.LTGEmM.
> retrying (1/3)... The unit files have no [Install] section. They are
> not meant to be enabled using systemctl.
> Possible reasons for having this kind of units are:
> 1) A unit may be statically enabled by being symlinked from another
> unit's .wants/ or .requires/ directory.
> 2) A unit's purpose may be to act as a helper for some other unit which
> has a requirement dependency on it.
> 3) A unit may be started when needed via activation (socket, path,
> timer, D-Bus, udev, scripted systemctl call, ...).
This is the only part that bugs me -- something prevented it from
umounting the image, and the retry counter seems to be broken.
> error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora: import read failed(2).
> Packages within this LiveCD
> ....
> ....
> ....
> Updating index cache for path `/usr/share/man/nl/man1'.
> Wait.../usr/bin/mandb: warning: /usr/share/man/nl/man1/dos2unix.1.gz:
> whatis parse for dos2unix(1) failed /usr/bin/mandb:
> warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2dos
> (1) failed /usr/bin/mandb:
> warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2mac
> (1) failed /usr/bin/mandb:
> warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for mac2unix
> (1) failed
> ....
> ....
> cp: cannot stat
>
'/home/maitra/remix/tmp/imgcreate-mHq7up/install_root/usr/share/doc/*-release-*/GPL':
> No such file or directory
These are all from the %post scripts
--
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)
--
livecd mailing list
livecd(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/livecd
--
Important Notice: This mailbox is ignored: e-mails are set to be
deleted on receipt. Please respond to the mailing list if appropriate.
For those needing to send personal or professional e-mail, please use
appropriate addresses.
____________________________________________________________
FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
Check it out at http://www.inbox.com/earth
12:10 a.m.
Hello,
I made some changes, but I still get the following errors/warnings:
......
No '/dev/log' or 'logger' included for syslog logging
No '/dev/log' or 'logger' included for syslog logging
......
mkfs.fat 3.0.24 (2013-11-23)
Loop device does not match a floppy size, using default hd params
Initialized /dev/loop1 as a 20 MB HFS Plus volume
The unit files have no [Install] section. They are not meant to be
enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another
unit's .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which
has a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path,
timer, D-Bus, udev, scripted systemctl call, ...).
......
0 old database entries were purged.
Updating index cache for path `/usr/share/man/nl/man1'.
Wait.../usr/bin/mandb: warning: /usr/share/man/nl/man1/dos2unix.1.gz:
whatis parse for mac2unix(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2mac
(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for dos2unix
(1) failed /usr/bin/mandb:
warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2dos
(1) failed Updating index cache for path `/usr/share/man/nl/man5'.
Wait...done. Checking for stray cats under /usr/share/man/nl...
Checking for stray cats under /var/cache/man/nl... Processing manual
pages under /usr/share/man/ja... Updating index cache for path
`/usr/share/man/ja/man5'. Wait...done. Checking for stray cats
under /usr/share/man/ja... Checking for stray cats
under /var/cache/man/ja... Processing manual pages
under /usr/share/man/zh_CN... Updating index cache for path
`/usr/share/man/zh_CN/man5'. Wait...done. Checking for stray cats
under /usr/share/man/zh_CN... Checking for stray cats
under /var/cache/man/zh_CN... Processing manual pages
under /usr/share/man/cs... Updating index cache for path
`/usr/share/man/cs/man5'. Wait...done. Checking for stray cats
under /usr/share/man/cs... Checking for stray cats
under /var/cache/man/cs... Processing manual pages
under /usr/share/man/id... Updating index cache for path
`/usr/share/man/id/man5'. Wait...done. Checking for stray cats
under /usr/share/man/id... Checking for stray cats
under /var/cache/man/id... Processing manual pages
under /usr/local/share/man... Updating index cache for path
`/usr/local/share/man/man4'. Wait...done. Checking for stray cats
under /usr/local/share/man... Checking for stray cats
under /var/cache/man/local... 105 man subdirectories contained newer
manual pages. 3183 manual pages were added. 0 stray cats were added. 0
old database entries were
purged. /etc/selinux/targeted/contexts/files/file_contexts: line 765
has invalid context
system_u:object_r:docker_lock_t:s0 /etc/selinux/targeted/contexts/files/file_contexts:
line 2406 has invalid context
system_u:object_r:speech-dispatcher_log_t:s0
/etc/selinux/targeted/contexts/files/file_contexts:
line 2635 has invalid context
system_u:object_r:vmtools_unit_file_t:s0
/etc/selinux/targeted/contexts/files/file_contexts:
line 2751 has invalid context
system_u:object_r:speech-dispatcher_unit_file_t:s0
/etc/selinux/targeted/contexts/files/file_contexts:
line 3743 has invalid context
system_u:object_r:vmtools_exec_t:s0 /etc/selinux/targeted/contexts/files/file_contexts:
line 3893 has invalid context
system_u:object_r:snapperd_exec_t:s0 /etc/selinux/targeted/contexts/files/file_contexts:
line 4862 has invalid context
system_u:object_r:speech-dispatcher_exec_t:s0
0.1%/etc/selinux/targeted/contexts/files/file_contexts: has invalid
context system_u:object_r:vmtools_exec_t:s0
I: -input-charset not specified, using utf-8 (detected in locale
settings) Size of boot image is 4 sectors -> No emulation
Size of boot image is 10064 sectors -> No emulation
Size of boot image is 40320 sectors -> No emulation
I have put the kickstart files up at the following directory:
http://www.public.iastate.edu/~maitra/shunya/
so that if possible, someone can take a look and advise me on
what I am doing wrong.
The files are:
fedora-livecd-shunya-20.ks
fedora-live-base-20.ks
fedora-live-minimization-20.ks
fedora-shunya-packages.ks
fedora-repo.ks
fedora-repo-not-rawhide.ks
fedora-repo-rawhide.ks
I have been using the following command (after sudo setenforce 0)
sudo livecd-creator --releasever=20 --config=fedora-livecd-shunya.ks
--tmpdir=tmp --fslabel=Fedora-Shunya-20_x86_64
Note that there are three rpms (aNu, wbar, thaali) which I created and
are in a local repo, but I can provide them if needed.
Thanks again for any help and advice!
It is very appreciated!
Best wishes,
Ranjan
On Mon, 20 Jan 2014 07:01:36 -0800 "Brian C. Lane" <bcl(a)redhat.com>
wrote:
On Fri, Jan 17, 2014 at 05:06:01PM -0600, Ranjan Maitra wrote:
> Hello,
>
> I created a livecd disk using a kickstart file which I modified from
> the LXDE spin and got these error messages (at different points of the
> ISO creation):
>
> I wonder if any of these messages are serious. In any case, is there an
> easy way to get rid of them?
Most of them are normal, there isn't any easy way to get rid of them
without also masking real errors. The unmount error is the one that may
cause problems. Sometimes it happens, some people seem to see it more
than others (eg. I don't see it myself). My suspicion is that some
desktop related thing is grabbing the mount when it shows up but I
haven't been able to confirm that.
>
> Many thanks,
> Ranjan
>
> ....
> No '/dev/log' or 'logger' included for syslog logging (3 times)
Those come from dracut while making the initrd.
> ....
> ....
> Opening default zone 'public'
> No changes to default zone needed.
> Note: Forwarding request to 'systemctl enable NetworkManager.service'.
> Note: Forwarding request to 'systemctl disable sshd.service'.
> rm '/etc/systemd/system/multi-user.target.wants/sshd.service'
These are firewall and service setup related.
> mkfs.fat 3.0.24 (2013-11-23)
> Loop device does not match a floppy size, using default hd params
> Initialized /dev/loop1 as a 20 MB HFS Plus volume
That is from mkefiboot, it decides on the options to use based on the
filesystem size.
> ERROR:program:umount: /tmp/lorax.imgutils.OtNm0z: target is busy
> umount: /tmp/lorax.imgutils.OtNm0z: target is busy
> ERROR:program: (In some cases useful info about processes that
> (In some cases useful info about processes that
> ERROR:program: use the device is found by lsof(8) or fuser(1).)
> use the device is found by lsof(8) or fuser(1).)
> WARNING:pylorax.imgutils:failed to unmount /tmp/lorax.imgutils.OtNm0z.
> retrying (1/3)... ERROR:program:umount: /tmp/lorax.imgutils.LTGEmM:
> target is busy umount: /tmp/lorax.imgutils.LTGEmM: target is busy
> ERROR:program: (In some cases useful info about processes that
> (In some cases useful info about processes that
> ERROR:program: use the device is found by lsof(8) or fuser(1).)
> use the device is found by lsof(8) or fuser(1).)
> WARNING:pylorax.imgutils:failed to unmount /tmp/lorax.imgutils.LTGEmM.
> retrying (1/3)... The unit files have no [Install] section. They are
> not meant to be enabled using systemctl.
> Possible reasons for having this kind of units are:
> 1) A unit may be statically enabled by being symlinked from another
> unit's .wants/ or .requires/ directory.
> 2) A unit's purpose may be to act as a helper for some other unit which
> has a requirement dependency on it.
> 3) A unit may be started when needed via activation (socket, path,
> timer, D-Bus, udev, scripted systemctl call, ...).
This is the only part that bugs me -- something prevented it from
umounting the image, and the retry counter seems to be broken.
> error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora: import read failed(2).
> Packages within this LiveCD
> ....
> ....
> ....
> Updating index cache for path `/usr/share/man/nl/man1'.
> Wait.../usr/bin/mandb: warning: /usr/share/man/nl/man1/dos2unix.1.gz:
> whatis parse for dos2unix(1) failed /usr/bin/mandb:
> warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2dos
> (1) failed /usr/bin/mandb:
> warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for unix2mac
> (1) failed /usr/bin/mandb:
> warning: /usr/share/man/nl/man1/dos2unix.1.gz: whatis parse for mac2unix
> (1) failed
> ....
> ....
> cp: cannot stat
>
'/home/maitra/remix/tmp/imgcreate-mHq7up/install_root/usr/share/doc/*-release-*/GPL':
> No such file or directory
These are all from the %post scripts
--
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)
--
livecd mailing list
livecd(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/livecd
--
Important Notice: This mailbox is ignored: e-mails are set to be
deleted on receipt. Please respond to the mailing list if appropriate.
For those needing to send personal or professional e-mail, please use
appropriate addresses.
____________________________________________________________
GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at http://www.inbox.com/smileys
Works with AIM®, MSN® Messenger, Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails
3746
days inactive
3753
days old
livecd@lists.fedoraproject.org
3 comments
2 participants
participants (2)
-
Brian C. Lane -
Ranjan Maitra