to be continued…

Fuehrt man ein OS Upgrade auf dem Ipod Touch oder was auch immer durch, muss man in Virtualbox mehrmals das den Ipod wieder mit dem Gastsystem verbinden, will sagen ‘reconnecten’ in dem man den Haken vor dem Geraet anklickt. Ansonsten bricht itunes die Installation ab und der Ipod ist unbrauchbar.

There error drraw prints out is “You must specify at least one RRA to add!”

drraw.cgi 2.1.3 <1.185.2.18>

Perl 5.008008

CGI.pm 3.15

RRDs.pm 1.2019

Here is the diff for drraw.cgi

1c1
< #! /usr/bin/perl -T
—
> #! /usr/local/bin/perl -T
2607c2607
<           = RRDs::fetch($file, $cf, 0, 0);
—
>                 = RRDs::fetch($file, $cf, ‘-s’, 0, ‘-e’, 0);

cryptdisk

Ubuntu 7.10 didn’t ask for my passphrase to decrypt my partitions after upgrade. After startup was able to run /etc/init./cryptdisks again and entering my passphrase. I found a workaround here

slimserver

I’m a proud owner of a Rokulabs Soundbridge M1001 which works very well in my environment. After upgrading my music server wasn’t recognized by the M1001 anymore.
After hours of reinstalling music server, resetting the Soundbridge I remembered John’s posting about network issues in Ubuntu 7.10 Obviously the problem is not only limited to DNS queries and not every piece of software is compatible with IP v6.

So i disabled IP v6 support in Ubuntu and voila I got my music archive back:

#alias net-pf-10 ipv6
alias net-pf-10 off

1. Man liest sich aufmerksam das entsprechende Kapitel im Debian Policy Handbuch durch.
2. Man schaut sich die Vorlage in/etc/init.d/skeleton an
3. Man schaut sich andere Start/Stop-Skripte an und stellt fest das die “echten” Entwickler die Vorgaben aus dem Policy Handbuch nicht immer beachten.
4. Dann passt man das skeleton-Skript an seine eigenen Vorgaben an und versucht sich an das Policy-Handbuch zu halten.
5. Test des Skripts auf Debian-basierten Systemen.
6. Veröffentlichen der Skripte und auf Fehlerberichte warten

Damit es bei mir unter Ubuntu 7.04 funktioniert, musste ich noch folgende Pakete installieren:
sudo apt-get install libqt4-core libqt4-gui

Leider vergesse ich immer bei einem Kernel-Update auch das Paket linux-restricted-modules zu installieren, das unter anderem den propietären NVIDIA-Treiber enthält. Schade das es keine Abhängigkeiten zwischen den Kernel-Paketen und dem Modul-Paktet gibt, so das die Aktualisierung automatisch erfolgen würde.
Bei mir hilft:
apt-get install linux-restricted-modules-2.6.20-16-generic

Setting up Tomcat Monitoring in Hyperic is easy by reading the documentation.
If you’re going to do that in Debian-based Distributions it’s a little bit different to the original documentation. I set up tomcat monitoring on Nexenta GNU/OpenSolaris and Ubunbtu 6.06 LTS Here it ist:

At first download an install an Hyperic Agent on your Tomcat-Machine. For Ubuntu use hyperic-hq-agent-n.n.n-nnn-x86-linux.tgz oder for 64-Bit AMD Systems hyperic-hq-agent-n.n.n-nnn-amd64-linux.tgz.
My Nexenta installation is in Virtual Machine on a x86-System, so I got hyperic-hq-agent-3.0.4-389-noJRE.tgz and installed a Java Runtime Environement for myself.

To enable monitoring of Tomcat servers and services the Tomcat server must be instrumented using a filter to collect metrics and a webapp to deliver the metric data into HQ. The web application, filter and any additional jars are packaged in the HQ agent directory under product_connectors/servlet-3.0.4 for HQ Agent 3.0.4. All commands below should be issued from this directory.

If you are using Apache/JK to front your Tomcat installation you will need to setup a mount point. This can be done by adding the following to your Apache configuration /etc/apache2/conf.d/jk file.
You can find an example in /usr/share/doc/libapache2-mod-jk/httpd_example_apache2.conf

JkMount /hyperic-hq/* ajp13_worker

Keep in mind that depending on how you configured your Apache the whole world can access the hyperic webapp ! I would advise you to use secure it by set up up the following Apache directive:
<Location>
Order Deny,Allow
Deny from all
Allow from localhost
#or
Allow from iphyperichq
</Location>

The first step to making Tomcat monitorable is to install the filter, JMX jars and webapp. These are used to collect internal Tomcat metrics.

cp libs/hq-filter.jar /usr/lib/tomcat5/common/lib
cp libs/mx4j-jmx.jar /usr/lib/tomcat5/common/lib
cp -R hyperic-hq /usr/lib/tomcat5/webapps

In fact you can copy your files also to /usr/share/tomcat5/ which is a symbolic link to /usr/lib/tomcat5/.

Finally, the filter must be enabled. The following must be added to /etc/tomcat5/web.xml. Keep in mind that each tag type must be grouped together.

<filter>
<filter-name>JMXFilter</filter-name>
<filter-class>org.hyperic.hq.product.servlet.filter.JMXFilter</filter-class>

<!– Uncomment the following line to enable response time logging.
The directory you specify as the param can include properties
referenced from the System.properties of the vm.

The ResponseTime log file will by default store the last 1 hour’s
worth of response time data. This file gets truncated as soon as
data is succesfully sent into the server. The file is named uniquely
for each webapp in the form: yourContextName_HQResponseTime.log

If this fragment is included in the global web.xml for the container,
all webapps in it will generate response time data, and have logs
following the format described above. You can enable it individually
on each webapp as well if you dont want every webapp to generate
response time data

–>
<!–
<init-param>
<param-name>responseTimeLogDir</param-name>
<param-value>/var/lib/tomcat5/logs</param-value>
</init-param>
–>

<!– these are optional parameters which you can override to optimize logging –>
<!–
<init-param>
<param-name>bufferSize</param-name>
<param-value>8k</param-value>
</init-param>

<init-param>
<param-name>bufferTime</param-name>
<param-value>1h</param-value>
</init-param>
–>
</filter>

<filter-mapping>
<filter-name>JMXFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>

<listener>
<listener-class>org.hyperic.hq.product.servlet.filter.JMXSessionListener</listener-class>
</listener>

<servlet>
<servlet-name>JMXWebappMetricServlet</servlet-name>
<servlet-class>org.hyperic.hq.product.servlet.filter.JMXFilterInitServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>

This can be tested by verifying your webapps show up correctly in the JMX Servlet. You may need to modify the hostname in the URL if your jmxUrl is configured relative to the agent host or if you use Apache in front of your Tomcat-Installation as described above.

Configure Tomcat 5.0 for Log Tracking

To enable Log Tracking in HQ, Tomcat must be configured with log4j. These steps are based on the standard Tomcat documentation.

On a blank Ubuntu-Installation /usr/lib/tomcat5/common/classes/log4j.properties does not exist, so create one with the following example contents:

#These properties can be modified. The only requirement is that the
#ConversionPattern includes the priority (%p)
log4j.rootLogger=INFO, R
log4j.appender.R.File=${catalina.home}/logs/tomcat.log
log4j.appender.R.MaxBackupIndex=1
log4j.appender.R.MaxFileSize=5000KB
log4j.appender.R.layout.ConversionPattern=%d %-5p [%c{1}] %m%n
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R=org.apache.log4j.RollingFileAppender

Next, copy the following jars unless they have already been installed:

cp pdk/lib/log4j.jar /usr/lib/tomcat5/common/lib
cp pdk/lib/commons-logging.jar /usr/lib/tomcat5/common/lib

Restart Tomcat for the changes to take effect: /etc/init.d/tomcat5 restart

Eine Diskussion zu dem Thema findet sich in den Ubuntu Forums.

UPDATE: Der entsprechende Bugeintrag bei launchpad