git add-on: invalid SSH passphrase (and logging)
Posted: Sat Sep 10, 2022 2:43 am
I use my institute's git repo with the git add-on, and up till recently (modulo my post-pandemic comings and goings , which is to say that I am not sure what "recently" stands for, precisely), everything was fine but now, the add-on keeps telling me that the "previous SSH passphrase was invalid", and when I enter the same password as the one that I successfully use on the commandline, the client fails to connect and pops up the same dialog again. Resetting credentials hasn't helped. I have found a nice piece of advice by Sorin at post60238.html , suggesting that it's possible to enable logging of the add-on's errors. That would help a lot, but I can't seem to be able to get it to work.
Sorin says there:
I have created the file in the directory where oXygen is installed (~/Oxygen XML Editor 24) and tried both the "${user.home}" as well as absolute path of my home dir, but the oxygenLog/ directory isn't there in ~/Desktop although I've closed and reopened oXygen and fooled around with the add-on.
(I wasn't able to find "user.home" anywhere else, when grepping recursively across the installation directory, so I thought I'd make sure that it's not an obsolete variable name -- but neither option works).
Perhaps after the log4j crisis, logging is handled differently now? May I ask, in the first step, for confirmation that the snippet above should work at present?
Thanks in advance! :-)
Sorin says there:
For investigating the authentication problem, you could create a "log4j.properties" file inside Oxygen's installation folder with the following content:
Code: Select all
log4j.rootCategory=info, R2
log4j.appender.R2=org.apache.log4j.RollingFileAppender
log4j.appender.R2.File=${user.home}/Desktop/oxygenLog/oxygen.log
log4j.appender.R2.MaxFileSize=12000KB
log4j.appender.R2.MaxBackupIndex=20
log4j.appender.R2.layout=org.apache.log4j.PatternLayout
log4j.appender.R2.layout.ConversionPattern=%r %p [ %t ] %c - %m%n
log4j.category.com.oxygenxml.git=debug
(I wasn't able to find "user.home" anywhere else, when grepping recursively across the installation directory, so I thought I'd make sure that it's not an obsolete variable name -- but neither option works).
Perhaps after the log4j crisis, logging is handled differently now? May I ask, in the first step, for confirmation that the snippet above should work at present?
Thanks in advance! :-)