smbizuser

Q: Wiki fails during update to 5.1.5

Hello,

 

I am attempting to update a mac mini running OS X 10.11.3 and OS X Server (5.0.4)  to OS X 10.11.5 and OS X Server (5.1.5). There are no apparent issues running the OS update. However, once updated the newest version of OS X server (5.1.5) is required and this is where the wiki service becomes completely non functional. While running the setup for the new version of server I get this error message:

Screen Shot 2016-05-19 at 12.26.27 PM.png

It seems clear that the problem is related to a failure to update the wiki database (see logs below) but I have no idea how to go about fixing it.

 

From ServerSetup.log:

 

Jun 3 13:03:42.298 WikiServer<7fabe8fe4f30> Running 'wikiadmin updateSchema'

Jun 3 13:03:45.816 WikiServer<7fabe8fe4f30> Error running 'wikiadmin' [3518.474996 ms]

Jun 3 13:03:45.912 WikiServer<7fabe8fe4f30> 'wikiadmin' Error: The operation couldn’t be completed. (wikiadmin error 27.) [27]

Jun 3 13:03:45.912 WikiServer<7fabe8fe4f30> Running 'serveradmin stop collabd'

Jun 3 13:03:46.219 WikiServer<7fabe8fe4f30> 'serveradmin' succeeded [306.674004 ms]

 

From System.log:

 

Jun  3 13:32:43 inovati wikiadmin[10640]: [PGCConnection.m:176 7bc79000 +0ms] Error in TXN: Error executing query [CREATE TABLE migration_entity (entity_uid_fk   uuid PRIMARY KEY REFERENCES entity(uid))]: ERROR:  relation "migration_entity" already exists

 

  (

  0   CoreFoundation                      0x00007fff9ba594f2 __exceptionPreprocess + 178

  1   libobjc.A.dylib                     0x00007fff9d4f9f7e objc_exception_throw + 48

  2   PostgreSQLClient                    0x0000000106f80771 -[PGCConnection checkResultOK:forSQL:] + 700

  3   PostgreSQLClient                    0x0000000106f80c57 -[PGCConnection executeQuery:] + 238

  4   wikiadmin                           0x0000000106f34c74 wikiadmin + 281716

  5   wikiadmin                           0x0000000106f342b7 wikiadmin + 279223

  6   PostgreSQLClient                    0x0000000106f7fe53 -[PGCConnection transactionInBlock:onError:] + 78

  7   wikiadmin                           0x0000000106f34200 wikiadmin + 279040

  8   wikiadmin                           0x0000000106f34476 wikiadmin + 279670

  9   CSService                           0x0000000106faefac +[CSExecutionTimer recordTime:ofBlock:] + 76

  10  CSService                           0x0000000106faede5 +[CSExecutionTimer timerNamed:aroundBlock:] + 76

  11  wikiadmin                           0x0000000106f34385 wikiadmin + 279429

  12  wikiadmin                           0x0000000106f34b2e wikiadmin + 281390

  13  PostgreSQLClient                    0x0000000106f7fea2 -[PGCConnection transactionInBlock:onError:] + 157

  14  wikiadmin                           0x0000000106f345ec wikiadmin + 280044

  15  wikiadmin                           0x0000000106efce8a wikiadmin + 52874

  16  libdyld.dylib                       0x00007fff9b7ae5ad start + 1

  )

Jun  3 13:32:43 inovati wikiadmin[10640]: [main.m:771 7bc79000 +0ms] Caught top-level exception: [PGCQueryError] Error executing query [CREATE TABLE migration_entity (entity_uid_fk   uuid PRIMARY KEY REFERENCES entity(uid))]: ERROR:  relation "migration_entity" already exists

  , exiting

--------------------------------------

 

Any suggestions would be appreciated.

 

Thanks.

Mac mini, OS X El Capitan (10.11.3)

Posted on Jun 3, 2016 1:47 PM

Close

Q: Wiki fails during update to 5.1.5

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Jun 4, 2016 9:18 AM in response to smbizuser
    Level 10 (207,926 points)
    Applications
    Jun 4, 2016 9:18 AM in response to smbizuser

    This is why you should never update a server directly. Always expect the data migration to fail. You clone the startup volume to another drive and update that first. If it fails, all you have to do is reboot.


    You have two choices. One is to to restore the volume from one of the backups that you made right before updating. Then either skip the update or try to get Apple Enterprise Support to figure out what the problem is (which they probably can't.)


    The other choice is to adapt the instructions in this ASC thread. Wherever "postgresql9.2" occurs in those instructions, change it to "postgresql9.3". The file paths will also have to be changed. Success with this approach is by no means assured.

  • by smbizuser,

    smbizuser smbizuser Jun 6, 2016 9:27 AM in response to Linc Davis
    Level 1 (4 points)
    Servers Enterprise
    Jun 6, 2016 9:27 AM in response to Linc Davis

    Linc,

     

    Thanks for the feedback. I will try the instructions you linked.  I should have mentioned in the original post that I do in fact have multiple cloned backups of the startup volume and I am working from one of the clones on a separate computer.