Difference between revisions of "Upgrade to Maverick"

From Finninday
Jump to: navigation, search
Line 5: Line 5:
 
* traceroute is no longer supported by Canonical?
 
* traceroute is no longer supported by Canonical?
  
I got errors during the upgrade about these items:
+
===I got errors during the upgrade about these items===
  
 
* squid (claimed that it didn't upgrade)
 
* squid (claimed that it didn't upgrade)
Line 14: Line 14:
 
But, YAY, media wiki didn't get messed up.
 
But, YAY, media wiki didn't get messed up.
  
 +
===php5 mhash.so===
 
* a vestigal php5 config file was left behind for mhash which caused this error to be emailed to root every 30 min:
 
* a vestigal php5 config file was left behind for mhash which caused this error to be emailed to root every 30 min:
 
<pre>
 
<pre>
Line 24: Line 25:
 
The fix was to remove the file /etc/php5/cli/conf.d/mhash.ini
 
The fix was to remove the file /etc/php5/cli/conf.d/mhash.ini
  
 +
===two canonical landscape banners===
 
* when I ssh into my machine, I now get two landscape banners, one for lucid and one for maverick:
 
* when I ssh into my machine, I now get two landscape banners, one for lucid and one for maverick:
 
<pre>
 
<pre>
Line 73: Line 75:
 
My fix was to remove the file /etc/motd.tail
 
My fix was to remove the file /etc/motd.tail
  
 +
===amavisd not running===
 
* hobbit says that amavisd is no longer running
 
* hobbit says that amavisd is no longer running
 
synaptic said that amavisd-new was installed, but amavisd-new-postfix was not
 
synaptic said that amavisd-new was installed, but amavisd-new-postfix was not
Line 88: Line 91:
  
 
I get the same error when manually trying to start amavis:
 
I get the same error when manually trying to start amavis:
 +
 
<pre>
 
<pre>
 
root@weasel:~# /etc/init.d/amavis start
 
root@weasel:~# /etc/init.d/amavis start
Line 102: Line 106:
  
 
Now hobbit reports all services are green.
 
Now hobbit reports all services are green.
 +
 +
Hmmm, the mail queue is not draining as fast as I would expect.  I'll have to follow the path through my configs again.  I wish I had written down how it all works a little bit better.
 +
 +
I removed the amavisd-new-postfix package and restarted, but still no joy.  New mail is piling up in the queue without being delivered.
 +
 +
===sshd refuses connection from localhost===
 +
This pisses off hobbit which tests sshd by trying to connect to localhost.  So now ssh is showing as yellow in my hobbit report.  I'll get to that later.

Revision as of 05:54, 20 October 2010

  • Started dist upgrade at 5:45pm

I didn't feel like burning a CD this time and I had performed a few successful upgrades relying on the servers. My work desktop managed an upgrade in about an hour and a half.

  • traceroute is no longer supported by Canonical?

I got errors during the upgrade about these items

  • squid (claimed that it didn't upgrade)
  • phpmyadmin
  • samba
  • something about the updater

But, YAY, media wiki didn't get messed up.

php5 mhash.so

  • a vestigal php5 config file was left behind for mhash which caused this error to be emailed to root every 30 min:
PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/lib/php5/20090626/mhash.so' - /usr/lib/php5/20090626/mhash.so: cannot open shared object file: No such file or directory in Unknown on line 0

The bug is documented here: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/541439/+activity

The fix was to remove the file /etc/php5/cli/conf.d/mhash.ini

two canonical landscape banners

  • when I ssh into my machine, I now get two landscape banners, one for lucid and one for maverick:
diana:~ rday$ ssh finninday.net
Linux weasel 2.6.35-22-generic #34-Ubuntu SMP Sun Oct 10 09:26:05 UTC 2010 x86_64 GNU/Linux
Ubuntu 10.10

Welcome to Ubuntu!
 * Documentation:  https://help.ubuntu.com/

  System information as of Tue Oct 19 10:11:06 PDT 2010

  System load:  0.15                Processes:           269
  Usage of /:   15.8% of 223.21GB   Users logged in:     1
  Memory usage: 24%                 IP address for eth0: xxx.xxx.xx.xx
  Swap usage:   0%                  IP address for eth1: 10.0.0.3
  Temperature:  22 C

  Graph this data and manage this system at https://landscape.canonical.com/

2 packages can be updated.
0 updates are security updates.

Ubuntu 10.04.1 LTS

Welcome to Ubuntu!
 * Documentation:  https://help.ubuntu.com/

  System information as of Mon Oct 18 13:54:58 PDT 2010

  System load:  0.06                Processes:           275
  Usage of /:   15.1% of 223.21GB   Users logged in:     1
  Memory usage: 24%                 IP address for eth1: 10.0.0.3
  Swap usage:   6%                  IP address for eth0: xxx.xx.xxx.xx
  Temperature:  22 C

  Graph this data and manage this system at https://landscape.canonical.com/

5 packages can be updated.
0 updates are security updates.

*** System restart required ***
Last login: Tue Oct 19 10:04:09 2010 from somewhere.somewhere.com

This bug is tracked here: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/659738

My fix was to remove the file /etc/motd.tail

amavisd not running

  • hobbit says that amavisd is no longer running

synaptic said that amavisd-new was installed, but amavisd-new-postfix was not so I installed amavisd-new-postfix and got this error:

Stopping amavisd: (not running).
Starting amavisd:   The value of variable $myhostname is "weasel", but should have been
  a fully qualified domain name; perhaps uname(3) did not provide such.
  You must explicitly assign a FQDN of this host to variable $myhostname
  in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's 
  network name!
(failed).
invoke-rc.d: initscript amavis, action "restart" failed.

I get the same error when manually trying to start amavis:

root@weasel:~# /etc/init.d/amavis start
Starting amavisd:   The value of variable $myhostname is "weasel", but should have been
  a fully qualified domain name; perhaps uname(3) did not provide such.
  You must explicitly assign a FQDN of this host to variable $myhostname
  in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's 
  network name!
(failed).

I love lucid and helpful error statements. I entered a FQDN in the config file and restarted amavis.

There were 29 messages in the queue when I got amavis restarted. Within a minute, the queue started to drain by itself.

Now hobbit reports all services are green.

Hmmm, the mail queue is not draining as fast as I would expect. I'll have to follow the path through my configs again. I wish I had written down how it all works a little bit better.

I removed the amavisd-new-postfix package and restarted, but still no joy. New mail is piling up in the queue without being delivered.

sshd refuses connection from localhost

This pisses off hobbit which tests sshd by trying to connect to localhost. So now ssh is showing as yellow in my hobbit report. I'll get to that later.