Differences

This shows you the differences between two versions of the page.

Link to this comparison view

fujitsu:hpcgateway:guides:admin:install:installation_update_install_1.1.2 [2016/06/29 16:32] (current)
Line 1: Line 1:
 +===== Manual operation after an update to core 1.1.2 =====
 +
 +HPCG version : 3.2.2
 +
 +Torii version : 1.1.2
 +
 +----
 +
 +==== hpcgadmin can not login due to the UID threshold ====
 +
 +We changed the threshold in /​opt/​hpcg/​core/​jetty/​etc/​login.conf
 +
 +<​code>​
 +13:​51:​56,​329 ​ WARN qtp1858609436-34 com.fujitsu.fse.torii.authentication.SshLoginModule:​228 - Cannot login with the account '​hpcgadmin'​ .It is considered as a service account ( 1002 <1025 )
 +[hpcgadmin@dex700 hpcg]$ vi core/​jetty/​etc/​login.conf
 +...
 +ssh-login-module {
 +   ​com.fujitsu.fse.torii.authentication.SshLoginModule required
 +   ​debug="​true"​
 +   ​hostname="​localhost"​
 +   ​port="​22"​
 +   ​uidMin="​1000";​
 +};
 +</​code>​
 +
 +----
 +
 +==== The monitor is not working ====
 +
 +We use robomongo to check the monitor phase for all the applications. In robomongo:
 +
 +<​code>​
 +db.applications.update({},​ { $addToSet: { phases: '​monitor'​ } }, {multi: true})
 +</​code>​
 +
 +----
 +
 +==== The shortcuts are broken ====
 +
 +The preferences and shortcuts collections are no more valid.
 +
 +We have to alter them directly with robomongo:
 +
 +<​code>​
 +## Clean the Preferences collection
 +db.preferences.update({},​ {$set: {'​settings':​ []}, set: {'​shortcuts':​ []}}, {multi: true})
 +</​code>​
 +
 +In the shell, restore favorites - change the cluster name by your cluster name.
 +
 +<​code>​
 +mongoexport --db Torii --collection preferences --out preferences.json
 +sed -i '​s/"​cluster":"​myclustername","​path"/"​clusterName":"​myclustername","​absolutePath"/​g'​ preferences.json
 +mongoimport --db Torii --collection preferences --drop --file preferences.json
 +</​code>​
 +
 +In robomongo:
 +
 +<​code>​
 +## Clean the shortcut collection
 +db.shortcuts.update({},​ {$rename: {'​user':'​owner'​},​ $set: {'​shared':​ true}, $unset: {'​removable':​ ''​}},​ {multi: true})
 +db.shortcuts.update({},​ {$unset: {'​tool':​ ''​}},​ {multi: true})
 +db.shortcuts.update({'​context.type':​null},​ {$set: {'​context.type',​ '​profile'​}},​ {multi: true}}
 +</​code>​
 +
 +----
 +
 +==== There is no mount point in the file explorer ====
 +
 +We create one mount point Root accessible for every member of Public.
 +
 +Change the cluster name and id to the one in your installation. Use robomongo to do so.
 +
 +<​code>​
 +{
 +     "​cluster"​ : {
 +        "​id"​ : "​5668270b9ee045755b37fc56",​
 +        "​name"​ : "​mycluster"​
 +    },
 +    "​name"​ : "​Root",​
 +    "​runnable"​ : true,
 +    "​description"​ : "Root directory",​
 +    "​absolutePath"​ : "/",​
 +    "​teams"​ : [
 +        {
 +            "​id"​ : "​568e3a3cddff3a6ccdaf92c8",​
 +            "​name"​ : "​Public"​
 +        }
 +    ],
 +    "​order"​ : 0
 +}
 +</​code>​