adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-11-03 10:52:22 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

Save config after upgrade #684

New Issue
Open
opened 2026-10-05 04:38:24 +02:00 by adam · 9 comments
adam commented 2026-10-05 04:38:24 +02:00
Owner
Copy link
Copy source

Hi,

recently i have upgraded my ZNC 1.4-2 of Debian Jessie to 1.6.2-2~bpo8+1 from Jessie Backports.

During the upgrade i have killed znc and started it again. After the first start the following is shown which seems to be legit:

[ ** ] Found old config from ZNC 1.4. Saving a backup of it.
[ .. ] Creating a config backup...
[ >> ] /path/to/.znc/configs/znc.conf.pre-1.6.2

However after the next kill of znc and a restart the following is shown again:

[ ** ] Found old config from ZNC 1.4. Saving a backup of it.
[ .. ] Creating a config backup...
[ !! ] File exists

When having a look at the .znc/config/znc.conf the version of the file seems still 1.4:

Version = 1.4

According to http://wiki.znc.in/FAQ#Upgrading_.2F_updating_from_a_previous_release.2C_to_a_new_version the config should be upgraded automatically.

Is there anything else what needs to be done / checked here? I also wasn't able to identify any fixes in the 1.6.3 changelog which might have solved this.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31398205-save-config-after-upgrade?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
Hi, recently i have upgraded my ZNC 1.4-2 of Debian Jessie to 1.6.2-2~bpo8+1 from Jessie Backports. During the upgrade i have killed znc and started it again. After the first start the following is shown which seems to be legit: ``` [ ** ] Found old config from ZNC 1.4. Saving a backup of it. [ .. ] Creating a config backup... [ >> ] /path/to/.znc/configs/znc.conf.pre-1.6.2 ``` However after the next kill of znc and a restart the following is shown again: ``` [ ** ] Found old config from ZNC 1.4. Saving a backup of it. [ .. ] Creating a config backup... [ !! ] File exists ``` When having a look at the .znc/config/znc.conf the version of the file seems still 1.4: ``` Version = 1.4 ``` According to http://wiki.znc.in/FAQ#Upgrading_.2F_updating_from_a_previous_release.2C_to_a_new_version the config should be upgraded automatically. Is there anything else what needs to be done / checked here? I also wasn't able to identify any fixes in the 1.6.3 changelog which might have solved this. ## <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31398205-save-config-after-upgrade?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github). </bountysource-plugin> <!-- github-sync-id:137036684 -->
adam commented 2026-10-05 04:38:25 +02:00
Author
Owner
Copy link
Copy source

Did you kill ZNC or something before it had time to save config by itself? What if you /msg *status saveconfig

Did you kill ZNC or something before it had time to save config by itself? What if you `/msg *status saveconfig` <!-- github-comment-id:189838876 -->
adam commented 2026-10-05 04:38:26 +02:00
Author
Owner
Copy link
Copy source

Hi,

thanks for your reply. znc was running for about 12 hours after the upgrade. Should that be enough for saving the config?

But will also try this saveconfig later this day, thanks for that hint.

Hi, thanks for your reply. znc was running for about 12 hours after the upgrade. Should that be enough for saving the config? But will also try this saveconfig later this day, thanks for that hint. <!-- github-comment-id:189848307 -->
adam commented 2026-10-05 04:38:27 +02:00
Author
Owner
Copy link
Copy source

ZNC doesn't save config with no reason. It's saved either explicitly by user request, or if you join some channel with chansaver module loaded, or if you change some setting in webadmin.

ZNC doesn't save config with no reason. It's saved either explicitly by user request, or if you join some channel with chansaver module loaded, or if you change some setting in webadmin. <!-- github-comment-id:189848672 -->
adam commented 2026-10-05 04:38:27 +02:00
Author
Owner
Copy link
Copy source

@DarthGandalf Ok, thanks. Then it might be useful to add this notice to:

http://wiki.znc.in/FAQ#Upgrading_.2F_updating_from_a_previous_release.2C_to_a_new_version

Currently some one might assume that the config update wen't wrong or similar. From what i have seen there is no notice that ZNC needs to save the config once so it get upgraded.

@DarthGandalf Ok, thanks. Then it might be useful to add this notice to: http://wiki.znc.in/FAQ#Upgrading_.2F_updating_from_a_previous_release.2C_to_a_new_version Currently some one might assume that the config update wen't wrong or similar. From what i have seen there is no notice that ZNC needs to save the config once so it get upgraded. <!-- github-comment-id:189849310 -->
adam commented 2026-10-05 04:38:28 +02:00
Author
Owner
Copy link
Copy source

Ah, the link is also explicitly saying:

Your existing configuration will be upgraded to new version when you start it.

which is then a wrong statement according to your posted info.

Ah, the link is also explicitly saying: > Your existing configuration will be upgraded to new version when you start it. which is then a wrong statement according to your posted info. <!-- github-comment-id:189849599 -->
adam commented 2026-10-05 04:38:29 +02:00
Author
Owner
Copy link
Copy source

It meant that ZNC can read old config and upgrades it "in memory". Then when it saves config, such upgraded config will be saved.
But it's confusing, I agree...

It meant that ZNC can read old config and upgrades it "in memory". Then when it saves config, such upgraded config will be saved. But it's confusing, I agree... <!-- github-comment-id:189850001 -->
adam commented 2026-10-05 04:38:29 +02:00
Author
Owner
Copy link
Copy source

Ok, thats fine. I was just reading that statement and thought something went wrong during the upgrad. :-)

Thanks again for your reply.

Ok, thats fine. I was just reading that statement and thought something went wrong during the upgrad. :-) Thanks again for your reply. <!-- github-comment-id:189850845 -->
adam commented 2026-10-05 04:38:30 +02:00
Author
Owner
Copy link
Copy source

Probably ZNC should be fixed to actually save config after upgrade instead of fixing wiki.
"[ .. ] Creating a config backup... [ !! ] File exists" is confusing regardless of what wiki says.

Probably ZNC should be fixed to actually save config after upgrade instead of fixing wiki. "[ .. ] Creating a config backup... [ !! ] File exists" is confusing regardless of what wiki says. <!-- github-comment-id:189851688 -->
adam commented 2026-10-05 04:38:31 +02:00
Author
Owner
Copy link
Copy source

Yes, that sounds like something i had expected during an upgrade. Thanks again.

My original issue is solved by saving the config.

Yes, that sounds like something i had expected during an upgrade. Thanks again. My original issue is solved by saving the config. <!-- github-comment-id:189885249 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#684