afrender.service on NFS mount

Installation and configuration.
Post Reply
keyframe
Posts: 40
Joined: Sat Jan 21, 2017 9:43 pm

afrender.service on NFS mount

Post by keyframe » Wed Dec 18, 2019 2:48 pm

Heya,

Previously running 2.2.3 I was able to deploy afanasy via a centrally installed NFS mount symlinked to /opt/cgru.
Since version 2.3.1 has shifted to systemd, it seems that i'm unable to run the same scam, since the unit file must reside on a filesystem available at PID1.

AFAIK, this is not a dependency/order to service startup issue, but a hard requirement.

Does anyone have any insight?

G

ps: the primary reason for central deployment is having to modify one set of config files, once... rather then having unique files for each machine.
--
centOS 8.1, cgru 2.3.1

keyframe
Posts: 40
Joined: Sat Jan 21, 2017 9:43 pm

Re: afrender.service on NFS mount

Post by keyframe » Wed Dec 18, 2019 3:07 pm

For posterity, I was able to hack around this by relocating the service file to a local drive, and repointing the symlink to it... but it's kinda bleh.

A more elegant solution would be awesome.

G
--
centOS 8.1, cgru 2.3.1

User avatar
timurhai
Site Admin
Posts: 526
Joined: Sun Jan 15, 2017 8:40 pm
Location: Russia, Korolev
Contact:

Re: afrender.service on NFS mount

Post by timurhai » Thu Dec 19, 2019 12:56 pm

Hi.

Everything is normal.
You deploy Afanasy in any custom way.
You can write any own init.d/systedm.d service or modify existing.

For example, i am not using a nfs share for binaries.
And we have such /opt/cgru/config.json:

Code: Select all

{"cgru_config":{

	"include":["/cg/tank/config.json"],

	"":""
}}
And /cg/tank is our (nfs) shared tools/scripts/configs location.
Timur Hairulin
CGRU 2.4.0, Ubuntu 18.04 LTS, MS Windows 10 (clients only).

keyframe
Posts: 40
Joined: Sat Jan 21, 2017 9:43 pm

Re: afrender.service on NFS mount

Post by keyframe » Fri Dec 20, 2019 3:18 pm

Heya Timur,

As you pointed out, everything is normal.

What I didn't know ahead of this process (that I know now) is that service unit files for systemd MUST live on a local file system due to some internal caching/dependency build mechanism.
Basically, if I host the unit files on a remote drives, the system can't see it at boot, and the service fails to start - and it's not simply a matter of waiting for the remote drive to be mounted.

see here: https://github.com/systemd/systemd/issues/8307
G
--
centOS 8.1, cgru 2.3.1

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests