[04:42:17]
<choyer> Good morning, I updated Yunohost last night and got the following two warnings. Is that something concerning, should I re-run some script?
2023-06-11 22:41:00,668: WARNING - chown: cannot dereference '/etc/systemd/system/dbus-org.freedesktop.timesync1.service': No such file or directory
2023-06-11 22:41:01,671: WARNING - Could not run script: /usr/share/yunohost/hooks/conf_regen/01-yunohost
[04:45:35]
<choyer> Good morning, I updated Yunohost last night and got the following two warnings. Is that something concerning, should I re-run some script?
2023-06-11 22:41:00,668: WARNING - chown: cannot dereference '/etc/systemd/system/dbus-org.freedesktop.timesync1.service': No such file or directory
2023-06-11 22:41:01,671: WARNING - Could not run script: /usr/share/yunohost/hooks/conf_regen/01-yunohost
Full log here: https://paste.yunohost.org/raw/juxuzipoqa
[04:45:49]
<choyer> Good morning, I updated Yunohost last night and got the following two warnings. Is that something concerning, should I re-run some script?
2023-06-11 22:41:00,668: WARNING - chown: cannot dereference '/etc/systemd/system/dbus-org.freedesktop.timesync1.service': No such file or directory
2023-06-11 22:41:01,671: WARNING - Could not run script: /usr/share/yunohost/hooks/conf_regen/01-yunohost
Full log here: https://paste.yunohost.org/raw/juxuzipoqa
[04:47:20]
<choyer> Good morning, I updated Yunohost last night and got the following two warnings. Is that something concerning, should I re-run some script?
2023-06-11 22:41:00,668: WARNING - chown: cannot dereference '/etc/systemd/system/dbus-org.freedesktop.timesync1.service': No such file or directory
2023-06-11 22:41:01,671: WARNING - Could not run script: /usr/share/yunohost/hooks/conf_regen/01-yunohost
Full log here: https://paste.yunohost.org/raw/juxuzipoqa
[05:03:01]
<tituspijean[m]> choyer: Hello! There was a bug in that release, I guess you encountered it. cf. https://forum.yunohost.org/t/probleme-d-authentification-apres-mise-a-jour-vers-yunohost-11-1-21/25101/10?u=tituspijean
[05:18:36]
<choyer> I see. I updated to the very latest (bug-free) version this morning, is there anything more I need to do to rectify those warnings?
[06:05:46]
<tituspijean[m]> choyer: when are you getting these errors?
[06:08:58]
<choyer> I have been getting those during yesterday’s update, but all seems to work at the moment.
[10:26:23]
<Chatpitaine Caverne> Bonjour, j'ai une question sur Archivist.
Est-ce qu'il ne garde les fichiers chiffrés que s'il y a un recipient où les déposer.
Parce que mon répertoire enc\_backup\_dir reste désespérément vide alors que la log passe bien par "Encrypt backups".
[10:26:23]
<Chatpitaine Caverne> Bonjour, j'ai une question sur Archivist.
Est-ce qu'il ne garde les fichiers encryptés que s'il y a un recipient où les déposer.
Parce que mon répertoire enc\_backup\_dir reste désespérément vide alors que la log passe bien par "Encrypt backups".
[11:48:56]
<nadine[m]> Hello,
can anybody firm with Postfix help with this? https://forum.yunohost.org/t/postfix-mails-to-main-domain-are-not-sent-user-unknown/24896
[11:51:24]
<Aleks (he/him/il/lui)> i would check that `yunohost tools regen-conf postfix` does not complain about any manually modified files (forget about the /var/www/.well-known/autoconfig, this is not the issue)
[11:51:54]
<Aleks (he/him/il/lui)> and double check that the mail address you're sending to is in fact registered as the main address (or an alias) for this user
[12:30:06]
<nadine[m]> > <@Alekswag[m]:libera.chat> i would check that `yunohost tools regen-conf postfix` does not complain about any manually modified files (forget about the /var/www/.well-known/autoconfig, this is not the issue)
I ran the command. There are no complaints about manually modified files.
[12:32:07]
<nadine[m]> > <@Alekswag[m]:libera.chat> and double check that the mail address you're sending to is in fact registered as the main address (or an alias) for this user
This is a misunderstanding. The main domain's MX record doesn't point to yunohost server but to an external mail server which needs to stay the way it is for various reasons atm. So, I want postfix to send mails to my main domain via external routing but the problem is it thinks that it should be a user which is purposely not the case.
[12:35:57]
<debenny> Hello,
I came across some strange behaviour today. I can connect to yunohost through SSH, it is pingable and even minetest, Email and XMPP are working, but not through Web. That is, whenever I try to connect through the Borwser I get a timeout message. Accordingly the diagnosis gives me this:
[WARNING] Could not diagnose if domains are reachable from outside in IPv4.
- Error: HTTPSConnectionPool(host='diagnosis.yunohost.org', port=443): Read timed out. (read timeout=30)
[WARNING] Could not diagnose if domains are reachable from outside in IPv6.
- Error: HTTPSConnectionPool(host='diagnosis.yunohost.org', port=443): Read timed out. (read timeout=30)
I wonder where to start searching for the error, as systemctl status nginx also tells me it was up and running. Any hints appreciated.
[12:40:44]
<Chatpitaine Caverne> debenny: Is your nginx service started ?
`sudo yunohost service status nginx`
[12:41:08]
<Chatpitaine Caverne> > <@chatpitaine:cirkau.art> debenny: Is your nginx service started ?
> `sudo yunohost service status nginx`
Sorry, I didn't see your last sentence.
[12:41:15]
<debenny> let me check again, command line is laggy now
[12:42:19]
<debenny> yes, output as follows:
configuration: valid
description: Stellt Daten aller Websiten auf dem Server bereit
last_state_change: 2023-06-12 06:02:36
start_on_boot: enabled
status: running
[12:44:42]
<debenny> but now I realised, it became laggy when I had minetest open, so maybe this slows the server down. I realised in htop the average load went above 1, although the CPU usage and RAM usage where rather low (which seems to make no sense to me, but that's what it was like).
Maybe I have too many services running? With 500GB HDD, 16 GB RAM and 6 CPUs I thought this would take a while to take its toll...
[13:00:46]
<debenny> uninstalling lemmy did the trick, aeasy as that
[14:26:36]
<choyer> > <@choyer:tchncs.de> Good morning, I updated Yunohost last night and got the following two warnings. Is that something concerning, should I re-run some script?
>
2023-06-11 22:41:00,668: WARNING - chown: cannot dereference '/etc/systemd/system/dbus-org.freedesktop.timesync1.service': No such file or directory
2023-06-11 22:41:01,671: WARNING - Could not run script: /usr/share/yunohost/hooks/conf_regen/01-yunohost
> Full log here: https://paste.yunohost.org/raw/juxuzipoqa
Can I ask again - after the above happened I updated to the very latest (bug-free) version this morning, is there anything more I need to do to rectify those warnings?
[14:32:24]
<Aleks (he/him/il/lui)> choyer: can you share the output of `ls -l /etc/systemd/system/dbus-org.freedesktop.timesync1.service`
[15:10:22]
<choyer> > <@Alekswag:matrix.org> choyer: can you share the output of `ls -l /etc/systemd/system/dbus-org.freedesktop.timesync1.service`
Output is:
lrwxrwxrwx 1 root root 45 Aug 16 2021 /etc/systemd/system/dbus-org.freedesktop.timesync1.service -> /lib/systemd/system/systemd-timesyncd.service
[15:11:04]
<Aleks (he/him/il/lui)> hmkay
[15:11:39]
<Aleks (he/him/il/lui)> and does `find /etc/systemd/system/ -name '*.service' -maxdepth 1` list this file ? (/etc/systemd/system/dbus-org.freedesktop.timesync1.service)
[15:11:42]
<Aleks (he/him/il/lui)> ah sorry
[15:11:51]
<Aleks (he/him/il/lui)> `find /etc/systemd/system/ -name '*.service' -maxdepth 1 -type f`
[15:13:45]
<choyer> No, doesn’t.
[15:14:29]
<choyer> > <@Alekswag:matrix.org> `find /etc/systemd/system/ -name '*.service' -maxdepth 1 -type f`
find: warning: you have specified the global option -maxdepth after the argument -name, but global options are not positional, i.e., -maxdepth affects
tests specified before it as well as those specified after it. Please specify global options before other arguments.
/etc/systemd/system/yunohost-firewall.service
/etc/systemd/system/proc-hidepid.service
/etc/systemd/system/yunomdns.service
/etc/systemd/system/mastodon-sidekiq.service
/etc/systemd/system/yunohost-api.service
/etc/systemd/system/mastodon-web.service
/etc/systemd/system/writefreely.service
/etc/systemd/system/mastodon-streaming.service
/etc/systemd/system/yunoprompt.service
[15:16:27]
<Aleks (he/him/il/lui)> :|
[15:17:12]
<Aleks (he/him/il/lui)> what about `find /etc/systemd/system/*.service -type f`, is it listed in there ?
[15:17:48]
<Aleks (he/him/il/lui)> (or maybe there's this error `chown: cannot dereference [blah blah]`
[15:23:40]
<choyer> > <@Alekswag:matrix.org> what about `find /etc/systemd/system/*.service -type f`, is it listed in there ?
No, its not there…
/etc/systemd/system/mastodon-sidekiq.service
/etc/systemd/system/mastodon-streaming.service
/etc/systemd/system/mastodon-web.service
/etc/systemd/system/proc-hidepid.service
/etc/systemd/system/writefreely.service
/etc/systemd/system/yunohost-api.service
/etc/systemd/system/yunohost-firewall.service
/etc/systemd/system/yunomdns.service
/etc/systemd/system/yunoprompt.service
[15:24:11]
<Aleks (he/him/il/lui)> meh then I don't understand where that error is coming from :|
[15:24:25]
<Aleks (he/him/il/lui)> i guess one way to get further detail would be to run `yunohost tools regen-conf yunohost --debug`
[15:26:09]
<choyer> It was the error through the earlier update. I have since updated with the latest yunohost version which went error free. Could it be it has been rectified with the newer update?
[15:26:43]
<Aleks (he/him/il/lui)> ah, yes ...
[15:26:48]
<Aleks (he/him/il/lui)> yes this got fixed ..
[15:29:07]
<choyer> Just wanted to ensure I dont have to take additional steps to rectify the earlier warnings from the first update.
[15:43:54]
<choyer> > <@Alekswag:matrix.org> yes this got fixed ..
Thank you kindly for your help.
[23:00:34]
<Gabriel Klavans> Hello! My UEFI installation on a Bee-Link N100 keeps saying that it detects another os installed in Non-UEFI, so I tell it to force UEFI, but then fails on the partitioning step. It says “No UEFI partition detected”, then I select to continue anyway, then it sets up the partitions (I know cause I can see them in G-Parted live after the fact), and then the installation fails. Completely removing all existing partitions and running the installer again gets me as far as “Executing ‘grub-install /dev/nvme0n1’ failed.” I’ve tested installing Debian 12 to make sure the hardware is fine, and it works perfectly. Any advice?
[23:00:46]
<Gabriel Klavans> Hello! My UEFI installation on a Bee-Link N100 keeps saying that it detects another os installed in Non-UEFI, so I tell it to force UEFI, but then fails on the partitioning step. It says “No UEFI partition detected”, then I select to continue anyway, then it sets up the partitions (I know cause I can see them in G-Parted live after the fact), and then the installation fails. Completely removing all existing partitions using gparted live usb and running the installer again gets me as far as “Executing ‘grub-install /dev/nvme0n1’ failed.” I’ve tested installing Debian 12 to make sure the hardware is fine, and it works perfectly. Any advice?
[23:01:14]
<Gabriel Klavans> It also still says that it detects a legacy bios install even when there are 0 partitions on the target drive. Strange!