FS#33368 - [tomcat7] 404's instead of serving webapp after package upgrade.

Attached to Project: Arch Linux
Opened by Leif Warner (pdxleif) - Saturday, 12 January 2013, 01:42 GMT
Last edited by Guillaume ALAUX (galaux) - Tuesday, 22 January 2013, 08:48 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Guillaume ALAUX (galaux)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Tomcat server 404's instead of serving my app, after upgrading the package.

Could add "systemctl restart tomcat7.service" to the post_upgrade hook in tomcat7.install.

True, it might be intrusive to have a package update do that, but my site doesn't work anyways after the tomcat update, so it wouldn't cause any extra disruption.

I ran pacman -Syu on that server, and didn't notice the site was 404'd until someone else told me.
This task depends upon

Closed by  Guillaume ALAUX (galaux)
Tuesday, 22 January 2013, 08:48 GMT
Reason for closing:  Won't implement
Comment by Jan de Groot (JGC) - Monday, 21 January 2013, 11:47 GMT
We don't touch running services, that's up to the user. Same applies to MySQL, Apache, etc. If you do a pacman -Syu without even looking at the output of it on servers, you should be asking yourself if you should be running (archlinux on) a server.
Comment by Guillaume ALAUX (galaux) - Tuesday, 22 January 2013, 08:47 GMT
+1 on what Jan says. I know Debian does start some daemons like tomcat for instance but it always shocks me when I witness it. The Arch way is NOT to (re)start daemons.

Loading...