On Fri, Mar 14, 2014 at 8:09 PM, Laurent Bercot <[email protected]> wrote: > >> The pid remains the same, consistently. So, what can be the meaning of >> "0 seconds"? (The service is not working, no firewall logs received.) > > > Has the system clock been modified after the service has been launched ? > "0 seconds" is what s6-svstat displays when it sees that the service has > been launched in the future. > > If it's not the case, please send an strace of what's happening. > (If your run file is written in execline, adding "fdmove -c 2 1 strace -vf" > at the top of your script, and restarting the service, will print the strace > in your logs.) > Well, I already found the problem. My fault entirely. The time was being wrongly set on booting (1 day ahead), due to a silly, trivial to correct, bug in my program that sets the system time out of the hardware clock time (I don't use hwclock). A few moments later the time was corrected via sntpclock/clockadd, but the harm was already done.
Thanks, Jorge
