API tools faq
paste
Advertisement
Guest User

Untitled

a guest
May 22nd, 2011
715
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.48 KB | None | 0 0
raw download clone embed print report
  1. wired@desktop:/etc/init.d$ sudo /etc/init.d/postgresql restart
  2. + [ -r /usr/share/postgresql-common/init.d-functions ]
  3. + . /usr/share/postgresql-common/init.d-functions
  4. + . /lib/lsb/init-functions
  5. + FANCYTTY=
  6. + [ -e /etc/lsb-base-logging.sh ]
  7. + . /etc/lsb-base-logging.sh
  8. + LOG_DAEMON_MSG=
  9. + [ -n ]
  10. + get_versions
  11. + versions=
  12. + local v
  13. + ls /usr/lib/postgresql/
  14. + [ -x /usr/lib/postgresql/8.4/bin/pg_ctl ]
  15. + [ ! -x /etc/init.d/postgresql-8.4 ]
  16. + versions= 8.4
  17. + restart 8.4
  18. + do_ctl_all restart 8.4 Restarting PostgreSQL 8.4 database server
  19. + [ restart ]
  20. + [ 8.4 ]
  21. + [ -d /etc/postgresql/8.4 ]
  22. + ls /etc/postgresql/8.4
  23. + [ main ]
  24. + [ -x /usr/lib/postgresql/8.4/bin/postmaster ]
  25. + status=0
  26. + log_daemon_msg Restarting PostgreSQL 8.4 database server
  27. + [ -z Restarting PostgreSQL 8.4 database server ]
  28. + log_use_fancy_output
  29. + TPUT=/usr/bin/tput
  30. + EXPR=/usr/bin/expr
  31. + [ -t 1 ]
  32. + [ xxterm != x ]
  33. + [ xxterm != xdumb ]
  34. + [ -x /usr/bin/tput ]
  35. + [ -x /usr/bin/expr ]
  36. + /usr/bin/tput hpa 60
  37. + /usr/bin/tput setaf 1
  38. + [ -z ]
  39. + FANCYTTY=1
  40. + true
  41. + /usr/bin/tput xenl
  42. + /usr/bin/tput cols
  43. + COLS=118
  44. + [ 118 ]
  45. + [ 118 -gt 6 ]
  46. + /usr/bin/expr 118 - 7
  47. + COL=111
  48. + log_use_plymouth
  49. + [ n = y ]
  50. + plymouth --ping
  51. + printf * Restarting PostgreSQL 8.4 database server
  52. * Restarting PostgreSQL 8.4 database server + /usr/bin/expr 118 - 1
  53. + /usr/bin/tput hpa 117
  54. + printf
  55. + [ -e /etc/postgresql/8.4/main/postgresql.conf ]
  56. + basename /etc/postgresql/8.4/main
  57. + name=main
  58. + [ -e /etc/postgresql/8.4/main/start.conf ]
  59. + sed s/#.*$//; /^[[:space:]]*$/d; s/^\s*//; s/\s*$// /etc/postgresql/8.4/main/start.conf
  60. + start=auto
  61. + [ auto = auto ]
  62. + log_progress_msg main
  63. + :
  64. + set +e
  65. + [ restart = stop ]
  66. + [ restart = restart ]
  67. + pg_ctlcluster --force 8.4 main restart
  68. + ERRMSG=The PostgreSQL server failed to start. Please check the log output:
  69. 2011-05-22 02:34:58 EDT LOG: could not bind IPv4 socket: Address already in use
  70. 2011-05-22 02:34:58 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
  71. 2011-05-22 02:34:58 EDT WARNING: could not create listen socket for "127.0.0.1"
  72. 2011-05-22 02:34:58 EDT FATAL: could not create shared memory segment: Invalid argument
  73. 2011-05-22 02:34:58 EDT DETAIL: Failed system call was shmget(key=5432001, size=37879808, 03600).
  74. 2011-05-22 02:34:58 EDT HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 37879808 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 103).
  75. If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
  76. The PostgreSQL documentation contains more information about shared memory configuration.
  77. + res=1
  78. + set -e
  79. + [ 1 -eq 0 ]
  80. + [ 1 -eq 2 ]
  81. + status=1
  82. + [ 1 -ne 0 -a -n The PostgreSQL server failed to start. Please check the log output:
  83. 2011-05-22 02:34:58 EDT LOG: could not bind IPv4 socket: Address already in use
  84. 2011-05-22 02:34:58 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
  85. 2011-05-22 02:34:58 EDT WARNING: could not create listen socket for "127.0.0.1"
  86. 2011-05-22 02:34:58 EDT FATAL: could not create shared memory segment: Invalid argument
  87. 2011-05-22 02:34:58 EDT DETAIL: Failed system call was shmget(key=5432001, size=37879808, 03600).
  88. 2011-05-22 02:34:58 EDT HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 37879808 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 103).
  89. If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
  90. The PostgreSQL documentation contains more information about shared memory configuration. ]
  91. + log_failure_msg The PostgreSQL server failed to start. Please check the log output:
  92. 2011-05-22 02:34:58 EDT LOG: could not bind IPv4 socket: Address already in use
  93. 2011-05-22 02:34:58 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
  94. 2011-05-22 02:34:58 EDT WARNING: could not create listen socket for "127.0.0.1"
  95. 2011-05-22 02:34:58 EDT FATAL: could not create shared memory segment: Invalid argument
  96. 2011-05-22 02:34:58 EDT DETAIL: Failed system call was shmget(key=5432001, size=37879808, 03600).
  97. 2011-05-22 02:34:58 EDT HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 37879808 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 103).
  98. If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in wh+ [ -t 1 ]
  99. + [ xxterm != x ]
  100. + [ xxterm != xdumb ]
  101. + [ -x /usr/bin/tput ]
  102. + [ -x /usr/bin/expr ]
  103. + /usr/bin/tput hpa 60
  104. + /usr/bin/tput setaf 1
  105. + [ -z 1 ]
  106. + true
  107. + true
  108. + /usr/bin/tput setaf 1
  109. + RED=
  110. + /usr/bin/tput op
  111. + NORMAL=
  112. + echo * The PostgreSQL server failed to start. Please check the log output:
  113. 2011-05-22 02:34:58 EDT LOG: could not bind IPv4 socket: Address already in use
  114. 2011-05-22 02:34:58 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
  115. 2011-05-22 02:34:58 EDT WARNING: could not create listen socket for "127.0.0.1"
  116. 2011-05-22 02:34:58 EDT FATAL: could not create shared memory segment: Invalid argument
  117. 2011-05-22 02:34:58 EDT DETAIL: Failed system call was shmget(key=5432001, size=37879808, 03600).
  118. 2011-05-22 02:34:58 EDT HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 37879808 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 103).
  119. If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
  120. The PostgreSQL documentation contains more information about shared memory configuration.
  121. * The PostgreSQL server failed to start. Please check the log output:
  122. 2011-05-22 02:34:58 EDT LOG: could not bind IPv4 socket: Address already in use
  123. 2011-05-22 02:34:58 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
  124. 2011-05-22 02:34:58 EDT WARNING: could not create listen socket for "127.0.0.1"
  125. 2011-05-22 02:34:58 EDT FATAL: could not create shared memory segment: Invalid argument
  126. 2011-05-22 02:34:58 EDT DETAIL: Failed system call was shmget(key=5432001, size=37879808, 03600).
  127. 2011-05-22 02:34:58 EDT HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 37879808 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 103).
  128. If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
  129. The PostgreSQL documentation contains more information about shared memory configuration.
  130. + log_end_msg 1
  131. + [ -z 1 ]
  132. + [ 111 ]
  133. + [ -x /usr/bin/tput ]
  134. + log_use_plymouth
  135. + [ n = y ]
  136. + plymouth --ping
  137. + printf \r
  138. + /usr/bin/tput hpa 111
  139. + [ 1 -eq 0 ]
  140. + printf [
  141. [+ /usr/bin/tput setaf 1
  142. + printf fail
  143. fail+ /usr/bin/tput op
  144. + echo ]
  145. ]
  146. + return 1
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!