JZ006 connection refused

CentOS 7.3 安装SYBASE ASE 16.0时遇到JZ006连接拒绝问题及解决方案
在CENTOS 7.3.1611上安装SYBASE Adaptive Server Enterprise 16.0时,遭遇JZ006错误,导致Job Scheduler 'LOCALHOST_JSAGENT'安装失败。错误源于IOException: Connection refused。解决方案是禁用IPv6。
CENTOS 7.3.1611

SYBASE ase 16.0安装时出现错误:


Building Job Scheduler 'LOCALHOST_JSAGENT':
Writing entry into directory services...
Directory services entry complete.
Installing required script(s) in related SAP Adaptive Server Enterprise...
installjsdb: 10% complete.
installjsdb: 20% complete.
installjsdb: 30% complete.
installjsdb: 40% complete.
installjsdb: 50% complete.
installjsdb: 60% complete.
installjsdb: 70% complete.
installjsdb: 80% complete.
installjsdb: 90% complete.
installjsdb: 100% complete.
jst_get_object_quoted_name: 10% complete.
jst_get_object_quoted_name: 20% complete.
jst_get_object_quoted_name: 30% complete.
jst_get_object_quoted_name: 100% complete.
jst_check_reorg_space: 10% complete.
jst_check_reorg_space: 20% complete.
jst_check_reorg_space: 30% complete.
jst_check_reorg_space: 100% complete.
jst_database_names: 10% complete.
jst_database_names: 20% complete.
jst_database_names: 30% complete.
jst_database_names: 100% complete.
jst_get_index_names: 10% complete.
jst_get_index_names: 20% complete.
jst_get_index_names: 30% complete.
jst_get_index_names: 100% complete.
jst_get_datachange: 10% complete.
jst_get_datachange: 20% complete.
jst_get_datachange: 100% complete.
jst_get_datestr: 10% complete.
jst_get_datestr: 20% complete.
jst_get_datestr: 30% complete.
jst_get_datestr: 100% complete.
jst_get_freespace: 10% complete.
jst_get_freespace: 20% complete.
jst_get_freespace: 100% complete.
jst_get_mdcache_type_config: 10% complete.
jst_get_mdcache_type_config: 20% complete.
jst_get_mdcache_type_config: 30% complete.
jst_get_mdcache_type_config: 40% complete.
jst_get_mdcache_type_config: 100% complete.
jst_get_usedspace: 10% complete.
jst_get_usedspace: 20% complete.
jst_get_usedspace: 100% complete.
jst_reconf_mdcache_type: 10% complete.
jst_reconf_mdcache_type: 20% complete.
jst_reconf_mdcache_type: 30% complete.
jst_reconf_mdcache_type: 100% complete.
jst_version_num: 10% complete.
jst_version_num: 20% complete.
jst_version_num: 30% complete.
jst_version_num: 100% complete.
jst_valid_ase_version: 10% complete.
jst_valid_ase_version: 20% complete.
jst_valid_ase_version: 30% complete.
jst_valid_ase_version: 40% complete.
jst_valid_ase_version: 50% complete.
jst_valid_ase_version: 100% complete.
jst_delete_statistics: 10% complete.
jst_delete_statistics: 20% complete.
jst_delete_statistics: 30% complete.
jst_delete_statistics: 100% complete.
jst_dump_databases: 10% complete.
jst_dump_databases: 20% complete.
jst_dump_databases: 30% complete.
jst_dump_databases: 40% complete.
jst_dump_databases: 50% complete.
jst_dump_databases: 60% complete.
jst_dump_databases: 100% complete.
jst_dump_logs: 10% complete.
jst_dump_logs: 20% complete.
jst_dump_logs: 30% complete.
jst_dump_logs: 40% complete.
jst_dump_logs: 50% complete.
jst_dump_logs: 60% complete.
jst_dump_logs: 70% complete.
jst_dump_logs: 100% complete.
jst_reclaim_index_space: 10% complete.
jst_reclaim_index_space: 20% complete.
jst_reclaim_index_space: 30% complete.
jst_reclaim_index_space: 100% complete.
jst_reclaim_table_space: 10% complete.
jst_reclaim_table_space: 20% complete.
jst_reclaim_table_space: 30% complete.
jst_reclaim_table_space: 100% complete.
jst_reconf_locks: 10% complete.
jst_reconf_locks: 20% complete.
jst_reconf_locks: 100% complete.
jst_reconf_mdcache: 10% complete.
jst_reconf_mdcache: 20% complete.
jst_reconf_mdcache: 100% complete.
jst_reconf_usr_conns: 10% complete.
jst_reconf_usr_conns: 20% complete.
jst_reconf_usr_conns: 30% complete.
jst_reconf_usr_conns: 100% complete.
jst_reorg_rebuild_indexes: 10% complete.
jst_reorg_rebuild_indexes: 20% complete.
jst_reorg_rebuild_indexes: 100% complete.
jst_reorg_rebuild_tables: 10% complete.
jst_reorg_rebuild_tables: 20% complete.
jst_reorg_rebuild_tables: 30% complete.
jst_reorg_rebuild_tables: 100% complete.
jst_update_statistics: 10% complete.
jst_update_statistics: 20% complete.
jst_update_statistics: 30% complete.
jst_update_statistics: 40% complete.
jst_update_statistics: 100% complete.
jst_svr_update_statistics: 10% complete.
jst_svr_update_statistics: 20% complete.
jst_svr_update_statistics: 30% complete.
jst_svr_update_statistics: 40% complete.
jst_svr_update_statistics: 50% complete.
jst_svr_update_statistics: 100% complete.
Installing SybBackupDbToDiskTemplate.xml in the SAP Adaptive Server
Enterprise...
Task failed

----------------------------------------------------------------
                  W E L C O M E   T O

  TemplateImport Utility [version 1.11]    Feb 18, 2017 1:52:59 PM

    Runtime Switches:

    TemplateImport Properties:

               Server_Machine_Name: localhost
                       Server_Name: LOCALHOST
                       Server_Port: 5000
     Template_Description_Override: Dumps specified database(s).
      Template_Group_Path_Override: Backups
                 Template_Language: en
            Template_Name_Override: Backup Database to Disk Template
         Template_Version_Override: 3.1
                 Template_XML_File: /opt/sap/ASE-16_0/jobscheduler/Templates/xml/en/SybBackupDbToDiskTemplate.xml
----------------------------------------------------------------
Reading XML File: /opt/sap/ASE-16_0/jobscheduler/Templates/xml/en/SybBackupDbToDiskTemplate.xml
XML File Read Completed Successfully
Creating Initial Template Record
SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused
SQLException during getConnection: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused
Exception  : SQLException when trying to connect
SQLException: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused
Exception in thread "main" java.lang.NullPointerException: while trying to invoke the method com.sybase.util.template.Connection.execUpdate(java.lang.String) of a null object loaded from field com.sybase.util.template.TemplateBase._conn of an object loaded from local variable 'this'
    at com.sybase.util.template.TemplateBase.execUpdate(TemplateBase.java:3296)
    at com.sybase.util.template.TemplateBase.createTemplate(TemplateBase.java:2311)
    at com.sybase.util.template.TemplateImport.importTemplate(TemplateImport.java:436)
    at com.sybase.util.template.TemplateImport.mainRoutine(TemplateImport.java:360)
    at com.sybase.util.template.TemplateImport.main(TemplateImport.java:348)
Server 'LOCALHOST_JSAGENT' was not created.

解决方法为:
禁用 IPV6

"Connection refused (Connection refused)"是一种网络连接错误,表示客户端无法连接到服务器。这种错误可能由多种原因引起。引用提供了一些可能导致此错误的原因和解决方法: 1)端口号被占用:需要杀死占用端口号的进程,释放端口,重新启动项目或彻底关闭Tomcat服务器。 2)服务器未运行或未监听端口:需要检查服务器是否正在运行并侦听正确的端口。 3)客户端和服务器之间没有网络连接:可能是因为客户端或服务器没有连接到任何网络,需要确保网络连接正常。 4)防火墙限制:如果企业网络受到防火墙保护,需要确保防火墙允许客户端与服务器的IP地址和端口号之间的连接。 5)连接字符串中的协议不正确:需要确保连接字符串中传递的协议与服务器期望的协议一致。 总结来说,"Connection refused (Connection refused)"错误可能是由于端口被占用、服务器未运行或未监听端口、网络连接问题、防火墙限制或连接字符串中的协议不正确等原因引起的。您可以根据具体情况检查并解决这些问题。<span class="em">1</span><span class="em">2</span> #### 引用[.reference_title] - *1* [putty connection refused问题](https://download.csdn.net/download/mowang12527210/10291215)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] - *2* [Connection refused: connect问题解决方案集合](https://blog.csdn.net/TomHaveNoCat/article/details/82868336)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值