Following up on this to see if anyone has any idea why this is happening
Thanks
On Tue, Jun 14, 2022 at 2:09 PM Prashantkumar dhotre
wrote:
> Hi,
> In systemd 243.2+ version, intermittently sometimes I see that 'systemctl
> kexec' does not result in kexec reboot but results in reg
Hi,
In systemd 243.2+ version, intermittently sometimes I see that 'systemctl
kexec' does not result in kexec reboot but results in reguler cold boot
reboot
In console logs, I see below logs.
At line#209, I see "FAIL" string but not sure where it is coming from.
In which cases do 'systemctl
Hi,
I see issue with OnFailure cfg
have a simple service which ignores sigterm and has OnFailure and Restart
cfg in its service file
issue restart of that service.
expectation is that OnFailure units will not be triggered (as per doc as
service is gonna restart even if it times out sigterm) but in
whenever it triggers
OnFailure ?
Thanks
On Fri, Feb 18, 2022 at 8:55 PM Prashantkumar dhotre
wrote:
> Hi,
> In my app, I am monitoring a few services and would like to do some
> cleanup in my app, when these services fail in such a way that they
> don't restart back up without
Hi,
In my app, I am monitoring a few services and would like to do some cleanup
in my app, when these services fail in such a way that they don't restart
back up without admin action.
>From dbus-monitor , I see that 'Result' dbus PropertiesChanged signal
comes first and then 'ActiveState'
Hi,
It seems that systemd cancels pending stop job if a start job is being
attempted to be enqueued (seen when we enable debug level logs)
so app will not get stopped and started and systemd leave the app as
running instead of stopping and starting
but this seems to be unexpected from
Hi,
Is there a batching of service stops by systemd during shutdown.
In journal logs, I see a batch of 40 odd 'Stopping' messages and then the
next batch is seen after few seconds (4-6 seconds)
Is this by design ?
I am looking for a faster way to shutdown. Is there any config that can
speed up
Hi
How to know what triggered a service start ?
For eg, service X may Require service Y, so starting service-Y will start
service-X.
Can I get this info from 'systemd-analyze' ?
If yes, which argument to use for systemd-analyze?
I am interested to see what actually triggered and not just list
Hi,
Is there a way to specify conditional dependency in service files ?
My use case is : I have a include file my.include that contains
'After=core.service' among other things.
I have services A,B,C and X. As of now , all include my.include.
Now my requirement is - I want services A,B and C to be
Follow up
On Wed, Mar 6, 2019 at 12:59 PM prashantkumar dhotre <
prashantkumardho...@gmail.com> wrote:
> But the doc says
> https://www.freedesktop.org/software/systemd/man/systemd.unit.html
> " however, they apply to all kinds of starts (including manual), not ju
uno Vernay wrote:
> Hi,
> I would say that they limit restarts on errors (process crashes)
> Not an explicit command to stop and restart. There are no errors here.
>
> Bruno
>
> On Wed, Mar 6, 2019 at 8:02 AM prashantkumar dhotre <
> prashantkumardho...@gmail.com> wrote:
Hi,
I use v230 systemd.
I see that even after repeated stop and start of my service, i dont see it
going to going to failed state.
I have not configured any StartLimitBurst/StartLimitInterval , so default
values should take effect but I dont se ethat happening. service always
restarts.
Is this
Hi,
Is there any side-effect of the 'reset-failed' operation on a service that
is not in failed state.
My understanding is , in that case, it is no-op.
I have an app which uses dbus API for systemd to start/stop services.
Here I always the startApp() of my app should always result in starting of
Thanks.
It seems like that call to zookeeper lib API is causing this exit with 251
and hence it is most likely in zookeeper lib code.
Regards
On Mon, Mar 4, 2019 at 5:26 PM Lennart Poettering
wrote:
> On Mo, 04.03.19 16:58, prashantkumar dhotre (prashantkumardho...@gmail.com)
> wrote:
&g
:
> You need to do some bit analysis - https://shapeshed.com/unix-exit-codes/
>
> On Mon, Mar 4, 2019 at 12:29 PM prashantkumar dhotre
> wrote:
> >
> > Hi,
> >
> > In my journal log, I see ;
> >
> > 1199473 Mar 01 15:46:03 evo-qfx-01 systemd[1]: if
Hi,
In my journal log, I see ;
1199473 Mar 01 15:46:03 evo-qfx-01 systemd[1]: ifmand.service: Main process
exited, code=exited, status=251/n/a
I want to know what does 251 means.
Can you please let me know where can I see the exit-code to meaning mapping
?
Thanks
Prashant
Hi
Failed state DBUS notification for ActiveState property
is not received on sigkill of service, for the service that supports
restart ('Restart' value in service faile). But i see that unit goes to
failed state in journal logs
++
Sep 25 08:52:00 mynode systemd[1]: alarmd.service: Unit
Hi,
Is there is dbus API for systemd to restart unit by sending sigkill /sighup
?
https://www.freedesktop.org/wiki/Software/systemd/dbus/
RestartUnit(in s name, in s mode, out o job);
My requirement is to have a way to restart unit by sending sigkill or
sighup (user can specify ) also along with
Hi
Currently it appears that systemd does not provide a way to put max time
limit for system reboot.
So there is no way to get system reboot within specified time limit even if
hardware watchdog is present in system.
Using RunTimeWatchDogSec,ShutDownTimeWatchDogSec and
Hi systemd-experts
I am seeing few issues related to watchdog in systemd 230 version.
Could you please help me with few queries below ?
1) How do I test hardware watchdog config RunTimeWatchDiogSec and
ShutDownTimeWatchDogSec
2) If I enable RunTimeWatchDogSec, should I also run
After=systemd-reboot.service
AllowIsolate=yes
#JobTimeoutSec=30min
JobTimeoutSec=5sec
JobTimeoutAction=reboot-force
[Install]
Alias=ctrl-alt-del.target
On Mon, Mar 19, 2018 at 11:41 AM, prashantkumar dhotre <
prashantkumardho...@gmail.com> wrote:
> Hi
> I am observing that Shutdow
Hi
I am observing that ShutdownWatchdogSec setting in system.conf
In man page, for ShutdownWatchdogSec, I see :
" It works as a safety net to ensure that the reboot takes place even if a
clean reboot attempt times out. "
I am not clear what is meant by 'clean reboot' and 'times out ' here
Thanks
I understand that
'systemctl isolate other.target' will stop all present services and start
services of other.target
My thinking is :
I can put all my apps in my.target
and my.target can start after multi-user.target.
When shutting down , somewhere first i will do 'systemctl iso
shut down
> with SIGKILL, so you should avoid using '--force' unless you know that
> everything running on the system is safe to shutdown with SIGKILL.
>
> On Thu, Mar 15, 2018 at 8:43 PM prashantkumar dhotre <
> prashantkumardho...@gmail.com> wrote:
>
>> Hi
>&g
Hi
I see that default reboot/systemctl reboot command issues SIGTERM to my
apps and hence it is doing graceful stop of apps and this may take some
time and hence shutdown time may be little longer.
I am looking for safe and fastest shutdown/reboot method.
a) It is OK if my apps are stopped
Hi
When time changes in system , I see
"systemd[1]: Time has been changed" journal log. From systemd,
Is there a way for my app to get notification about this time change event ?
>From code it does not look like we have a way.
Thanks
___
systemd-devel
lėnas" <graw...@gmail.com> wrote:
> On Tue, Nov 28, 2017 at 11:14 AM, prashantkumar dhotre <
> prashantkumardho...@gmail.com> wrote:
>
>> Hi
>> Sometimes i see that service restart fails with
>> systemd[1]: *my.service failed to schedule restart job:
Hi
Sometimes i see that service restart fails with
systemd[1]: *my.service failed to schedule restart job: Transaction is
destructive.*
above error is very rare.
I have defined ExecStopPost script in my service file.
this problem does not always happen and there is no defined steps to
recreate
dbus API is failing even though the socket is present.
So am I missing to add any dependency in my service file ?
On Sat, Apr 29, 2017 at 10:36 PM, Lennart Poettering
<lenn...@poettering.net> wrote:
> On Wed, 26.04.17 10:09, prashantkumar dhotre (prashantkumardho...@gmail.com)
> wr
Hi
What happens when SIGHUP is sent by some service to systemd (PID 1 ) ?
I see below lines in journalctl logs
systemd[1]: Received SIGHUP from PID 27128 (myservice).
systemd[1]: Reloading.
systemd[1]: Configuration file /lib/systemd/system/xyz.service is
marked executable. Please remove
Hi
For my service, I have:
# cat my.service
[Unit]
Description=My Service
After=dbus.service
Requires=dbus.service
...
...
Some time i see that my service fails to get dbus connection
(dbus_bus_get_private() fails without any error msg).
one possibility i think is that dbus is not fully
31 matches
Mail list logo
