[midPoint] Upgrade from 3.6 to 3.7 (standalone) leaves ownerref empty on tasks, can't start midPoint

[Pavol Mederly]

The Ninja tool can be used like this:

1) Do an export of users to see if the hypothesis is true and if so, to 
learn OID of the "wrong" administrator.

java [-cp <jdbc_driver_jar>] -jar ninja.jar --midpoint-home <midpoint 
home dir> *export -t USER*

2) Find OID of the conflicting object and delete it (in this sample I 
have chosen to delete 00000000-0000-0000-0000-000000000160):

java [-cp <jdbc_driver_jar>] -jar ninja.jar --midpoint-home <midpoint 
home dir> *delete -o 00000000-0000-0000-0000-000000000160 -r -a*

It then goes like this:

Initializing repository using midpoint home
Starting delete
Do you really want to delete object 
'report:00000000-0000-0000-0000-000000000160(Certification decisions 
report)'? Yes/No/Cancel
Yes
Delete finished. Processed: 1 objects, avg. 12414,0ms

And then you can just restart midPoint and have the correct 
"administrator" object be imported.

Hope this helps.

Pavol Mederly
Software developer
evolveum.com

On 06.02.2018 10:32, Pavol Mederly wrote:
>
> Hello Ramón,
>
> after looking at the logs I think the situation is like this:
>
>  1. there is no object with OID 00000000-0000-0000-0000-000000000002
>  2. however, there is some user with the name of "administrator"
>     (before or after normalization, so the name could be e.g.
>     "Administrator")
>
> Because of (1), initial import procedure tries to import file 
> 050-user-administrator.xml. And because of (2) the import fails.
>
> It should be possible to fix that using various means, e.g. by 
> manually renaming or deleting the conflicting object in the repo, but 
> I would suggest using the Ninja 
> <https://wiki.evolveum.com/display/midPoint/Ninja> tool. (It has also 
> a delete option that is not shown in the wiki. Just start it and it 
> will print the help to sysout.)
>
> I will try that and provide you with a sample usage; but just now I 
> have to go offline for a while. You can try it in the meanwhile if you 
> want.
>
> Pavol Mederly
> Software developer
> evolveum.com
> On 25.01.2018 15:49, Ramón Cahenzli wrote:
>> Hi again Pavol and everyone,
>>
>> Unfortunately, the issue does not stay fixed even when I manually
>> assign owners to the tasks. Sooner or later they appear to lose their
>> owners.
>>
>> I tried an upgrade to 3.7 based on this supposedly fixed data, but
>> midPoint never really starts. It attempts to start and then throws
>> exceptions, see attached log file.
>>
>> If I read things correctly, it tries to create an administrator user
>> even though there is one already. I'm happy to supply logs that are more
>> interesting.
>>
>> Cheers and thanks,
>>
>>
>>
>>
>> _______________________________________________
>> midPoint mailing list
>> midPoint at lists.evolveum.com
>> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20180206/4c8a642b/attachment.htm>