MTU ISO - Troubleshooting

  • If you are using the GNU compiler (gcc) you should be at version 3.3.2 or greater.

  • Are you using Solaris and GCC? You're probably getting weird errors when you try and 'make'. That's because the configure script, currently, doesn't check for the compiler type. On Solaris it assumes Sun's C compiler. All you should have to do is edit the Makefile and change all the "-R" flags to "-Wl,-rpath," flags and change "-KPIC" to "-fpic".

  • One of the best ways to troubleshoot the Apache module is to watch the web server's error_log. If you really want to see everything that the module is doing edit your httpd.conf file and change "LogLevel" to "debug". Then restart the web server.

  • It is important that the time on your web server closely matches that of

  • Cookies are hostname based. As a result you can not test an application running on an unresolvable host. The web server must be running on a machine whose name ends in "".

  • One of the most common problems comes from OpenSSL errors. Please check here to translate any OpenSSL error codes you may be seeing. These codes are returned by the authentication routines. NOTE: if you constantly get error codes about expiration or not yet valid then you should make sure the time on your machine is correct. MTU does maintain an NTP and RDATE server for use at To help debug issues with time in regard to OpenSSL please check out this list of useful OpenSSL commands.

  • Having trouble with getting the module to link correctly? Wondering where the went? Me too! I believe this is a bug in the libtool distributed with Apache 2.0.53 and 2.0.54. They seem to agree. Check out:

    The module still builds. It can be found in the .libs subdirectory of the source tree. However, if you perform an ldd .libs/ you will probably notice the following at the top: " => (file not found)". One solution is to set your LD_LIBRARY_PATH environment variable so Apache can find when it starts. Another solution is a tad more complicated, but keeps you from having to set your LD_LIBRARY_PATH for Apache. Instructions/Clues on the complicated solution are below.

    1. Build the module as normal.

    2. Find the last line from the 'make' command. It should look something like this:

      <apache_install_dir>/build/libtool --silent --mode=link /usr/local/bin/gcc -o -rpath,/dcs/local/mtuiso/mtuiso-1.6.0/lib -rpath,/dcs/local/web/ -L/dcs/local/mtuiso/mtuiso-1.6.0/lib -L/dcs/local/web/ -lmtuiso -lapr-0 -laprutil-0 -rpath /dcs/local/web/ -module -avoid-version mod_authnz_mtuiso.lo

    3. Copy this, but remove the --silent part.

    4. Run the command without the --silent part.

    5. The last line from this command should look like this:

      Solaris Example
      <compiler_command> -shared -Wl,-h -Wl, -o .libs/ .libs/mod_authnz_mtuiso.o -R/dcs/local/web/ -R/dcs/local/web/ -L/dcs/local/mtuiso/mtuiso-1.6.0/lib -L/dcs/local/web/ -lmtuiso /dcs/local/web/ /dcs/local/web/ -lc

      Linux Example
      <compiler_command> -shared .libs/mod_authnz_mtuiso.o -Wl,--rpath -Wl,/services/linux/web/ -Wl,--rpath -Wl,/services/linux/web/ -L/services/linux/web/ -L/services/linux/web/ -L/services/linux/web/ -L/services/linux/web/ -L/services/linux/web/ -lmtuiso /services/linux/web/ /services/linux/web/ -Wl,-soname -Wl, -o .libs/

    6. Solaris
      If you notice, there is no -R<path to libmtuiso>. Add a -R<path to libmtuiso> if you don't have one. If you do just keep reading.

      Remove the "-Wl,--rpath" flags. Change the "-Wl,<path>" flags to "-Wl,-rpath,<path>". Again, if you don't have a "-Wl,-rpath,<path to libmtuiso>" add one.

    7. Run the edited command.

    8. Now when you ldd .libs/ the module should know where is.