Re: Autostart with manage-procs and network mounts

[Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov>]

On 8/4/21 2:25 AM, Smith, William wrote:
> Hi Michael,
> 
> I am using /etc/fstab
> 
> I solved the problem for my case by adding: "name-of-mount.mount" in the end of the After line like this:
> 
> After=network.target remote-fs.target name-of-mount.mount

Well, this is unexpected.  Can you share the line from /etc/fstab?
I'm wondering if the special '_netdev' option has been omitted?
This is how systemd recognizes a network mount, and knows to add
the dependency on 'remote-fs.target'.

https://www.freedesktop.org/software/systemd/man/systemd.mount.html#_netdev


> I found the name-of-mount using
> 
>> systemctl list-units --type=mount
> 
> I used this for help: https://unix.stackexchange.com/a/247547
> 
> Obviously this doesn’t work in a general case, only for my deployment system. For now I have edited the generator.py file of manage-procs.  I haven't looked at used autofs before.
> 
> I will follow the github issue you've made and post anything else there if I think of anything.
> 
> Best
> 
> Will
> 
> 
> 
> -----Original Message-----
> From: Michael Davidsaver <mdavidsaver at gmail.com>
> Sent: Tuesday, August 3, 2021 7:17 PM
> To: Smith, William <william.smith at helmholtz-berlin.de>
> Cc: wayne.lewis at ess.eu; tech-talk at aps.anl.gov
> Subject: Re: Autostart with manage-procs and network mounts
> 
> On 8/3/21 3:07 AM, Smith, William via Tech-talk wrote:
>> Hi,
>>
>>
>>
>> I am using manage-procs to deploy and manage IOC’s using systemd. It creates the systemd files that look something like what is shown below. I mount a network drive over nfs at boot that contains the built IOC binaries for the service to run. The service is enabled, it should start at boot but it doesn’t because the ConditionPathIsDirectory fails. If I go to the directory after the system has booted, I can see that it has been mounted correctly and exists. I cc Wayne because I seem to remember us having a similar problem at ESS about 2 years ago but I can’t remember how we solved it! Does anybody have any ideas?
> 
> How is the relevant NFS share being mounted?  Via /etc/fstab, autofs, or some other initiator?
> 
> I think that "After=network.target remote-fs.target" should be enough to ensure ordering.  You could try adding "Requires=network.target remote-fs.target".
> 
> 
>> Many thanks,
>>
>>
>>
>> Will
>>
>>
>>
>> emil@sissy-ioc-01:/etc/systemd/system$ cat
>> procserv-EMIL_KTH_00.service
>>
>>
>>
>> [Unit]
>>
>> Description=procServ for EMIL_KTH_00
>>
>> After=network.target remote-fs.target
>>
>> ConditionPathIsDirectory=/home/emil/Apps/epics/R7.0.4.1/prod/ioc/EMILE
>> L/EMIL_KTH_00/1-4-0/iocBoot/iocEMIL_KTH_00
>>
>>
>>
>> [Service]
>>
>> Type=simple
>>
>> ExecStart=/usr/local/bin/procServ-launcher --system EMIL_KTH_00
>>
>> RuntimeDirectory=procserv-EMIL_KTH_00
>>
>> StandardOutput=syslog
>>
>> StandardError=inherit
>>
>> SyslogIdentifier=procserv-EMIL_KTH_00
>>
>>
>>
>> User=emil
>>
>> Group=emil
>>
>>
>>
>> [Install]
>>
>> WantedBy=multi-user.target
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> ----------
>>
>> Helmholtz-Zentrum Berlin für Materialien und Energie GmbH
>>
>> Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren e.V.
>>
>> Aufsichtsrat: Vorsitzender Dr. Volkmar Dietz, stv. Vorsitzende Dr.
>> Jutta Koch-Unterseher
>> Geschäftsführung: Prof. Dr. Jan Lüning (Sprecher), Prof. Dr. Bernd
>> Rech, Thomas Frederking
>>
>> Sitz Berlin, AG Charlottenburg, 89 HRB 5583
>>
>> Postadresse:
>> Hahn-Meitner-Platz 1
>> 14109 Berlin
>> Deutschland
> 
> 
> ________________________________
> 
> Helmholtz-Zentrum Berlin für Materialien und Energie GmbH
> 
> Mitglied der Hermann von Helmholtz-Gemeinschaft Deutscher Forschungszentren e.V.
> 
> Aufsichtsrat: Vorsitzender Dr. Volkmar Dietz, stv. Vorsitzende Dr. Jutta Koch-Unterseher
> Geschäftsführung: Prof. Dr. Jan Lüning (Sprecher), Prof. Dr. Bernd Rech, Thomas Frederking
> 
> Sitz Berlin, AG Charlottenburg, 89 HRB 5583
> 
> Postadresse:
> Hahn-Meitner-Platz 1
> 14109 Berlin
> Deutschland
>