Justin: Check your mysql logs as to why.
To reiterate, the bug is that the upgrade scripts depend on the
successful starting of MySQL. They absolutely should not (there are
plenty of reasons why an installation may not start).
--
Infinite loop upgrading to 5.1.41-3ubuntu12.6
https://bugs.launchp
Was there a prompt: No.
How long did I wait? At least five minutes to the best of my memory.
daemon.log from the earliest log entry for today:
Aug 10 14:14:11 sutton mysqld[3694]:
Aug 10 14:14:11 sutton mysqld[3694]: PLEASE REMEMBER TO SET A PASSWORD FOR THE
MySQL root US
ER !
Aug 10 14:14:11 s
Public bug reported:
If MySQL is not startable, the package cannot continue. History...
Performed a dist-upgrade on a Lucid box installed a few weeks ago.
The dist-upgrade became stuck:
Setting up libmysqlclient16 (5.1.41-3ubuntu12.6) ...
Setting up mysql-client-core-5.1 (5.1.41-3ubuntu12.6) ..
I've now tried with http://kernel.ubuntu.com/~kernel-
ppa/mainline/daily/current/linux-
image-2.6.35-999-generic_2.6.35-999.201007021009_i386.deb which
continues to suffer.
I've also used Wireshark to examine my XP machine's packets, and I
repeatedly see lots of QUERY_PATH_INFO examining the vario
I've switched my VM to run Linux ubuntu 2.6.32-23-generic #37-Ubuntu SMP
Fri Jun 11 07:54:58 UTC 2010 i686 GNU/Linux and re-ran the phpunit test.
It's still slow as a dog (2m30 to do 240 tests is insane).
syslog during the run:
Jul 2 12:41:46 ubuntu kernel: [ 100.435401] CIFS VFS: No response f
Using a remote 9.10 box I mounted the same Windows ControlPanel share
and ran phpunit on it. The speed was back to how my VM used to be prior
to it's kernel upgrade yesterday morning.
Feels like a regression that's hit my configuration spectacularly badly.
--
cifs hangs with "Server not respondi
I've just tried switching back to smbfs in fstab (no change). Then back
again to cifs. Then added noserverinfo (no change) then added nounix (no
change).
** Package changed: ubuntu => samba (Ubuntu)
--
cifs hangs with "Server not responding"
https://bugs.launchpad.net/bugs/600565
You received t
Does this mean other mount.X utils will be similarly affected?
Does the fstab man page now need to be updated to say that the 'user'
flag does not apply to cifs and possibly others?
--
mount.cifs won't mount shares; set uid bit not set
https://bugs.launchpad.net/bugs/563805
You received this bug
