You are listing two versions here. Does it really affect both versions?
YES
> Severity: grave
Please use appropriate severity levels. `grave' is reserved for data
loss, security holes are issues that make the package entirely unusable
by anyone. Refer to https://www.debian.org/Bugs/Developer#severities for
a more detailed explanation.
YES i setup some services and when users are acting on those.. data will lose!
I appreciate your help with reporting a bug. The additional polemic is
not constructive though. Please stop that.
recently kamailio bugs was the same, a systemd service path was provide at upstream..
recently lithttpd have similar problem that uptream solved and was related to systemd
* Please specify versions of the following components:
* Debian release in use
jessie (and later i install strech to test)
* systemd
215-17+deb8up6 ?? the includes in jessie!
* lighttpd
1.4.35-4+deb8u1
* How reliable is the problem? Does it happen every time you restart
lighttpd?
nop! only after some time waqs passed
and specially if some changes are made to configuration
* In your log I marked the spot where lighttpd occurs in the process
list. Notably, it lacks the -D flag, but the .service file supplies
-D. Are you sure that this process is created by the .service file?
i use the command "service lighttpd restart" and seems in some cases
if there are a init script wil be converted on the fly to the "great" systemd format!
* Did you customize the configuration or the .service file? Can you be
specific about notable adjustments?
not! only added or change modules at the lighty.. main lighty config file are original!
* Can you try reproducing the failure in a reduced setting (e.g. set up
a VM with a bare minimal package set)?
that was a minimal install at VM
was hapened since jessie.. in wheeze does not happened..
as important point. i setup just for curiosity a Devuan VM and problems doe snot happenD!
same was for kamailio conunterparts of systemd related scripts!
Helmut