typo indeed, I got no permission errors.
So, I fiddled around with the permissions, got some action then and it turned out also my log files and indexed had changes made to the permissions and/or owner settings after the update. Error messages helped me to fix these one by one and once all these were set it started complaining about the fact I had an old Xpack file. Finally after removing that one it started to work again.
It still does not want to run on boot using my previous settings but ok, I can always reconstruct these ones. At least using the command line ES started working again.
Unfortunately, now Kibana is playing nasty. Same issues, permissions and groups were changed all over the place, modified them all again, got complaints about xPack as for ES, was not able to remove using the normal commands but removing manually seemed to fix this and now I can start it also from the command line again.
But, I still can't open it in the browser now. Kibana starts complaining giving below message :
[no_shard_available_action_exception] No shard available for [get [.kibana][doc][config:6.3.0]: routing [null]] :: {"path":"/.kibana/doc/config%3A6.3.0","query":{} ,"statusCode":503,"response":"{"error":{"root_cause":[{"type":"no_shard_available_action_exception","reason":"No shard available for [get [.kibana][doc][config:6.3.0]: routing [null]]"}],"type":"no_shard_available_a ction_exception","reason":"No shard available for [get [.kibana][doc][config:6.3.0]: routing [null]]"},"status":503}"}
Any idea what goes wrong now ?