Closed Jeanoo closed 3 years ago
Can you please connect to your instance over ssh, execute the following command and include its output (make sure to replace all IP addresses and urls with placeholders):
ncc notify_push:self-test
I have copied the command in Putty, but I get the following error
There are no commands defined in the "notify_push" namespace.
I have a raspberypi 4
Oh, I see. HPB is only relevant for Nextcloud version 21 and higher. You can ignore that error as long as you didn't update your NC version
One of my customers is facing the same issue. He is running NC 22.2.2 on a RasPi 4 and HPB service is still down.
@nephilim75 I have created a new issue, as this is a different bug: #1397
I am in exactly the same situation
One of my customers is facing the same issue. He is running NC 22.2.2 on a RasPi 4 and HPB service is still down.
@Jeanoo @nephilim75 Please reboot ncp or run systemctl restart notify_push
. A fix has been pushed to devel, so this shouldn't occur anymore in the future
after executing the order, it's always the same HPB service down
per@raspberrypi:~ $ systemctl restart notify_push
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentification requise pour redémarrer « notify_push.service ».
Authenticating as: ,,, (pi)
Password:
==== AUTHENTICATION COMPLETE ===
per@raspberrypi:~ $
@Jeanoo try again with
sudo systemctl restart notify_push
Also please use the forum if you need assistance or have questions.
thank you for the help
always the same thing HPB service | down
@Jeanoo In that case, that's yet a different bug or configuration issue. Please use the forum (as recommended by @ovpc) to check that. Please include the output of ncp-report
and ncc notify_push:self-test
. If it turns out to be another bug, you can create a new issue and describe the bug in detail.
this is very strange! i updated several apps, then ran sudo systemctl restart notify_push
and the HPB service is up
I have again problems with HPB service
sudo ncp-report
<--! Paste this in GitHub report -->
sudo ncc notify_push:self-test ✓ redis is configured 🗴 can't connect to push server: cURL error 6: Could not resolve host: raspberrypi (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://raspberrypi/push/test/cookie
@Jeanoo Can you run systemctl restart notify_push
and check again? Currently, the HPB service sometimes doesn't survive nextcloud updates (it's on my list)
thank you theCalcaholic this time did not correct the problem, it remains unavailable
Same for me. I did an ncp-dist-upgrade, ran into an unmet dependency error with smbclient, solved it by following the steps mentioned here, and reran the ncp-dist-upgrade. I've rebooted a few times and run the systemctl command above prior to the most recent reboot. HPB service is down and the 80 and 443 ports are closed.
@Jeanoo Okay, I think I understand the issue. I'll work on a fix tomorrow
Ok
I'm also getting HPB service down
. I'm using nextcloudpi v1.49.0 using docker.
ncc notify_push:self-test
reports the following
redis is configured
can't connect to push server: cURL error 6: Could not resolve host: 335f71e044c0 (see ...) for https://335f71e044c0/push/test/cookie
I have no idea where it got that 335f71e044c0
from. Can I fix the push server URL anywhere?
It happened to me after one day of fresh install. On LXC.
I have the same issue. Everytime I checked HPB service was down. It looks like it´s related to php-json
dependency to php8.2
. I trid to run ncc
but the PHP client by command line is 8.2 and I got the message
This version of Nextcloud is not compatible with PHP>=8.2.<br/>You are currently running 8.2.0.
I fixed it setting PHP 8.1 as php client
sudo update-alternatives --set php /usr/bin/php8.1
After that everything is good.
I hope this could help others!
Thank you
A fix for this is in the pipeline in the development branch, removing the deprecated php-json
package, it's now included in the base php package instead and if the php-json
package is installed apt update
ends up installing some php 8.2 packages which are incompatible with the nextcloud version
I disable Collabora Online - Built-in CODE Server (ARM64) and Nextcloud Office app then enable again. This problem then resolve
Hello I saw this today Nextcloudpi 1.39.1