hitch not working after update
Closed this issue · 7 comments
I have a ArchLinux server.
It has hitch that is installed using the hitch-git AUR package. To install use cower -d hitch-git then cd into the hitch-git directory then do a makepkg -si.
I did an update on the system today, the pacman packages as well as the AUR packages and now something is wrong. After a reboot and visiting my page at: https://minho.win it seems that my TLS is not working. Before the update it was working but after the update it complains in the https:// version of my page (http://minho.win is ok).
I reinstalled hitch-git and still I got this error of TLS. I believe that maybe a error with the new version of hitch in git.
Can you please help me?
NOTE:
When I do systemctl start hitch I get this normal output:
* hitch.service - hitch
Loaded: loaded (/usr/lib/systemd/system/hitch.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2018-04-28 20:35:47 UTC; 4s ago
Process: 10749 ExecStart=/usr/bin/hitch --daemon $HITCH_OPTIONS (code=exited, status=0/SUCCESS)
Process: 10748 ExecStartPre=/usr/bin/hitch -t $HITCH_OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 10750 (hitch)
Tasks: 6 (limit: 4698)
Memory: 1.5M
CGroup: /system.slice/hitch.service
|-10750 /usr/bin/hitch --daemon --config /etc/hitch/hitch.conf
|-10751 /usr/bin/hitch --daemon --config /etc/hitch/hitch.conf
|-10752 /usr/bin/hitch --daemon --config /etc/hitch/hitch.conf
|-10753 /usr/bin/hitch --daemon --config /etc/hitch/hitch.conf
|-10754 /usr/bin/hitch --daemon --config /etc/hitch/hitch.conf
`-10755 /usr/bin/hitch --daemon --config /etc/hitch/hitch.conf
Apr 28 20:35:47 rock64 systemd[1]: Starting hitch...
Apr 28 20:35:47 rock64 systemd[1]: Started hitch.
Apr 28 20:35:48 rock64 hitch[10748]: Trying to initialize SSL contexts with your certificates
Apr 28 20:35:48 rock64 hitch[10748]: hitch configuration looks ok.
MORE INFO:
My pacman.log is:
[2018-04-28 18:30] [PACMAN] Running 'pacman -Syyu'
[2018-04-28 18:30] [PACMAN] synchronizing package lists
[2018-04-28 18:30] [PACMAN] starting full system upgrade
[2018-04-28 18:32] [ALPM] transaction started
[2018-04-28 18:32] [ALPM] upgraded linux-api-headers (4.14.8-1 -> 4.16.1-1)
[2018-04-28 18:32] [ALPM] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
[2018-04-28 18:32] [ALPM] upgraded glibc (2.26-11 -> 2.27-2)
[2018-04-28 18:32] [ALPM-SCRIPTLET] Generating locales...
[2018-04-28 18:32] [ALPM-SCRIPTLET] pt_BR.UTF-8... done
[2018-04-28 18:32] [ALPM-SCRIPTLET] pt_PT.UTF-8... done
[2018-04-28 18:32] [ALPM-SCRIPTLET] Generation complete.
[2018-04-28 18:32] [ALPM] upgraded binutils (2.29.1-3 -> 2.30-3)
[2018-04-28 18:32] [ALPM] upgraded gcc-libs (7.3.1+20180312-2 -> 7.3.1+20180406-1)
[2018-04-28 18:32] [ALPM] upgraded gcc (7.3.1+20180312-2 -> 7.3.1+20180406-1)
[2018-04-28 18:32] [ALPM] upgraded jemalloc (1:5.0.1-4 -> 1:5.0.1-4.1)
[2018-04-28 18:32] [ALPM] installed libnsl (1.2.0-1)
[2018-04-28 18:32] [ALPM] upgraded libuv (1.20.0-1 -> 1.20.1-1)
[2018-04-28 18:32] [ALPM] upgraded pam (1.3.0-1 -> 1.3.0-2)
[2018-04-28 18:33] [ALPM] upgraded linux-aarch64 (4.16.3-1 -> 4.16.5-1)
[2018-04-28 18:33] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2018-04-28 18:33] [ALPM] warning: /etc/php/php.ini installed as /etc/php/php.ini.pacnew
[2018-04-28 18:33] [ALPM] upgraded php (7.2.4-1 -> 7.2.5-1)
[2018-04-28 18:33] [ALPM] upgraded php-gd (7.2.4-1 -> 7.2.5-1)
[2018-04-28 18:34] [ALPM] upgraded nextcloud (13.0.1-1 -> 13.0.2-1)
[2018-04-28 18:34] [ALPM] upgraded perl-uri (1.73-1 -> 1.74-1)
[2018-04-28 18:34] [ALPM] upgraded php-apache (7.2.4-1 -> 7.2.5-1)
[2018-04-28 18:34] [ALPM] upgraded php-imap (7.2.4-1 -> 7.2.5-1)
[2018-04-28 18:34] [ALPM] upgraded php-intl (7.2.4-1 -> 7.2.5-1)
[2018-04-28 18:34] [ALPM] upgraded phpmyadmin (4.8.0-1 -> 4.8.0.1-1)
[2018-04-28 18:34] [ALPM] upgraded pinentry (1.1.0-1 -> 1.1.0-2)
[2018-04-28 18:38] [ALPM] upgraded python (3.6.5-1 -> 3.6.5-2)
[2018-04-28 18:38] [ALPM] upgraded thin-provisioning-tools (0.7.5-1 -> 0.7.6-1)
[2018-04-28 18:38] [ALPM] upgraded varnish (5.2.1-2 -> 5.2.1-3)
[2018-04-28 18:38] [ALPM] transaction completed
[2018-04-28 18:38] [ALPM] running '99-linux-aarch64.hook'...
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-aarch64.preset: 'default'
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> -k 4.16.5-1-ARCH -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> Starting build: 4.16.5-1-ARCH
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> WARNING: No modules were added to the image. This is probably not what you want.
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-aarch64.preset: 'fallback'
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> -k 4.16.5-1-ARCH -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> Starting build: 4.16.5-1-ARCH
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2018-04-28 18:38] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-04-28 18:38] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-04-28 18:39] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-04-28 18:39] [ALPM] running 'detect-old-perl-modules.hook'...
[2018-04-28 18:40] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-04-28 18:40] [ALPM] running 'systemd-sysusers.hook'...
[2018-04-28 18:40] [ALPM] running 'systemd-tmpfiles.hook'...
[2018-04-28 18:40] [ALPM] running 'systemd-update.hook'...
[2018-04-28 18:40] [ALPM] running 'texinfo-install.hook'...
[2018-04-28 18:50] [PACMAN] Running 'pacman --color auto -Sy'
[2018-04-28 18:50] [PACMAN] synchronizing package lists
[2018-04-28 18:52] [PACMAN] Running 'pacman --color auto -U --asdeps /tmp/yaourt-tmp-daniel/PKGDEST.HjO/php-igbinary-2.0.5-1-any.pkg.tar.xz'
[2018-04-28 18:52] [ALPM] transaction started
[2018-04-28 18:52] [ALPM] installed php-igbinary (2.0.5-1)
[2018-04-28 18:52] [ALPM] transaction completed
[2018-04-28 18:52] [ALPM] running 'systemd-update.hook'...
[2018-04-28 18:53] [PACMAN] Running 'pacman --color auto -U /tmp/yaourt-tmp-daniel/PKGDEST.ySD/php-redis-4.0.2-1-aarch64.pkg.tar.xz'
[2018-04-28 18:53] [ALPM] transaction started
[2018-04-28 18:53] [ALPM] upgraded php-redis (4.0.0-1 -> 4.0.2-1)
[2018-04-28 18:53] [ALPM] transaction completed
[2018-04-28 18:53] [ALPM] running 'systemd-update.hook'...
I've successfully updated to Hitch 1.4.8 from git (1f5e538, tagged 1.4.8) on Debian buster now. No errors seen.
@alexandre1985 Hi. There is nothing in this issue that points to anything not working as expected. Your logs does not include anything about hitch. Can you re-state what the problem is?
Ok. To see my error visit my page https://mysite00524.com. You'll see there.
Maybe it is something with my tls certificates issuing.
I believe the root of this error is because I have emitted a test certificate last time and now I have to wait like 6 days before I can emit a real one because I have achieve rate limit
Well, it isn't a certificate question.
It is hitch that is giving this problem. I have reinstalled hitch last time and since then it hasn't been able to serve https pages. Need help please!
Hi.
This issue tracker is for tracking software bugs.
Unless you can report something wrong with Hitch, or provide enough information that a documentation update is in order, you're probably better off getting help elsewhere.
Also, with the exception of the people employed by Varnish Software, we're all doing this for free. Please don't think that asking people to check your site and debug it for you is acceptable behaviour. Welcome to open source software, if it breaks you get to keep both pieces.
well, thanks.
How can I get some logs out of hitch?
Well I'm better informed now.
When I try to connect to https://mysite00524.com I get my page correctly but when I try to connect to the https version of it, hitch logs say:
20180504T163509.635701 [ 964] {backend-connect}: Connection refused
My page doesn't use database, so what in the backend may be wrong?