Warnings during updates: should I be worried?

Support
,
1

My YunoHost server

Hardware: VPS bought online
YunoHost version: 11.1.21.4 (stable).
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

I have several warnings in the last system updates I did, and that for several weeks, but I don’t know if I should be worried or not:

2023-06-29 21:30:23,020: INFO - + Setting up yunohost (11.1.21.4) ...
2023-06-29 21:30:23,042: INFO - + Regenerating configuration, this might take a while...
2023-06-29 21:30:54,145: WARNING - The configuration file '/etc/systemd/system/ntp.service.d/ynh-override.conf' has been manually modified and will not be updated
2023-06-29 21:30:54,263: WARNING - The configuration file '/etc/ldap/slapd.ldif' has been manually modified and will not be updated
2023-06-29 21:30:54,387: WARNING - The configuration file '/var/www/.well-known/domain2.tld/autoconfig/mail/config-v1.1.xml' has been manually modified and will not be updated
2023-06-29 21:30:54,547: INFO - + Configuration updated for 'dnsmasq'

2023-06-29 21:31:45,589: INFO - + Updating application catalog...
2023-06-29 21:31:45,797: WARNING - Unable to download the default app catalog: Corrupted JSON read from https://app.yunohost.org/default/v3/apps.json (reason: Unterminated string starting at: line 1 column 65132 (char 65131))

Full log : https://paste.yunohost.org/raw/omipubebin

Thanks in advance for your advices :slight_smile:

2

I think you should have a look on this command

yunohost tools regen-conf --with-diff --dry-run

Have a look https://yunohost.org/en/ssh#some-useful-commands

and on the man page

man yunohost | grep regen

This warning appears if you have modified manually some conf files

3

Thanks for your answer.

Very strange because I don’t think I did.

I used

and get an enormous file (with I think a lot of sensitive information about my server).

The only custom change I did and want to keep is custom port for SSH authentification and no ssh password authentification…

4

Perhpas a old update which don’t update this files … And since that time they have remained unchanged

We would have to wait for an opinion from a great sage :wink:

If you are a player, you can try to apply this regeneration
You just have to remove the option --dry-run

Make a backup first though.

1 Like
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.