Upgrade to trusty
Jump to navigation
Jump to search
- first did a gratuitous reboot to make sure filesystem checks wouldn't factor in
# do-release-upgrade Reading cache Checking package manager Continue running under SSH? This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover. If you continue, an additional ssh daemon will be started at port '1022'. Do you want to continue? Continue [yN] y Starting additional sshd To make recovery in case of failure easier, an additional sshd will be started on port '1022'. If anything goes wrong with the running ssh you can still connect to the additional one. If you run a firewall, you may need to temporarily open this port. As this is potentially dangerous it's not done automatically. You can open the port with e.g.: 'iptables -I INPUT -p tcp --dport 1022 -j ACCEPT' To continue please press [ENTER] <snip>lots of packages</snip> Calculating the changes Do you want to start the upgrade? 34 packages are going to be removed. 316 new packages are going to be installed. 2359 packages are going to be upgraded. You have to download a total of 1,753 M. This download will take about 31 minutes with your connection. Installing the upgrade can take several hours. Once the download has finished, the process cannot be canceled. Continue [yN] Details [d] samba diffs removes interfaces = eth1 bind interfaces only = yes avserver.conf diffs renamed from ffserver only comments warning on haproxy: stats ignored for frontend terraria because it requires http mode spamassassin diffs keep our config update process started puppet which applied a bunch of junk! hopefully my git repo will save me I should have done a commit in /etc before the upgrade.... phew, it looks like the puppet run was a noop sysctl.conf diffs keep our config cups diffs comments out SyncOnClose Yes keep our config because it has certs apache serve-cgi-bin.conf diffs take new version. lots of changes nfs-kernel-server diffs take the new version, nothing lost mediawiki/apache.conf diffs moves alias from /wiki to /mediawiki take new version A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.4 MB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ............................................................... *** As a part of the bug reporting process, you'll be asked as series of questions to help provide a more descriptive bug report. Please answer the following questions to the best of your abilities. Afterwards, a browser will be opened to finish filing this as a bug in the Launchpad bug tracking system. Upgrade complete The upgrade has completed but there were errors during the upgrade process. removed samba-common apt-get autoremove to get rid of 147 packages # upgrade complete at 11:03pm Sat # Xymon reports that mostly everything is working # but still can't get samba to work # reinstalled samba-common # but it failed. Preconfiguring packages ... Selecting previously unselected package samba-common. dpkg: warning: files list file for package 'squid-langpack' missing; assuming package has no files currently installed (Reading database ... 552720 files and directories currently installed.) Preparing to unpack .../samba-common_2%3a4.1.6+dfsg-1ubuntu2_all.deb ... Unpacking samba-common (2:4.1.6+dfsg-1ubuntu2) ... Selecting previously unselected package samba-common-bin. Preparing to unpack .../samba-common-bin_2%3a4.1.6+dfsg-1ubuntu2_amd64.deb ... Unpacking samba-common-bin (2:4.1.6+dfsg-1ubuntu2) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up samba-common (2:4.1.6+dfsg-1ubuntu2) ... rmdir: failed to remove ‘/etc/dhcp3/dhclient-enter-hooks.d’: No such file or directory No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package samba-common (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of samba-common-bin: samba-common-bin depends on samba-common (= 2:4.1.6+dfsg-1ubuntu2); however: Package samba-common is not configured yet. dpkg: error processing package samba-common-bin (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: samba-common samba-common-bin E: Sub-process /usr/bin/dpkg returned an error code (1) root@weasel:~# dpkg-reconfigure samba-common /usr/sbin/dpkg-reconfigure: samba-common is broken or not fully installed
Had to do a "apt-get purge samba-common" in order to move ahead.
brought my puppet recipes up to date with changes from upgrade[edit]
Now that I can do a "puppet agent -t --noop" and no changes show.
Next step is to get samba working again.
enable samba[edit]
root@weasel:/etc# apt-get install samba Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: samba-common samba-common-bin tdb-tools Suggested packages: bind9 bind9utils ldb-tools smbldap-tools winbind heimdal-clients The following NEW packages will be installed: samba samba-common samba-common-bin tdb-tools 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. ... root@weasel:/etc# service samba status * nmbd is running * smbd is running
That was easy.
Now reconcile the working samba with my puppet module. Just two files under puppet control:
- smb.conf
- smbpasswd
And puppet has nothing to say about smbpasswd, so just one file to fiddle with.
Folded in the worthy changes. Kept the necessary customizations.
Now samba is back:
root@hexli:~# smbclient -L weasel Enter root's password: Domain=[DAYNET] OS=[Unix] Server=[Samba 4.1.6-Ubuntu] Sharename Type Comment --------- ---- ------- IPC$ IPC IPC Service (weasel server (Samba, Ubuntu)) drobo2 Disk drobo Disk big Disk store Disk print$ Disk Printer Drivers hp_LaserJet_1160 Printer Automatically setup by HPLIP Domain=[DAYNET] OS=[Unix] Server=[Samba 4.1.6-Ubuntu] Server Comment --------- ------- Workgroup Master --------- ------- WORKGROUP WEASEL
Huh? How can weasel be the master of "workgroup"? Whatever. I'm calling this closed.