Solved

Cannot view sybase SCC in browser using Linux

Posted on 2013-06-15
5
1,786 Views
Last Modified: 2013-07-15
I tried with open sybase SCC in browser but the web page return page could not be found, I have verified scc is started and process is running in Linux. why the web browser not allow me to access scc ?
SCC-

scc processscc started
0
Comment
Question by:motioneye
  • 3
  • 2
5 Comments
 
LVL 21

Accepted Solution

by:
Mazdajai earned 500 total points
ID: 39249933
Check if firewall is running and port 8282 is listening.
You can verify them with iptables and netstat.

Also post  service-config.xml from SCC and log from SCC -

SCC-<version>\services\EmbeddedWebContainer\service-config.xml
SCC-<version>\log

Open in new window

0
 

Author Comment

by:motioneye
ID: 39250345
I looked at status of the EmbeddedWebContainer, it says status "false"

<?xml version="1.0" encoding="ISO-8859-1"?>
<service-config
      id="EmbeddedHttpService" version="3.2.0"
      name="Embedded Web Container Service"
      class="com.sybase.ua.services.http.EmbeddedHttpService"
      provider-name="Sybase, Inc."
      register-on-startup="false"
      mbean-type="Model MBean"
      mbean-descriptor="mbean-descriptor.xml"
      arl-config="arl.xml" >
      
  <properties>    
    <set-property property="http.provider.directory" value="container/Jetty-7.6.2.v20120308" migrate="false" since="3.2.7" />
    <set-property property="http.port" value="8282" />
    <set-property property="https.port" value="8283" />
    <set-property property="http.ssl.enabled" value="true" />
    <set-property property="https.ssl.keystore.file" value="keystore" />
    <set-property property="https.ssl.truststore.file" value="cacerts" />
    <set-property property="https.ssl.keystore.password" value="REVTe1NZVUFGfWNvbS5zdW4uY3J5cHRvLnByb3ZpZGVyLlN1bkpDRXtTWVVBRn1pcVJzMGh3WlVuRE9RSDJDN1NPUXhBPT0=" />
    <set-property property="https.ssl.truststore.password" value="REVTe1NZVUFGfWNvbS5zdW4uY3J5cHRvLnByb3ZpZGVyLlN1bkpDRXtTWVVBRn1pcVJzMGh3WlVuRE9RSDJDN1NPUXhBPT0=" />
    <set-property property="jetty.maxFormContentSize" value="2000000" />
   
    <set-property property="http.jetty.MaxPendingTaskQueueSize" value="1000" />
    <set-property property="http.jetty.ThreadPoolCoreSize" value="16" />
    <set-property property="http.jetty.ThreadPoolMaxSize" value="128" />
    <set-property property="http.jetty.ThreadPoolMaxIdleTime" value="1" />
    <set-property property="http.jetty.ThreadPoolMaxIdleTimeUnit" value="MINUTES" />
   
  </properties>
 
  <!-- is there a need to explicitly add security service as a dependency?  -->
  <!--  this dependency is strictly for getting the appropriate library dependencies for the scc.war -->
  <dependencies>
    <dependency type="service" id="SccService" version="3.1.0" auto-unregister-when-not-referenced="false" auto-unregister-grace-period="30" />
    <dependency type="service" id="RepositoryService" version="3.1.0" auto-unregister-when-not-referenced="false" auto-unregister-grace-period="30" />
  </dependencies>
 
  <!-- Optional logger configuration added since v2.5.0 -->
  <loggers>
    <!-- default log configuration to delegate to parent (agent) log -->
    <logger name="com.sybase.ua.services.http" level="INFO"/>
  </loggers>  
</service-config>
 


**********************************************************************


SCC Log on start up

2013-06-16 00:47:18,590 [INFO ] [startup.Main                                 ] [main] - Agent Home:            /opt/sybase/SCC-3_2
2013-06-16 00:47:18,594 [INFO ] [startup.Main                                 ] [main] - Agent Version:         SCC Framework Server 3.2.7.4817
2013-06-16 00:47:18,594 [INFO ] [startup.Main                                 ] [main] - Node:                  localhost.localdomain(127.0.0.1)
2013-06-16 00:47:18,594 [INFO ] [startup.Main                                 ] [main] - RMI Address:           localhost.localdomain(127.0.0.1)
2013-06-16 00:47:18,595 [INFO ] [startup.Main                                 ] [main] - RMI Port:              9999
2013-06-16 00:47:18,595 [INFO ] [startup.Main                                 ] [main] - OS Name:               Linux
2013-06-16 00:47:18,595 [INFO ] [startup.Main                                 ] [main] - OS Version:            2.6.32-358.el6.x86_64
2013-06-16 00:47:18,595 [INFO ] [startup.Main                                 ] [main] - OS Architecture:       amd64
2013-06-16 00:47:18,596 [INFO ] [startup.Main                                 ] [main] - Platform:              linux
2013-06-16 00:47:18,596 [INFO ] [startup.Main                                 ] [main] - Bitwidth:              64
2013-06-16 00:47:18,790 [INFO ] [startup.Main                                 ] [main] - Available Processors:  4
2013-06-16 00:47:18,807 [INFO ] [startup.Main                                 ] [main] - Total Physical Memory: 1869 MB
2013-06-16 00:47:18,807 [INFO ] [startup.Main                                 ] [main] - Free Physical Memory:  1027 MB
2013-06-16 00:47:18,808 [INFO ] [startup.Main                                 ] [main] - java.library.path:     /opt/sybase/SCC-3_2/rtlib:/opt/sybase/SCC-3_2/bin/sa/bin_linux64
2013-06-16 00:47:18,808 [INFO ] [startup.Main                                 ] [main] - Java Home:             /opt/sybase/shared/JRE-7_0_1_64BIT
2013-06-16 00:47:18,808 [INFO ] [startup.Main                                 ] [main] - Java Version:          1.7.0_01
2013-06-16 00:47:18,808 [INFO ] [startup.Main                                 ] [main] - Java VM Version:       21.1-b02
2013-06-16 00:47:18,808 [INFO ] [startup.Main                                 ] [main] - VM Process ID          3523@localhost.localdomain
2013-06-16 00:47:18,810 [INFO ] [startup.Main                                 ] [main] - VM Arguments:          -Xms128m, -XX:MaxPermSize=128m, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath="/opt/sybase/SCC-3_2/log", -Dcom.sybase.home=/opt/sybase, -Dcom.sybase.ua.toplevel=/opt/sybase/SCC-3_2, -Dcom.sybase.ua.home=/opt/sybase/SCC-3_2, -Dcom.sybase.platform=linux, -Djava.library.path=/opt/sybase/SCC-3_2/rtlib:/opt/sybase/SCC-3_2/bin/sa/bin_linux64, -Djava.security.policy=/opt/sybase/SCC-3_2/conf/java.policy, -Djava.util.logging.manager=com.sybase.ua.util.logging.bridge.JavaToLog4jLogManager, -Dcom.sybase.security.BootstrapConfigurationURL=file:////opt/sybase/SCC-3_2/conf/csibootstrap.properties
2013-06-16 00:47:18,810 [INFO ] [startup.Main                                 ] [main] - Message level:         WARN
2013-06-16 00:47:18,974 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Initializing BootstrapService...
2013-06-16 00:47:18,974 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Starting BootstrapService...
2013-06-16 00:47:18,999 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Loading 7 primordial services...
2013-06-16 00:47:19,150 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Registered Agent Service
2013-06-16 00:47:19,156 [INFO ] [services.Agent                               ] [Agent Bootstrap Thread] - Initializing Agent Service...
2013-06-16 00:47:19,156 [INFO ] [services.Agent                               ] [Agent Bootstrap Thread] - Starting Agent Service...
2013-06-16 00:47:19,180 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Registered Environment Service
2013-06-16 00:47:19,182 [INFO ] [services.EnvironmentDiscoveryService         ] [Agent Bootstrap Thread] - Initializing Environment Service...
2013-06-16 00:47:19,183 [INFO ] [services.EnvironmentDiscoveryService         ] [Agent Bootstrap Thread] - Starting Environment Service...
2013-06-16 00:47:19,200 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Registered Configuration Service
2013-06-16 00:47:19,203 [INFO ] [services.ConfigService                       ] [Agent Bootstrap Thread] - Initializing Configuration Service...
2013-06-16 00:47:19,203 [INFO ] [services.ConfigService                       ] [Agent Bootstrap Thread] - Starting Configuration Service...
2013-06-16 00:47:19,204 [INFO ] [services.ConfigService                       ] [Agent Bootstrap Thread] - Loading config XML: /opt/sybase/SCC-3_2/conf/agent-config.xml...
2013-06-16 00:47:19,241 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Registered Session Service
2013-06-16 00:47:19,244 [INFO ] [session.SessionService                       ] [Agent Bootstrap Thread] - Initializing Session Service...
2013-06-16 00:47:19,257 [INFO ] [session.SessionService                       ] [Agent Bootstrap Thread] - Starting Session Service...
2013-06-16 00:47:19,358 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Registered Security Service
2013-06-16 00:47:19,360 [INFO ] [security.SecurityService                     ] [Agent Bootstrap Thread] - Initializing Security Service...
2013-06-16 00:47:19,387 [INFO ] [security.SecurityService                     ] [Agent Bootstrap Thread] - Starting Security Service...
2013-06-16 00:47:19,610 [INFO ] [security.SecurityService                     ] [Agent Bootstrap Thread] - Security configuration: /opt/sybase/SCC-3_2/conf/csi_config.xml
2013-06-16 00:47:19,664 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Registered Service Registration Service
2013-06-16 00:47:19,665 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Initializing Service Registration Service...
2013-06-16 00:47:19,665 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Starting Service Registration Service...
2013-06-16 00:47:20,275 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Validated 19 extended services.
2013-06-16 00:47:20,275 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Check circular dependencies...
2013-06-16 00:47:20,280 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - OK. No circular dependencies are found.
2013-06-16 00:47:20,280 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - SelfDiscoveryService: Found 1 dependencies.
2013-06-16 00:47:20,280 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Dependent service RMIService needs to be registered...
2013-06-16 00:47:20,293 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - Initializing RMI Service...
2013-06-16 00:47:20,302 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - Starting RMI Service...
2013-06-16 00:47:20,330 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - RMI registry service started at port 9999.
2013-06-16 00:47:20,501 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - RMI Service listener address : localhost.localdomain/127.0.0.1
2013-06-16 00:47:20,501 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - RMI Service using dynamic listener address with java.rmi.server.hostname=localhost.localdomain
2013-06-16 00:47:20,510 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - Starting JMX Connector Server with address localhost.localdomain/127.0.0.1...
2013-06-16 00:47:20,534 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - RMI connector server started on localhost.localdomain/127.0.0.1.
2013-06-16 00:47:20,534 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - Agent URL in long format: service:jmx:rmi:///jndi/rmi://localhost.localdomain:9999/agent
2013-06-16 00:47:20,534 [INFO ] [rmi.RMIService                               ] [Agent Bootstrap Thread] - Agent URL in short format: rmi://localhost.localdomain:9999
2013-06-16 00:47:20,536 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - SelfDiscoveryService: successfuly resolved dependencies.
2013-06-16 00:47:20,554 [INFO ] [discovery.SelfDiscoveryService               ] [Agent Bootstrap Thread] - Initializing Self Discovery Service...
2013-06-16 00:47:20,554 [INFO ] [discovery.SelfDiscoveryService               ] [Agent Bootstrap Thread] - Starting Self Discovery Service...
2013-06-16 00:47:20,557 [INFO ] [discovery.SelfDiscoveryService               ] [Agent Bootstrap Thread] - Loaded discovery adaptor com.sybase.ua.services.discovery.SelfDiscoveryServiceUDPAdaptor
2013-06-16 00:47:20,577 [INFO ] [discovery.SelfDiscoveryService               ] [Agent Bootstrap Thread] - Loaded discovery adaptor com.sybase.ua.services.discovery.SelfDiscoveryServiceJiniAdaptor
2013-06-16 00:47:20,578 [INFO ] [discovery.UDPMulticastServer                 ] [UDPMulticastServerThread] - UDP listener started at port 4446
2013-06-16 00:47:20,641 [discovery.SelfDiscoveryService               ] [Agent Bootstrap Thread] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:47:20,644 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Jini Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,683 [INFO ] [ft.FileTransferService                       ] [Agent Bootstrap Thread] - Initializing File Transfer Service...
2013-06-16 00:47:20,699 [INFO ] [ft.FileTransferService                       ] [Agent Bootstrap Thread] - Starting File Transfer Service...
2013-06-16 00:47:20,699 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - SNMP Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,699 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - DeploymentService: Found 1 dependencies.
2013-06-16 00:47:20,700 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Dependent service RemoteShellService needs to be registered...
2013-06-16 00:47:20,729 [INFO ] [rshell.RemoteShellService                    ] [Agent Bootstrap Thread] - Initializing Remote Shell Service...
2013-06-16 00:47:20,729 [INFO ] [rshell.RemoteShellService                    ] [Agent Bootstrap Thread] - Starting Remote Shell Service...
2013-06-16 00:47:20,729 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - DeploymentService: successfuly resolved dependencies.
2013-06-16 00:47:20,746 [INFO ] [deployment.DeploymentService                 ] [Agent Bootstrap Thread] - Initializing Deployment Service...
2013-06-16 00:47:20,747 [INFO ] [deployment.DeploymentService                 ] [Agent Bootstrap Thread] - The template directories has been preset to: [/opt/sybase/SCC-3_2/templates]
2013-06-16 00:47:20,779 [INFO ] [deployment.DeploymentService                 ] [Agent Bootstrap Thread] - Starting Deployment Service...
2013-06-16 00:47:20,860 [INFO ] [impl.TaskExecutionService                    ] [Agent Bootstrap Thread] - Initializing TaskExecution Service...
2013-06-16 00:47:20,868 [INFO ] [impl.TaskExecutionService                    ] [Agent Bootstrap Thread] - Starting TaskExecution Service...
2013-06-16 00:47:20,907 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - RepositoryService will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,907 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Scheduler Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,907 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - ASAInstanceManagerService will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,921 [INFO ] [sybasehome.SybaseHomeService                 ] [Agent Bootstrap Thread] - Initializing Sybase Home Service...
2013-06-16 00:47:20,926 [INFO ] [sybasehome.SybaseHomeService                 ] [Agent Bootstrap Thread] - Starting Sybase Home Service...
2013-06-16 00:47:20,926 [INFO ] [sybasehome.SybaseHomeService                 ] [Agent Bootstrap Thread] - The Sybase Home Service list is set to [/opt/sybase]
2013-06-16 00:47:20,926 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Alert Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,926 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Sybase Control Center Collections Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,926 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - SCC Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,926 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Messaging Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,926 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - Embedded Web Container Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,926 [INFO ] [extservice.ExtendedServiceRegistrationService] [Agent Bootstrap Thread] - TDS Service will not be registered because registerOnStartup is false.
2013-06-16 00:47:20,945 [INFO ] [plugin.PluginRegisterService                 ] [Agent Bootstrap Thread] - Initializing Plugin Registration Service...
2013-06-16 00:47:20,945 [INFO ] [plugin.PluginRegisterService                 ] [Agent Bootstrap Thread] - Starting Plugin Registration Service...
2013-06-16 00:47:21,030 [INFO ] [plugin.PluginRegisterService                 ] [Agent Bootstrap Thread] - Validated 2 plugin directories.
2013-06-16 00:47:21,412 [INFO ] [plugin.PluginRegisterService                 ] [Agent Bootstrap Thread] - Plugin registered. Updating lookup info...
2013-06-16 00:47:21,413 [discovery.SelfDiscoveryService               ] [Agent Bootstrap Thread] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:47:21,520 [INFO ] [ase.ASEAgentPlugin                           ] [Agent Bootstrap Thread] - com.sybase.ase - Sybase Home: /opt/sybase
2013-06-16 00:47:21,651 [INFO ] [ase.ASEAgentPlugin                           ] [Agent Bootstrap Thread] - com.sybase.ase - ASE Home: /opt/sybase/ASE-15_0
2013-06-16 00:47:21,652 [INFO ] [ase.ASEAgentPlugin                           ] [Agent Bootstrap Thread] - com.sybase.ase - The Interfaces File /opt/sybase/interfaces has been confirmed as existing and readable.
2013-06-16 00:47:21,652 [INFO ] [ase.ASEAgentPlugin                           ] [Agent Bootstrap Thread] - com.sybase.ase - Discovering the Interfaces File in /opt/sybase
2013-06-16 00:47:21,654 [INFO ] [ase.ASEAgentPlugin                           ] [Agent Bootstrap Thread] - com.sybase.ase - Successfully discovered the interfaces file: /opt/sybase/interfaces
2013-06-16 00:47:21,655 [INFO ] [ase.ASEAgentPlugin                           ] [Agent Bootstrap Thread] - com.sybase.ase - ASE Start command: /opt/sybase/ASE-15_0/install/RUN_LOCALHOST
2013-06-16 00:47:21,655 [INFO ] [ase.ASEAgentPlugin                           ] [Agent Bootstrap Thread] - com.sybase.ase - ASE Server LOCALHOST Start command is /opt/sybase/ASE-15_0/install/RUN_LOCALHOST
2013-06-16 00:47:21,705 [INFO ] [ase.ASEVersion                               ] [Agent Bootstrap Thread] - com.sybase.ase - ASE Version: Adaptive Server Enterprise/15.7.0/EBF 20373 SMP ESD#02 /P/x86_64/Enterprise Linux/ase157esd2/3109/64-bit/FBO/Sat Jul  7 05:36:19 2012
2013-06-16 00:47:22,012 [INFO ] [ase.ASEConnections                           ] [Agent Bootstrap Thread] - com.sybase.ase - Connecting to server using URL:jdbc:sybase:Tds:localhost.localdomain:5000
2013-06-16 00:47:22,492 [INFO ] [ase.ASEConnections                           ] [Agent Bootstrap Thread] - com.sybase.ase - Database Product Name: adaptive server enterprise
2013-06-16 00:47:22,492 [INFO ] [ase.ASEConnections                           ] [Agent Bootstrap Thread] - com.sybase.ase - Created db connection: jdbc:sybase:Tds:localhost.localdomain:5000
2013-06-16 00:47:22,497 [discovery.SelfDiscoveryService               ] [Agent Bootstrap Thread] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:47:22,500 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Finished loading primordial services.
2013-06-16 00:47:22,501 [INFO ] [services.BootstrapService                    ] [Agent Bootstrap Thread] - Bootstrap completed successfully.  Message level set to WARN
2013-06-16 00:48:22,603 [discovery.SelfDiscoveryService               ] [Timer-0] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:49:22,546 [discovery.SelfDiscoveryService               ] [Timer-0] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:50:22,535 [discovery.SelfDiscoveryService               ] [Timer-0] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:51:22,505 [discovery.SelfDiscoveryService               ] [Timer-0] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:52:22,508 [discovery.SelfDiscoveryService               ] [Timer-0] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:53:22,505 [discovery.SelfDiscoveryService               ] [Timer-0] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:54:22,516 [discovery.SelfDiscoveryService               ] [Timer-0] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
2013-06-16 00:55:22,506 [discovery.SelfDiscoveryService               ] [Timer-0] - Cannot connect to Jini service: jini://localhost:4160 java.net.ConnectException: Connection refused
0
 
LVL 21

Expert Comment

by:Mazdajai
ID: 39250351
What about -

Check if firewall is running and port 8282 is listening.
0
 

Author Comment

by:motioneye
ID: 39250445
Hi,
I use iptables and netstat but not sure how to verify the port is listen or not.

But I guess my firewall is running, but not sure how to check 8282 is listening or not sice netstat -an , it seems I couldnt found port 8282

[root@localhost ~]# iptables -n -L -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination        
 1015  241K ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED
    1    48 ACCEPT     icmp --  *      *       0.0.0.0/0            0.0.0.0/0          
   78  4680 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0          
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:22
  137 12239 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination        
    0     0 REJECT     all  --  *      *       0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT 1141 packets, 215K bytes)
 pkts bytes target     prot opt in     out     source               destination        
[root@localhost ~]#
0
 
LVL 21

Assisted Solution

by:Mazdajai
Mazdajai earned 500 total points
ID: 39250451
Try stopping iptables temporary.
For Fedora/Redhat;
service iptables stop

Open in new window

for debian\Ubuntu
service ufw stop

Open in new window

0

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Over the last ten+ years I have seen Linux configuration tools come and go. In the early days there was the tried-and-true, all-powerful linuxconf that many thought would remain the one and only Linux configuration tool until the end of times. Well,…
If you have a server on collocation with the super-fast CPU, that doesn't mean that you get it running at full power. Here is a preamble. When doing inventory of Linux servers, that I'm administering, I've found that some of them are running on l…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

932 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now