https://bugzilla.novell.com/show_bug.cgi?id=730326 https://bugzilla.novell.com/show_bug.cgi?id=730326#c1 Reinhard Max changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #1 from Reinhard Max 2011-11-15 12:03:00 CET --- Looks like systemd broke it. Frederic, wasn't it said, that normal start/stop scripts don't need to be touched when transiting to systemd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=730326 https://bugzilla.novell.com/show_bug.cgi?id=730326#c3 Bruno Friedmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #3 from Bruno Friedmann 2011-11-17 14:06:29 UTC --- I've postgresql 9.1.1 running under factory from month and I can assure you that it work. Now perhaps the first start is special, which is the initialization phase. You can bypass systemd by doing to /etc/init.d/ and then /postgresql start also go and check in /var/lib/pgsql/ + data any logs which can give you a clue about the failed start status -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=730326 https://bugzilla.novell.com/show_bug.cgi?id=730326#c5 --- Comment #5 from Di Pe 2011-11-18 12:29:56 UTC --- /root # rcpostgresql start x Initializing the PostgreSQL database at location /home/postgres/datainstall: cannot create directory `/home/postgres': Permission denied ....ah, we have nfs mounted home dirs ... don't many people have that ? Ok may be not on their dedicated DB servers. 7 # In which directory should the PostgreSQL database reside? 8 # 9 ##POSTGRES_DATADIR="~postgres/data" 10 POSTGRES_DATADIR="/var/lib/pgsql/data" may be this is a better default location for the db? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=730326 https://bugzilla.novell.com/show_bug.cgi?id=730326#c7 Maik Wagner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maikwagner@yahoo.com --- Comment #7 from Maik Wagner 2013-01-28 12:39:24 UTC --- (In reply to comment #3)

You can bypass systemd by doing to /etc/init.d/ and then ./postgresql start

also go and check in /var/lib/pgsql/ + data any logs which can give you a clue about the failed start status

I am also having problems starting PostgreSQL-Server The approach mentioned here doesn't work for me: extensa5230e:/etc/init.d # ./postgresql start redirecting to systemctl Starting PostgreSQL 9.1.7 pg_ctl: konnte Server nicht starten Prüfen Sie die Logausgabe. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=730326 https://bugzilla.novell.com/show_bug.cgi?id=730326#c9 --- Comment #9 from Maik Wagner 2013-01-29 12:15:40 UTC --- This is what /var/log/messages tells me: Jan 29 13:11:36 extensa5230e su: (to root) mwagner on /dev/pts/1 Jan 29 13:11:36 extensa5230e su: pam_apparmor(su:session): Unknown error occurred changing to root hat: Die Operation ist nicht erlaubt Jan 29 13:11:37 extensa5230e su: (to postgres) mwagner on /dev/pts/1 Jan 29 13:11:37 extensa5230e su: pam_apparmor(su-l:session): Unknown error occurred changing to postgres hat: Operation not permitted Jan 29 13:11:37 extensa5230e su: (to postgres) mwagner on /dev/pts/1 Jan 29 13:11:37 extensa5230e su: pam_apparmor(su-l:session): Unknown error occurred changing to postgres hat: Operation not permitted Jan 29 13:12:51 extensa5230e dhclient[1417]: DHCPREQUEST on wlan0 to 192.168.44.1 port 67 Jan 29 13:12:51 extensa5230e dhclient[1417]: DHCPACK from 192.168.44.1 Jan 29 13:12:51 extensa5230e dhclient[1417]: bound to 192.168.44.163 -- renewal in 274 seconds. Jan 29 13:15:44 extensa5230e su: (to root) mwagner on /dev/pts/1 Jan 29 13:15:44 extensa5230e su: pam_apparmor(su:session): Unknown error occurred changing to root hat: Die Operation ist nicht erlaubt Please let me know if you need further information. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=730326 https://bugzilla.novell.com/show_bug.cgi?id=730326#c11 --- Comment #11 from Maik Wagner 2013-01-29 12:33:57 UTC --- Thanks for the quick reply. I checked my postmaster.log and noticed it to be empty: extensa5230e:/var/lib/pgsql/data # cat postmaster.log I also had a look at the syslog but I suppose I am not doing it correctly: extensa5230e:/etc/sysctl.d # cat /run/systemd/journal/syslog cat: /run/systemd/journal/syslog: Kein passendes Gerät bzw. keine passende Adresse gefunden extensa5230e:/etc/sysctl.d # less /run/systemd/journal/syslog /run/systemd/journal/syslog is not a regular file (use -f to see it) extensa5230e:/etc/sysctl.d # tail -f /run/systemd/journal/syslog tail: „/run/systemd/journal/syslog“ kann nicht zum Lesen geöffnet werden: Kein passendes Gerät bzw. keine passende Adresse gefunden -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=730326 https://bugzilla.novell.com/show_bug.cgi?id=730326#c13 --- Comment #13 from Maik Wagner 2013-01-29 15:09:49 UTC --- I just uninstalled apparmor. It doesn't show up in YaST anymore. I had a look into the Runlevel-Editor in Yast and noticed that the service is shown as running?: Yes* - I tried to get rid of the star by deactivating the service in Yast (which worked fine) and starting it up again (which resulted in error code 1). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.