some errors on boot

[Frank White]

Hi, as my previous messages I have some problems to boot.
One error is that F. does not find some users..
Those are the errors:

Dec 14 12:49:54 localhost chronyd[818]: chronyd version 1.31.1 starting
Dec 14 12:49:54 localhost chronyd[818]: Fatal error : getpwnam(chrony) failed
Dec 14 12:49:54 localhost avahi-daemon[813]: Failed to find user 'avahi'.
Dec 14 12:49:54 localhost rpcbind[823]: cannot get uid of 'rpc':
Permission denied

BUT

# egrep -i "chrony|avahi" passwd shadow group
passwd:avahi:x:70:70:Avahi mDNS/DNS-SD Stack:/var/run/avahi-daemon:/sbin/nologin
passwd:avahi-autoipd:x:170:170:Avahi IPv4LL
Stack:/var/lib/avahi-autoipd:/sbin/nologin
passwd:chrony:x:993:992::/var/lib/chrony:/sbin/nologin
shadow:avahi:!!:15883::::::
shadow:avahi-autoipd:!!:15883::::::
shadow:chrony:!!:15883::::::
group:avahi:x:70:
group:avahi-autoipd:x:170:
group:chrony:x:992:

Thank u.

[Michael Schwendt]

On Mon, 14 Dec 2015 11:59:58 +0000, Frank White wrote:
> Hi, as my previous messages I have some problems to boot.
> One error is that F. does not find some users..
> Those are the errors:
>
> Dec 14 12:49:54 localhost chronyd[818]: chronyd version 1.31.1 starting
> Dec 14 12:49:54 localhost chronyd[818]: Fatal error : getpwnam(chrony) failed
> Dec 14 12:49:54 localhost avahi-daemon[813]: Failed to find user 'avahi'.
> Dec 14 12:49:54 localhost rpcbind[823]: cannot get uid of 'rpc':
> Permission denied

Keep all your messages in a single thread unless you know they are not
related.

Try booting with SELinux set to permissive mode (enforcing=0 kernel parameter).
Does that help already? If so, trigger relabeling of your file system.
Else, stay in permissive mode and verify all packages (rpm -Va). Reinstall
any packages that are clearly damaged (i.e. not passing the checksum check
for non-config files).

[Frank White]

Hi,
I have not resolved my problem... I have seen an automatic reboot
after the relabeling job. And I have a freeze during reinstall of
polkit packages.. and some others packages...
anyway this is my boot log:
http://pastebin.com/4G77jkcB

Thank you very much..

2015-12-14 13:53 GMT+00:00 Michael Schwendt :
> On Mon, 14 Dec 2015 11:59:58 +0000, Frank White wrote:
> > Hi, as my previous messages I have some problems to boot.
> > One error is that F. does not find some users..
> > Those are the errors:
> >
> > Dec 14 12:49:54 localhost chronyd[818]: chronyd version 1.31.1 starting
> > Dec 14 12:49:54 localhost chronyd[818]: Fatal error : getpwnam(chrony) failed
> > Dec 14 12:49:54 localhost avahi-daemon[813]: Failed to find user 'avahi'.
> > Dec 14 12:49:54 localhost rpcbind[823]: cannot get uid of 'rpc':
> > Permission denied
>
> Keep all your messages in a single thread unless you know they are not
> related.
>
> Try booting with SELinux set to permissive mode (enforcing=0 kernel parameter).
> Does that help already? If so, trigger relabeling of your file system.
> Else, stay in permissive mode and verify all packages (rpm -Va). Reinstall
> any packages that are clearly damaged (i.e. not passing the checksum check
> for non-config files).
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org

[Michael Schwendt]

On Tue, 15 Dec 2015 12:21:26 +0000, Frank White wrote:
> Hi,
> I have not resolved my problem... I have seen an automatic reboot
> after the relabeling job. And I have a freeze during reinstall of
> polkit packages.. and some others packages...
> anyway this is my boot log:
> http://pastebin.com/4G77jkcB
>
> Thank you very much..

Why do you run a Fedora 20 kernel with at least one package being Fedora 21?
Is it supposed to be an installation of Fedora 21?

Both distributions have reached end of life!

Give more details. Problems like that don't occur suddenly and without
the user/admin messing with the system/installation. How often do you
check for errors anyway? There are quite a lot in your boot messages, and
*you* should be much more familiar with how you use your machine than
anyone else skimming over those messages.

Lots of errors. Even a crash of pykickstart. What have you done with it?

Dec 15 13:42:37 localhost systemd-cgroups-agent: Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: No such file or directory

Dec 15 13:42:54 localhost lm_sensors-modprobe-wrapper: No sensors with loadable kernel modules configured.
Dec 15 13:42:54 localhost lm_sensors-modprobe-wrapper: Please, run 'sensors-detect' as root in order to search for available sensors.

Dec 15 13:42:56 localhost abrtd: File 'time' doesn't contain valid unix time stamp('')
Dec 15 13:42:56 localhost abrtd: Unlocked '/var/spool/abrt/oops-2015-07-03-11:41:48-869-0' (no or corrupted 'time' file)

Dec 15 13:42:57 localhost smartd[795]: Warning via /usr/libexec/smartmontools/smartdnotify to root produced unexpected output (32 bytes) to STDOUT/STDERR:

ec 15 13:43:09 localhost initial-setup: parsing input kickstart /root/anaconda-ks.cfg
Dec 15 13:43:09 localhost initial-setup: kickstart parsing failed
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/initial_setup/__main__.py", line 90, in <module>
    parser.readKickstart(INPUT_KICKSTART_PATH)
  File "/usr/lib/python2.7/site-packages/pykickstart/parser.py", line 730, in readKickstart
    self.readKickstartFromString(s, reset=False)
  File "/usr/lib/python2.7/site-packages/pykickstart/parser.py", line 703, in readKickstartFromString
    self._stateMachine (i)
  File "/usr/lib/python2.7/site-packages/pykickstart/parser.py", line 686, in _stateMachine
    self._tryFunc(lambda: self.handleCommand(lineno, args))
  File "/usr/lib/python2.7/site-packages/pykickstart/parser.py", line 606, in _tryFunc
    fn()
  File "/usr/lib/python2.7/site-packages/pykickstart/parser.py", line 686, in <lambda>
    self._tryFunc(lambda: self.handleCommand(lineno, args))
  File "/usr/lib/python2.7/site-packages/pyanaconda/kickstart.py", line 1890, in handleCommand
    return KickstartParser.handleCommand(self, lineno, args)
  File "/usr/lib/python2.7/site-packages/pykickstart/parser.py", line 496, in handleCommand
    retval = self.handler.dispatcher(args, lineno)
  File "/usr/lib/python2.7/site-packages/pykickstart/base.py", line 427, in dispatcher
    obj = self.commands[cmd].parse(args[1:])
  File "/usr/lib/python2.7/site-packages/pykickstart/commands/group.py", line 81, in parse
    (opts, _extra) = self.op.parse_args(args=args, lineno=self.lineno)
  File "/usr/lib/python2.7/site-packages/pykickstart/options.py", line 105, in parse_args
    return OptionParser.parse_args(self, **kwargs)
  File "/usr/lib/python2.7/optparse.py", line 1405, in parse_args
    return self.check_values(values, args)
  File "/usr/lib/python2.7/site-packages/pykickstart/options.py", line 82, in check_values
    raise KickstartValueError(formatErrorMsg(self.lineno, _("Option %s is required") % option))
KickstartValueError: Si è verificato il seguente problema sulla riga 7 del file di kickstart:

[Frank White]

2015-12-15 13:56 GMT+00:00 Michael Schwendt :
> On Tue, 15 Dec 2015 12:21:26 +0000, Frank White wrote:
> > Hi,
> > I have not resolved my problem... I have seen an automatic reboot
> > after the relabeling job. And I have a freeze during reinstall of
> > polkit packages.. and some others packages...
> > anyway this is my boot log:
> > http://pastebin.com/4G77jkcB
> >
> > Thank you very much..
>
> Why do you run a Fedora 20 kernel with at least one package being Fedora 21?
> Is it supposed to be an installation of Fedora 21?
>
> Both distributions have reached end of life!
>
> Give more details. Problems like that don't occur suddenly and without
> the user/admin messing with the system/installation. How often do you
> check for errors anyway? There are quite a lot in your boot messages, and
> *you* should be much more familiar with how you use your machine than
> anyone else skimming over those messages.
>
> Lots of errors. Even a crash of pykickstart. What have you done with it?

The problem come from a dirty upgrade from f20 to f21... This time I
have booted with an old kernel.. but on grub I have a f21 kernel.
Anyway the problems are still there.
Now I try to upgrade again. The command I have used is:
# fedup  --network 21 --product=workstation
I am sorry I havenot said it before... but I don't use my workstation
since months and I have forgotten the last time I have used it was the
upgrade time.
Maybe it's better to upgrade with the cd ?

[Rick Stevens]

On 12/15/2015 06:36 AM, Frank White wrote:
> 2015-12-15 13:56 GMT+00:00 Michael Schwendt :
> > On Tue, 15 Dec 2015 12:21:26 +0000, Frank White wrote:
> > > Hi,
> > > I have not resolved my problem... I have seen an automatic reboot
> > > after the relabeling job. And I have a freeze during reinstall of
> > > polkit packages.. and some others packages...
> > > anyway this is my boot log:
> > > http://pastebin.com/4G77jkcB
> > >
> > > Thank you very much..
> >
> > Why do you run a Fedora 20 kernel with at least one package being Fedora 21?
> > Is it supposed to be an installation of Fedora 21?
> >
> > Both distributions have reached end of life!
> >
> > Give more details. Problems like that don't occur suddenly and without
> > the user/admin messing with the system/installation. How often do you
> > check for errors anyway? There are quite a lot in your boot messages, and
> > *you* should be much more familiar with how you use your machine than
> > anyone else skimming over those messages.
> >
> > Lots of errors. Even a crash of pykickstart. What have you done with it?
>
> The problem come from a dirty upgrade from f20 to f21... This time I
> have booted with an old kernel.. but on grub I have a f21 kernel.
> Anyway the problems are still there.
> Now I try to upgrade again. The command I have used is:
> # fedup  --network 21 --product=workstation
> I am sorry I havenot said it before... but I don't use my workstation
> since months and I have forgotten the last time I have used it was the
> upgrade time.
> Maybe it's better to upgrade with the cd ?

You cannot use fedup to an end-of-life version of the system. Fedora 20
and 21 are both at end-of-life. You will need to do an upgrade from the
CD. Get the live spin of the desktop you prefer (Gnome, KDE, XFCE,
whatever), burn it to CD, boot it and install to hard disk.

----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-        Hard work has a future payoff. Laziness pays off now.       -
----------------------------------------------------------------------

[Joe Zeff]

On 12/15/2015 09:31 AM, Rick Stevens wrote:
> You cannot use fedup to an end-of-life version of the system. Fedora 20
> and 21 are both at end-of-life.

Wherever did you get that wrong idea?  The upgrade will work as long as 
the repos are still there.

[Gordon Messmer]

On 12/15/2015 10:42 AM, Joe Zeff wrote:
> On 12/15/2015 09:31 AM, Rick Stevens wrote:
> > You cannot use fedup to an end-of-life version of the system. Fedora 20
> > and 21 are both at end-of-life.
>
> Wherever did you get that wrong idea?  The upgrade will work as long 
> as the repos are still there.

Yes, but one should not expect EOL repos to be present.  F20, for 
instance, is not.  I'm not sure what Fedora's process for archiving 
releases is.  I can't find it.

[Kevin Fenzi]

On Tue, 15 Dec 2015 11:17:06 -0800
Gordon Messmer  wrote:
> On 12/15/2015 10:42 AM, Joe Zeff wrote:
> > On 12/15/2015 09:31 AM, Rick Stevens wrote:
> > > You cannot use fedup to an end-of-life version of the system.
> > > Fedora 20 and 21 are both at end-of-life.
> >
> > Wherever did you get that wrong idea?  The upgrade will work as
> > long as the repos are still there.
>
> Yes, but one should not expect EOL repos to be present.  F20, for 
> instance, is not.  I'm not sure what Fedora's process for archiving 
> releases is.  I can't find it.

It's pretty simple:

Some weeks after a release goes end of life, the entire release tree
for that release is moved to archives.

ie, right now Fedora 21 is at: 
http://dl.fedoraproject.org/pub/fedora/linux/releases/21/
it will be moved to:
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/21/

At that point a number of mirrors that don't carry the archives will no
longer have Fedora 21 available at all.

Note that we never remove old releases from Mirrormanager, so metalinks
and mirrorlists will continue to work and point you to the archive
space and those hosts that mirror it.

kevin

[Frank White]

Hi Again,
I tried to upgrade to fedora 22 with fedora-upgrade but it crashed
(freeze) in the middle of the upgrade.
I made a runtime poweroff but after the reboot now I have a mixed
system 22 and 23. I download the dvd, it boot but It stop at the end
loading.. well when it finish to load the fedora logo.  Looks it does
not find the disks.. maybe the problem come from my dvd reader.. it is
a usb dvd read becuase the installed reader is broken.
Anyway it does not find the disks and does not ask me the passphrase
to open the encrypted disks.

2015-12-15 17:31 GMT+00:00 Rick Stevens :
> On 12/15/2015 06:36 AM, Frank White wrote:
> > 2015-12-15 13:56 GMT+00:00 Michael Schwendt :
> > > On Tue, 15 Dec 2015 12:21:26 +0000, Frank White wrote:
> > > > Hi,
> > > > I have not resolved my problem... I have seen an automatic reboot
> > > > after the relabeling job. And I have a freeze during reinstall of
> > > > polkit packages.. and some others packages...
> > > > anyway this is my boot log:
> > > > http://pastebin.com/4G77jkcB
> > > >
> > > > Thank you very much..
> > >
> > > Why do you run a Fedora 20 kernel with at least one package being Fedora
> > > 21?
> > > Is it supposed to be an installation of Fedora 21?
> > >
> > > Both distributions have reached end of life!
> > >
> > > Give more details. Problems like that don't occur suddenly and without
> > > the user/admin messing with the system/installation. How often do you
> > > check for errors anyway? There are quite a lot in your boot messages, and
> > > *you* should be much more familiar with how you use your machine than
> > > anyone else skimming over those messages.
> > >
> > > Lots of errors. Even a crash of pykickstart. What have you done with it?
> >
> > The problem come from a dirty upgrade from f20 to f21... This time I
> > have booted with an old kernel.. but on grub I have a f21 kernel.
> > Anyway the problems are still there.
> > Now I try to upgrade again. The command I have used is:
> > # fedup  --network 21 --product=workstation
> > I am sorry I havenot said it before... but I don't use my workstation
> > since months and I have forgotten the last time I have used it was the
> > upgrade time.
> > Maybe it's better to upgrade with the cd ?
>
> You cannot use fedup to an end-of-life version of the system. Fedora 20
> and 21 are both at end-of-life. You will need to do an upgrade from the
> CD. Get the live spin of the desktop you prefer (Gnome, KDE, XFCE,
> whatever), burn it to CD, boot it and install to hard disk.
> Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
> AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
>                                                                -
>    Hard work has a future payoff. Laziness pays off now.       -
>
> --
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org