[Spacewalk-list] Spacewalk-hostname-rename behavior

[Jan Dobes]

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,
-- 
Jan Dobes
Satellite Engineering, Red Hat