Glenn Strouhal

Also I suspect this is related but the ini to xml conversion utility added the following to the new XML file: <NotificationFragments> <BackgroundServiceFragment name="BackgroundServiceFragment:0"> <BackgroundServiceHost><![CDATA[localhost]]></BackgroundServiceHost> <BackgroundServicePort><![CDATA[4444]]></BackgroundServicePort> <BackgroundServiceJobChainName><![CDATA[/sos/jade/jade_history]]></BackgroundServiceJobChainName> </BackgroundServiceFragment> </NotificationFragments> And in individual profiles,...

This is probably an easy, maybe even stupid, question but after upgrading from 1.11.6 to 1.13.11, I can't seem to get what was formerly called a HistoryFileName. I was using INI before. This is what I added to the XML file. Is this not the new equivalent? <General> <Logging> <LogFile><![CDATA[${HOME}/logs/yade_history.csv]]></LogFile> </Logging>

Thank you so much. I got the updated file. You should know that the default Download button points to sosftp_client.0.9.1.tar.gz!

Solved. That log4j bridge does not translate everything to 2.X. That special renderer is an example of something that log4j-1.2-api-2.17.0.jar does not handle so if anyone else encounters this know that you are just out of luck with a drop in fix.

Anyone still watching this forum? We are currently running 1.11.6 on Linux and I am trying to migrate from the installed log4j-1.2.16.jar by using the log4j 1.x bridge. Unsuccessfull so far. I've different tried different variations of jar files but they all give the same error. Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/log4j/or/RendererMap at org.apache.log4j.Hierarchy.<init>(Hierarchy.java:97) at org.apache.log4j.LogManager.<clinit>(LogManager.java:82) at org.apache.log4j.Logger.getLogger(Logger.java:117)...

Magnus, Here is part of my 1.11 config. Be sure you are using the older keepass database. [globals] include = MailSettings , JADEHistory, BackgroundService title = Global Profile thishost = ${LOCALIP} basedir = ${HOME} serverenv = ${SERVERENV} yadeenv1 = ${YADEENV1} yadeenv2 = ${YADEENV2} targetenv = ${TARGETENV} kpdb = ${KPDB} ;; ;; Default Transfer Settings ;If you transfer files via SFTP then we recommend the following option to increase the transfer speed: load_class_name = com.sos.VirtualFileSystem.SFTP.SOSVfsSFtpJCraft...

Hello, This week I have run into a nasty issue. I am using Linux based YADE 1.11.6. We are slowly bringing a new system online and one particular profile found thousands of files to transfer to the new environment. All other profiles run fine including those that might find 100+ files. In the problem profile, all files do transfer successfully, the post cmd runs successfully, but during the delete off of the source system there is always a failure to delete a file. The file appears to be different...