I get to /step4b and all I get is a blank screen

Any ideas?

Jason

Blank screen often has to do with not enough memory or execution time on the server. But I am not a server expert here.

What is the memory limit?

holch are rigth : need server error log.

I'll take a look at server memory - what log should I be looking in?

Jason

edit: Server is running Debian Wheezy and has 4GB ram

total used free shared buffers cached
Mem: 4147084 1320632 2826452 0 209728 823744
-/+ buffers/cache: 287160 3859924
Swap: 5041148 0 5041148

jasonweir wrote: I'll take a look at server memory - what log should I be looking in?

Jason

edit: Server is running Debian Wheezy and has 4GB ram

total used free shared buffers cached
Mem: 4147084 1320632 2826452 0 209728 823744
-/+ buffers/cache: 287160 3859924
Swap: 5041148 0 5041148

Not the server memory .....

memory_limit in php.ini (see phpconfig)

ANd the apache server error log.

Denis

; Maximum amount of memory a script may consume (128MB)
; php.net/memory-limit
memory_limit = 128M

cat /var/log/apache2/error.log
[Wed Jul 29 12:17:54 2015] [warn] RSA server certificate CommonName (CN) `xxxxxx.xxx' does NOT match server name!?
[Wed Jul 29 12:17:54 2015] [warn] RSA server certificate CommonName (CN) `xxxxxx.xxx'' does NOT match server name!?
[Wed Jul 29 12:17:54 2015] [notice] Apache/2.2.22 (Debian) PHP/5.4.43-1~dotdeb+7.1 mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations

edit: Just changed memory_limit to -1 (no limit) and get the same blank screen and same 3 messages in the error.log

I am facing the same problem. I use limesurvey through the BitNami stack. Until the updates for version 2.05+ (150520) everything worked perfectly fine. When leaving the updates to version 2.06+ updates do not complete. I have done tests changing the php memory_limit to 256M and 512M but the problem persists. In apache error_log file of BitNami stack, it is not recorded any message. Any other ideas than I can check to try to make the updating via comfort upgrade sucessfully? thanks

same problem for upgrading 150520 to 150723 (and newer 150731) on unix server:
System SunOS silene5 5.11 11.2 i86pc
Apache API Version 20120211
PHP Version 5.5.11
mysql Client API version 5.5.34

ok on linux servers with memory_limit 128M:
Linux 3.10.9-xxxx-grs-ipv6-64 #1 SMP Wed Aug 21 11:51:59 CEST 2013 x86_64

seems to be linked with db upgrade; "blank page" on step 4b, /index.php/admin/update/sa/step4b , then no way to recover limesurvey (both public and admin), only a complete re-install with backups of the old version works

nothing in apache logs

are the other concerned on a unix like OS?

Hello,

sorry, another Problem. I tried using the Comfort Upgrade but at Step 2 there is an error.
Maybe a CHMOD Problem but the installer shows not the affected file. > see screenshot (german installation)
installed Version: 2.05+ (150520)
actuel Version: 2.06+ (150723)
any ideas?

How often did you already updated via the ComfortUpdater? The error message can be interpreted in the way that the whole directory and all files are read-only. You need to check via FTP or other tools for the granted permissions. Which Provider do you use and which package?

Partial solution to the problem.

Finally managed to make the update to version 2.06+

After many attempts, successfully managed to make the update to version 2.06+ editing the config.php file and by setting the variable debug to 1.

After the change, managed to successfully perform the update of the version 2.05+ Build 150520 for version 2.06+ Build 150731.

Following this update, also via comfort possible update was successfully perform the update for version 2.06+ Build 150831.

I tested my surveys and everything ran well.

But after changing the debug parameter in config.php to 0, the administrative interface is no longer charged.
The loading of the web server is at 100% and after a long time, I am redirected to the login link interface, however nothing appears. The page is completely blank.

To again change the debug parameter to 1, and try to charge the administrative interface, everything works perfectly fine.

Here is a tip for those who want to upgrade to version 2.06+, and so developers can better identify what may be causing the problem involving the parameter debug.