dracoblue.net

Es gab mal einen

Blog-Eintrag auf dem Gmail-Blog, welcher erklärt hat, wie man seinen eigenen smtp server benutzen kann. Dadurch würde die "Im Auftrag von"-Information z.B. in Outlook nicht mehr angezeigt.

Das toole ist nun, dass das nicht nur klappt, wenn man einen eigenen smtp-server hat! Ich hab mal versucht smtp.gmail.com als eigenen Server einzufügen, und siehe da: "Im Auftrag von" ist verschwunden!

There was a blogpost on gmailblog a while back, which explained how to use a own smtp server to avoid the "on behalf of" message in clients like Outlook.

The cool thing, this does not only work, if you have a custom smtp-server! I tried to add smtp.gmail.com as custom server: the "on behalf of" was gone!

Today I am pleased to announce the new version 1.3.0 of the Agavi PHP DebugToolbar for download.

New features include full propel support (thanks tim), rows+time+memory display for the database queries and some small bugfixes.

The source can be found on github now http://github.com/DracoBlue/PhpDebugToolbar, feel free to fork it and send pull request with new features!

Download for PhpDebugToolbar 1.3.0 (just 23KB) is also available here at dracoblue.net.

Short installation and configuration information can be found in the readme. Thanks to all contributors!

When I upgraded my ubuntu server to a more recent mysql version, the mysql server didn't come up anymore.

The error.log said:

InnoDB: Log scan progressed past the checkpoint lsn 0 726937418
110103 23:55:57  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Error: tried to read 65536 bytes at offset 0 4220416.
InnoDB: Was only able to read 23040.
InnoDB: Fatal error: cannot read from file. OS error number 17.
110103 23:55:57  InnoDB: Assertion failure in thread 140594203866912 in file ../../../storage/innobase/os/os0file.c line 2291
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.

The deamon.log only stated:

Jan  3 23:55:57 myhostname init: mysql post-start process (28722) terminated with status 1

On the web I found the hint to add skip-innodb, which didn't help, because I needed innodb for this project.

The solution was (thanks

sr):

# mv /var/lib/mysql/ib* /root/

This moved the inno db index files and after that I restarted mysql and everything was fine again.

# restart mysql

My dedicated server still runs on ubuntu jaunty. I wanted to move on to php 5.3 (php 5.2.16 was the final release of the php 5.2 series). The issue is: php 5.3 is not available in jaunty repositories, because it will stay at 5.2.

Installing php 5.3 was simple, just add to:

$ vim /etc/apt/sources.list

the following:

deb http://php53.dotdeb.org stable all 
deb-src http://php53.dotdeb.org stable all

Install the dotdeb pgp key:

# curl http://www.dotdeb.org/dotdeb.gpg | apt-key add -

Update the apt cache and upgrade php5:

# apt-get update

# apt-get install php5

But when you want to install phpmyadmin again now, it fails.

php5-mcrypt: Depends: libltdl3 (>= 1.5.2-2) but it is not installable

Luckily you can get that (mcrypt) by adding the lenny updates repository manually:

# vim /etc/apt/sources.list

add:

http://security.debian.org/debian-security lenny/updates main

Install the debian gpg:

# gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 9AA38DCD55BE302B

Now update again:

# apt-get update

and install php5-mcrypt flawlessly:

# apt-get php5-mcrypt

I commented out the new sources.list entries after the install, because I don't need them to be checked on every update.