Fixed this issue. In 5.0.16 I had LDAP setup for anonymous login, but
when I upgraded this to 5.0.19 it broke LDAP users from being able to
log in. Once I changed the LDAP config settings to include LDAP
administrator account LDAP users were able to log in and the "Can't get
cache storage, user not logged in" errors were gone.
On 7/30/15 4:36 PM, CJ Keist wrote:
Okay, Scratch the Enterprise issue. It might not be LDAP issue, this is
what I'm getting in the owncloud.log file when a user tries to log in:
{"app":"core","message":"Can't get cache storage, user not logged
in","level":3,"time":"2015-07-30T22:35:23+00:00"}
I found someone asking about this very same issue, but there was no
follow up.
On 7/30/15 11:01 AM, CJ Keist wrote:
Just noticed that the older version I'm downloading from:
https://owncloud.org/changelog/
Are the Enterprise versions. Could this be a licensing issue since it
not the free open source editions?
-------------------------------
Thank you.
I'm working on upgrading to 5.0.19 and running into issue that the
new owncloud server is not authenticating with our LDAP servers.
Under the Admin account and in the admin pages, when I click the test
configuration button for LDAP it says it was successful in making a
connection. It is seeing all our LDAP groups, but not the users.
Any ideas?
What I have done is rsync the owncloud folder from the old server to the
new owncloud server. I then exported the owncloud database and imported
into new mysql server on the new server.
Then did the upgrade:
cd /net/10.1.20.102/clouddata/src/
tar xvf owncloud-5.0.19.tar
cd /var/www/html/
rsync --inplace -rtv /net/10.1.20.102/clouddata/src/owncloud/
owncloud/
Then edited the config.php file and updated server names and database
location and file paths to match on new server.
I then logged into the new cloud server and it did say it was updating
the owncloud database. And allowed my local admin account in. But no
users on LDAP can login.
On 7/29/15 9:42 PM, Chris wrote:
Hi,
so if there is a way to do this upgrades in increments let me know.
Say
first upgrade to OC 6, then 7 and then 8?
yes the correct way of doing this is:
5.0.16 > 5.0.19 > 6.0.9 > 7.0.7 > 8.05 > 8.1.0
like described in the upgrade docs.
--
View this message in context:
http://owncloud.10557.n7.nabble.com/migrating-from-OC-5-0-16-to-8-1-tp15541p15542.html
Sent from the Users mailing list archive at Nabble.com.
_______________________________________________
User mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/user
--
C. J. Keist Email: [email protected]
Systems Group Manager Solaris 10 OS (SAI)
Engineering Network Services Phone: 970-491-0630
College of Engineering, CSU Fax: 970-491-5569
Ft. Collins, CO 80523-1301
All I want is a chance to prove 'Money can't buy happiness'
_______________________________________________
User mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/user
