Intermittent Auto-start issue with PMS

General Discussions
1

I am having intermittent auto-start issue with my PMS that i have been dealing with for a while now.

I am using a custom configuration and have done the recommended steps with the override file

But it seems most times when i reboot the server PMS fails to start.

bw6hzz4p25c7.png942×274 11.1 KB

Override file:

yyiqsduvxijb.png775×289 8.65 KB

Change the UMask to Umask, still unable to start on boot up

s1m5l8i9of0r.png943×246 12.2 KB

When i start it manual i get below

3e8tzcdg8uo4.png941×275 9.61 KB

Note that service does start up fine if i start it manually.

System:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION=“Ubuntu 16.04.3 LTS”
NAME=“Ubuntu”
VERSION=“16.04.3 LTS (Xenial Xerus)”

PMS: Version 1.11.0.4666

I need help, must be missing something. Thanks.

2

What does your override.conf contain?

3

screenshot in the original problem description

yyiqsduvxijb.png775×289 8.65 KB

4

Sorry for the delay. I was detained.

As I stated in the configuration doc, Some hosts want UMask and others want Umask. It looks like you system is stricter on autostart versus manual start. That’s an interesting twist.

Have you edited the override and performed the systemctl daemon-reload to update it?

5

Yea, perform reload on every change to the override.

Steps is have tried:
Tried with UMask and 0002
Tried with Umask and 0002
Tried getting UMask from /etc/login.defs

Tried with UMask and 0022
Tried with Umask and 0022

Still same issue.

6

what distro and version is that? I’ve not seen both fail.

7

System:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION=“Ubuntu 16.04.3 LTS”
NAME=“Ubuntu”
VERSION=“16.04.3 LTS (Xenial Xerus)”

PMS: Version 1.11.0.4666

8

Crap… Be right back. I will spin up a specific 16.04.3 VM to confirm but it looks like we’re dealing with a Ubuntu bug.

9

I just created a fresh 16.04.3 VM

  1. Ubuntu no longer allows Umask=xxxx
  2. Ubuntu does allow UMask=xxxx

Please remember to issue `systemctl daemon-reload after changing the value but before restarting and try again?

10

I went over the steps again to confirm everything, it all looks good but PMS still failing on start-up. Guessing the issue is not with the config file?

Steps:

gdegb3rxya27.png1373×1253 69.7 KB

Error:

khdg7x7bmxs6.png1375×524 43.6 KB

11

That must be something on your machine, unfortunately.

I’ve built a full fresh VM and cannot replicate both failing.

I did make a notation about the change in 16.04.3 regarding UMask but otherwise it is solid on autostart.

12

Closing loop on this.

Was finally able to detect and resolve the issue with ‘Intermittent Auto-start issue with PMS’ last month and i thought i share.

The issue was with the PMS service starting before the data disk with configuration is mounted. resolved issue by putting a 30 seconds delay on the override file.

ExecStartPre=/bin/sleep 30