Just upgraded from 10.10 to 11.04, looks fine, but I have one issue: postfix can no longer perform rDNS queries. Must be related to postfix chroot mode. Does anyone know how to fix this?

I'm using virtualbox to check Nasty Narwhal before upgrading, and noticed that apache's mod_rewrite is not enable by default. Use the command:

a2enmod rewrite

(a2enmod = apache2 enable module) followed by a restart to enable it.

James

There may be an answer here later as well:

http://groups.google.com/group/mailing. ... b79bc60c5/

James

The upgrade process ran smooth as silk, no problems encountered during the upgrade or in regression testing.

James

Are you saying you don't have the problem I described?
I found Ubuntu already has confirmed high priority bug for this:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/764096

I found it!

/etc/init.d/postfix:

replace these two lines:

rm -f lib/libnss_*so*
tar cf - /lib/libnss_*so* 2>/dev/null |tar xf -

with these two:

rm -f lib/x86_64-linux-gnu/libnss_*so*
tar cf - /lib/x86_64-linux-gnu/libnss_*so* 2>/dev/null |tar xf -

My fix is specific for x64 architecture, change it if you use x86.
It should be possible to create architecture independent fix, but I don't know how.

now thats nasty!

I am upgrading Ubuntu to 11.04 and during the dist-upgrade I get this.

Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up python2.7-minimal (2.7.1-5ubuntu2) ...
Linking and byte-compiling packages for runtime python2.7...
E: pycompile:240: Requested versions are not installed
dpkg: error processing python2.7-minimal (--configure):
 subprocess installed post-installation script returned error exit status 3
Errors were encountered while processing:
 python2.7-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Failed to process build dependencies

Google has yet to reveal an answer so I am stuck for now.

I think it's related to bug 689306.

Short answer: you have to update python2.6 before upgrade to python2.7.

Thanks for the effort, I found this page too and too cryptic for me. I am running Python 2.6.6

gary@leroy:~$ python
Python 2.6.6 (r266:84292, Sep 15 2010, 15:52:39)
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more information.

Which seems to be the newest of the 2.6 line. http://www.python.org/download/releases/

Everything is still running it seems so I will have to wait till it affects others. If I find a resolution I will post.

So I don't know why this works but here is how I got past my problem.

https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/689306

I'm glad you all had a great experience. Mine really sucked.

I had no problem last week upgrading 10.10 -> 11.04 on a backup VPS with another vendor, using their simple console.

On my Linode VPS, followint suggestions, I used LISH. I could enter D, Y, N, OK on prompts to consider new or old .conf files. However, on the grub-pc page, I could not enter any marks in the [ ] spaces, and I did no want to continue without installing grub's. After a few tries, LISH crahed and disconnected. I ssh'd in and had to do something like `dpkg -configure -a` which brought up the grub-pc again. I guess this is an ncurses screen, and I still could not get past this page?

Since it seemed my system was close to being hosed, I decided to simply use my Backups (which I have for extra fees) and restore my old 10.10 from this morning's backups. It took a few correspondences with Support to get the info that I had to basically Shutdown -> Delete my Ubuntu and Swap -> Backup -> Restore. This restore on my smallest Linode (16 GB I believe) is taking unbelievably long. At this rate, it will be some hours until I can try to log in and check it out.

I think in the future on Linode, it makes sense to temporarily buy a new Linode2, "Restore" a backup from my Linode1 -> Linode2, try to upgrade Linode2 and back that up -> Restore (as above) backup from Linode2 -> Linode1, then delete the Linode2 account. Is this what other people here do?

_________________
http://www.ingber.com

I just was referred to
http://library.linode.com/troubleshooti ... _upgrading
where I see that the method prompted in my 10.10 login, which I followed, `do-release-upgrade` has failed for others on Linode.

_________________
http://www.ingber.com

If you decide to go that route, the last steps are unnecessary, if the upgrade on your Linode2 works, you can just delete your Linode1.

if linode1 has been running, that could end up with lost stats, data, etc.