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.

Sign up for GitHub

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

Jump to bottom

Upgrade 0.46 to 0.53 does not work #811

Closed
hhlotter opened this issue Jul 8, 2019 · 16 comments
Closed

Upgrade 0.46 to 0.53 does not work #811

hhlotter opened this issue Jul 8, 2019 · 16 comments

Comments

@hhlotter
Copy link

hhlotter commented Jul 8, 2019

I am running Baikal on Synology DS214play with the latest 6.2.2-24922-2.

Stopped Baikal from running.

I have made a backup of my SQLite database and a backup of the baikal directory (as the upgrade did not work, I played everything back which worked). I downloaded baikal-0.5.3.zip from github and upload the contents of the zip file to the server (without the Specific directory) and copied the files into the respective directory.

Started Baikal.

However I cannot get the the administration page and log myself in: http://x.x.x.x/baikal/html/admin/

As said, when I copy back the files everything works again.

What do I do wrong?
@ByteHamster
Copy link
Member

ByteHamster commented Jul 8, 2019 •
edited

Did you copy the whole specific folder with all files or just the database? You should copy the whole folder.

@hhlotter
Copy link
Author

hhlotter commented Jul 8, 2019 via email

@ByteHamster
Copy link
Member

I did not receive the screenshot but overwriting all files except the Specific folder should work in most cases. Did you change any lines in the htaccess file that now get overwritten? Do you get an error message when accessing the admin interface?

@hhlotter
Copy link
Author

hhlotter commented Jul 8, 2019 via email

@ByteHamster
Copy link
Member

By the way, the "/.well-known/caldav" and "/.well-known/carddav" folders
exist but are empty

That shouldn't be a problem

With 0.53 there is an empty page.

Does the empty page have something in its source code or is is really totally empty? Is there anything in the error log files of the server?

@hhlotter
Copy link
Author

hhlotter commented Jul 8, 2019 via email

@ByteHamster
Copy link
Member

It's not possible to help without the actual error message from the log files. The 500 error can be caused by a ton of different things. On Linux systems, have a look at /var/log/httpd/error_log or /var/log/apache2/error.log. If you use a hosting service, you might find a logs folder in the ftp root folder or something in the hoster's admin interface.

@hhlotter
Copy link
Author

hhlotter commented Jul 8, 2019 via email

@hhlotter
Copy link
Author

hhlotter commented Jul 8, 2019 via email

@ByteHamster
Copy link
Member

ByteHamster commented Jul 8, 2019 •
edited

Please only post the last 10 lines, directly after triggering the 500 error again. You can review these lines manually.

Edit: you already posted. Thanks

@ByteHamster
Copy link
Member

It says error in file /volume1/web/baikal.app/admin/index.php. Shouldn't it use something with html in its path instead? It complains about the missing function in line 57, even though the function is not called in the current sources. I think that you are still using an old file from before the upgrade there. It might be better to delete the whole baikal folder, replace with the new one and then restore the Specific folder. This makes sure that you do not accidentally leave old files in place.

@hhlotter
Copy link
Author

hhlotter commented Jul 8, 2019 via email

@ByteHamster
Copy link
Member

ByteHamster commented Jul 8, 2019 •
edited

That's what I do on my server. Baikal might be configured to use a MySQL database that is not stored in the Specific folder (only the server address). If this is the case, you might want to back-up the database, too. You can view the database path on the Baïkal system settings page.

I do not use Baikal on a DiskStation but I don't think that it is modified to store the data differently there. So playing back should work, yes.

@hhlotter
Copy link
Author

hhlotter commented Jul 8, 2019

Done. Please see the last lines of the error log. Fixed the first errors by giving access to html. But still does not work.

2019-07-08T19:10:43+02:00 DiskStation [Mon Jul 08 19:10:43 2019] [crit] [client 192.168.1.51] (13)Permission denied: /var/services/web/baikal/html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
2019-07-08T19:10:43+02:00 DiskStation [Mon Jul 08 19:10:43 2019] [error] [client 192.168.1.51] File does not exist: /var/services/web/missing, referer: http://X.X.X.X/baikal/html/admin/
2019-07-08T19:10:43+02:00 DiskStation [Mon Jul 08 19:10:43 2019] [error] [client 192.168.1.51] File does not exist: /var/services/web/favicon.ico
2019-07-08T19:10:46+02:00 DiskStation [Mon Jul 08 19:10:46 2019] [crit] [client 192.168.1.51] (13)Permission denied: /var/services/web/baikal/html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
2019-07-08T19:10:46+02:00 DiskStation [Mon Jul 08 19:10:46 2019] [error] [client 192.168.1.51] File does not exist: /var/services/web/missing, referer: http://X.X.X.X/baikal/html/admin/
2019-07-08T19:11:24+02:00 DiskStation [Mon Jul 08 19:11:24 2019] [crit] [client 192.168.1.51] (13)Permission denied: /var/services/web/baikal/html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
2019-07-08T19:11:24+02:00 DiskStation [Mon Jul 08 19:11:24 2019] [error] [client 192.168.1.51] File does not exist: /var/services/web/missing, referer: http://X.X.X.X/baikal/html/admin/
2019-07-08T19:18:12+02:00 DiskStation [Mon Jul 08 19:18:12 2019] [crit] [client 37.5.251.154] (13)Permission denied: /var/services/web/baikal/html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
2019-07-08T19:18:12+02:00 DiskStation [Mon Jul 08 19:18:12 2019] [crit] [client 37.5.251.154] (13)Permission denied: /var/services/web/baikal/html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable

After here I had changed the access rights on html

2019-07-08T19:24:03+02:00 DiskStation [Mon Jul 08 19:24:03 2019] [error] [client 192.168.1.51] FastCGI: server "/default-php-YYY" stderr: PHP message: PHP Warning: require(/volume1/web/baikal.app/vendor/autoload.php): failed to open stream: Permission denied in /volume1/web/baikal.app/html/admin/index.php on line 47
2019-07-08T19:24:03+02:00 DiskStation [Mon Jul 08 19:24:03 2019] [error] [client 192.168.1.51] FastCGI: server "/default-php-YYY" stderr: PHP message: PHP Fatal error: require(): Failed opening required '/volume1/web/baikal.app/vendor/autoload.php' (include_path='.') in /volume1/web/baikal.app/html/admin/index.php on line 47

@ByteHamster
Copy link
Member

Looks like you have to grant read permissions to vendor, too. Probably also to Core if the errors continue.

@hhlotter
Copy link
Author

hhlotter commented Jul 8, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ByteHamster @hhlotter