Troubleshooting

Keyboard number pad stopped working

The numeric keypad stopped working after upgrading from Ubuntu 8.04 to 10.04. To enable the numeric keypad goto System->Preferences->Keyboard and click on the Mouse Keys tab. Uncheck the Allow to control pointer using the keyboard and you should be back in business.

MySQL, PHP, Apache, and UTF-8 Issues

UTF-8 is hell. I have run into problems with UTF-8 before (see Migrating MySQL to UTF-8 encoding).

I moved a site that was displaying fine from an old Apache server to a new Apache2 server and quickly identified that the Apache2 server was displaying odd characters.

The site is running a PHP application with a MySQL backend. The MySQL database is using latin1_swedish_ci character encoding. The old site was displaying correctly. Both the new and old site are using the same database.

So what was going on?

'No space left on device' Issue With vserver

I was running into an issue with a vserver where the disk space usage was at 23% but I was getting a 'No space left on device' error message. I run vserver with 12 virtual servers and none of the other servers exhibited the same behavior.

module-alsa-sink.c: Error opening PCM device front:0: Device or resource busy

I ran into an problem with sound on a Dell Inspiron 518 workstation running Ubuntu 8.04. I had paused Amarok and then viewed a Flash video on youtube. When I went to play Amarok again Amarok stalled and hung there. I had to kill the amarok process to shut it down. The syslog gave up:

pulseaudio[29142]: module-alsa-sink.c: Error opening PCM device front:0: Device or resource busy

MySQL Error: Specified key was too long; max key length is 1000 bytes

When updating a MySQL database table to use UTF-8 I came across an error:

ERROR 1071 (42000) at line 1: Specified key was too long; max key length is 1000 bytes

Initial research indicates that the maximum key size in MySQL is 1000 bytes. Given that latin1 uses one (1) byte per character and UTF-8 uses three (3) bytes per character some indexes will exceed the 1000 byte limit. This accounts for the generated error when converting tables with large or compound indexes from latin1 to UTF8 encoding.

According to the MySQL bug tracker this issue has yet to be resolved. Currently the only solution is to limit indexing on UTF-8 encoded tables or use latin1 instead. Not the best of choices to say the least.

Syndicate content