This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I just installed new ram into my laptop....soon after that Fedora forced me to run fcsk (or something like that)..I think it's kind of like ScanDisk??
Anyway after running that , my postgresql service cannot start... I'm not sure how to fix it...Any ideas?
If I try connect this is the error I get :
Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused Is the server running on host "localhost" and accepting TCP/IP connections on port 5432? could not connect to server: Connection refused Is the server running on host "localhost" and accepting TCP/IP connections on port 5432?
Here is my hba.conf :
local all all trust
host all all 127.0.0.1/32 trust
host all all ::1/128 trust
The fsck was probably requested because when you create a filesystem in Linux, a parameter gets set that tells Linux how many times the system may be restarted before fsck will be run automatically to detect/repair damage. Which is a pretty useless option on my servers, which reboot on average about once every 8 months.
You can also get an fsck request if the filesystem was not shut down cleanly. Either because the system crashed or because you got impatient and pulled power before the filesystem had been closed for shutdown. Since you had a dangling lockfile, I'd say that your fsck came from a non-clean shutdown, as the "service postgres stop" command issued by /sbin/shutdown processing would have deleted the lockfile.
A lot of Linux apps use a lockfile to prevent multiple instances of a service or application from being started. The exact location of that file may vary, depending on the program, but there are a few places that are popular, such as /var/run and /var/lock. An astute observer would notice that part of the lockfile for PostgreSQL was the port ID 5432. That's because you can run multiple PostgreSQL instances as long as they each listen on a port of their own. Mostly you'd only do that if you're either customizing and testing a PostgreSQL server or if you have a critical database that you want isolated.
So now you know. If a server/the system crashes and you cannot restart, look for a lock file and delete it manually. But do check to make sure that the program in question really isn't running!
Customer surveys are for companies who didn't pay proper attention to begin with.
GDM is the Graphical Display Manager, I think, but why it should own the PostgreSQL lock I do not know unless somehow the PostgreSQL and GDM group names both got assigned to the same numeric ID (check /etc/group).