cubicweb #1446723 Cubicweb crashes when upgrade postgres on debian [rejected]
When doing a debian upgrade of postgres (which probably does a restart) cubicweb silently crashes. On status we get a "instance has pid XXX but doesn't seem to be running" | |
| priority | normal |
|---|---|
| type | bug |
| done in | <not specified> |
| load | 0.000 |
| load left | 0.000 |
| closed by | <not specified> |
Comments
-
2011/03/29 07:06, written by sthenault
-
2011/03/29 07:25, written by alutz
- install postgres version X
- install cubicweb and create instance
- have the cw instance running
- enable a source where you have a newer version of postgres
- update debian and upgrade postgres
- check cw-ctl status
-
2011/03/29 07:36, written by sthenault
-
2011/03/29 07:52, written by alutz
-
2011/03/29 07:57, written by sthenault
add commentwill be rejected if no more info are provided.
Test case is the following :
what does mean "enable a source where you have a newer version of postgres" ?
For example, install a lenny that has postgres version 8.3.14-0lenny1, then enable lenny-backports that has 8.4.7-0squeeze1~bpo50+1 in it.
This simulates the version upgrade procedure.
Does a c-c restart fix the pb ?
Is the older version of postgres removed ?
Isn't it because debian package change the default version of postgres,
making the 'port' configuration mandatory in the sources file, while it
wasn't earlier?
I'm not sure we can't anything about it in that later case. IMO the
responsible is the postgres debian package which change the default PG
version without asking.