API tools faq
paste
Advertisement
Guest User

pgpool.log

a guest
Dec 30th, 2014
575
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 24.20 KB | None | 0 0
raw download clone embed print report
  1. 2014-12-30 23:25:51: pid 6420: LOG:  child process received shutdown request signal 2
  2. 2014-12-30 23:25:51: pid 10184: LOG:  child process received shutdown request signal 2
  3. 2014-12-30 23:25:51: pid 6193: LOG:  child process received shutdown request signal 2
  4. 2014-12-30 23:25:51: pid 477: LOG:  child process received shutdown request signal 2
  5. 2014-12-30 23:25:51: pid 1085: LOG:  child process received shutdown request signal 2
  6. 2014-12-30 23:25:51: pid 32354: LOG:  child process received shutdown request signal 2
  7. 2014-12-30 23:25:51: pid 6419: LOG:  child process received shutdown request signal 2
  8. 2014-12-30 23:25:51: pid 2436: LOG:  child process received shutdown request signal 2
  9. 2014-12-30 23:25:51: pid 3449: LOG:  child process received shutdown request signal 2
  10. 2014-12-30 23:25:51: pid 1968: LOG:  child process received shutdown request signal 2
  11. 2014-12-30 23:25:51: pid 6362: LOG:  child process received shutdown request signal 2
  12. 2014-12-30 23:25:51: pid 2492: LOG:  child process received shutdown request signal 2
  13. 2014-12-30 23:25:51: pid 2396: LOG:  child process received shutdown request signal 2
  14. 2014-12-30 23:25:51: pid 1239: LOG:  child process received shutdown request signal 2
  15. 2014-12-30 23:25:51: pid 2431: LOG:  child process received shutdown request signal 2
  16. 2014-12-30 23:25:51: pid 8584: LOG:  child process received shutdown request signal 2
  17. 2014-12-30 23:25:51: pid 9898: LOG:  child process received shutdown request signal 2
  18. 2014-12-30 23:25:51: pid 2522: LOG:  child process received shutdown request signal 2
  19. 2014-12-30 23:25:51: pid 627: LOG:  child process received shutdown request signal 2
  20. 2014-12-30 23:25:51: pid 1691: LOG:  child process received shutdown request signal 2
  21. 2014-12-30 23:25:51: pid 6375: LOG:  child process received shutdown request signal 2
  22. 2014-12-30 23:25:51: pid 6426: LOG:  child process received shutdown request signal 2
  23. 2014-12-30 23:25:51: pid 6317: LOG:  child process received shutdown request signal 2
  24. 2014-12-30 23:25:51: pid 6376: LOG:  child process received shutdown request signal 2
  25. 2014-12-30 23:25:51: pid 23323: LOG:  child process received shutdown request signal 2
  26. 2014-12-30 23:25:51: pid 31704: LOG:  child process received shutdown request signal 2
  27. 2014-12-30 23:25:51: pid 2233: LOG:  child process received shutdown request signal 2
  28. 2014-12-30 23:25:51: pid 900: LOG:  child process received shutdown request signal 2
  29. 2014-12-30 23:25:51: pid 4862: LOG:  child process received shutdown request signal 2
  30. 2014-12-30 23:25:51: pid 451: LOG:  child process received shutdown request signal 2
  31. 2014-12-30 23:25:51: pid 3067: LOG:  child process received shutdown request signal 2
  32. 2014-12-30 23:25:51: pid 6318: LOG:  child process received shutdown request signal 2
  33. 2014-12-30 23:25:51: pid 6339: LOG:  child process received shutdown request signal 2
  34. 2014-12-30 23:25:51: pid 19699: LOG:  child process received shutdown request signal 2
  35. 2014-12-30 23:25:51: pid 11592: LOG:  child process received shutdown request signal 2
  36. 2014-12-30 23:25:51: pid 4984: LOG:  child process received shutdown request signal 2
  37. 2014-12-30 23:25:51: pid 950: LOG:  child process received shutdown request signal 2
  38. 2014-12-30 23:25:51: pid 2583: LOG:  child process received shutdown request signal 2
  39. 2014-12-30 23:25:51: pid 6319: LOG:  child process received shutdown request signal 2
  40. 2014-12-30 23:25:51: pid 10706: LOG:  child process received shutdown request signal 2
  41. 2014-12-30 23:25:51: pid 6315: LOG:  child process received shutdown request signal 2
  42. 2014-12-30 23:25:51: pid 6436: LOG:  child process received shutdown request signal 2
  43. 2014-12-30 23:25:51: pid 32355: LOG:  child process received shutdown request signal 2
  44. 2014-12-30 23:25:51: pid 6151: LOG:  child process received shutdown request signal 2
  45. 2014-12-30 23:25:51: pid 10498: LOG:  child process received shutdown request signal 2
  46. 2014-12-30 23:25:51: pid 16063: LOG:  child process received shutdown request signal 2
  47. 2014-12-30 23:25:51: pid 1286: LOG:  child process received shutdown request signal 2
  48. 2014-12-30 23:25:51: pid 6320: LOG:  child process received shutdown request signal 2
  49. 2014-12-30 23:25:51: pid 32013: LOG:  child process received shutdown request signal 2
  50. 2014-12-30 23:25:51: pid 32392: LOG:  child process received shutdown request signal 2
  51. 2014-12-30 23:25:51: pid 7566: LOG:  child process received shutdown request signal 2
  52. 2014-12-30 23:25:51: pid 2224: LOG:  child process received shutdown request signal 2
  53. 2014-12-30 23:25:51: pid 2378: LOG:  child process received shutdown request signal 2
  54. 2014-12-30 23:25:51: pid 1687: LOG:  child process received shutdown request signal 2
  55. 2014-12-30 23:25:51: pid 4924: LOG:  child process received shutdown request signal 2
  56. 2014-12-30 23:25:51: pid 13367: LOG:  child process received shutdown request signal 2
  57. 2014-12-30 23:25:51: pid 1773: LOG:  child process received shutdown request signal 2
  58. 2014-12-30 23:25:51: pid 15345: LOG:  child process received shutdown request signal 2
  59. 2014-12-30 23:25:51: pid 2232: LOG:  child process received shutdown request signal 2
  60. 2014-12-30 23:25:51: pid 2377: LOG:  child process received shutdown request signal 2
  61. 2014-12-30 23:25:51: pid 2395: LOG:  child process received shutdown request signal 2
  62. 2014-12-30 23:25:51: pid 32402: LOG:  child process received shutdown request signal 2
  63. 2014-12-30 23:25:51: pid 27134: LOG:  child process received shutdown request signal 2
  64. 2014-12-30 23:25:51: pid 10973: LOG:  child process received shutdown request signal 2
  65. 2014-12-30 23:25:51: pid 32291: LOG:  child process received shutdown request signal 2
  66. 2014-12-30 23:25:51: pid 1780: LOG:  child process received shutdown request signal 2
  67. 2014-12-30 23:25:51: pid 32313: LOG:  child process received shutdown request signal 2
  68. 2014-12-30 23:25:51: pid 2950: LOG:  child process received shutdown request signal 2
  69. 2014-12-30 23:25:51: pid 5659: LOG:  child process received shutdown request signal 2
  70. 2014-12-30 23:25:51: pid 2226: LOG:  child process received shutdown request signal 2
  71. 2014-12-30 23:25:51: pid 23655: LOG:  child process received shutdown request signal 2
  72. 2014-12-30 23:25:51: pid 11844: LOG:  child process received shutdown request signal 2
  73. 2014-12-30 23:25:51: pid 10496: LOG:  child process received shutdown request signal 2
  74. 2014-12-30 23:25:51: pid 32489: LOG:  child process received shutdown request signal 2
  75. 2014-12-30 23:25:51: pid 2389: LOG:  child process received shutdown request signal 2
  76. 2014-12-30 23:25:51: pid 23657: LOG:  child process received shutdown request signal 2
  77. 2014-12-30 23:25:51: pid 6594: LOG:  stop request sent to pgpool. waiting for termination...
  78. 2014-12-30 23:25:51: pid 2781: LOG:  child process received shutdown request signal 2
  79. 2014-12-30 23:25:51: pid 2238: LOG:  child process received shutdown request signal 2
  80. 2014-12-30 23:25:51: pid 2435: LOG:  child process received shutdown request signal 2
  81. ....2014-12-30 23:25:54: pid 1697: LOG:  watchdog bringing down delegate IP
  82. 2014-12-30 23:25:54: pid 1697: DETAIL:  ifconfig down succeeded
  83. ....done.
  84. 2014-12-30 23:25:59: pid 6631: LOG:  Setting up socket for 0.0.0.0:9999
  85. 2014-12-30 23:25:59: pid 6631: LOG:  Setting up socket for :::9999
  86. 2014-12-30 23:26:01: pid 6631: LOG:  watchdog started
  87. 2014-12-30 23:26:01: pid 6631: LOG:  pgpool-II successfully started. version 3.4.0 (tataraboshi)
  88. 2014-12-30 23:26:01: pid 6631: LOG:  find_primary_node: checking backend no 0
  89.    
  90. 2014-12-30 23:26:01: pid 6631: LOG:  find_primary_node: primary node id is 0
  91. 2014-12-30 23:26:02: pid 6647: LOG:  createing watchdog heartbeat receive socket.
  92. 2014-12-30 23:26:02: pid 6647: DETAIL:  bind receive socket to device: "eth0"
  93. 2014-12-30 23:26:02: pid 6647: LOG:  set SO_REUSEPORT option to the socket
  94. 2014-12-30 23:26:02: pid 6647: LOG:  creating watchdog heartbeat receive socket.
  95. 2014-12-30 23:26:02: pid 6647: DETAIL:  set SO_REUSEPORT
  96. 2014-12-30 23:26:02: pid 6648: LOG:  creating socket for sending heartbeat
  97. 2014-12-30 23:26:02: pid 6648: DETAIL:  bind send socket to device: eth0
  98. 2014-12-30 23:26:02: pid 6648: LOG:  set SO_REUSEPORT option to the socket
  99. 2014-12-30 23:26:02: pid 6648: LOG:  creating socket for sending heartbeat
  100. 2014-12-30 23:26:02: pid 6648: DETAIL:  set SO_REUSEPORT
  101. 2014-12-30 23:27:24: pid 6646: LOG:  watchdog escalation
  102. 2014-12-30 23:27:24: pid 6646: DETAIL:  escalating to master pgpool
  103. 2014-12-30 23:27:28: pid 6646: LOG:  watchdog bringing up delegate IP, 'ifconfig up' succeeded
  104. 2014-12-30 23:27:31: pid 6646: LOG:  sending watchdog response
  105. 2014-12-30 23:27:31: pid 6646: DETAIL:  receive add request from 10.88.9.216:9999 and accept it
  106. 2014-12-30 23:34:52: pid 6736: WARNING:  failed to execute regex matching, pattern is NULL
  107. 2014-12-30 23:34:52: pid 6651: WARNING:  failed to execute regex matching, pattern is NULL
  108. 2014-12-30 23:34:52: pid 6748: WARNING:  failed to execute regex matching, pattern is NULL
  109. 2014-12-30 23:35:28: pid 6748: LOG:  Frontend terminated
  110. 2014-12-30 23:35:28: pid 6748: DETAIL:  received message kind 'X' from frontend
  111. 2014-12-30 23:35:28: pid 6651: LOG:  Frontend terminated
  112. 2014-12-30 23:35:28: pid 6651: DETAIL:  received message kind 'X' from frontend
  113. 2014-12-30 23:35:28: pid 6733: WARNING:  failed to execute regex matching, pattern is NULL
  114. 2014-12-30 23:35:28: pid 6730: WARNING:  failed to execute regex matching, pattern is NULL
  115. 2014-12-30 23:35:41: pid 6733: ERROR:  unable to read data from frontend
  116. 2014-12-30 23:35:41: pid 6733: DETAIL:  socket read failed with an error "Connection reset by peer"
  117. 2014-12-30 23:35:41: pid 6736: ERROR:  unable to read data from frontend
  118. 2014-12-30 23:35:41: pid 6736: DETAIL:  socket read failed with an error "Connection reset by peer"
  119. 2014-12-30 23:35:41: pid 6730: ERROR:  unable to read data from frontend
  120. 2014-12-30 23:35:41: pid 6730: DETAIL:  socket read failed with an error "Connection reset by peer"
  121. 2014-12-30 23:35:41: pid 6631: WARNING:  child process with pid: 6730 was terminated by segmentation fault
  122. 2014-12-30 23:35:41: pid 6631: WARNING:  child process with pid: 6733 was terminated by segmentation fault
  123. 2014-12-30 23:35:41: pid 6631: WARNING:  child process with pid: 6736 was terminated by segmentation fault
  124. 2014-12-30 23:37:09: pid 6909: WARNING:  failed to execute regex matching, pattern is NULL
  125. 2014-12-30 23:37:09: pid 6722: WARNING:  failed to execute regex matching, pattern is NULL
  126. 2014-12-30 23:37:09: pid 6726: WARNING:  failed to execute regex matching, pattern is NULL
  127. 2014-12-30 23:37:46: pid 6726: LOG:  Frontend terminated
  128. 2014-12-30 23:37:46: pid 6726: DETAIL:  received message kind 'X' from frontend
  129. 2014-12-30 23:37:46: pid 6722: LOG:  Frontend terminated
  130. 2014-12-30 23:37:46: pid 6722: DETAIL:  received message kind 'X' from frontend
  131. 2014-12-30 23:38:21: pid 6909: ERROR:  unable to read data from frontend
  132. 2014-12-30 23:38:21: pid 6909: DETAIL:  socket read failed with an error "Connection reset by peer"
  133. 2014-12-30 23:38:21: pid 6631: WARNING:  child process with pid: 6909 was terminated by segmentation fault
  134. 2014-12-30 23:38:46: pid 6725: WARNING:  failed to execute regex matching, pattern is NULL
  135. 2014-12-30 23:38:46: pid 6731: WARNING:  failed to execute regex matching, pattern is NULL
  136. 2014-12-30 23:38:46: pid 6735: WARNING:  failed to execute regex matching, pattern is NULL
  137. 2014-12-30 23:39:24: pid 6731: LOG:  Frontend terminated
  138. 2014-12-30 23:39:24: pid 6731: DETAIL:  received message kind 'X' from frontend
  139. 2014-12-30 23:39:24: pid 6725: LOG:  Frontend terminated
  140. 2014-12-30 23:39:24: pid 6725: DETAIL:  received message kind 'X' from frontend
  141. 2014-12-30 23:40:21: pid 6728: WARNING:  failed to execute regex matching, pattern is NULL
  142. 2014-12-30 23:40:21: pid 6721: WARNING:  failed to execute regex matching, pattern is NULL
  143. 2014-12-30 23:40:22: pid 6731: WARNING:  failed to execute regex matching, pattern is NULL
  144. 2014-12-30 23:40:22: pid 6725: WARNING:  failed to execute regex matching, pattern is NULL
  145. 2014-12-30 23:40:22: pid 6719: WARNING:  failed to execute regex matching, pattern is NULL
  146. 2014-12-30 23:40:40: pid 6721: ERROR:  unable to read data from frontend
  147. 2014-12-30 23:40:40: pid 6721: DETAIL:  socket read failed with an error "Connection reset by peer"
  148. 2014-12-30 23:40:40: pid 6728: ERROR:  unable to read data from frontend
  149. 2014-12-30 23:40:40: pid 6728: DETAIL:  socket read failed with an error "Connection reset by peer"
  150. 2014-12-30 23:40:40: pid 6731: ERROR:  unable to read data from frontend
  151. 2014-12-30 23:40:40: pid 6731: DETAIL:  socket read failed with an error "Connection reset by peer"
  152. 2014-12-30 23:40:40: pid 6735: ERROR:  unable to read data from frontend
  153. 2014-12-30 23:40:40: pid 6735: DETAIL:  socket read failed with an error "Connection reset by peer"
  154. 2014-12-30 23:40:40: pid 6719: ERROR:  unable to read data from frontend
  155. 2014-12-30 23:40:40: pid 6719: DETAIL:  socket read failed with an error "Connection reset by peer"
  156. 2014-12-30 23:40:40: pid 6725: ERROR:  unable to read data from frontend
  157. 2014-12-30 23:40:40: pid 6725: DETAIL:  socket read failed with an error "Connection reset by peer"
  158. 2014-12-30 23:40:40: pid 6631: WARNING:  child process with pid: 6719 was terminated by segmentation fault
  159. 2014-12-30 23:40:40: pid 6631: WARNING:  child process with pid: 6725 was terminated by segmentation fault
  160. 2014-12-30 23:40:40: pid 6631: WARNING:  child process with pid: 6721 was terminated by segmentation fault
  161. 2014-12-30 23:40:40: pid 6631: WARNING:  child process with pid: 6735 was terminated by segmentation fault
  162. 2014-12-30 23:40:40: pid 6631: WARNING:  child process with pid: 6728 was terminated by segmentation fault
  163. 2014-12-30 23:40:40: pid 6631: WARNING:  child process with pid: 6731 was terminated by segmentation fault
  164. 2014-12-30 23:46:52: pid 6734: ERROR:  unable to read data
  165. 2014-12-30 23:46:52: pid 6734: DETAIL:  child connection forced to terminate due to client_idle_limit:600 is reached
  166. 2014-12-30 23:46:52: pid 6631: WARNING:  child process with pid: 6734 was terminated by segmentation fault
  167. 2014-12-30 23:50:55: pid 6996: WARNING:  failed to execute regex matching, pattern is NULL
  168. 2014-12-30 23:53:43: pid 6667: WARNING:  failed to execute regex matching, pattern is NULL
  169. 2014-12-30 23:53:43: pid 7136: WARNING:  failed to execute regex matching, pattern is NULL
  170. 2014-12-30 23:53:43: pid 7007: WARNING:  failed to execute regex matching, pattern is NULL
  171. 2014-12-30 23:54:10: pid 7136: FATAL:  unable to read data from frontend
  172. 2014-12-30 23:54:10: pid 7136: DETAIL:  EOF encountered with frontend
  173. 2014-12-30 23:54:10: pid 7007: FATAL:  unable to read data from frontend
  174. 2014-12-30 23:54:10: pid 7007: DETAIL:  EOF encountered with frontend
  175. 2014-12-30 23:54:10: pid 6667: FATAL:  unable to read data from frontend
  176. 2014-12-30 23:54:10: pid 6667: DETAIL:  EOF encountered with frontend
  177. 2014-12-31 00:01:56: pid 6675: WARNING:  failed to execute regex matching, pattern is NULL
  178. 2014-12-31 00:01:56: pid 7039: WARNING:  failed to execute regex matching, pattern is NULL
  179. 2014-12-31 00:01:56: pid 7320: WARNING:  failed to execute regex matching, pattern is NULL
  180. 2014-12-31 00:02:24: pid 6675: ERROR:  unable to read data from frontend
  181. 2014-12-31 00:02:24: pid 6675: DETAIL:  socket read failed with an error "Connection reset by peer"
  182. 2014-12-31 00:02:24: pid 7039: ERROR:  unable to read data from frontend
  183. 2014-12-31 00:02:24: pid 7039: DETAIL:  socket read failed with an error "Connection reset by peer"
  184. 2014-12-31 00:02:24: pid 7320: ERROR:  unable to read data from frontend
  185. 2014-12-31 00:02:24: pid 7320: DETAIL:  socket read failed with an error "Connection reset by peer"
  186. 2014-12-31 00:02:25: pid 6631: WARNING:  child process with pid: 7320 was terminated by segmentation fault
  187. 2014-12-31 00:02:25: pid 6631: WARNING:  child process with pid: 6675 was terminated by segmentation fault
  188. 2014-12-31 00:02:25: pid 6631: WARNING:  child process with pid: 7039 was terminated by segmentation fault
  189. 2014-12-31 00:04:21: pid 6951: WARNING:  failed to execute regex matching, pattern is NULL
  190. 2014-12-31 00:04:21: pid 6737: WARNING:  failed to execute regex matching, pattern is NULL
  191. 2014-12-31 00:04:21: pid 7495: WARNING:  failed to execute regex matching, pattern is NULL
  192. 2014-12-31 00:04:29: pid 7493: WARNING:  failed to execute regex matching, pattern is NULL
  193. 2014-12-31 00:04:29: pid 7005: WARNING:  failed to execute regex matching, pattern is NULL
  194. 2014-12-31 00:04:29: pid 7494: WARNING:  failed to execute regex matching, pattern is NULL
  195. 2014-12-31 00:04:56: pid 6737: FATAL:  unable to read data from frontend
  196. 2014-12-31 00:04:56: pid 6737: DETAIL:  EOF encountered with frontend
  197. 2014-12-31 00:04:57: pid 7495: FATAL:  unable to read data from frontend
  198. 2014-12-31 00:04:57: pid 7495: DETAIL:  EOF encountered with frontend
  199. 2014-12-31 00:04:57: pid 6951: FATAL:  unable to read data from frontend
  200. 2014-12-31 00:04:57: pid 6951: DETAIL:  EOF encountered with frontend
  201. 2014-12-31 00:05:01: pid 7493: ERROR:  unable to read data from frontend
  202. 2014-12-31 00:05:01: pid 7493: DETAIL:  socket read failed with an error "Connection reset by peer"
  203. 2014-12-31 00:05:01: pid 7005: ERROR:  unable to read data from frontend
  204. 2014-12-31 00:05:01: pid 7005: DETAIL:  socket read failed with an error "Connection reset by peer"
  205. 2014-12-31 00:05:01: pid 7494: ERROR:  unable to read data from frontend
  206. 2014-12-31 00:05:01: pid 7494: DETAIL:  socket read failed with an error "Connection reset by peer"
  207. 2014-12-31 00:05:02: pid 6631: WARNING:  child process with pid: 7494 was terminated by segmentation fault
  208. 2014-12-31 00:05:02: pid 6631: WARNING:  child process with pid: 7005 was terminated by segmentation fault
  209. 2014-12-31 00:05:02: pid 6631: WARNING:  child process with pid: 7493 was terminated by segmentation fault
  210. 2014-12-31 00:05:58: pid 6727: ERROR:  unable to read data
  211. 2014-12-31 00:05:58: pid 6727: DETAIL:  child connection forced to terminate due to client_idle_limit:600 is reached
  212. 2014-12-31 00:05:58: pid 6631: WARNING:  child process with pid: 6727 was terminated by segmentation fault
  213. 2014-12-31 00:06:49: pid 6996: ERROR:  unable to read data
  214. 2014-12-31 00:06:49: pid 6996: DETAIL:  child connection forced to terminate due to client_idle_limit:600 is reached
  215. 2014-12-31 00:06:50: pid 6631: WARNING:  child process with pid: 6996 was terminated by segmentation fault
  216. 2014-12-31 00:07:23: pid 7577: WARNING:  failed to execute regex matching, pattern is NULL
  217. 2014-12-31 00:07:25: pid 7577: LOG:  Unable to parse the query: "select * from trailer
  218.     select * FROM unit" from client 10.88.4.226(38929)
  219. 2014-12-31 00:07:25: pid 7577: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 9195 statement: "select * from trailer
  220.     select * FROM unit" message: "syntax error at or near "select""
  221. 2014-12-31 00:07:25: pid 7577: LOG:  Parse: Error or notice message from backend: : DB node id: 0 backend pid: 9195 statement: "select * from trailer
  222.     select * FROM unit" message: "syntax error at or near "select""
  223. 2014-12-31 00:07:28: pid 7574: WARNING:  failed to execute regex matching, pattern is NULL
  224. 2014-12-31 00:07:28: pid 6718: WARNING:  failed to execute regex matching, pattern is NULL
  225. 2014-12-31 00:07:28: pid 6680: WARNING:  failed to execute regex matching, pattern is NULL
  226. 2014-12-31 00:07:52: pid 6718: FATAL:  unable to read data from frontend
  227. 2014-12-31 00:07:52: pid 6718: DETAIL:  EOF encountered with frontend
  228. 2014-12-31 00:07:52: pid 6680: FATAL:  unable to read data from frontend
  229. 2014-12-31 00:07:52: pid 6680: DETAIL:  EOF encountered with frontend
  230. 2014-12-31 00:07:52: pid 7574: FATAL:  unable to read data from frontend
  231. 2014-12-31 00:07:52: pid 7574: DETAIL:  EOF encountered with frontend
  232. 2014-12-31 00:09:52: pid 6699: WARNING:  failed to execute regex matching, pattern is NULL
  233. 2014-12-31 00:09:52: pid 6995: WARNING:  failed to execute regex matching, pattern is NULL
  234. 2014-12-31 00:09:52: pid 6738: WARNING:  failed to execute regex matching, pattern is NULL
  235. 2014-12-31 00:10:16: pid 6995: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 9260 statement: "insert into Trailer (bodyframe, color, doortype, liftgate, maker, model, suspensiontype, trailertype, vin, year, idunit) values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11)" message: "null value in column "trailertype" violates not-null constraint"
  236. 2014-12-31 00:10:16: pid 6995: LOG:  pool_send_and_wait: Error or notice message from backend: : DB node id: 0 backend pid: 9260 statement: "SELECT NULL AS TABLE_CAT, n.nspname AS TABLE_SCHEM, c.relname AS TABLE_NAME,  CASE n.nspname ~ '^pg_' OR n.nspname = 'information_schema'  WHEN true THEN CASE  WHEN n.nspname = 'pg_catalog' OR n.nspname = 'information_schema' THEN CASE c.relkind   WHEN 'r' THEN 'SYSTEM TABLE'   WHEN 'v' THEN 'SYSTEM VIEW'   WHEN 'i' THEN 'SYSTEM INDEX'   ELSE NULL   END  WHEN n.nspname = 'pg_toast' THEN CASE c.relkind   WHEN 'r' THEN 'SYSTEM TOAST TABLE'   WHEN 'i' THEN 'SYSTEM TOAST INDEX'   ELSE NULL   END  ELSE CASE c.relkind   WHEN 'r' THEN 'TEMPORARY TABLE'   WHEN 'i' THEN 'TEMPORARY INDEX'   WHEN 'S' THEN 'TEMPORARY SEQUENCE'   WHEN 'v' THEN 'TEMPORARY VIEW'   ELSE NULL   END  END  WHEN false THEN CASE c.relkind  WHEN 'r' THEN 'TABLE'  WHEN 'i' THEN 'INDEX'  WHEN 'S' THEN 'SEQUENCE'  WHEN 'v' THEN 'VIEW'  WHEN 'c' THEN 'TYPE'  ELSE NULL  END  ELSE NULL  END  AS TABLE_TYPE, d.description AS REMARKS  FROM pg_catalog.pg_namespace n, pg_catalog.pg_class c  LEFT JOIN pg_catalog.pg_description d ON (c.oid = d.objoid AND d.objsubid = 0)  LEFT JOIN pg_catalog.pg_class dc ON (d.classoid=dc.oid AND dc.relname='pg_class')  LEFT JOIN pg_catalog.pg_namespace dn ON (dn.oid=dc.relnamespace AND dn.nspname='pg_catalog')  WHERE c.relnamespace = n.oid  AND c.relname LIKE 'PROBABLYNOT'  AND (false  OR ( c.relkind = 'r' AND n.nspname !~ '^pg_' AND n.nspname <> 'information_schema' ) )  ORDER BY TABLE_TYPE,TABLE_SCHEM,TABLE_NAME " message: "current transaction is aborted, commands ignored until end of transaction block"
  237. 2014-12-31 00:10:16: pid 6995: LOG:  Parse: Error or notice message from backend: : DB node id: 0 backend pid: 9260 statement: "SELECT NULL AS TABLE_CAT, n.nspname AS TABLE_SCHEM, c.relname AS TABLE_NAME,  CASE n.nspname ~ '^pg_' OR n.nspname = 'information_schema'  WHEN true THEN CASE  WHEN n.nspname = 'pg_catalog' OR n.nspname = 'information_schema' THEN CASE c.relkind   WHEN 'r' THEN 'SYSTEM TABLE'   WHEN 'v' THEN 'SYSTEM VIEW'   WHEN 'i' THEN 'SYSTEM INDEX'   ELSE NULL   END  WHEN n.nspname = 'pg_toast' THEN CASE c.relkind   WHEN 'r' THEN 'SYSTEM TOAST TABLE'   WHEN 'i' THEN 'SYSTEM TOAST INDEX'   ELSE NULL   END  ELSE CASE c.relkind   WHEN 'r' THEN 'TEMPORARY TABLE'   WHEN 'i' THEN 'TEMPORARY INDEX'   WHEN 'S' THEN 'TEMPORARY SEQUENCE'   WHEN 'v' THEN 'TEMPORARY VIEW'   ELSE NULL   END  END  WHEN false THEN CASE c.relkind  WHEN 'r' THEN 'TABLE'  WHEN 'i' THEN 'INDEX'  WHEN 'S' THEN 'SEQUENCE'  WHEN 'v' THEN 'VIEW'  WHEN 'c' THEN 'TYPE'  ELSE NULL  END  ELSE NULL  END  AS TABLE_TYPE, d.description AS REMARKS  FROM pg_catalog.pg_namespace n, pg_catalog.pg_class c  LEFT JOIN pg_catalog.pg_description d ON (c.oid = d.objoid AND d.objsubid = 0)  LEFT JOIN pg_catalog.pg_class dc ON (d.classoid=dc.oid AND dc.relname='pg_class')  LEFT JOIN pg_catalog.pg_namespace dn ON (dn.oid=dc.relnamespace AND dn.nspname='pg_catalog')  WHERE c.relnamespace = n.oid  AND c.relname LIKE 'PROBABLYNOT'  AND (false  OR ( c.relkind = 'r' AND n.nspname !~ '^pg_' AND n.nspname <> 'information_schema' ) )  ORDER BY TABLE_TYPE,TABLE_SCHEM,TABLE_NAME " message: "current transaction is aborted, commands ignored until end of transaction block"
  238. 2014-12-31 00:10:16: pid 6732: WARNING:  failed to execute regex matching, pattern is NULL
  239. 2014-12-31 00:10:16: pid 6995: LOG:  Frontend terminated
  240. 2014-12-31 00:10:16: pid 6995: DETAIL:  received message kind 'X' from frontend
  241. 2014-12-31 00:10:17: pid 6699: FATAL:  unable to read data from frontend
  242. 2014-12-31 00:10:17: pid 6699: DETAIL:  EOF encountered with frontend
  243. 2014-12-31 00:10:17: pid 6732: FATAL:  unable to read data from frontend
  244. 2014-12-31 00:10:17: pid 6732: DETAIL:  EOF encountered with frontend
  245. 2014-12-31 00:10:17: pid 6738: FATAL:  unable to read data from frontend
  246. 2014-12-31 00:10:17: pid 6738: DETAIL:  EOF encountered with frontend
  247. 2014-12-31 00:17:29: pid 7577: ERROR:  unable to read data
  248. 2014-12-31 00:17:29: pid 7577: DETAIL:  child connection forced to terminate due to client_idle_limit:600 is reached
  249. 2014-12-31 00:17:29: pid 6631: WARNING:  child process with pid: 7577 was terminated by segmentation fault
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!