Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Baikal Upgrade Problem #665

Closed
Mrres58 opened this issue Jan 23, 2017 · 11 comments
Closed

Baikal Upgrade Problem #665

Mrres58 opened this issue Jan 23, 2017 · 11 comments
Labels

Comments

@Mrres58
Copy link

Mrres58 commented Jan 23, 2017

Hi. When I call up the baikal administration page in Firefox something like http://dav.example.org/baikal/html/admin/ I get a blank page. No error messages, just a plain white page. I have given everyone read/write permissions to the specific and db directories after copying the contents of the extracted baikal directory into my web directory. Currently I am running 0.2.7-001 on my synology. Thank you in advance for your help.

@ErikBasalt
Copy link

Are you trying to upgrade from 0.2.7 to 0.4.6 and you get this white page on 0.4.6 only?
Did you ever made a fix in Core/Frameworks/Flake/Framework.php of 0.2.7 ?
Which DSM version are you running on your Synology?
Which php version ? (php -v)

@derStephan
Copy link

I had the very same issue when upgrading my installation from 0.2.7. You need to raise the maximum execution time. Otherwise, the script will be stopped after 30s in the middle of the upgrade process and your data will be corrupted.

This gets worse with each entry you have in the database.

So, restore your backup, raise maximum execution time a lot and run the upgrade script again.

@Mrres58
Copy link
Author

Mrres58 commented Jan 25, 2017 via email

@Mrres58
Copy link
Author

Mrres58 commented Jan 25, 2017 via email

@untitaker
Copy link
Member

@Mrres58 To change the maximum execution time you have to edit php.ini and then, in some cases, restart your webserver. Where this file is depends... on mine it is at /etc/php/php.ini.

@derStephan
Copy link

derStephan commented Jan 26, 2017

@Mrres58 If you have no access to your PHP configuration on your NAS, try adding

ini_set('max_execution_time', 3000); //3000 seconds = 50 minutes

to line 1 in the baikal-file /html/admin/install/index.php

right after <?php

Then run your upgrade and be patient.

@evert May I suggest to add something like this to the official file in the repository? If this is allowed, then everyting is fine. If not, it will just fail silently without doing any harm.

@Mrres58
Copy link
Author

Mrres58 commented Jan 26, 2017 via email

@ErikBasalt
Copy link

Have a look at this issue, maybe the solution works for you too:
#573

@derStephan
Copy link

I found a tool on my synology which allows me to edit various php settings

Try setting error reporting to E_ALL. So PHP-Errors will be shown.

The white page still comes and there is no indication that anything is happening.

Did you restore your backup before doing this? This is necessary in my opinion.

Did you have to restart your webserver for the changes to take effect?

yes.

m thinking of doing a new installation. If I were, and then copy my databank into the new installation, do you think that would work?

You can give it a try, but i think it is not enough to copy the sqLite-file. You have to copy the whole "Specific" folder. And even then, it will try to update the database schema.

The only thing you could do is:

  1. export all data from the old installation using your client software
  2. do a clean install
  3. create all your users, calendars and addressbooks new
  4. import all data to your new calendars and addressbooks

This may be some work but it is a good opportunity to clean everything up and get it all running without your specific problem.

@staabm
Copy link
Member

staabm commented Jan 27, 2017

I somehow remember that those NAS systems use a very old libxml

@evert evert added the question label Jan 28, 2017
@evert
Copy link
Member

evert commented Jan 28, 2017

Closing this issue at it seems like it is answered. If there's still problems, don't hesitate commenting here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants