[07:49:19] <godog>	 !log tools resize tools-nfs-3 to match tools-nfs-2 (g4.cores16.ram64.disk20.10xiops) - T404584
[07:49:23] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[07:49:24] <stashbot>	 T404584: [tools,nfs,infra] Address tools NFS getting stuck with processes in D state - https://phabricator.wikimedia.org/T404584
[07:52:08] <godog>	 !log tools tools-nfs-3 is back - T404584
[07:52:11] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[08:53:23] <godog>	 !log tools shut down tools-nfs-2 - T404584
[08:53:28] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[08:53:28] <stashbot>	 T404584: [tools,nfs,infra] Address tools NFS getting stuck with processes in D state - https://phabricator.wikimedia.org/T404584
[16:08:11] <wm-bb>	 <ferdi2005> Hello, to access an instance which is in rescue mode should I just do ssh root@instance usual address?
[16:18:38] <wm-bb>	 <ferdi2005> Because I cannot find any docs on the rescue mode (re @ferdi2005: Hello, to access a Cloud VPS instance which is in rescue mode do I just do ssh root@instance usual address?)
[16:26:46] <bd808>	 @ferdi2005: If Horizon is showing an instance in rescue mode I think you probably will need help from a Cloud VPS admin to get things back. Which project is this in?
[17:25:19] <andrewbogott>	 hello! What is the instance name and project?
[17:25:35] <andrewbogott>	 I do not think I've ever seen a VM spontaneously marked as 'rescue'
[17:26:14] <andrewbogott>	 @ferdi2005 ^
[17:26:34] <andrewbogott>	 Oh, maybe you mean that on boot it drops into a rescue prompt
[17:46:38] <Guest94>	 function plugin_dir_path( $file ) {wwwzygnetcore.net_kiwiirc
[17:46:38] <Guest94>	    _return trailingslashit( dirname( $file ) );}
[17:58:14] <wm-bb>	 <ferdi2005> No no I have put it into rescue mode to fix a problem with the sssd daemon log file which makes me unable to SSH into it. It’s the wlmitvisual01 (re @wmtelegram_bot: <andrewbogott> Oh, maybe you mean that on boot it drops into a rescue prompt)
[17:58:32] <wm-bb>	 <ferdi2005> I need to recreate the log file to make it work
[18:02:17] <andrewbogott>	 There isn't a good way for you to access your VM other than ssh, so your scheme isn't likely to work. If you have a simple change you'd like me to make I might be able to do that from the root console.
[18:02:32] <andrewbogott>	 But most often in a scenario like this I'd suggest you just make a new VM
[18:05:25] <wm-bb>	 <ferdi2005> Yeah maybe, I think it would be easier to fix the problem. Do you have Telegram? Can I write to you privately? (re @wmtelegram_bot: <andrewbogott> There isn't a good way for you to access your VM other than ssh, so your scheme isn't likely to work. If you have...)
[18:06:29] <andrewbogott>	 Best if we continue the conversation here so that I'm not the only one helping you :)
[18:09:11] <wm-bb>	 <ferdi2005> Ok. I need to recreate sssd log file
[18:09:12] <wm-bb>	 <ferdi2005> sudo mkdir -p /var/log/sssd
[18:09:13] <wm-bb>	 <ferdi2005> sudo chmod 700 /var/log/sssd
[18:09:15] <wm-bb>	 <ferdi2005> sudo chown sssd:sssd /var/log/sssd (re @wmtelegram_bot: <andrewbogott> Best if we continue the conversation here so that I'm not the only one helping you :))
[18:09:21] <wm-bb>	 <ferdi2005> Thank you!