[Freeipa-devel] [PATCHES] 0039-0040 systemd ipactl fixes

[Alexander Bokovoy]

On Wed, 10 Jul 2013, Ana Krivokapic wrote:
>On 07/08/2013 08:32 AM, Alexander Bokovoy wrote:
>> On Thu, 20 Jun 2013, Ana Krivokapic wrote:
>>> Hello,
>>>
>>> Attached patches fix systemd and ipactl related bugs:
>>>
>>> https://fedorahosted.org/freeipa/ticket/3730
>>> https://fedorahosted.org/freeipa/ticket/3729
>> NACK. For me upgrade case fails (rpm -Uhv), dirsrv didn't restart on
>> upgrade properly and everything else has failed afterwards.
>>
>
>This was caused due to 'systemctl is-active' returning exit status 3
>('activating'), and our code treating the non-zero exit status as a failure. I
>handled this case in the updated patch.
>
>As for the ipa.service and dependency ordering, I have done some further testing
>and found out the adding the '--ignore-dependencies' switch alone solves the
>shutdown issue. So I think that no modification of ipa.service file is necessary.
>
>Updated patches are attached.
This is much better. However, 'ipactl stop' doesn't stop ns-slapd and
dogtag:

  1155 ?        Sl     0:00 /usr/sbin/ns-slapd -D
/etc/dirsrv/slapd-EXAMPLE-COM -i /var/run/dirsrv/slapd-EXAMPLE-COM.pid
-w /var/run/dirsrv/slapd-EXAMPLE-COM.startpid
  1485 ?        Sl     0:11 /usr/lib/jvm/jre/bin/java
-DRESTEASY_LIB=/usr/share/java/resteasy -classpath
/usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar
-Dcatalina.base=/var/lib/pki/pki-tomcat
-Dcatalina.home=/usr/share/tomcat -Djava.endorsed.dirs=
-Djava.io.tmpdir=/var/lib/pki/pki-tomcat/temp -Djava.security.manager
-Djava.security.policy==/var/lib/pki/pki-tomcat/conf/catalina.policy
-Djava.util.logging.config.file=/var/lib/pki/pki-tomcat/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
org.apache.catalina.startup.Bootstrap start

# systemctl status dirsrv.target
dirsrv.target - 389 Directory Server
    Loaded: loaded (/usr/lib/systemd/system/dirsrv.target; disabled)
    Active: inactive (dead) since Чт 2013-07-11 12:32:19 EEST; 1min 52s ago

июл 11 12:31:31 ipa.example.com systemd[1]: Stopping 389 Directory Server.
июл 11 12:31:31 ipa.example.com systemd[1]: Starting 389 Directory Server.
июл 11 12:31:31 ipa.example.com systemd[1]: Reached target 389 Directory Server.
июл 11 12:32:19 ipa.example.com systemd[1]: Stopping 389 Directory Server.
июл 11 12:32:19 ipa.example.com systemd[1]: Stopped target 389 Directory Server.

# systemctl status dirsrv at EXAMPLE-COM
dirsrv at EXAMPLE-COM.service - 389 Directory Server EXAMPLE-COM.
    Loaded: loaded (/lib/systemd/system/dirsrv at .service; enabled)
    Active: active (running) since Чт 2013-07-11 12:31:32 EEST; 2min 59s ago
   Process: 1121 ExecStopPost=/bin/rm -f /var/run/dirsrv/slapd-%i.pid (code=exited, status=0/SUCCESS)
   Process: 1123 ExecStart=/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-%i -i /var/run/dirsrv/slapd-%i.pid -w /var/run/dirsrv/slapd-%i.startpid (code=exited, status=0/SUCCESS)
  Main PID: 1155 (ns-slapd)
    CGroup: name=systemd:/system/dirsrv at .service/dirsrv at EXAMPLE-COM.service
            └─1155 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-EXAMPLE-COM -i /var/run/dirsrv/slapd-EXAMPLE-COM.pid -w /var/run/dirsrv/slapd-EXAMPLE-COM.startpi...

июл 11 12:31:34 ipa.example.com ns-slapd[1155]: GSSAPI server step 2
июл 11 12:31:34 ipa.example.com ns-slapd[1155]: GSSAPI server step 3
июл 11 12:31:34 ipa.example.com ns-slapd[1155]: GSSAPI server step 2
июл 11 12:31:34 ipa.example.com ns-slapd[1155]: GSSAPI server step 3
июл 11 12:31:56 ipa.example.com ns-slapd[1155]: GSSAPI server step 1
июл 11 12:31:56 ipa.example.com ns-slapd[1155]: GSSAPI server step 2
июл 11 12:31:56 ipa.example.com ns-slapd[1155]: GSSAPI server step 3
июл 11 12:31:56 ipa.example.com ns-slapd[1155]: GSSAPI server step 1
июл 11 12:31:56 ipa.example.com ns-slapd[1155]: GSSAPI server step 2
июл 11 12:31:56 ipa.example.com ns-slapd[1155]: GSSAPI server step 3


When I issue 'ipactl restart' all processes are restarted properly.

-- 
/ Alexander Bokovoy