[Spacewalk-list] Spacewalk-hostname-rename behavior

[Sander Kuusemets]

Hello,

The distribution is

$ cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core) x86_64

Using a spacewalk repository with this url:

http://yum.spacewalkproject.org/2.4/RHEL/7/$basearch/

There, yum says that spacewalk-postgresql is version 2.4.2.

Adding the output of 'yum list spacewalk*' in a textfile, just in case:

> Installed Packages
> spacewalk-admin.noarch 2.4.2-1.el7          @spacewalk
> spacewalk-backend.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-app.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-applet.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-config-files.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-config-files-common.noarch 2.4.23-1.el7         
> @spacewalk
> spacewalk-backend-config-files-tool.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-iss.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-iss-export.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-libs.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-package-push-server.noarch 2.4.23-1.el7         
> @spacewalk
> spacewalk-backend-server.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-sql.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-sql-postgresql.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-tools.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-xml-export-libs.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-backend-xmlrpc.noarch 2.4.23-1.el7         @spacewalk
> spacewalk-base.noarch 2.4.3-1.el7          @spacewalk
> spacewalk-base-minimal.noarch 2.4.3-1.el7          @spacewalk
> spacewalk-base-minimal-config.noarch 2.4.3-1.el7          @spacewalk
> spacewalk-branding.noarch 2.4.6-1.el7          @spacewalk
> spacewalk-certs-tools.noarch 2.4.7-1.el7          @spacewalk
> spacewalk-common.noarch 2.4.2-1.el7          @spacewalk
> spacewalk-config.noarch 2.4.1-1.el7          @spacewalk
> spacewalk-doc-indexes.noarch 2.4.1-1.el7          @spacewalk
> spacewalk-html.noarch 2.4.3-1.el7          @spacewalk
> spacewalk-java.noarch 2.4.78-1.el7         @spacewalk
> spacewalk-java-config.noarch 2.4.78-1.el7         @spacewalk
> spacewalk-java-lib.noarch 2.4.78-1.el7         @spacewalk
> spacewalk-java-postgresql.noarch 2.4.78-1.el7         @spacewalk
> spacewalk-jpp-workaround.noarch 2.3.4-1.el7          @spacewalk
> spacewalk-postgresql.noarch 2.4.2-1.el7          @spacewalk
> spacewalk-repo.noarch 2.4-3.el7            installed
> spacewalk-reports.noarch 2.4.5-1.el7          @spacewalk
> spacewalk-schema.noarch 2.4.24-1.el7         @spacewalk
> spacewalk-search.noarch 2.4.2-1.el7          @spacewalk
> spacewalk-selinux.noarch 2.3.2-1.el7          @spacewalk
> spacewalk-setup.noarch 2.4.6-1.el7          @spacewalk
> spacewalk-setup-jabberd.noarch 2.3.2-1.el7          @spacewalk
> spacewalk-setup-postgresql.noarch 2.3.1-1.el7          @spacewalk
> spacewalk-taskomatic.noarch 2.4.78-1.el7         @spacewalk
> spacewalk-utils.noarch 2.4.20-1.el7         @spacewalk

Best regards,

-- Sander Kuusemets
University of Tartu, High Performance Computing, IT Specialist
Skype: sander.kuusemets1
+372 737 5694

On 12/9/2015 5:50 PM, Jan Dobes wrote:
> On 9.12.2015 08:04 Sander Kuusemets wrote:
>> Hello!
>>
>> Running spacewalk-hostname-rename on my spacewalk instance, I stumbled
>> into a bizarre .. bug?
>>
>> I'm using the internal postgres you get by installing the
>> spacewalk-postgresql package before installing spacewalk itself, and
>> upon running the command, the output is:
>>
>>> [root at localhost ~]# spacewalk-hostname-rename ip
>>> Validating IP ... OK
>>> =============================================
>>> hostname: localhost
>>> ip: ip
>>> =============================================
>>> Stopping rhn-satellite services ... OK
>>> Testing DB connection ... FAILED
>>> Your database isn't running.
>>> Fix the problem and run /usr/bin/spacewalk-hostname-rename again
>>
>> Which means that for some reason, this rename command first shuts down
>> postgresql, and then tries to connect to it. I got around this by
>> starting the postgres service just after it completed "Stopping
>> rhn-satellite services", but I am wondering:
>>
>> Is this the desired behavior?
>>
>> Best regards,
>>
>
> Hi,
>
> I checked the spacewalk-hostname-rename script and it first stop all 
> services but then start database silently. But it's likely there are 
> some bugs - it's only checking for /etc/init.d/postgresql and 
> /etc/init.d/postgresql92-postgresql path and if you are differently 
> named postgresql service or not having it in this old init.d directory 
> it will not find it.
>
> What distribution and postgresql version from what source do you use?
>
> Regards,