• 0_1496340156762_fog_error4.png

  • @illustry said in Ubuntu is FOG's enemy:

    In short … it updated itself along with its configuration.

    Another example of Canonical thinking they know better than the administrator. It has never been ok to overwrite configuration set by the administrator, nor will it ever be. Updating the schema of a configuration file while preserving the configuration is one thing, but overwriting custom configuration is unacceptable.

  • My first post here, but I thought it timely to add this. This unattended-upgrades, up until 4/29, been setup to check for security updates only. In short, on that day (or rather, at 1am my time), it updated itself along with its configuration. You can see this in the log sample below. This of course wreaked some havoc on my production systems when it updated all sorts of packages and nuked everything. Needless to say, this feature is now permanently DISABLED.

    2017-04-23 04:49:04,987 INFO Allowed origins are: [‘o=Ubuntu,a=xenial-security’]
    2017-04-27 15:46:07,068 INFO Allowed origins are: [‘o=Ubuntu,a=xenial-security’]
    2017-04-28 12:35:25,599 INFO Allowed origins are: [‘o=Ubuntu,a=xenial-security’]
    2017-04-28 12:35:29,950 INFO Packages that will be upgraded: unattended-upgrades
    2017-04-30 03:19:04,933 INFO Allowed origins are: [‘o=Ubuntu,a=xenial’, ‘o=Ubuntu,a=xenial-security’]
    2017-04-30 15:35:41,094 INFO Allowed origins are: [‘o=Ubuntu,a=xenial’, ‘o=Ubuntu,a=xenial-security’]

  • I concur with Tom’s post. I did write a huge thing I was going to post, but then realized it was like three pages long… so I deleted it. I’ll summarize that you’ll have less problems if you use RHEL, CentOS, or Debian for server OSs. Ubuntu is my favorite workstation OS, but I won’t use it for a server if I can at-all avoid it. And I do speak from some experience. Tom of course speaks from way, way more experience.

    @Canonical I wish you’d stop changing stuff so much so often, and stop assuming that you know better than the administrator. If we set a setting via SQL manually, post OS installation, and post-mysql installation, you have no right to change it with an update that you push out at whim. I’m sick and tired of the unity-webapps-common package, I think it’s source code should be deleted forever. And I think that automatic updates via unattended-upgrades is complete bogus. Often I’ve found that even though I select “Do not update automatically” during the OS installation, the unattended-upgrades package still applies updates. This is evidenced by the message “You need to restart your server” when I log in via SSH. Then you went off and fell in love with Microsoft, I don’t approve of this. I think you’re too young to be in a relationship with such an older company. Surely, the older company will take advantage of you and you’ll end up pregnant with a WinBuntu baby, or worse get some kind of virus that you’ll need to see Dr. Symantec for.

  • If, for some reason, you fail to follow the instructions.

    The mysql -u root and apt-get -y remove unattended-upgrades commands can be run prepended with sudo to elevate privileges.

    sudo mysql -u root
    sudo apt-get -y remove unattended-upgrades