[DRE-maint] Bug#916306: gitlab: Error during gitlab installation

Pranith Kumar bobby.prani at gmail.com
Thu Dec 13 19:52:52 GMT 2018


OK. I manually copied gitlab-debian.conf from /var/lib/gitlab/ to
/etc/gitlab/ and it was overwritten during the configure step with the
package maintainers version. It now proceeds past the previous error
message.

Now, I am seeing a new error as follows:

$ sudo dpkg --configure gitlab
Setting up gitlab (11.3.11+dfsg-1) ...
Creating runtime directories for gitlab...
Updating file permissions...
Configuring hostname and email...
Registering /usr/lib/tmpfiles.d/gitlab.conf via ucf
/etc/systemd/system/gitlab-mailroom.service.d/override.conf already exist
/etc/systemd/system/gitlab-unicorn.service.d/override.conf already exist
/etc/systemd/system/gitlab-sidekiq.service.d/override.conf already exist
/etc/systemd/system/gitlab-workhorse.service.d/override.conf already exist
Registering /etc/gitlab-shell/config.yml via ucf
Registering /etc/gitlab/gitlab.yml via ucf
Registering /etc/gitlab/gitlab-debian.conf via ucf
Reloading nginx configuration...
nginx.service is not active, cannot reload.
invoke-rc.d: initscript nginx, action "reload" failed.
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 gitlab

Thanks,

On Thu, Dec 13, 2018 at 11:38 AM Pirate Praveen
<praveen at onenetbeyond.org> wrote:
>
> On 12/14/18 12:58 AM, Pranith Kumar wrote:
> > Hmm, I don't understand what you mean by "feel of the installation".
>
> Just so you see the prompt, but you saw it already, so ignore that part.
>
> > The fqdn prompt did show up the first time, but due to other errors
> > the installation did not finish then.
>
> yes.
>
> > Now that the other problems are resolved, I need a way to reset the
> > fqdn setting. Ideally, a purge should remove the configuration file
> > that holds this setting. Do you know which config file has this? It is
> > not /etc/gitlab/gitlab-debian.conf since that file does not exist yet.
> >
> > I think the purge is not deleting everything it should.
>
> purge only tries to delete things it can and ignores any failures. In
> local systems I tried, purge always brings back those questions.
>
> This is the regular debconf questions if you want to dig deeper. Or try
> to modify the postinst script to strip 'https://' in that host
> configuration step.
>
> https://salsa.debian.org/ruby-team/gitlab/blob/master/debian/gitlab.postinst#L133
>
> Once you modify, build the new deb and try installing that.
>


-- 
Pranith



More information about the Pkg-ruby-extras-maintainers mailing list