"-- Unit postgresql.service has begun shutting down.
Mar 07 08:16:19 rockstor-build pg_ctl: pg_ctl: PID file “/var/lib/pgsql/data/postmaster.pid” does not exist
Mar 07 08:16:19 rockstor-build pg_ctl: Is server running?
Mar 07 08:16:19 rockstor-build systemd: postgresql.service: control process exited, code=exited status=1
Mar 07 08:16:19 rockstor-build systemd: postgresql.service: main process exited, code=exited, status=1/FAILURE
Mar 07 08:16:19 rockstor-build systemd: Unit postgresql.service entered failed state.
Mar 07 08:16:19 rockstor-build systemd: postgresql.service failed.
Mar 07 08:16:19 rockstor-build systemd: Starting PostgreSQL database server…
– Subject: Unit postgresql.service has begun start-up
journalctl -xe show this error:
Mar 07 08:16:21 rockstor-build initrock: File “/root/rockstor/rockstor-core/src/rockstor/system/osi.py”, line 176, in run_command
Mar 07 08:16:21 rockstor-build initrock: raise CommandException(cmd, out, err, rc)
Mar 07 08:16:21 rockstor-build initrock: system.exceptions.CommandException: Error running a command. cmd = su - postgres -c psql storageadmin -f /root/rockstor/rockstor-core//conf/storageadmin.sql.in. rc = 1. stdout = [’’]. stde Mar 07 08:16:21 rockstor-build systemd: Removed slice user-26.slice.
– Unit user-26.slice has begun shutting down.
Mar 07 08:16:21 rockstor-build systemd: rockstor-pre.service: main process exited, code=exited, status=1/FAILURE
Mar 07 08:16:21 rockstor-build systemd: Failed to start Tasks required prior to starting Rockstor.
– Subject: Unit rockstor-pre.service has failed
can anyone help me to solve this problem? thank you
@Marvin, welcome to the community forums. I assume, you are building from source on Tumbleweed or other flavor of OpenSUSE?
Which version of postgresql is the system using before you starting the installation? I have to rely on @phillxnet to confirm that this is still required or not, but there seemed to have been a similar issue early on related to the postgresql version used by default:
in this post:
and specifically here:
Take a look and see whether helps address your issue.
As indicated by @Hooverdan our new development targeted is Leap15.1 because it has much newer btrfs back-port and btrfs is supported by the openSUSE developers.
So yes if you wish to contribute to the development it is required to use an openSUSE base, ideally both Leap15.1 and Tumbleweed but mainly Leap15.1 currrently. But also all changes must be tested on CentOS. But our openSUSE notes are currently better.
The following is our up-to-date guide for developers for this newer platform:
Also note that if you just want to test newest releases (currently not as functional as our CentOS rpms) you also have the option of our ‘Built on openSUSE’ rpm releases. They can also update themselves which a source install cannot.
PS: I use a VMware® Workstation 15 Pro to create a Leap15.1 virtual machine for build.
source code is 3.9.2-54.tar.gz
The same error still happen:
– The user manager instance for user 26 has been started. All services queued
– for starting have been started. Note that other services might still be starting
– up or be started at any later time.
– Startup of the manager took 39026 microseconds.
Mar 10 23:55:42 linux-2rf8 su: pam_unix(su-l:session): session closed for user postgres
Mar 10 23:55:42 linux-2rf8 initrock: Traceback (most recent call last):
Mar 10 23:55:42 linux-2rf8 initrock: File “/root/rockstor-rockstor-core-f3f6cd8/bin/initrock”, line 39, in
Mar 10 23:55:42 linux-2rf8 initrock: sys.exit(scripts.initrock.main())
Mar 10 23:55:42 linux-2rf8 initrock: File “/root/rockstor-rockstor-core-f3f6cd8/src/rockstor/scripts/initrock.py”, line 375, in main
Mar 10 23:55:42 linux-2rf8 initrock: run_command([‘su’, ‘-’, ‘postgres’, ‘-c’, “psql storageadmin -f %s/conf/storageadmin.sql.in” % BASE_DIR]) # noqa E501
Mar 10 23:55:42 linux-2rf8 initrock: File “/root/rockstor-rockstor-core-f3f6cd8/src/rockstor/system/osi.py”, line 176, in run_command
Mar 10 23:55:42 linux-2rf8 initrock: raise CommandException(cmd, out, err, rc)
Mar 10 23:55:42 linux-2rf8 initrock: system.exceptions.CommandException: Error running a command. cmd = su - postgres -c psql storageadmin -f /root/rockstor-rockstor-core-f3f6cd8//conf/storageadmin.sql.in. rc = 1. stdout = [‘’].>
Mar 10 23:55:42 linux-2rf8 systemd: Stopping User Manager for UID 26…
– Subject: Unit email@example.com has begun shutting down
– Defined-By: systemd
– Support: systemd-devel Info Page
linux-2rf8:~/rockstor-rockstor-core-f3f6cd8 # alternatives --config postgresql
There is only one alternative in link group postgresql (providing /usr/lib/postgresql): /usr/lib/postgresql10
Nothing to configure.
That’s great, well done. But to avoid others reading this and copying that location my suggestion was:
Do not use /opt/rockstor
That location is reserved for the rpm. A source install can, if desired, be transitioned to an rpm install and if you use "/opt/rockstor’ this will fail badly.
So please do not use “/opt/rockstor” Pretty much anything except that and /root will work but as I stated previously I’d go with:
Not plain rockstor. This facility to move from a source install to an rpm install is particularly important for those developing on rockstor for a short period as they may then wish, once their fix is released in the rpms, to return to a supported self upgrading solution, in place. A database wipe will ensure but it’s still really handy to be able to do this. But using “/opt/rockstor” to build in will break this feature.
Thanks for sharing your success here though. Always good to see another source build, and hopefully development contributions, take palce.
You might like to take a look at our outstanding GitHub issues in case you fancy taking any of them on. Do please indicate on the relevant issue if you do though as that will help to avoid duplication of effort:
Again well done on getting this sorted and also welcome to the development of Rockstor.
@phillxnet , I change build directory to /opt/rockstor-dev, and reinstall leap- 15.1 OS. rebuild rockstor master.
Internal Server Error . still exist.
Any one can help me to solve the problem? Thank you .
Fantastic. I was really scratching my head over this so this is a great find. Well done.
Thanks for sharing your findings. Much appreciated. I’ll let you know when we are public beta testing our new installer as it would be great to have this confirmed as working or otherwise within your initially selected timezone.
Nice find and quite a relieve that you now have this up-and-running. Apologies I wasn’t able to help with this last bit though. It was quite a puzzle.