Quantcast

Problem updating from EGW 1.8 to 16.1 EPL

classic Classic list List threaded Threaded
5 messages Options
StefS StefS
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Problem updating from EGW 1.8 to 16.1 EPL

Hello,

i try to update my old egroupware installation to the current
16.1.20170415 release, using the OpenSUSE Build service deb packages for
Debian 8.

I used a new VM, just installed mariadb 10, apache2 and php5.6 before
the egroupware packages.

After installation of the egroupware-epl package (that only worked using
cli with "apt-get install egroupware-epl and not via interactive session
with aptitude) i had an first installation. Than i dropped the
egroupware database and restored my old egroupware 1.8 one.

After that i visited the "/egroupware/setup" website and tried to update
the database. The program correctly recognized the 1.8 table layout but
was unable to update it successfully to 16.1 It crashes every time with
an "Invalid SQL" error. Restarting the update after the first error it
recognized a 14.3.907 table layout but update fails again with the same
error message:

===
process->pass(): #1 for upgrade processing
process->upgrade(): Incoming : appname: phpgwapi, version: 1.8.007, status:
process->upgrade(): No table upgrade required/availible for phpgwapi
process->upgrade(): Outgoing : appname: phpgwapi, status: C
process->upgrade(): Incoming : appname: emailadmin, version: 1.9.006,
status:
process->upgrade(): emailadmin(1.9.006 --> 14.3.001): running
emailadmin_upgrade1_9_006() --> 1.9.007
process->upgrade(): emailadmin(1.9.007 --> 14.3.001): running
emailadmin_upgrade1_9_007() --> 1.9.008
process->upgrade(): emailadmin(1.9.008 --> 14.3.001): running
emailadmin_upgrade1_9_008() --> 1.9.009
process->upgrade(): emailadmin(1.9.009 --> 14.3.001): running
emailadmin_upgrade1_9_009() --> 1.9.010
process->upgrade(): emailadmin(1.9.010 --> 14.3.001): running
emailadmin_upgrade1_9_010() --> 1.9.011
process->upgrade(): emailadmin(1.9.011 --> 14.3.001): running
emailadmin_upgrade1_9_011() --> 1.9.015
process->upgrade(): emailadmin(1.9.015 --> 14.3.001): running
emailadmin_upgrade1_9_015() --> 1.9.016
process->upgrade(): emailadmin(1.9.016 --> 14.3.001): running
emailadmin_upgrade1_9_016() --> 1.9.017
process->upgrade(): emailadmin(1.9.017 --> 14.3.001): running
emailadmin_upgrade1_9_017() --> 1.9.018
process->upgrade(): emailadmin(1.9.018 --> 14.3.001): running
emailadmin_upgrade1_9_018() --> 1.9.019
process->upgrade(): emailadmin(1.9.019 --> 14.3.001): running
emailadmin_upgrade1_9_019() --> 14.1
process->upgrade(): emailadmin(14.1 --> 14.3.001): running
emailadmin_upgrade14_1() --> 14.2
process->upgrade(): emailadmin(14.2 --> 14.3.001): running
emailadmin_upgrade14_2() --> 14.2.001
process->upgrade(): emailadmin(14.2.001 --> 14.3.001): running
emailadmin_upgrade14_2_001() --> 14.3
process->upgrade(): emailadmin(14.3 --> 14.3.001): running
emailadmin_upgrade14_3() --> 14.3.001
process->upgrade(): Upgrade of emailadmin to 14.3.001 is completed.
process->upgrade(): Outgoing : appname: emailadmin, status: C
process->upgrade(): Incoming : appname: api, version: 14.3.907, status: U
process->upgrade(): api(14.3.907 --> 16.1.005): running
api_upgrade14_3_907() --> 16.1
process->upgrade(): api(16.1 --> 16.1.005): running api_upgrade16_1()
--> 16.1.001
process->upgrade(): api(16.1.001 --> 16.1.005): running
api_upgrade16_1_001() --> 16.1.002
process->upgrade(): api(16.1.002 --> 16.1.005): running
api_upgrade16_1_002() --> 16.1.003
process->upgrade(): api(16.1.003 --> 16.1.005): running
api_upgrade16_1_003() --> 16.1.004
process->upgrade(): api(16.1.004 --> 16.1.005): running
api_upgrade16_1_004()
Invalid SQL: SELECT fs_id,prop_namespace,prop_name,MAX(prop_id) AS prop_id
FROM egw_sqlfs_props
GROUP BY fs_id,prop_namespace,prop_name
HAVING COUNT(*) > 1
Unknown column 'prop_id' in 'field list' (1054)
==

Some help is appreciated...

Thanks in advance,
S. Seide


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
eGroupWare-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/egroupware-users
StefanU StefanU
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem updating from EGW 1.8 to 16.1 EPL

Hi StefS,

please take a look:
http://egroupware.219119.n3.nabble.com/Upgrade-to-16-1-005-prop-id-td4014448.html

Hope it helps.

Greetings
Stefan

StefS wrote
Hello,

i try to update my old egroupware installation to the current
16.1.20170415 release, using the OpenSUSE Build service deb packages for
Debian 8.

I used a new VM, just installed mariadb 10, apache2 and php5.6 before
the egroupware packages.

After installation of the egroupware-epl package (that only worked using
cli with "apt-get install egroupware-epl and not via interactive session
with aptitude) i had an first installation. Than i dropped the
egroupware database and restored my old egroupware 1.8 one.

After that i visited the "/egroupware/setup" website and tried to update
the database. The program correctly recognized the 1.8 table layout but
was unable to update it successfully to 16.1 It crashes every time with
an "Invalid SQL" error. Restarting the update after the first error it
recognized a 14.3.907 table layout but update fails again with the same
error message:

===
process->pass(): #1 for upgrade processing
process->upgrade(): Incoming : appname: phpgwapi, version: 1.8.007, status:
process->upgrade(): No table upgrade required/availible for phpgwapi
process->upgrade(): Outgoing : appname: phpgwapi, status: C
process->upgrade(): Incoming : appname: emailadmin, version: 1.9.006,
status:
process->upgrade(): emailadmin(1.9.006 --> 14.3.001): running
emailadmin_upgrade1_9_006() --> 1.9.007
process->upgrade(): emailadmin(1.9.007 --> 14.3.001): running
emailadmin_upgrade1_9_007() --> 1.9.008
process->upgrade(): emailadmin(1.9.008 --> 14.3.001): running
emailadmin_upgrade1_9_008() --> 1.9.009
process->upgrade(): emailadmin(1.9.009 --> 14.3.001): running
emailadmin_upgrade1_9_009() --> 1.9.010
process->upgrade(): emailadmin(1.9.010 --> 14.3.001): running
emailadmin_upgrade1_9_010() --> 1.9.011
process->upgrade(): emailadmin(1.9.011 --> 14.3.001): running
emailadmin_upgrade1_9_011() --> 1.9.015
process->upgrade(): emailadmin(1.9.015 --> 14.3.001): running
emailadmin_upgrade1_9_015() --> 1.9.016
process->upgrade(): emailadmin(1.9.016 --> 14.3.001): running
emailadmin_upgrade1_9_016() --> 1.9.017
process->upgrade(): emailadmin(1.9.017 --> 14.3.001): running
emailadmin_upgrade1_9_017() --> 1.9.018
process->upgrade(): emailadmin(1.9.018 --> 14.3.001): running
emailadmin_upgrade1_9_018() --> 1.9.019
process->upgrade(): emailadmin(1.9.019 --> 14.3.001): running
emailadmin_upgrade1_9_019() --> 14.1
process->upgrade(): emailadmin(14.1 --> 14.3.001): running
emailadmin_upgrade14_1() --> 14.2
process->upgrade(): emailadmin(14.2 --> 14.3.001): running
emailadmin_upgrade14_2() --> 14.2.001
process->upgrade(): emailadmin(14.2.001 --> 14.3.001): running
emailadmin_upgrade14_2_001() --> 14.3
process->upgrade(): emailadmin(14.3 --> 14.3.001): running
emailadmin_upgrade14_3() --> 14.3.001
process->upgrade(): Upgrade of emailadmin to 14.3.001 is completed.
process->upgrade(): Outgoing : appname: emailadmin, status: C
process->upgrade(): Incoming : appname: api, version: 14.3.907, status: U
process->upgrade(): api(14.3.907 --> 16.1.005): running
api_upgrade14_3_907() --> 16.1
process->upgrade(): api(16.1 --> 16.1.005): running api_upgrade16_1()
--> 16.1.001
process->upgrade(): api(16.1.001 --> 16.1.005): running
api_upgrade16_1_001() --> 16.1.002
process->upgrade(): api(16.1.002 --> 16.1.005): running
api_upgrade16_1_002() --> 16.1.003
process->upgrade(): api(16.1.003 --> 16.1.005): running
api_upgrade16_1_003() --> 16.1.004
process->upgrade(): api(16.1.004 --> 16.1.005): running
api_upgrade16_1_004()
Invalid SQL: SELECT fs_id,prop_namespace,prop_name,MAX(prop_id) AS prop_id
FROM egw_sqlfs_props
GROUP BY fs_id,prop_namespace,prop_name
HAVING COUNT(*) > 1
Unknown column 'prop_id' in 'field list' (1054)
==

Some help is appreciated...

Thanks in advance,
S. Seide
Stefan Unverricht
EGroupware Community Manager

EGroupware GmbH
Leibnizstraße 17
D-67663 Kaiserslautern
E-Mail su@egroupware.org
WWW www.egroupware.org

Geschäftsführung Ralf und Birgit Becker
Registergericht Kaiserslautern HRB 3587
el_es el_es
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem updating from EGW 1.8 to 16.1 EPL

In reply to this post by StefS
On 27/04/17 20:00, S. Seide wrote:

> Hello,
>
> i try to update my old egroupware installation to the current
> 16.1.20170415 release, using the OpenSUSE Build service deb packages for
> Debian 8.
>
> I used a new VM, just installed mariadb 10, apache2 and php5.6 before
> the egroupware packages.
>
> After installation of the egroupware-epl package (that only worked using
> cli with "apt-get install egroupware-epl and not via interactive session
> with aptitude) i had an first installation. Than i dropped the
> egroupware database and restored my old egroupware 1.8 one.
>
[...]

why this way ? why dropping the database ?

Migrating to 16.x from 1.8x worked for me so far when I 'just' restored the
backup without dropping the database (this means : when freshly installed the 16.x,
when it's completely fresh, go to the /setup and restore the data from a backup made in 1.8.x-
this can take A LONG TIME on some machines depending on how much data is there -
but i (as a trial) restored 2 instances that way, even from 2 'single domain' installs to
one 'multi domain' install)

> Some help is appreciated...
>
> Thanks in advance,
> S. Seide
>
-L.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
eGroupWare-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/egroupware-users
StefS StefS
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem updating from EGW 1.8 to 16.1 EPL

In reply to this post by StefS
Thanks for the answers - doing a fresh install, than importing the
backup via Setup-GUI and updating database tables afterwards was working
without error.

> Migrating to 16.x from 1.8x worked for me so far when I 'just'
> restored the backup without dropping the database (this means : when >
freshly installed the 16.x, when it's completely fresh, go to the
> /setup and restore the data from a backup made in 1.8.x- this can
> take A LONG TIME on some machines depending on how much data is
> there - but i (as a trial) restored 2 instances that way, even from
> 2 'single domain' installs to one 'multi domain' install)

@Lukasz Sokol:
Can you please provide some more information on your way to create one
new multi domain server from two single instance backups?
I think about splitting my existing system into two domains via
importing the (modified) backup twice and deleting some of the users for
each new domain...

Thanks,
S. Seide


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
eGroupWare-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/egroupware-users
el_es el_es
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Problem updating from EGW 1.8 to 16.1 EPL

On 03/05/17 10:32, S. Seide wrote:

> Thanks for the answers - doing a fresh install, than importing the
> backup via Setup-GUI and updating database tables afterwards was working
> without error.
>
>> Migrating to 16.x from 1.8x worked for me so far when I 'just'
>> restored the backup without dropping the database (this means : when >
> freshly installed the 16.x, when it's completely fresh, go to the
>> /setup and restore the data from a backup made in 1.8.x- this can
>> take A LONG TIME on some machines depending on how much data is
>> there - but i (as a trial) restored 2 instances that way, even from
>> 2 'single domain' installs to one 'multi domain' install)
>
> @Lukasz Sokol:
> Can you please provide some more information on your way to create one
> new multi domain server from two single instance backups?
> I think about splitting my existing system into two domains via
> importing the (modified) backup twice and deleting some of the users for
> each new domain...
>
> Thanks,
> S. Seide
>

Yes :

- first, when installed fresh, you go to the Header Setup, as header admin,
and create as many database instances as you need (when installed, it shows one already in,
so you need to create as many as you think you need) - each with their own
database name, and database user/password combination;

- then your /etc/apache2/conf.d/egroupware (or a corresponding Apache .conf file for your
distribution - I used Debian 7 / Wheezy here) need to be edited to add the 2 disparate domains
and restart Apache;

- then back to setup - you will see the domain choice there above the management username field - select the one you want;
 - you need to go through the setup steps for each domain including database creation and editing the configuration;
   - in the 'edit your current configuration' step, pay attention to
   "Enter the location of EGroupware's URL."  field - needs to be set up appropriately for each domain
    EXACTLY as you got it in the apache conf file for the vhost.

- and in the last steps of the above, 'just' restore your db backup to each domain.

This lets you access your 2 disparate egw domains as

https://your.server.address/egroupwarefirstdomain
and
https://your.server.address/egroupwareotherdomain

and still needs to have access to

https://your.server.address/egroupware - in fact , it probably is advised so,
as you select your domain at this point when logging in as 'normal user'.



(I wrote this in a post to this group/mailing list on 30/03/17 10:04 : )

Quote:
"
in /etc/apache2/conf.d/egroupware file I have added:

# this makes EGroupware available for all vhosts
Alias /egroupware /usr/share/egroupware

# to run 2 disparate domains
Alias /egroupwaredomain1 /usr/share/egroupware
Alias /egroupwaredomain2 /usr/share/egroupware

and in each domain's setup (through config admin) :

"Enter the location of EGroupware's URL." : /egroupwaredomain1
and
"Enter the location of EGroupware's URL." : /egroupwaredomain2

now when I log in to one (e.g. select domain 1)

then go to /egroupware/login again and select domain2,

I now have 2 concurrent views of disparate set of data open in nearby tabs :) logged in as a different username into each one;

Which seems to be AMAZING if it is THIS simple. Hope I did not omit something important?"

(emphasis on the last question)...

(I still don't really know how would I need to configure this to have access of like
 https://firstvps.myserver.address/egroupware and
 https://othervps.myserver.address/egroupware ... this info is somehow sparse to find)

Hope this helps,
also you're doing it at your own risk and all that ;) the steps above seemed to have worked for me, but YMMV.

Kind Regards
Lukasz




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
eGroupWare-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/egroupware-users
Loading...