Sponsored Content
Special Forums IP Networking telnet for port 5433 is not working while it works for port 22 Post 302693673 by rishav on Wednesday 29th of August 2012 12:41:01 PM
Old 08-29-2012
thanks @hergp will do the same and post the result.

@RudiC: I am not getting any error in Unix/CentOS side (and my application is also running fine on this box) but when i try to telnet port 5433 on this machine from a Windows box I am getting "Connection Refused" error.
 

10 More Discussions You Might Find Interesting

1. IP Networking

block telnet to specific port

Hello All I am running redhat linux 7.2 and would like to know how i can block telnetting to a specified port . say for example i would like to block telnet acesses to port 80. regards Xiamin (5 Replies)
Discussion started by: xiamin
5 Replies

2. Solaris

disabled telnet now need port 23 or port 22

we disabled telnet on solaris 9 via previous a thread. We use CMS (call management system) supervisor which used port 23 (telnet). We cannot use telnet via local directive and it was shut down as stated when we shut down telnet in the inetd file. I cannot now log into the CMS box since port 23 is... (3 Replies)
Discussion started by: panzerkw
3 Replies

3. UNIX for Advanced & Expert Users

telnet on specific port??

Hi all, I have a problem. I have machine names and their IP addresses in /etc/hosts file. My application does telnet on that machine host name. The application does not uses IP address for tenet. It will fetch the host name from /etc/hosts file. Now the telnet server runs on customized port.... (6 Replies)
Discussion started by: zing_foru
6 Replies

4. Shell Programming and Scripting

Telnet IP and Port Script

Hi, I would like to create a simple script that will telnet a number of IP and Ports one after the other to confirm connectivity to those addresses. I don't need to log on, just output to a file what the response is, i.e Escape Character, connectivity refused etc. Complete newbie to... (6 Replies)
Discussion started by: asou
6 Replies

5. AIX

Telnet to port

can some one help me ? what happens when we telnet to a port ? example telnet 192.168.0.xx 1234 where 1234 is a port number Thank you (5 Replies)
Discussion started by: anwesh
5 Replies

6. Windows & DOS: Issues & Discussions

Telnet to a serial port

Hello all. I have an old computer with M$-DOS 7. I want to use it like a dumb terminal, with telnet. I need to connect it to my desktop These are my questions: How can i configure the serial port on dos? How can i telnet form dos to the serial port? How can i set up a telnet server on the... (12 Replies)
Discussion started by: mghis
12 Replies

7. Cybersecurity

Can't telnet to port 25 on the host.

Hi, we have recently setup a new UNIX server with solaris 10 and I am having issue with with SMTP/sendmail. telnet localhost 25 --- works telnet hostname.domain.com 25 -- does not work. # telnet hostname.domain.com 25 Trying 10.122.1.111... telnet: Unable to connect to remote host:... (1 Reply)
Discussion started by: esmgr
1 Replies

8. Red Hat

telnet port 23

My linux version is 2.6.18-194.e14 (Oracle enterprise linux). Could you please tell me how to enable telnet on the server. When I try to connect the server through another pc using telnet it is throwing error. Connecting To <ip address>...Could not open connection to the host, on port 23.... (3 Replies)
Discussion started by: oradba_arun
3 Replies

9. UNIX for Dummies Questions & Answers

telnet echoing 'trying ip' but no port number

Hi, Well this is probably a silly one that I should know...but I don't ! I'm telnetting to various ports from a shell script and the telnet is echoing back that it's 'trying xxx.xx.xx.xx...' but not the port number it's trying! Any help much appreciated Thanks (1 Reply)
Discussion started by: Grueben
1 Replies

10. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
PG_CTL(1)                                                 PostgreSQL Server Applications                                                 PG_CTL(1)

NAME
pg_ctl - start, stop, or restart a PostgreSQL server SYNOPSIS
pg_ctl start [ -w ] [ -t seconds ] [ -s ] [ -D datadir ] [ -l filename ] [ -o options ] [ -p path ] [ -c ] pg_ctl stop [ -W ] [ -t seconds ] [ -s ] [ -D datadir ] [ -m [ s[mart] ] [ f[ast] ] [ i[mmediate] ] ] pg_ctl restart [ -w ] [ -t seconds ] [ -s ] [ -D datadir ] [ -c ] [ -m [ s[mart] ] [ f[ast] ] [ i[mmediate] ] ] [ -o options ] pg_ctl reload [ -s ] [ -D datadir ] pg_ctl status [ -D datadir ] pg_ctl kill [ signal_name ] [ process_id ] pg_ctl register [ -N servicename ] [ -U username ] [ -P password ] [ -D datadir ] [ -w ] [ -t seconds ] [ -o options ] pg_ctl unregister [ -N servicename ] DESCRIPTION
pg_ctl is a utility for starting, stopping, or restarting the PostgreSQL backend server (postgres(1)), or displaying the status of a run- ning server. Although the server can be started manually, pg_ctl encapsulates tasks such as redirecting log output and properly detaching from the terminal and process group. It also provides convenient options for controlled shutdown. In start mode, a new server is launched. The server is started in the background, and standard input is attached to /dev/null. The standard output and standard error are either appended to a log file (if the -l option is used), or redirected to pg_ctl's standard output (not standard error). If no log file is chosen, the standard output of pg_ctl should be redirected to a file or piped to another process such as a log rotating program like rotatelogs; otherwise postgres will write its output to the controlling terminal (from the background) and will not leave the shell's process group. In stop mode, the server that is running in the specified data directory is shut down. Three different shutdown methods can be selected with the -m option: ``Smart'' mode waits for online backup mode to finish and all the clients to disconnect. This is the default. ``Fast'' mode does not wait for clients to disconnect and will terminate an online backup in progress. All active transactions are rolled back and clients are forcibly disconnected, then the server is shut down. ``Immediate'' mode will abort all server processes without a clean shut- down. This will lead to a recovery run on restart. restart mode effectively executes a stop followed by a start. This allows changing the postgres command-line options. reload mode simply sends the postgres process a SIGHUP signal, causing it to reread its configuration files (postgresql.conf, pg_hba.conf, etc.). This allows changing of configuration-file options that do not require a complete restart to take effect. status mode checks whether a server is running in the specified data directory. If it is, the PID and the command line options that were used to invoke it are displayed. kill mode allows you to send a signal to a specified process. This is particularly valuable for Microsoft Windows which does not have a kill command. Use --help to see a list of supported signal names. register mode allows you to register a system service on Microsoft Windows. unregister mode allows you to unregister a system service on Microsoft Windows, previously registered with the register command. OPTIONS
-c Attempt to allow server crashes to produce core files, on platforms where this available, by lifting any soft resource limit placed on them. This is useful in debugging or diagnosing problems by allowing a stack trace to be obtained from a failed server process. -D datadir Specifies the file system location of the database files. If this is omitted, the environment variable PGDATA is used. -l filename Append the server log output to filename. If the file does not exist, it is created. The umask is set to 077, so access to the log file from other users is disallowed by default. -m mode Specifies the shutdown mode. mode can be smart, fast, or immediate, or the first letter of one of these three. -o options Specifies options to be passed directly to the postgres command. The options are usually surrounded by single or double quotes to ensure that they are passed through as a group. -p path Specifies the location of the postgres executable. By default the postgres executable is taken from the same directory as pg_ctl, or failing that, the hard-wired installation directory. It is not necessary to use this option unless you are doing something unusual and get errors that the postgres executable was not found. -s Only print errors, no informational messages. -t The number of seconds to wait when waiting for start or shutdown to complete. -w Wait for the start or shutdown to complete. The default wait time is 60 seconds. This is the default option for shutdowns. A suc- cessful shutdown is indicated by removal of the PID file. For starting up, a successful psql -l indicates success. pg_ctl will attempt to use the proper port for psql. If the environment variable PGPORT exists, that is used. Otherwise, it will see if a port has been set in the postgresql.conf file. If neither of those is used, it will use the default port that PostgreSQL was compiled with (5432 by default). When waiting, pg_ctl will return an accurate exit code based on the success of the startup or shutdown. -W Do not wait for start or shutdown to complete. This is the default for starts and restarts. OPTIONS FOR WINDOWS -N servicename Name of the system service to register. The name will be used as both the service name and the display name. -P password Password for the user to start the service. -U username User name for the user to start the service. For domain users, use the format DOMAINusername. ENVIRONMENT
PGDATA Default data directory location. PGPORT Default port for psql(1) (used by the -w option). For additional server variables, see postgres(1). This utility, like most other PostgreSQL utilities, also uses the environment variables supported by libpq (see in the documentation). FILES
postmaster.pid The existence of this file in the data directory is used to help pg_ctl determine if the server is currently running or not. postmaster.opts If this file exists in the data directory, pg_ctl (in restart mode) will pass the contents of the file as options to postgres, unless overridden by the -o option. The contents of this file are also displayed in status mode. postgresql.conf This file, located in the data directory, is parsed to find the proper port to use with psql when the -w is given in start mode. NOTES
Waiting for complete start is not a well-defined operation and might fail if access control is set up so that a local client cannot connect without manual interaction (e.g., password authentication). For additional connection variables, see in the documentation, and for pass- words, also see in the documentation. EXAMPLES
STARTING THE SERVER To start up a server: $ pg_ctl start An example of starting the server, blocking until the server has come up is: $ pg_ctl -w start For a server using port 5433, and running without fsync, use: $ pg_ctl -o "-F -p 5433" start STOPPING THE SERVER $ pg_ctl stop stops the server. Using the -m switch allows one to control how the backend shuts down. RESTARTING THE SERVER Restarting the server is almost equivalent to stopping the server and starting it again except that pg_ctl saves and reuses the command line options that were passed to the previously running instance. To restart the server in the simplest form, use: $ pg_ctl restart To restart server, waiting for it to shut down and to come up: $ pg_ctl -w restart To restart using port 5433 and disabling fsync after restarting: $ pg_ctl -o "-F -p 5433" restart SHOWING THE SERVER STATUS Here is a sample status output from pg_ctl: $ pg_ctl status pg_ctl: server is running (pid: 13718) Command line was: /usr/local/pgsql/bin/postgres '-D' '/usr/local/pgsql/data' '-p' '5433' '-B' '128' This is the command line that would be invoked in restart mode. SEE ALSO
postgres(1) Application 2010-05-14 PG_CTL(1)
All times are GMT -4. The time now is 03:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy