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

update to ownCloud 9.1.1 (with intermediate upgrades) #894

Merged
merged 15 commits into from
Oct 18, 2016

Conversation

yodax
Copy link
Contributor

@yodax yodax commented Jul 27, 2016

This PR upgrades owncloud to 9.1.0.

When upgrading owncloud you can't skip a minor version, this PR will upgrade from 8 to 9 to 9.1.

After going to 9 we need to migrate the existing contacts and calendars. This has to be done when you're at version 9, otherwise the option (and storage) is removed when upgrading to version 9.1. (Yes really, you will lose data)

When upgrading to 9, memcached doesn't seem to work. I have moved to the recommend (by Owncloud) APC method of caching. (memcached doesn't work well with file locking according to owcloud). This has to be done before the migrations and occ command line upgrades, otherwise these will fail.

We can't install the contacts/calendar app from github any more. These now need to be build, to do that you need npm, etc. Which we could install, but owncloud also supply packages. So I install directly from these packages.

I have tested this by upgrading many times from 8.2.3 to 9.1.0. I have tested:

  • Files
  • Calendars and contacts in the Web UI, Z-Push and DAV

The tests have been done on iOS with z-push and on macOS with Calendar and Contacts.

Even though I tried to test this quite thoroughly, I think more people should test this on a system for which they have backups or do not care about.

What I did to test this was copy /usr/local/lib/owncloud to ~/owncloud-lib and /home/user-data/owncloud. If you then run this script:

#!/bin/bash
rm -rf /home/user-data/owncloud/ && cp -r ~/owncloud /home/user-data/ && rm -rf /usr/local/lib/owncloud/ && cp -r ~/owncloud-lib/ /usr/local/lib/owncloud
chmod 750 /usr/local/lib/owncloud/{apps,config}

STORAGE_ROOT=/home/user-data
ln -sf $STORAGE_ROOT/owncloud/config.php /usr/local/lib/owncloud/config/config.php
chown -f -R www-data.www-data $STORAGE_ROOT/owncloud /usr/local/lib/owncloud
chown www-data.www-data $STORAGE_ROOT/owncloud/config.php

And after the script rerun the setup/owncloud.sh from the master branch. This will restore everything to 8.2.3. Then checkout this branch and run the setup.

@yodax yodax mentioned this pull request Jul 28, 2016
@yodax
Copy link
Contributor Author

yodax commented Jul 29, 2016

I was thinking that we should perhaps stop the upgrade if the current system isn't on the expected owncloud version. Otherwise the user might lose data.

@yodax
Copy link
Contributor Author

yodax commented Jul 29, 2016

I made a mistake when going from 8.2.3 to 9.1.0. When 9.1.0 was installed the backup from 8.2.3 was overwritten with the one from 9.0.

Sorry, I try to thoroughly test before opening a PR.

I made the upgrade slightly more forgiving when checking to go to 9.0. Every point release on 8.2.x is now accepted if someone manually upgraded.

People upgrading from versions of miab before 0.18 will run in to issues. This has always been a problem if you skipped to many version. Shall I add an upgrade path from 8.1.1 into this? That should go to 8.2.3.

@yodax
Copy link
Contributor Author

yodax commented Jul 30, 2016

Every time I sleep on it, I think of some more test cases.

I have tested an upgrade from 0.17c. (I had to add another upgrade path) This now works.
I also tested on a clean install, this worked but gave a few error messages. I cleaned that up a bit.

Since the fail2ban changes have been merged to master I tested with that. Of course that doesn't work.. Manual testing shows that normal banning via the UI works. However no log messages are created when supplying bad login information via webdav. I don't think that is fixable from our end.

It was planned for 9.1 to block repeated failed login attempts from owncloud it self. That didn't make it.

@yodax
Copy link
Contributor Author

yodax commented Jul 31, 2016

I figured out what the problem was with fail2ban and owncloud logging. Owncloud will not log failures to the log if the username is unknown. So somebody can (trivially via a timing attack) figure out your usernames. When the attacker tries to login via those usernames we will start banning:

http_test /cloud/remote.php/webdav 401 None None ['MY_SPECIFIC_USER', 'aa'] ...
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 * blocked [OK]

Imho; if they target a miab, they will most likely already know your email address.

@JoshData shall we stay at 8.2 for this issue?

Also I found a problem with the owncloud upgrades when somebody was trying to use owncloud at the same time. Before an upgrade I stop the service, this solved the issue.

I think this should be it for this PR unless somebody can come up with another test I can perform?

@JoshData
Copy link
Member

JoshData commented Aug 1, 2016

Very nice work. We'll want to upgrade ownCloud anyway eventually.

  1. For cp /home/user-data/owncloud/owncloud.db /tmp, it should assign a unique name to the target file, otherwise running the install script multiple times could clobber the original db backup. Also, since this file may have user data, we may want to put it into a backup place in STORAGE_ROOT so that we don't leave possibly sensitive user day laying around the system.

  2. Iterating through the directories in STORAGE_ROOT/owncloud may not get a complete list of users. I think that might only be users who have used the files app, maybe?

@yodax
Copy link
Contributor Author

yodax commented Aug 1, 2016

Very nice work.

Thank you!

  1. For cp /home/user-data/owncloud/owncloud.db /tmp....

I pushed a commit for this.

  1. Iterating through the directories in STORAGE_ROOT/owncloud may not get a complete list of users. I think that might only be users who have used the files app, maybe?

I ran a test where I deleted my user account and then only accessed owncloud via carddav. A new directory was created when I did that.
The reason why I went with the directory scan is that we don't delete owncloud users when we delete a mail account. If the user is recreated the data will have been migrated. (Not saying it is a good reason, but I hate for someone to lose data)

I used the following command to delete my account, that also deleted the directory:

sudo -u www-data php /usr/local/lib/owncloud/occ user:delete [email protected]

@JoshData
Copy link
Member

JoshData commented Aug 1, 2016

Got it. Ok. I'll give this a test when I get the time.

@MariusBluem
Copy link
Contributor

MariusBluem commented Aug 9, 2016

Have you already considered about taking this big upgrade as a step and a chance to move from ownCloud to Nextcloud? Nextcloud is a fork of ownCloud by Frank Karlitschek (founder of ownCloud) and a big part of the main developers.

  • The way of development will be designed more open and transparent (e.g. you dont need to sign a CLA if you want to contribute to the core-repositories)
  • They want to integrate contacts and calendar in the main-development better (which could be nice for MiaB as this is the part you actually use )
  • We will provide a new updater and migration path in the coming months, so that the upgrade experience (which was not always good for all of you in the past) will be much better.
  • Nextcloud 10 (will be released in the coming weeks, and is based on ownCloud 9.1) will have some new fuctions (Brute force protection, pluggable authentification) which are not included into ownCloud. The other way around Nextcloud is supporting all functions and features ownCloud does.

The migration process would be as easy as an upgrade to a new version. You would just need to install Nextcloud 10 with this script (which is nice 👊 ), instead of ownCloud 9.1 😉

I should add that I am a part of the Nextcloud community 😅

If you have more questions or want to talk about that, feel free to ask me here ... visit our forums (help.nextcloud.com) or talk to us at our freenode IRC #nextcloud-dev 💬

cc @jospoortvliet

@yodax
Copy link
Contributor Author

yodax commented Aug 10, 2016

Brute force protection

That would be a compelling argument. Since username failures are no longer logged. (Still wondering why that happend... I could only find something in the change log stating that there were changes to that area)

However work is also been done to move to just a backend that does just card/caldav and integrate separate frontend's for that.

Ultimately the direction the project goes is up to @JoshData.

@MariusBluem
Copy link
Contributor

I could only find something in the change log stating that there were changes to that area

nextcloud/server#479

@yodax
Copy link
Contributor Author

yodax commented Aug 10, 2016

I was refering to the fact that login failures with an incorrect username aren't logged anymore.

But good news on the brute force front.

@JoshData
Copy link
Member

@Mar1u5 If we go to ownCloud 9 first, can we move to Nextcloud 10 later?

@MariusBluem
Copy link
Contributor

MariusBluem commented Aug 11, 2016

ownCloud 9 -> Nextcloud 9
ownCloud 9.1 -> Nextcloud 10
ownCloud 9.2 -> Nextcloud 11

Keep in mind, that 9.1 is a Major Release as 9. Because of this confusing names we decided to call it 10 and 11 instead of 9.1 ;)

Currently - our releases are compatible to provide an easy Migration. But this will/may change in the future.

@yodax
Copy link
Contributor Author

yodax commented Aug 14, 2016

I have merged with master and tested the upgrade from 8.2.7. No issues.

@MariusBluem
Copy link
Contributor

Nextcloud 10 RC1 (ownCloud 9.1) is out. I've tested it with MiaB - no issues ;)

@MariusBluem
Copy link
Contributor

Nextcloud 10 is out now 💪 ...do you have any plans about deploying it with the next version? @JoshData

@JoshData
Copy link
Member

JoshData commented Sep 9, 2016

This whole ownCloud/Nextcloud thing is exactly the sort of mess that reinforces why I want to move away from ownCloud entirely. So probably not.

@MariusBluem
Copy link
Contributor

MariusBluem commented Sep 9, 2016

I am sorry to hear about your decision 😞 @JoshData ... The question is, what you want to do now: I think you will not find an solution as Nextcloud which makes it so easy for people to manage their data, calendar and contacts ;) (ok ... would be crazy if I would say something different 😅)

However: For now, there is no solution which fits for you, and the 8.X contacts and calendar implementation is not longer supported. With ownCloud/Nextcloud 9.0+ the community is providing an innovative, supported and IMHO more reliable calendar and contacts.

We have a PR which works (many thanks to @yodax btw 👊) and which is (obviously) better than nothing - I think you'll see that point. If I hear what you are saying about ownCloud/Nextcloud here and in some other threads I mean that it could not be more un-reliable as it currently is ... so why don't you give it a try?

@yodax
Copy link
Contributor Author

yodax commented Oct 17, 2016

So ownCloud's calendar maintainers bailed on the project too any now they're shipping a NextCloud app instead that also works with ownCloud?

I hadn't noticed that (well spotted!), I copied the link from the ownCloud app store. But indeed so it seems. I don't like the whole ownCloud/nextCloud thing at all. There probably isn't a "right" choice here, however calendar and contacts are the main focus for us and if that is maintained by nextCloud it might be an argument for moving to nextCloud.

The cron job that we install is giving an error

I haven't been able to reproduce that. I ran it manually and I checked the logs. Could it be that cron job ran during the upgrade? Did you get any more after the first one?

The output is very scary though! We will need to warn folks about that.

Agreed. I started with adding some visual separation between the different upgrades. Do you think that is enough? We could use hide_output or print an extra warning before going to 9 and 9.1. Normally the upgrades aren't that chatty.

@jospoortvliet
Copy link

Note that in Nextcloud 10.0.1 we've made the first big step in improving the upgrade process - this replaces files reliably with the new ones. Now the rest of the process is as it was but we're working on that, too.

I know the split from ownCloud was messy, I'm real sorry for it - if we could've fixed things at ownCloud, we would have. But if you wonder about the future of the projects, the activity graphs are clear enough:
https://www.openhub.net/p/owncloud vs https://www.openhub.net/p/nextcloud
You can also compare the pulse on github for example. If you just look at the core repo the difference is even bigger as openHUB also shows the work happening in repo's which haven't yet migrated to Nextcloud and are thus co-maintained.

We don't want to drop ownCloud users, you should have time to upgrade - see for example this where we helped out with security:
https://rhinosecuritylabs.com/2016/10/operation-ownedcloud-exploitation-post-exploitation-persistence/

@ponychicken
Copy link
Contributor

But it looks like the ownCloud maintainers elected not to fix it?
What can we do to mitigate it?

Am 17.10.2016 um 09:56 schrieb Jos Poortvliet [email protected]:

Note that in Nextcloud 10.0.1 we've made the first big step in improving the upgrade process - this replaces files reliably with the new ones. Now the rest of the process is as it was but we're working on that, too.

I know the split from ownCloud was messy, I'm real sorry for it - if we could've fixed things at ownCloud, we would have. But if you wonder about the future of the projects, the activity graphs are clear enough:
https://www.openhub.net/p/owncloud vs https://www.openhub.net/p/nextcloud
You can also compare the pulse on github for example. If you just look at the core repo the difference is even bigger as openHUB also shows the work happening in repo's which haven't yet migrated to Nextcloud and are thus co-maintained.

We don't want to drop ownCloud users, you should have time to upgrade - see for example this where we helped out with security:
https://rhinosecuritylabs.com/2016/10/operation-ownedcloud-exploitation-post-exploitation-persistence/


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@jospoortvliet
Copy link

jospoortvliet commented Oct 17, 2016

Yeah, we can't/couldn't make the ownCloud guys see the problem with it, at least from a security pov.

If you're on an older version you can try to use the patch we did for Nextcloud, I suppose. A wholesale update to Nextcloud is not much more painful than a bugfix upgrade either, so that's another option.

@yodax yodax changed the title update to ownCloud 9.1.0 (with intermediate upgrades) update to ownCloud 9.1.1 (with intermediate upgrades) Oct 18, 2016
@JoshData JoshData merged commit 2151d81 into mail-in-a-box:master Oct 18, 2016
@JoshData
Copy link
Member

Merged!

(The conversation about NextCloud should be happening in one of the threads about that.)

@bronson
Copy link
Contributor

bronson commented Oct 18, 2016

Wow! Fantastic work @yodax @JoshData and @ponychicken 🏁

@yodax
Copy link
Contributor Author

yodax commented Oct 18, 2016

Thanks for the reviews and help in completing this. I just rolled the update on my production box. Upgrade went smooth and everything is working fine.

@sqeezy80
Copy link

@yodax i commented on the commit thread my installation went smooth no visible error or break but thats my output under /cloud

Memcache \OC\Memcache\APC not available for local cache Is the matching PHP module installed and enabled?

thats the nginx error log

FastCGI sent in stderr: "PHP message: PHP Fatal error: Class 'OCA\DAV\Connector\Sabre\ExceptionLoggerPlugin' not found in /usr/local/lib/owncloud/remote.php on line 54" while reading response header from upstream

@yodax
Copy link
Contributor Author

yodax commented Oct 19, 2016

@sqeezy80 could you post the config file /home/user-data/owncloud/config.php ? Please remove the hashes from the config before posting. Or just post this section:

'memcache.local' => '\\OC\\Memcache\\APC',
  'memcached_servers' => 
  array (
    0 => 
    array (
      0 => 'localhost',
      1 => 11211,
    ),
  ),

Also could you show me the output of:

dpkg --get-selections | grep apc

@sqeezy80
Copy link

sqeezy80 commented Oct 19, 2016

@yodax

<?php  
$CONFIG = array (  
  'datadirectory' => '/home/user-data/owncloud',  
  'instanceid' => 'xxxxxxx',  
  'trusted_domains' =>   
  array (  
    0 => 'box.xxxx.email',  
  ),  
  'forcessl' => true,  
  'overwritewebroot' => '/cloud',  
  'user_backends' =>   
  array (  
    0 =>   
    array (  
      'class' => 'OC_User_IMAP',  
      'arguments' =>   
      array (  
        0 => '{localhost:993/imap/ssl/novalidate-cert}',  
      ),  
    ),  
  ),  
  'memcached_servers' =>   
  array (  
    0 =>   
    array (  
      0 => 'localhost',  
      1 => 11211,  
    ),  
  ),  
  'mail_smtpmode' => 'smtp',  
  'mail_smtpauthtype' => 'LOGIN',  
  'mail_from_address' => 'administrator',  
  'mail_domain' => 'box.xxxxx.email',  
  'logtimezone' => 'Europe/Berlin',  
  'passwordsalt' => 'xxxxxxxxxxxxxx',  
  'dbtype' => 'sqlite3',  
  'version' => '9.1.1.3',  
  'installed' => true,  
  'loglevel' => '1',  
  'maintenance' => false,  
  'secret' => 'xxxxxxxxxxxx',  
  'memcache.local' => '\\OC\\Memcache\\APC',  
  'overwrite.cli.url' => '/cloud',  
  'trashbin_retention_obligation' => 'auto',  
:
dpkg --get-selections | grep apc  
php-apc                                         install  
php5-apcu                                       install  

@yodax
Copy link
Contributor Author

yodax commented Oct 19, 2016

The apc install looks fine. My 'memcache.local' => '\OC\Memcache\APC' is near the other memcache setting. That is very weird. Did you manually upgrade in the past?

'memcache.local' => '\\OC\\Memcache\\APC',
  'memcached_servers' => 
  array (
    0 => 
    array (
      0 => 'localhost',
      1 => 11211,
    ),
  ),

It shouldn't be a problem that they aren't next to each other, but it is something you can try. Perhaps give it a reboot. Otherwise you could try to restore the install and try again.

@yodax
Copy link
Contributor Author

yodax commented Oct 19, 2016

It would be interesting to see the log during the install, do you still have that? If you don't and it still isn't working you can restore the previous version; during the install the system made a backup for you.

root at box in ~/mailinabox on master [$]
$ tools/owncloud-restore.sh 
Usage: owncloud-restore.sh <backup directory>

WARNING: This will restore the database to the point of the installation!
         This means that you will lose all changes made by users after that point


Backups are stored here: /home/user-data/owncloud-backup/

Available backups:

/home/user-data/owncloud-backup/2016-10-18-13:00:41

Supply the directory that was created during the last installation as the only commandline argument

@sqeezy80
Copy link

i don't have the log This machine is running miab for a long time, but i did not install anything aside from mosh.

i did run the backup wich worked fine and restored a working owncloud install.
i would like to retry a owncloud update.
do you have any suggestions on how to do it to generate a good log file ?

@yodax
Copy link
Contributor Author

yodax commented Oct 19, 2016

If you run the setup again it will upgrade again. If you run it without mosh you can scroll back and copy the log and paste it here. There is some personal info in there so please redact it.

@sqeezy80
Copy link

sqeezy80 commented Oct 19, 2016

i did the reinstall, same result but here is the log

Installing ownCloud (contacts/calendar)...
upgrading ownCloud to 9.1.1 (backing up existing ownCloud installation, configuration and database to directory to /home/user-data/owncloud-backup/2016-10-19-10:42:16...
We are running version 8.2.x, upgrading to 9.0.2 first

Upgrading to ownCloud version 9.0.2

            ownCloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Set log level to debug
Turned on maintenance mode
Checking whether the database schema can be updated (this can take a long time depending on the database size)
Checked database schema update
Checking updates of apps
Checking whether the database schema for <activity> can be updated (this can take a long time depending on the database size)
Checking whether the database schema for <files_sharing> can be updated (this can take a long time depending on the database size)
Checking whether the database schema for <files_trashbin> can be updated (this can take a long time depending on the database size)
Checked database schema update for apps
Updating database schema
Updated database
Disabled 3rd-party app: calendar
Disabled 3rd-party app: contacts
Disabled 3rd-party app: files_videoviewer
Disabled 3rd-party app: updater
Updating <files_pdfviewer> ...
Updated <files_pdfviewer> to 0.8.1
Updating <files_texteditor> ...
Updated <files_texteditor> to 2.1
Updating <gallery> ...
Updated <gallery> to 14.5.0
Updating <files> ...
Updated <files> to 1.4.4
Updating <activity> ...
Updated <activity> to 2.2.1
Updating <files_sharing> ...
Updated <files_sharing> to 0.9.1
Updating <files_trashbin> ...
Updated <files_trashbin> to 0.8.0
Updating <files_versions> ...
Updated <files_versions> to 1.2.0
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Reset log level
Start migration of all known users ...
   11 [============================]
Start migration for 
Start migration for ...@.......
...
...
...

Start birthday calendar sync for all users ...
   11 [============================]

Upgrading to ownCloud version 9.1.1

ownCloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Set log level to debug
Turned on maintenance mode
Checking whether the database schema can be updated (this can take a long time depending on the database size)
 Done                                                        
 6/6 [============================] 100%                     
Checked database schema update
Checking updates of apps
Checking whether the database schema for <activity> can be updated (this can take a long time depending on the database size)
 Done                                                        
 14/14 [============================] 100%                   
Checking whether the database schema for <dav> can be updated (this can take a long time depending on the database size)
 Done                                                        
 14/14 [============================] 100%                   
Checking whether the database schema for <federatedfilesharing> can be updated (this can take a long time depending on the database size)
 Done                                                        
 2/2 [============================] 100%                     
Checking whether the database schema for <federation> can be updated (this can take a long time depending on the database size)
 Done                                                        
 7/7 [============================] 100%                     
Checking whether the database schema for <files_sharing> can be updated (this can take a long time depending on the database size)
 Done                                                        
 9/9 [============================] 100%                     
Checking whether the database schema for <files_trashbin> can be updated (this can take a long time depending on the database size)
Checking whether the database schema for <notifications> can be updated (this can take a long time depending on the database size)
Checked database schema update for apps
Updating database schema
Updated database
Updating <federatedfilesharing> ...
Updated <federatedfilesharing> to 0.3.0
Updating <gallery> ...
Updated <gallery> to 15.0.0
Updating <provisioning_api> ...
Updated <provisioning_api> to 0.5.0
Updating <updatenotification> ...
Updated <updatenotification> to 0.2.1
Updating <federation> ...
Updated <federation> to 0.1.0
Updating <files> ...
Updated <files> to 1.5.1
Updating <activity> ...
Updated <activity> to 2.3.2
Updating <dav> ...
Fix classification for calendar objects
 Done                                                        
 580/580 [============================] 100%                 
Updated <dav> to 0.2.6
Updating <files_sharing> ...
Updated <files_sharing> to 0.10.0
Updating <files_trashbin> ...
Updated <files_trashbin> to 0.9.0
Updating <files_versions> ...
Updated <files_versions> to 1.3.0
Updating <comments> ...
Updated <comments> to 0.3.0
Updating <notifications> ...
Updated <notifications> to 0.3.0
Updating <systemtags> ...
Updated <systemtags> to 0.3.0
Drop old database tables
 Done                                                        
 28/28 [============================] 100%                   
Remove old (< 9.0) calendar/contact shares
 Done                                                        
 4/4 [============================] 100%                     
Fix permissions so avatars can be stored again
 Done                                                        
 2/2 [============================] 100%                     
Repair unmerged shares
 Done                                                        
 1/1 [============================] 100%                     
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Reset log level
ownCloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Set log level to debug
Turned on maintenance mode
Checking whether the database schema can be updated (this can take a long time depending on the database size)
Checked database schema update
Checking updates of apps
Checked database schema update for apps
Updating database schema
Updated database
Updating <calendar> ...
Updated <calendar> to 1.4.0
Updating <contacts> ...
Updated <contacts> to 1.4.0.0
Drop old database tables
 Done                                            
 28/28 [============================] 100%       
Remove old (< 9.0) calendar/contact shares
 Done                                            
 4/4 [============================] 100%         
Fix permissions so avatars can be stored again
 Done                                            
 2/2 [============================] 100%         
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Reset log level
Installing Z-Push (Exchange/ActiveSync server)...
Installing Mail-in-a-Box system management daemon...
Installing Munin (system monitoring)...

@yodax
Copy link
Contributor Author

yodax commented Oct 19, 2016

That looks clean. Still the same issue? box.dns.email/cloud gives an error?

@sqeezy80
Copy link

yep still the same error

Memcache \OC\Memcache\APC not available for local cache Is the matching PHP module installed and enabled?

and from the ngninx log
FastCGI sent in stderr: "PHP message: PHP Fatal error: Class 'OCA\DAV\Connector\Sabre\ExceptionLoggerPlugin' not found in /usr/local/lib/owncloud/remote.php on line 54" while reading response header from upstream

@sqeezy80
Copy link

php -v shows

PHP 5.5.9-1ubuntu4.20 (cli) (built: Oct  3 2016 13:00:37) 
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
    with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies

@yodax
Copy link
Contributor Author

yodax commented Oct 19, 2016

Everything looks exactly like on my machines. Could you run:

root at box in /etc/php5
$ grep -r apc *
mods-available/apcu.ini:extension=apcu.so

I didn't do this, but it might be worth a try:
owncloud/core#17329 (comment)

@sqeezy80
Copy link

sqeezy80 commented Oct 19, 2016

result of grep -r apc *

mods-available/apcu.ini:;extension=apcu.so
mods-available/apcu.ini:apc.enabled=0

so i changed the apcu.ini and everything is working and no i never touched the ini before might be good to check it

my apcu.ini is now looking like this

extension=apcu.so
;apc.enabled=0

it´s working now

@yodax
Copy link
Contributor Author

yodax commented Oct 19, 2016

What cloud provider are you using? I had this in a first iteration of the PR, but it didn't seem necessary.

@sqeezy80
Copy link

i am using netcup.de, with a kvm based virtual machine like this

@yodax
Copy link
Contributor Author

yodax commented Oct 19, 2016

@sqeezy80 thanks for testing and reporting the issue! I have created a PR that will make this work out of the box for others with the same configuration.

|| ! grep -q $owncloud_ver /usr/local/lib/owncloud/version.php; then
InstallOwncloud() {
echo
echo "Upgrading to ownCloud version $1"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it say "Upgrading" even when doing the initial install? :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First it says:

Installing ownCloud (contacts/calendar)...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent, apologies for reading it wrong.

I'll be running it later this week...

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

Successfully merging this pull request may close these issues.

7 participants