Opened 4 years ago
Closed 4 years ago
#277 closed task (fixed)
upgrade to Mapbender 3.2.2 release
Reported by: | Jeff McKenna | Owned by: | Jeff McKenna |
---|---|---|---|
Priority: | major | Milestone: | 4.0.5 release |
Component: | MS4W - Packages | Version: | 4.0.4 |
Keywords: | Cc: | TC Haddad, Astrid Emde (WhereGroup) | |
Blocked By: | Blocking: |
Description ¶
Change History (22)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
After trying to adjust to 3.2.0's new directory structure (/mapbender/web/ no longer exists, instead /mapbender/application/web/) and trying to load /app.php/ here are the errors:
Warning: require(D:\ms4w\apps\mapbender-starter-3.2.0\application\app/../vendor/autoload.php): failed to open stream: No such file or directory in D:\ms4w\apps\mapbender-starter-3.2.0\application\app\autoload.php on line 9 Fatal error: require(): Failed opening required 'D:\ms4w\apps\mapbender-starter-3.2.0\application\app/../vendor/autoload.php' (include_path='.;\ms4w\Apache\php') in D:\ms4w\apps\mapbender-starter-3.2.0\application\app\autoload.php on line 9
comment:3 by , 4 years ago
Reported to the Mapbender community through: https://lists.osgeo.org/pipermail/mapbender_dev/2020-July/003666.html
comment:4 by , 4 years ago
Using the correct archive for 3.2.0 (https://mapbender.org/builds/mapbender-starter-current.zip) the demo app hangs forever and does not load, and the Apache log contains errors of "get overlap result error"
[Fri Jul 31 09:30:01.907753 2020] [fcgid:warn] [pid 15624:tid 1544] (OS 109)The pipe has been ended. : [client 127.0.0.1:60651] mod_fcgid: get overlap result error, referer: http://127.0.0.1/mapbender/app.php/ [Fri Jul 31 09:30:01.907753 2020] [core:error] [pid 15624:tid 1544] [client 127.0.0.1:60651] End of script output before headers: app.php, referer: http://127.0.0.1/mapbender/app.php/
by , 4 years ago
Attachment: | httpd_mapbender.conf added |
---|
new Mapbedner configuration file for fcgi and mapbender 3.2.2
comment:6 by , 4 years ago
- added the new configuration file (see file attached)
- fixed fcgi-configuration
- reference to new mapbender 3.2.2.
- please download Mapbender 3.2.2 from: https://mapbender.org/builds/3.2.2/mapbender-starter-v3.2.2.zip
comment:7 by , 4 years ago
Milestone: | 4.1.0 release → 4.0.5 release |
---|---|
Summary: | upgrade to Mapbender 3.2.0 release → upgrade to Mapbender 3.2.2 release |
comment:8 by , 4 years ago
Cc: | added |
---|
comment:9 by , 4 years ago
I did much testing today on the MS4W build servers, unfortunately the same problems exist with the new FCGI settings in httpd_mapbender.conf (Internal Server Errors, or forever hanging)
I do notice that the changes work on 1 machine that doesn't have the usual read/write permissions on the C:/Windows/ directories.
Background: MS4W is specifically designed to not point to any "Windows" directories, to avoid write permission errors, "DLL hell" errors (same dll found in C:/Windows/System32 and inside MS4W causing crashes) etc. For example, MS4W also comes with its own writable "TMP" or "TEMP" directory, used by many applications: /ms4w/tmp/ms_tmp/
I will do more testing, avoiding any "WINROOT" or Windows path directories, with the new FCGI settings...
Thank-you so much for your feedback here (!!).
comment:10 by , 4 years ago
So maybe we change FcgidInitialEnv for the temp / tmp dir to /ms4w/tmp/ms_tmp/
FcgidInitialEnv TEMP "${WINROOT}/TEMP"
FcgidInitialEnv TMP "${WINROOT}/TEMP"
comment:11 by , 4 years ago
Agreed, that's why I mentioned the TMP example, I was trying that yesterday but no success. My gut feeling is that this is about an access (write) violation, as it works on a Windows machine without all of the usual restrictions on C:/Windows directories. I think setting the writeable TMP path is part of it, but I need to do more testing. Ideas are welcomed.
comment:12 by , 4 years ago
Maybe we just write a comment in the httpd_mapbender.conf file that there has to be write access on the machine to the TEMP /TMP file.
Then the user has to take care about this.
Like this
# Please make sure that you have write access to the TEMP/TMP-directories.
comment:13 by , 4 years ago
I meant: the TEMP/TMP writable directory for MS4W applications ( /ms4w/tmp/ms_tmp/) is not the solution to the Mapbender 3.2 problem. I can still trigger the errors when using the correct writable directory.
I believe it has to do with the other references to C:/Windows (WINROOT) etc, but more testing is needed to confirm. (I could be totally wrong)
Worst case, I will need to spend much effort running this through debuggers.
by , 4 years ago
Attachment: | httpd_mapbender.2.conf added |
---|
httpd_mapbender.conf version 2 with less env variables
comment:14 by , 4 years ago
I reduced the varibales in the httpd_mapbender.conf ( seeversion 2 with less env variables).
Mapbender is still slow but writes the tmp-files to /ms4w/tmp in the end. Maybe run F5 for the application if it is not there right away.
http://localhost/mapbender/
http://localhost/mapbender/app_dev.php/application/mapbender_user
/ms4w/tmp is also defined in the php.ini file
See also http://localhost/mapbender/app_dev.php/_profiler/phpinfo
comment:15 by , 4 years ago
I also tried this (removed all mention of Windows paths)
Same errors.
(am aware of MS4W's tmp settings for PHP, as I created them)
(of course I am monitoring through browser's developer tools)
Will keep testing and likely have to spend a few days of effort running through debuggers to find what Mapbender 3.2 requires, where Mapbender 3.2 needs access, and its FCGI demands...
(if anything, we can see now that MS4W is relied upon heavily by organizations on their production servers, for Mapbender)
comment:16 by , 4 years ago
There are many 500 errors (even after refreshing/F5), but one I frequently see is:
http://127.0.0.1/mapbender/app.php/application/mapbender_user/assets/trans 500: Internal Server Error
comment:17 by , 4 years ago
Will keep working on this.
If organizations can contact me to help fund all this effort, please do, as it seems very critical to so many organizations.
Thanks for the feedback!
comment:19 by , 4 years ago
I'm not sure what to say more now, other than it will take me time/effort to figure out what is causing these internal server errors, with Mapbender 3.2.x.
I'll keep this ticket updated with progress.
Thanks for those taking the time to test and provide feedback here.
comment:20 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I spent much effort on this. The entire stack was rebuilt for Mapbender 3.2.x
Today's MS4W 4.0.5 release includes Mapbender 3.2.3 and PHP 7.4.13 etc. etc.
Thanks for the feedback here.
It seems that the entire directory structure was changed for this release, and the install docs still have not been updated for those changes (https://doc.mapbender.org/en/installation/installation_windows.html), so this package update will have to wait.