Re: [otrs] Problem upgrading to 3.2.8 on Windows (cause?: old HTTPD binaries in latest installer?)

I'll set it up and give feedback in about 6 - 10 hours. Thanks! My trouble is... I think I just missed a maintenance window for this weekend to perform the upgrade to 3.2.8 because this situation looks like a stability problem with my configuration that I simply haven't planned to protect against. To tell the truth, I feel lucky it happened within the first few clicks because if it would've appeared on QA after a couple hours of light testing then I would've seen it in production within about 30 minutes to an hour and I would've had no way to rollback to 3.1.10. That would've been a nightmare. If I see that 3.2.8 doesn't crash immediately anymore, is there anything you can think of that I can try to further ensure the stability of the configuration deployed by this latest installer? On Wed, Jun 19, 2013 at 10:07 PM, Michiel Beijen wrote:

Hi Bogdan,

We switched to a newer version of mod_perl which was compiled by someone from apache; aparently with iconv and libapr versions that are causing all sorts of trouble. Very annoying.

I created a 3.2.8 version based on the 'old' apache, mod_perl and strawberry, please let me know if it helps!

http://users.otrs.com/~mb/otrs-3.2.8-win-installer-2.4.9.exe --

On Wed, Jun 19, 2013 at 3:37 PM, Bogdan Iosif wrote:

...

Hi list,

I'm trying to upgrade to 3.2.8, from 3.1.10, on Win 2008 R2 with SP1 and I'm running into an ugly problem that I think is related to the Apache config deployed by OTRS's Windows installer 2.4.8. I used this 3.2.8 package because I made the common sense assumption that its installer is more stable than the latest beta for OTRS's Windows installer 3.0.0.

First, I performed a clean install (in a VM where Windows itself was freshly installed) using otrs-3.2.8-win-installer-2.4.8.exe. When it came time to run the web installer I instead switched to following instructions for the upgrade from here: https://github.com/OTRS/otrs/blob/rel-3_2_8/UPGRADING.md

=Symptoms=

Everything went OK with the upgrade up to, and through, step "12. Restart your services".

When I reached step 13 and needed to start using OTRS's admin interface, I discovered the application is unusable because Apache's process crashes very suddenly after a few HTTP requests and OTRS is effectively shutdown afterwards. If I attempt to manually restart the Apache service then it crashes again very soon, following the same pattern. The Event Log contains some cryptic messages like:

==System Log==

The Apache2.2 service terminated unexpectedly.

==Application Log==

Faulting application name: httpd.exe, version: 2.2.22.0, time stamp: 0x4f242d7a Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x753a34c1 Faulting process id: 0x458 Faulting application start time: 0x01ce6cdea9707025 Faulting application path: C:\Program Files (x86)\OTRS\Apache\bin\httpd.exe Faulting module path: unknown Report Id: 3c668618-d8d2-11e2-b6da-000c29f4581a

Faulting application name: httpd.exe, version: 2.2.22.0, time stamp: 0x4f242d7a Faulting module name: IPHLPAPI.DLL_unloaded, version: 0.0.0.0, time stamp: 0x4ce7b859 Exception code: 0xc0000005 Fault offset: 0x753a34c1 Faulting process id: 0x6bc Faulting application start time: 0x01ce6cdeb6fa43b4 Faulting application path: C:\Program Files (x86)\OTRS\Apache\bin\httpd.exe Faulting module path: IPHLPAPI.DLL Report Id: 3bfdbf74-d8d2-11e2-b6da-000c29f4581a

=My Investigation=

The following recent post (in German) describes almost the same exact problem that I have: http://stefan.pachlina.net/index.php?option=com_content&view=article&id=317:...

Reading through Google Translate, I saw the author pinpointing the root cause to a faulty version of \OTRS\apache\bin\libapr-1.dll. He said the bad version is 1.4.5.0 and recommends instead either 1.3.6.0 or 1.4.6.0. Note that I currently have 1.4.5.0 in production and haven't ran into any problems. Also, I have no idea how the post author identified that DLL to be the problem.

The output from "httpd -v" is identical between my prod (3.1.10) and test (3.2.8) envs but after doing a folder comparison I see a lot of differences in files from apache\bin. First, there are a lot of *.DLL and *.SO files that are different and the versions deployed with 3.2.8 seem a lot older (from 2009) than those deployed with 3.1.10 (from 2012). Here is a report (copy/paste in notepad to see it clearly):

Name Version Size Modified Name Version Size Modified

------------------------------------------------------------------------------------------------------------------------------- bin 9`108`428 19-Jun-2013 15:52:38 bin 28`155`388 19-Jun-2013 15:50:52 +libaprutil-1.dll 1.4.1.0 192`604 28-Jan-2012 12:15:46 >> +libaprutil-1.dll 1.3.8.0 188`496 06-Jul-2009 23:21:36 +libapr-1.dll 1.4.5.0 139`347 28-Jan-2012 12:11:16 >> +libapr-1.dll 1.3.6.0 135`239 06-Jul-2009 23:21:20 +libapriconv-1.dll 1.2.1.0 36`958 28-Jan-2012 12:11:24 >> +libapriconv-1.dll 1.2.1.0 36`946 06-Jul-2009 23:21:24 +apr_dbd_oracle-1.dll 1.4.1.0 32`868 28-Jan-2012 12:15:54 >> +apr_dbd_oracle-1.dll 1.3.8.0 32`856 06-Jul-2009 23:21:38 +apr_dbd_sqlite3-1.dll 1.4.1.0 28`773 28-Jan-2012 12:15:52 >> +apr_dbd_sqlite3-1.dll 1.3.8.0 28`761 06-Jul-2009 23:21:38 +apr_dbd_pgsql-1.dll 1.4.1.0 28`771 28-Jan-2012 12:15:56 >> +apr_dbd_pgsql-1.dll 1.3.8.0 28`759 06-Jul-2009 23:21:38 +apr_dbd_mysql-1.dll 1.4.1.0 28`771 28-Jan-2012 12:15:58 >> +apr_dbd_mysql-1.dll 1.3.8.0 28`759 06-Jul-2009 23:21:38 +apr_dbd_odbc-1.dll 28`770 28-Jan-2012 12:15:50 >> +apr_dbd_odbc-1.dll 28`758 06-Jul-2009 23:21:38 \apr_ldap-1.dll 1.4.1.0 24`671 28-Jan-2012 12:15:50 >> \apr_ldap-1.dll 1.3.8.0 24`659 06-Jul-2009 23:21:36

-------------------------------------------------------------------------------------------------------------------------------

There are more differences, amongst which the most notable are a lot of *.SO files in \apache\bin\iconv that are even older (from 2008). Last but not least, there are a lot of *.PDB files sprinkled through \bin subfolders.

=Bottom Line=

I don't know what to make out of this difference in DLL versions. It seems the installer's author started to use older versions on purpose but I don't know why.

Can someone make sense of this problem or at least provide me with some info about a 3.2.x release whose Windows installer works on Windows 2008 R2?

/bogdan

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs