Cannot connect to Port 5432












2















My company has a Linux Database server. I only have one user that needs access to this server.



He is using PostgreSQL to access this server. It has been working fine for over a year. Today when he tried to log on he got this message



SERVER DOESN'T LISTEN


The server doesn't accept connections, the connection library reports:



Could not connect to server: Connection refused (0x0000274d/10061) is the server running on host 192.168.xx.xx and accepting TCP/IP connections on port 5432


The server has been rebooted and I can ping the Correct IP.
If I remote with Putty I can run NETSTAT and I DO NOT see port 5432 listening.



I have never used Linux before and could use some help.
I don't know why 5432 stopped listening, but I think I would be ok if I can make port 5432 listen.










share|improve this question

























  • In postgresql.conf did you set listen_addresses to localhost, private_ip?

    – Rinzwind
    Sep 16 '14 at 14:00
















2















My company has a Linux Database server. I only have one user that needs access to this server.



He is using PostgreSQL to access this server. It has been working fine for over a year. Today when he tried to log on he got this message



SERVER DOESN'T LISTEN


The server doesn't accept connections, the connection library reports:



Could not connect to server: Connection refused (0x0000274d/10061) is the server running on host 192.168.xx.xx and accepting TCP/IP connections on port 5432


The server has been rebooted and I can ping the Correct IP.
If I remote with Putty I can run NETSTAT and I DO NOT see port 5432 listening.



I have never used Linux before and could use some help.
I don't know why 5432 stopped listening, but I think I would be ok if I can make port 5432 listen.










share|improve this question

























  • In postgresql.conf did you set listen_addresses to localhost, private_ip?

    – Rinzwind
    Sep 16 '14 at 14:00














2












2








2








My company has a Linux Database server. I only have one user that needs access to this server.



He is using PostgreSQL to access this server. It has been working fine for over a year. Today when he tried to log on he got this message



SERVER DOESN'T LISTEN


The server doesn't accept connections, the connection library reports:



Could not connect to server: Connection refused (0x0000274d/10061) is the server running on host 192.168.xx.xx and accepting TCP/IP connections on port 5432


The server has been rebooted and I can ping the Correct IP.
If I remote with Putty I can run NETSTAT and I DO NOT see port 5432 listening.



I have never used Linux before and could use some help.
I don't know why 5432 stopped listening, but I think I would be ok if I can make port 5432 listen.










share|improve this question
















My company has a Linux Database server. I only have one user that needs access to this server.



He is using PostgreSQL to access this server. It has been working fine for over a year. Today when he tried to log on he got this message



SERVER DOESN'T LISTEN


The server doesn't accept connections, the connection library reports:



Could not connect to server: Connection refused (0x0000274d/10061) is the server running on host 192.168.xx.xx and accepting TCP/IP connections on port 5432


The server has been rebooted and I can ping the Correct IP.
If I remote with Putty I can run NETSTAT and I DO NOT see port 5432 listening.



I have never used Linux before and could use some help.
I don't know why 5432 stopped listening, but I think I would be ok if I can make port 5432 listen.







postgresql






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 18 '14 at 10:26









Sylvain Pineau

48.9k16107150




48.9k16107150










asked Sep 16 '14 at 13:35









JerryJerry

1112




1112













  • In postgresql.conf did you set listen_addresses to localhost, private_ip?

    – Rinzwind
    Sep 16 '14 at 14:00



















  • In postgresql.conf did you set listen_addresses to localhost, private_ip?

    – Rinzwind
    Sep 16 '14 at 14:00

















In postgresql.conf did you set listen_addresses to localhost, private_ip?

– Rinzwind
Sep 16 '14 at 14:00





In postgresql.conf did you set listen_addresses to localhost, private_ip?

– Rinzwind
Sep 16 '14 at 14:00










1 Answer
1






active

oldest

votes


















0














Probably the postgresql service is not running (either it crashed or it is not configured to start at boot time, since you rebooted the server).



Depending on the version of Ubuntu you are using, you should try to start it with command



sudo service postgresql start


or with



sudo /etc/init.d/postgresql start


If the service starts without error, the application should be running fine.






share|improve this answer
























  • Syldes, You are right the server was not running, But when I tried to start it, it failed. The error message was No space left on drive. I need to check the log output to see what is going on.I am not sure where to find the log. I think if I can clean some stuff off this drive I will be back in business.

    – Jerry
    Sep 17 '14 at 11:30













  • @Jerry, yes it seems you need to recover/add free space on the drive. df -h command might help to find which mount point is full.

    – syldes
    Sep 17 '14 at 13:26











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f524721%2fcannot-connect-to-port-5432%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Probably the postgresql service is not running (either it crashed or it is not configured to start at boot time, since you rebooted the server).



Depending on the version of Ubuntu you are using, you should try to start it with command



sudo service postgresql start


or with



sudo /etc/init.d/postgresql start


If the service starts without error, the application should be running fine.






share|improve this answer
























  • Syldes, You are right the server was not running, But when I tried to start it, it failed. The error message was No space left on drive. I need to check the log output to see what is going on.I am not sure where to find the log. I think if I can clean some stuff off this drive I will be back in business.

    – Jerry
    Sep 17 '14 at 11:30













  • @Jerry, yes it seems you need to recover/add free space on the drive. df -h command might help to find which mount point is full.

    – syldes
    Sep 17 '14 at 13:26
















0














Probably the postgresql service is not running (either it crashed or it is not configured to start at boot time, since you rebooted the server).



Depending on the version of Ubuntu you are using, you should try to start it with command



sudo service postgresql start


or with



sudo /etc/init.d/postgresql start


If the service starts without error, the application should be running fine.






share|improve this answer
























  • Syldes, You are right the server was not running, But when I tried to start it, it failed. The error message was No space left on drive. I need to check the log output to see what is going on.I am not sure where to find the log. I think if I can clean some stuff off this drive I will be back in business.

    – Jerry
    Sep 17 '14 at 11:30













  • @Jerry, yes it seems you need to recover/add free space on the drive. df -h command might help to find which mount point is full.

    – syldes
    Sep 17 '14 at 13:26














0












0








0







Probably the postgresql service is not running (either it crashed or it is not configured to start at boot time, since you rebooted the server).



Depending on the version of Ubuntu you are using, you should try to start it with command



sudo service postgresql start


or with



sudo /etc/init.d/postgresql start


If the service starts without error, the application should be running fine.






share|improve this answer













Probably the postgresql service is not running (either it crashed or it is not configured to start at boot time, since you rebooted the server).



Depending on the version of Ubuntu you are using, you should try to start it with command



sudo service postgresql start


or with



sudo /etc/init.d/postgresql start


If the service starts without error, the application should be running fine.







share|improve this answer












share|improve this answer



share|improve this answer










answered Sep 16 '14 at 13:59









syldessyldes

362




362













  • Syldes, You are right the server was not running, But when I tried to start it, it failed. The error message was No space left on drive. I need to check the log output to see what is going on.I am not sure where to find the log. I think if I can clean some stuff off this drive I will be back in business.

    – Jerry
    Sep 17 '14 at 11:30













  • @Jerry, yes it seems you need to recover/add free space on the drive. df -h command might help to find which mount point is full.

    – syldes
    Sep 17 '14 at 13:26



















  • Syldes, You are right the server was not running, But when I tried to start it, it failed. The error message was No space left on drive. I need to check the log output to see what is going on.I am not sure where to find the log. I think if I can clean some stuff off this drive I will be back in business.

    – Jerry
    Sep 17 '14 at 11:30













  • @Jerry, yes it seems you need to recover/add free space on the drive. df -h command might help to find which mount point is full.

    – syldes
    Sep 17 '14 at 13:26

















Syldes, You are right the server was not running, But when I tried to start it, it failed. The error message was No space left on drive. I need to check the log output to see what is going on.I am not sure where to find the log. I think if I can clean some stuff off this drive I will be back in business.

– Jerry
Sep 17 '14 at 11:30







Syldes, You are right the server was not running, But when I tried to start it, it failed. The error message was No space left on drive. I need to check the log output to see what is going on.I am not sure where to find the log. I think if I can clean some stuff off this drive I will be back in business.

– Jerry
Sep 17 '14 at 11:30















@Jerry, yes it seems you need to recover/add free space on the drive. df -h command might help to find which mount point is full.

– syldes
Sep 17 '14 at 13:26





@Jerry, yes it seems you need to recover/add free space on the drive. df -h command might help to find which mount point is full.

– syldes
Sep 17 '14 at 13:26


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f524721%2fcannot-connect-to-port-5432%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Human spaceflight

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

張江高科駅