<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Generator" content="Microsoft Exchange Server"> <style></style> </head> <body> <div> <div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black"> Hi,<br> <br> </div> <div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black"> I just found root cause for this sevice not to start. It was simple parent folder permission issue. In this case it was /opt/apps/sdc which was set to root:root. I changed it to sdc:sdc and it allowed actual sdc_home inside /opt/SP/apps to start service without error code. Can you suggest why it was not the issue for one server where other 5 servers i had to change ownership. Systemd version was same in all 6 servers. Only difference i found was switched-root .Just fyi i am very beginner in for rhel 7 and so systemd troubleshoot.<br> <br> </div> <div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black"> Thanks,<br> <br> </div> <div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black"> Krunal.<br> <br> </div> <div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black"> <div dir="auto" style="direction:ltr; margin:0; padding:0; font-family:sans-serif; font-size:11pt; color:black"> Get <a href="https://aka.ms/ghei36">Outlook for Android</a></div> <br> </div> <hr tabindex="-1" style="display:inline-block; width:98%"> <div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> systemd-devel <systemd-devel-bounces@lists.freedesktop.org> on behalf of Lennart Poettering <lennart@poettering.net><br> <b>Sent:</b> Monday, October 8, 2018 1:38:37 PM<br> <b>To:</b> Jérémy Rosen<br> <b>Cc:</b> systemd-devel@lists.freedesktop.org<br> <b>Subject:</b> Re: [systemd-devel] Default on failure dependencies</font> <div> </div> </div> </div> <font size="2"><span style="font-size:11pt;"> <div class="PlainText">On Mo, 08.10.18 09:58, Jérémy Rosen (jeremy.rosen@smile.fr) wrote:<br> <br> > <br> > > This all makes me wonder whether a different approach to all of this<br> > > wouldn't be better: maybe we should just consider this a logging<br> > > problem: let's make sure we log a recognizable log message (i.e. a<br> > > structured journal message with a well-defined MESSAGE_ID=) whenever a<br> > > service fails. With that in place it should be relatively easy to<br> > > write a system service that can run during regular system uptime and<br> > > can look in the journal for all failures, including getting live<br> > > notifications when something happens. Moreover, this resolves the<br> > > problems during early and late boot: the "cursor" logic of the journal<br> > > allows such a service to know exactly which failures it already<br> > > processed and which ones are still left, and it can process all<br> > > failures that took place while it was not running.<br> > > <br> > > Does that make sense?<br> > <br> > Could this be generalized to "a structured message whenever a unit changes<br> > state" or would that be too verbose ?<br> <br> We have that already but only in debug logging mode (systemd-analyze<br> log-level debug). It's a bit too much noise to turn on by default otherwise...<br> <br> Lennart<br> <br> -- <br> Lennart Poettering, Red Hat<br> _______________________________________________<br> systemd-devel mailing list<br> systemd-devel@lists.freedesktop.org<br> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br> </div> </span></font> </body> </html>