Kettle从Windows环境迁移到Linux运行报错

 

将Windows环境下的Kettle安装包,解压到Linux环境后,启动测试JOB运行报错如下:

[root@hehe001 data-integration]# ./pan.sh -file=/usr/local/kettle/kettleFile/dome.ktr 
03:13:12,690 INFO  [KarafInstance] 
*******************************************************************************
*** Karaf Instance Number: 1 at /usr/local/kettle/data-integration/./system ***
***   /karaf//data1                                                         ***
*** Karaf Port:8801                                                         ***
*** OSGI Service Port:9050                                                  ***
*******************************************************************************
九月 10, 2018 3:13:29 上午 org.apache.karaf.main.Main$KarafLockCallback lockAquired
INFO: Lock acquired. Setting startlevel to 100
D:\JobPerationSoftware\Kettle\data-integration\system\karaf/deploy does not exist, please create it.
Root path does not exist: /usr/local/kettle/data-integration/D:\JobPerationSoftware\Kettle\data-integration\system\karaf/deploy
2018/09/10 03:13:33 - cfgbuilder - Warning: The configuration parameter [org] is not supported by the default configuration builder for scheme: sftp
*ERROR* [org.osgi.service.cm.ManagedService, id=247, bundle=47/mvn:org.apache.aries.transaction/org.apache.aries.transaction.manager/1.1.1]: Unexpected problem updating configuration org.apache.aries.transaction
java.lang.ExceptionInInitializerError
	at org.apache.aries.transaction.internal.TransactionManagerService.<init>(TransactionManagerService.java:114)
	at org.apache.aries.transaction.internal.Activator.updated(Activator.java:63)
	at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:148)
	at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:81)
	at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1448)
	at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1404)
	at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103)
	at java.lang.Thread.run(Thread.java:722)
Caused by: java.util.MissingResourceException: Can't find bundle for base name org.apache.aries.transaction.txManager, locale zh_CN
	at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1499)
	at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1322)
	at java.util.ResourceBundle.getBundle(ResourceBundle.java:1028)
	at org.apache.aries.util.nls.MessageUtil.createMessageUtil(MessageUtil.java:152)
	at org.apache.aries.util.nls.MessageUtil.createMessageUtil(MessageUtil.java:107)
	at org.apache.aries.transaction.internal.NLS.<clinit>(NLS.java:25)
	... 8 more
2018-09-10 03:13:37.576:INFO:oejs.Server:jetty-8.1.15.v20140411
2018-09-10 03:13:37.755:INFO:oejs.AbstractConnector:Started NIOSocketConnectorWrapper@0.0.0.0:9050
log4j:ERROR Could not parse url [file:/usr/local/kettle/data-integration/./system/osgi/log4j.xml].
java.io.FileNotFoundException: /usr/local/kettle/data-integration/./system/osgi/log4j.xml (没有那个文件或目录)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.<init>(FileInputStream.java:138)
	at java.io.FileInputStream.<init>(FileInputStream.java:97)
	at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
	at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
	at org.apache.log4j.xml.DOMConfigurator$2.parse(DOMConfigurator.java:765)
	at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:871)
	at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:778)
	at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
	at org.apache.log4j.LogManager.<clinit>(LogManager.java:127)
	at org.apache.log4j.Logger.getLogger(Logger.java:104)
	at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:262)
	at org.apache.commons.logging.impl.Log4JLogger.<init>(Log4JLogger.java:108)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
	at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1025)
	at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:844)
	at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:541)
	at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:292)
	at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:269)
	at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:657)
	at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.<clinit>(ContextLoaderListener.java:253)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
	at java.lang.Class.newInstance0(Class.java:374)
	at java.lang.Class.newInstance(Class.java:327)
	at org.apache.felix.framework.Felix.createBundleActivator(Felix.java:4362)
	at org.apache.felix.framework.Felix.activateBundle(Felix.java:2149)
	at org.apache.felix.framework.Felix.startBundle(Felix.java:2072)
	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1299)
	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
	at java.lang.Thread.run(Thread.java:722)
log4j:WARN No appenders could be found for logger (org.springframework.osgi.extender.internal.activator.ContextLoaderListener).

这是由于缓存文件造成的错误,只需要找到..\pdi-ce-6.0.1.0-386\data-integration\system\karaf目录下缓存文件删除即可:如报错所示,删除 data1文件夹及其文件:rm -rf data1

再次执行后可以正常执行。

以下时成功的日志:

[root@hehe001 data-integration]# ./pan.sh -file=/usr/local/kettle/kettleFile/dome.ktr 
03:27:02,399 INFO  [KarafInstance] 
*******************************************************************************
*** Karaf Instance Number: 1 at /usr/local/kettle/data-integration/./system ***
***   /karaf//data1                                                         ***
*** Karaf Port:8801                                                         ***
*** OSGI Service Port:9050                                                  ***
*******************************************************************************
九月 10, 2018 3:27:19 上午 org.apache.karaf.main.Main$KarafLockCallback lockAquired
INFO: Lock acquired. Setting startlevel to 100
2018/09/10 03:27:22 - cfgbuilder - Warning: The configuration parameter [org] is not supported by the default configuration builder for scheme: sftp
03:27:32,653 ERROR [KarafLifecycleListener] The Kettle Karaf Lifycycle Listener failed to execute properly. Releasing lifecycle hold, but some services may be unavailable.
2018/09/10 03:27:32 - Pan - 开始运行.
2018/09/10 03:27:32 - dome - 为了转换解除补丁开始  [dome]
2018/09/10 03:27:33 - 表输出.0 - Connected to database [192.168.0.104 - myschool] (commit=1000)
2018/09/10 03:27:33 - 查询学生表.0 - Finished reading query, closing connection.
2018/09/10 03:27:33 - 查询学生表.0 - 完成处理 (I=10, O=0, R=0, W=10, U=0, E=0
2018/09/10 03:27:33 - 表输出.0 - 完成处理 (I=0, O=10, R=10, W=10, U=0, E=0
2018/09/10 03:27:33 - Pan - 完成!
2018/09/10 03:27:33 - Pan - 开始=2018/09/10 03:27:32.783, 停止=2018/09/10 03:27:33.397
2018/09/10 03:27:33 - Pan - 0 秒后处理结束.
2018/09/10 03:27:33 - dome -  
2018/09/10 03:27:33 - dome - 进程 查询学生表.0 成功结束, 处理了 10 行. ( - 行/秒)
2018/09/10 03:27:33 - dome - 进程 表输出.0 成功结束, 处理了 10 行. ( - 行/秒)

 

 

博主原创,转载请注明出处: https://blog.csdn.net/qq_36698956

版权声明:博客对我来说是记忆的笔记和知识的分享~此博文为博主原创转载请注明出处即可~   

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值