Bug#925478: restart action breaks with systemd (Again)
On Tue, Mar 26, 2019 at 06:25:07PM +0100, PICCORO McKAY Lenz wrote: > > 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! This is for typical installations. You can configure most software in a way that turns a normal bug into a data loss issue. Please apply common sense. > * Please specify versions of the following components: >* Debian release in use > > jessie (and later i install strech to test) I'm afraid that jessie is no longer supported. Even stretch won't be updated for such an issue. You're on your own here. Sorry. > * 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 You later indicated that you did not customize the 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! If there is a .service file, the init script won't be used. If you manage to use the init script anyway, this is not a bug in the lighttpd package. > * 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.. It's a bit surprising that nobody ever bothered to report a problem that you categorize as grave for years. In any case, working with such old releases will not move us forward. At this point, only buster and later releases are relevant. Please try reproducing the issue on a buster VM. If you do, please document your steps in detail. Otherwise I will be unable to help you. I still fail to reproduce the reported problem in any way. In principle, stretch could still be fixed via a stable update. If you want to go that route, please provide a patch. I also failed to reproduce the issue on stretch. The present data suggests that the issue only affects non-standard configurations of jessie and stretch. In that case, I won't be working on a solution. If you want to continue, I urge you to provide more details and avoid self-contradictory statements. I also issue a formal warning. Your polemic about init systems is not welcome here. Helmut
Bug#925478: restart action breaks with systemd (Again)
El mar., 26 de mar. de 2019 a la(s) 03:42, Helmut Grohne ( helmut.gro...@intenta.de) escribió: > 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 >
Bug#925478: restart action breaks with systemd (Again)
Control: severity -1 important Control: tags -1 + unreproducible moreinfo Thank you for the report. On Mon, Mar 25, 2019 at 12:18:02PM -0400, PICCORO McKAY Lenz wrote: > Package: lighttpd > Version: 1.4.35-4+deb8u1 > Version: 1.4.53-3 You are listing two versions here. Does it really affect both versions? > 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. > The systemd (again) seems have problems iwth lighttpd.. > when i try to restart the service aftyer some time.. service does not start > and a paralele service are in backgound.. > > that problem does not happen with wheeze , neither happen in Devuan > that used sysv-init > > until that days, systemd seems are mor a pain in the ass rather a solution! I appreciate your help with reporting a bug. The additional polemic is not constructive though. Please stop that. > root@ip-10-101-2-11:/etc/# service lighttpd status > ● lighttpd.service - Lighttpd Daemon >Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled) >Active: failed (Result: exit-code) since Mon 2019-03-25 16:08:05 UTC; 4s > ago > Process: 3019 ExecStart=/usr/sbin/lighttpd -D -f > /etc/lighttpd/lighttpd.conf (code=exited, status=255) > Process: 3011 ExecStartPre=/usr/sbin/lighttpd -t -f > /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS) > Main PID: 3019 (code=exited, status=255) > > Mar 25 16:08:05 ip-10-101-2-11 lighttpd[3011]: Syntax OK > Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon. > Mar 25 16:08:05 ip-10-101-2-11 lighttpd[3019]: 2019-03-25 16:08:05: > (network.c.409) can't bind to port: 80 Addre...n use > Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: lighttpd.service: main > process exited, code=exited, status=255/n/a > Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: Unit lighttpd.service > entered failed state. > Hint: Some lines were ellipsized, use -l to show in full. > root@ip-10-101-2-11:/etc/# ps -lxa | grep http > 0 0 3032 32390 20 0 12728 2188 - S+ pts/1 0:00 > grep --color=auto http > 133 20456 1 20 0 97324 2284 - S? 0:17 > /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf ^^^ (see below) > root@ip-10-101-2-11:/etc/# kill -9 20456 > root@ip-10-101-2-11:/etc/# service lighttpd start > root@ip-10-101-2-11:/etc/# service lighttpd status > ● lighttpd.service - Lighttpd Daemon >Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled) >Active: active (running) since Mon 2019-03-25 16:08:52 UTC; 11s ago > Process: 3050 ExecStartPre=/usr/sbin/lighttpd -t -f > /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS) > Main PID: 3058 (lighttpd) >CGroup: /system.slice/lighttpd.service >└─3058 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf > > Mar 25 16:08:52 ip-10-101-2-11 lighttpd[3050]: Syntax OK > Mar 25 16:08:52 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon. > Mar 25 16:08:58 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon. > root@ip-10-101-2-11:/etc/# I attempted reproducing this bug on a Debian buster system. After restarting lighttpd twenty times, I was not able to reproduce it in a single occasion. This does not imply absence of the bug, just that we need more information. Please answer the following questions and remove the moreinfo tag when doing so: * Please specify versions of the following components: * Debian release in use * systemd * lighttpd * How reliable is the problem? Does it happen every time you restart lighttpd? * 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? * Did you customize the configuration or the .service file? Can you be specific about notable adjustments? * Can you try reproducing the failure in a reduced setting (e.g. set up a VM with a bare minimal package set)? Helmut
Bug#925478: restart action breaks with systemd (Again)
Package: lighttpd Version: 1.4.35-4+deb8u1 Version: 1.4.53-3 Severity: grave The systemd (again) seems have problems iwth lighttpd.. when i try to restart the service aftyer some time.. service does not start and a paralele service are in backgound.. that problem does not happen with wheeze , neither happen in Devuan that used sysv-init until that days, systemd seems are mor a pain in the ass rather a solution! root@ip-10-101-2-11:/etc/# service lighttpd status ● lighttpd.service - Lighttpd Daemon Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled) Active: failed (Result: exit-code) since Mon 2019-03-25 16:08:05 UTC; 4s ago Process: 3019 ExecStart=/usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf (code=exited, status=255) Process: 3011 ExecStartPre=/usr/sbin/lighttpd -t -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS) Main PID: 3019 (code=exited, status=255) Mar 25 16:08:05 ip-10-101-2-11 lighttpd[3011]: Syntax OK Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon. Mar 25 16:08:05 ip-10-101-2-11 lighttpd[3019]: 2019-03-25 16:08:05: (network.c.409) can't bind to port: 80 Addre...n use Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: lighttpd.service: main process exited, code=exited, status=255/n/a Mar 25 16:08:05 ip-10-101-2-11 systemd[1]: Unit lighttpd.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. root@ip-10-101-2-11:/etc/# ps -lxa | grep http 0 0 3032 32390 20 0 12728 2188 - S+ pts/1 0:00 grep --color=auto http 133 20456 1 20 0 97324 2284 - S? 0:17 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf root@ip-10-101-2-11:/etc/# kill -9 20456 root@ip-10-101-2-11:/etc/# service lighttpd start root@ip-10-101-2-11:/etc/# service lighttpd status ● lighttpd.service - Lighttpd Daemon Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled) Active: active (running) since Mon 2019-03-25 16:08:52 UTC; 11s ago Process: 3050 ExecStartPre=/usr/sbin/lighttpd -t -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS) Main PID: 3058 (lighttpd) CGroup: /system.slice/lighttpd.service └─3058 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf Mar 25 16:08:52 ip-10-101-2-11 lighttpd[3050]: Syntax OK Mar 25 16:08:52 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon. Mar 25 16:08:58 ip-10-101-2-11 systemd[1]: Started Lighttpd Daemon. root@ip-10-101-2-11:/etc/# Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
