pg_ctlcluster: Could not create log file

Bug #372476 reported by QBall2U
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
postgresql-common (Debian)
Fix Released
Unknown
postgresql-common (Ubuntu)
Fix Released
Undecided
Martin Pitt

Bug Description

Binary package hint: postgresql-8.3

I just installed Ubuntu 9.04, updated it then opened Synaptic Pkg Mgr and selected some programs to download, the postgresql-8.3 happened to be part of the 'required files' that needed to be downloaded and installed with, I believe (I went to work and left the computer to download .... I guess I had ticked the "[ ] close this window when programs have installed" and the error was dispalyed on screen. I saw glom had not installed, I don't know if the two problems are related?) glom (1.8.7-0ubuntu1), which was not configured because of this.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: postgresql-8.3 8.3.7-1
SourcePackage: postgresql-8.3
Title: package postgresql-8.3 8.3.7-1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
QBall2U (jqball2u) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Please attach /var/log/postgresql/postgresql-8.3-main.log after a failed start attempt. Thank you!

Changed in postgresql-8.3 (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Pitt (pitti) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in postgresql-8.3 (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
stewsnooze (stewsnooze) wrote :

can we reopen this. I can upload whatever you need. For instance...

<pre>
stew@stewbuntu:~$ sudo /etc/init.d/postgresql-8.3 start
[sudo] password for stew:
 * Starting PostgreSQL 8.3 database server * Error: Could not create log file /var/log/postgresql/postgresql-8.3-main.log
                                                                         [fail]
</pre>

and
<pre>
root@stewbuntu:/var/log/postgresql# ls -la
total 8
drwxr-xr-x 2 root postgres 4096 2009-08-17 09:50 .
drwxr-x--- 19 root root 4096 2009-09-14 08:17 ..
</pre>

Revision history for this message
Martin Pitt (pitti) wrote :

> Starting PostgreSQL 8.3 database server * Error: Could not create log file /var/log/postgresql/postgresql-8.3-main.log

Did you happen to remove the file manually? It's usually created when the package gets installed (or when pg_createcluster is called).

Changed in postgresql-8.3 (Ubuntu):
status: Invalid → Incomplete
summary: - package postgresql-8.3 8.3.7-1 failed to install/upgrade: subprocess
- post-installation script returned error exit status 1
+ pg_ctlcluster: Could not create log file
affects: postgresql-8.3 (Ubuntu) → postgresql-common (Ubuntu)
Changed in postgresql-common (Debian):
status: Unknown → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Nevermind, I found the reason and fixed it in trunk (r965).

Changed in postgresql-common (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
status: Incomplete → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package postgresql-common - 103

---------------
postgresql-common (103) unstable; urgency=low

  * Move the lsb-release dependency of p-common to a recommends of
    p-client-common. (Closes: #562642)
  * Drop Oliver from Uploaders:, he has not been active any more for years.
  * t/005_PgCommon.t: Add '.' to library search path, so that this prefers
    testing PgCommon.pm from the source tree.
  * t/005_PgCommon.t: Add test cases for {set,disable,replace}_conf_value().
  * PgCommon.pm, replace_conf_value(): Do not append the new parameter if the
    old is not found.
  * PgCommon.pm, {set,disable,replace}_conf_value(): Intercept errors on
    writing data (which could happen when running out of disk space). Write
    into a new file and rename it in the end, instead of directly writing into
    the original file. Thanks to Yann Dirson for the original patch.
    (Closes: #549206)
  * pg_createcluster: Change effective gid as well when setting the socket
    directory, to avoid moving postgresql.conf's group to root (which would
    happen with the previous change).
  * Add t/042_upgrade_tablespaces.t: Test upgrading a cluster with
    tablespaces. Since this is not currently supported (and hard to do in an
    automated fashion due to the nature of tablespaces), just check that this
    errors out with a sane message and does not do any damage.
  * pg_upgradecluster: Add an early check for tablespaces. (Closes: #523574)
  * pg_lsclusters: Fix undefined value if owneruid cannot be determined (which
    can happen in special setups). Thanks to Daniel Pittman! (Closes: #541434)
  * t/020_create_sql_remove.t: Verify permissions of the data and
    configuration directories.
  * pg_createcluster: Make /etc/postgresql/<version> and
    /var/lib/postgresql/<version> owned by 'postgres', so that they can be
    administrated with 'postgres' privileges. Update t/030_errors.t
    accordingly. (LP: #236704, Closes: #525294)
  * t/020_create_sql_remove.t: Check that a missing log file is recreated by
    pg_ctlcluster (if it has enough permissions).
  * pg_ctlcluster: Make re-creation of log file actually work. (LP: #391119,
    #372476)
 -- Martin Pitt <email address hidden> Wed, 30 Dec 2009 23:06:10 +0100

Changed in postgresql-common (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.