[SERVER-1743] Problems with apt-get dist-upgrade Created: 06/Sep/10 Updated: 19/May/14 Resolved: 13/Dec/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Fabrizio Regini | Assignee: | Richard Kreuter (Inactive) |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux ubuntu 10.04 |
||
| Participants: |
| Description |
|
While updating a system with apt-get dist-upgrade, the upgrade causes the server to stop current connections. Webapps connected to the server stop to respond, and a manual stop and start is needed to restore the server. Webapps connected to the server need to be restarted as well. Is this an expected behaviour? Isn't it possibile to close connections and restart the server after the upgrade in an automated way? |
| Comments |
| Comment by Richard Kreuter (Inactive) [ 13/Dec/10 ] |
|
By inspection, most services (e.g., mysql and others) restart at upgrade time too, and it's really messy to do otherwise. So I'd suggest looking into apt pinning or dpkg holds to prevent package upgrades. |
| Comment by Richard Kreuter (Inactive) [ 13/Dec/10 ] |
|
My mistake. The service restart can be controlled by packaging scripts, but it's nasty. Sorting this out now. |
| Comment by Richard Kreuter (Inactive) [ 13/Dec/10 ] |
|
This is halfway between a won't fix and works as designed. |
| Comment by Richard Kreuter (Inactive) [ 13/Dec/10 ] |
|
This turns out to be a property of how Debian/Ubuntu's packaging system works. When you upgrade any package providing a service, it restarts the service. If you want to prevent that, you could use apt's "pinning" or dpkg's "hold" status to prevent the mongodb packages from upgrading as part of an apt-get upgrade. |