[Bug 109559] Re: Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts
** Changed in: lighttpd (Ubuntu) Status: New = Triaged ** Summary changed: - Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts + Please don't change permissions of /var/log/lighttpd during upgrade -- Please don't change permissions of /var/log/lighttpd during upgrade https://bugs.launchpad.net/bugs/109559 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109559] Re: Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts
Reopened, sorry.Resolution not seems to be acceptable for me, that's why... 1) I see no any valid reasons why updater should want to touch my (pre- existing and non-empty) logs directory (/var/logs/lighttpd) on working server.It already exists.It works.Logs are not part of package but a runtime-generated data and if server works, things are definitely tuned to do work right.Why the hell should updater then mess things up?I can understand if I'm installing package from scratch and there is no directory - ok to create new one with defaults.But changing parameters of pre-existing directories during update without a strong reason is a very bad idea, IMHO. 2) Touching logs directory of working server when it's not empty (during update) in best case will do exactly nothing.In not so lucky case it will sabotage lighttpd server's operation or do whatever else system administrator hardly will like.So, what is gained here, then? I'm thinking this operation on update is utterly stupid. 3) Non-default user may be convenient in some cases.Like it was in my one. 4) As a system administrator I want to trust to Ubuntu's installer and updater, up to level when scheduled updates are applied automatically in some cases when I can't manage things manually immediately.Right now this may lead to very poor experience.Updater is definitely not expected to apply destructive (but useless) changes to my system. P.S. actually, such behavior caused some real server outage (not critical one, luckily).While I can read any documentation, this will not change the fact that installer does meaningless but destructive action which sabotages server's normal operation.Do you really expect I will use such system with so competent repositories maintenance on some critical servers, then?Will try to reopen bug since it's pretty annoying. ** Changed in: lighttpd (Ubuntu) Status: Invalid = New -- Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts https://bugs.launchpad.net/bugs/109559 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109559] Re: Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts
Note: this annoying and unfair issue happens each time lighttpd is updated.Not just during OS updates but also during regular package updates during use of Kubuntu 7.04 and 7.10. -- Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts https://bugs.launchpad.net/bugs/109559 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109559] Re: Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts
I set this to invalid...because: user www-data, group www-data is the default user/group for webservers in debian/ubuntu. Changing this is an individual task and the server administrator should know about this issue and handle updates/upgrades more carefully. Regards, \sh ** Changed in: lighttpd (Ubuntu) Status: Confirmed = Invalid -- Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts https://bugs.launchpad.net/bugs/109559 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109559] Re: Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts
** Changed in: lighttpd (Ubuntu) Importance: Undecided = Wishlist Status: Unconfirmed = Confirmed -- Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts https://bugs.launchpad.net/bugs/109559 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109559] Re: Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts
Thanks for this additional information. I reassign to libhttpd as this package is responsible for any changes in /var/log/lighttpd ** Changed in: lighttpd (Ubuntu) Sourcepackagename: update-manager = lighttpd -- Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts https://bugs.launchpad.net/bugs/109559 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109559] Re: Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts
There is no apache at all.But I tracked problem down and fixed it.Here it comes. I did run lighttpd under custom non-default user I'd created myself.All worked fine, startup script launches lighttpd as root but I pointed out to server to change to restricted user upon startup (in it's config file I used server.username and server.groupname to switch to restricted user). During upgrade, owner and group of (existing and not empty!) lighttpd logs folder (/var/log/lighttpd) were changed for unknown reason to another user (intended to run www server but hey, I already had another user for this purpose!).Once server worked as restricted user and logs folder has been assigned to another owner\group, server was unable to write log file due to lack of permissions and exited due to this fact. So, I have to ask: why updater has to alter owner and group of already existing and non-empty folder during system upgrade?Imho it should be left as is (or at least, you have to change owner after confirmation since this potentially may affect server's operations). Anyway, not a serious issue - those who run servers have to be smart a bit or better do not run servers othervice. -- Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts https://bugs.launchpad.net/bugs/109559 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109559] Re: Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts
I think you need to remove apache2... ** Changed in: update-manager (Ubuntu) Sourcepackagename: None = update-manager -- Upgrade of Kubuntu 6.10 to 7.04 (x64) has caused that lighttpd to no longer starts https://bugs.launchpad.net/bugs/109559 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
