Hi guys,
I'm having some strange behaviour with nginx. I've a website which provides services across multiple third level domains (something like sitea.example.com, siteb.example.com and so on)

The file with server aliases is created dynamically and nginx reloaded with a cron job.

I noticed that a simple "reload" is not enough to tell to nginx to reload (and eventually create) the file with new aliases.

I use a simple "include" in the server section, that points to the file with aliases.

Any ideas/suggestion?

Thank you

This is somewhat common, it's not every time a systemctl reload nginx can do the trick, but you'll need to do a full restart (systemctl restart nginx) especially if you are using ssl

Hi JoakimR,
I solved the problem replacing the entry in crontab.
The command "service nginx reload" executed as root by crond caused the problem, instead, service nginx reload executed as root from terminal worked flawlessly.

So I replaced "service nginx reload" with "/etc/init.d/nginx reload" in crond and everything worked perfectly.

Thank you for your help.