Bristol Digest, Vol 620, Issue 4

Send Bristol mailing list submissions to
bristol@mailman.lug.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk

You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."


Today's Topics:

1. Re: Fedora 22 - Slow Shutdown (Peter Hemmings)


----------------------------------------------------------------------

Message: 1
Date: Sat, 10 Oct 2015 12:44:51 +0100
From: Peter Hemmings <peter@hemmings.eclipse.co.uk>
To: bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Fedora 22 - Slow Shutdown
Message-ID: <5618FA33.9040705@hemmings.eclipse.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed



On 07/10/15 11:44, Peter Hemmings wrote:
> Hi,
>
>
> On 07/10/15 10:53, Shane McEwan wrote:
>> I'm not sure (having not done anything with systemd yet) but if it
>> follows the usual conventions then I think you need to put the debug.sh
>> file into a /usr/lib/systemd/system-shutdown.d directory (note the
>> addition of '.d' to the end). That way it shouldn't clash with the
>> system-shutdown file. systemd should execute anything in the
>> /usr/lib/systemd/*.d directories.
>
> Thanks for the info.
>
> I do not have a "systen-shutdown.d directory atm but do have a
> /usr/lib/systemd/scripts/ directory.
>
> It has just one file in it "nfs-utils_env.sh", I assume I could put it
> in there rather than make a new directory!?
>
> As I understand it, the debug script is run almost at the end of
> shutdown and should show what process is not closing correctly.
>>
>> Shane.
>>
>> On 06/10/15 21:26, Peter Hemmings wrote:
>>> Hi,
>>>
>>> I am trying to diagnose a slow (2min approx) shutdown on my laptop using
>>> this:
>>>
>>> http://freedesktop.org/wiki/Software/systemd/Debugging/#shutdowncompleteseventually.
>>>
>>>
>>>
>>> I am trying to save the script as
>>> /usr/lib/systemd/system-shutdown/debug.sh
>>>
>>> I do not have a folder "system-shutdown" and have a file of the same
>>> name so cannot make a directory or perform the instruction.
>>>
>>> Is the instruction out of date, or is there another way to do it on
>>> fedora or am I doing something wrong!?
>>>
>>> Regards
>>>
>>
>> _______________________________________________
>> Bristol mailing list
>> Bristol@mailman.lug.org.uk
>> https://mailman.lug.org.uk/mailman/listinfo/bristol
>>
>
> I could just do a new clean install but I would prefer to find what
> caused this to happen.
>
> Regards
I did the debug in above url and got a lot of failures so not sure where
to start!:

[root@localhost ~]# cat /shutdown-log.txt | grep failed
[ 108.277273] systemd[1]:
ConditionPathExists=!/etc/alsa/state-daemon.conf failed for
alsa-store.service.
[ 108.277278] systemd[1]: Starting of alsa-store.service requested but
condition failed. Not starting unit.
[ 108.533088] systemd[1]: avahi-daemon.socket got notified about service
death (failed permanently: no)
[ 108.856758] systemd[1]: D-Bus activation failed for polkit.service:
Refusing activation, D-Bus is shutting down.
[ 109.900077] systemd[1]: D-Bus activation failed for
dbus-org.freedesktop.login1.service: Refusing activation, D-Bus is
shutting down.
[ 109.922449] systemd[1]: firewalld.service changed running -> failed
[ 109.922706] systemd[1]: Unit firewalld.service entered failed state.
[ 109.922779] systemd[1]: firewalld.service failed.
[ 109.926313] systemd[1]: dbus.socket got notified about service death
(failed permanently: no)
[ 110.986599] systemd[1]: cups.socket got notified about service death
(failed permanently: no)
[ 200.041105] systemd[1]: serviio.service changed stop-sigkill -> failed
[ 200.041460] systemd[1]: Unit serviio.service entered failed state.
[ 200.041569] systemd[1]: serviio.service failed.
[ 200.360262] systemd[1]: lvm2-lvmetad.socket got notified about service
death (failed permanently: no)
[root@localhost ~]#

Any ideas?

Regards

--
Peter H



------------------------------

Subject: Digest Footer

_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol

------------------------------

End of Bristol Digest, Vol 620, Issue 4
***************************************