ZNC not saving module settings to config files #484

New Issue

2026-10-05T04:24:31+02:00

adam commented

2026-10-05 04:24:31 +02:00

Problem i have been struggling for a while now. As i understand, ZNC keeps the configuration in memory. To store it to the on-disk config file you have to trigger a SIGUSR1 on the process.

This works fine for the main znc config, but the config for all loaded modules is not affected by this. So all settings for the modules are gone after restarting the service, rebooting, etc.

Version in use: ZNC 1.4 from EPEL7 repository on CentOS7.

Problem i have been struggling for a while now. As i understand, ZNC keeps the configuration in memory. To store it to the on-disk config file you have to trigger a SIGUSR1 on the process. This works fine for the main znc config, but the config for all loaded modules is not affected by this. So all settings for the modules are gone after restarting the service, rebooting, etc. Version in use: ZNC 1.4 from EPEL7 repository on CentOS7.

adam closed this issue

2026-10-05 04:24:31 +02:00

adam commented

2026-10-05 04:24:32 +02:00

You can either use webadmin or /msg *status saveconfig.

Version in use: ZNC 1.4 from EPEL7 repository on CentOS7.

As far as I am aware, ZNC doesn't support 1.4 anymore as 1.6.0 is released.

You can either use webadmin or `/msg *status saveconfig`. > Version in use: ZNC 1.4 from EPEL7 repository on CentOS7. As far as I am aware, ZNC doesn't support 1.4 anymore as 1.6.0 is released.

adam commented

2026-10-05 04:24:33 +02:00

Which exact module are you talking about? Most modules save their own
settings immediately, even without any /msg *status saveconfig

2015-02-24 6:41 GMT-08:00 Mikaela Suomalainen notifications@github.com:

You can either use webadmin or /msg *status saveconfig.

Version in use: ZNC 1.4 from EPEL7 repository on CentOS7.

As far as I am aware, ZNC doesn't support 1.4 anymore as 1.6.0 is released.

—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/issues/885#issuecomment-75768090.

Which exact module are you talking about? Most modules save their own settings immediately, even without any /msg *status saveconfig 2015-02-24 6:41 GMT-08:00 Mikaela Suomalainen notifications@github.com: > You can either use webadmin or /msg *status saveconfig. > > Version in use: ZNC 1.4 from EPEL7 repository on CentOS7. > > As far as I am aware, ZNC doesn't support 1.4 anymore as 1.6.0 is released. > > — > Reply to this email directly or view it on GitHub > https://github.com/znc/znc/issues/885#issuecomment-75768090.

adam commented

2026-10-05 04:24:34 +02:00

At least for the stickychan module there is PR #881 which basically adds "more automated saving".
@moodydeath could you mention a specific module you are having problems with?

At least for the stickychan module there is PR #881 which basically adds "more automated saving". @moodydeath could you mention a specific module you are having problems with?

adam commented

2026-10-05 04:24:34 +02:00

Sorry for the late response,

unfortunatelly did not have time to do more extensive testing on 1.4. (and won't do any help as it is not supported anymore)

Got 1.6 from EPEL7 repository a few days after reporting the bug.

No complaints from anyone on the server since then. Commonly used modules like 'simple_away', 'stickychan', 'autoop', 'autovoice', 'perform', etc. are active.

Sorry for the late response, unfortunatelly did not have time to do more extensive testing on 1.4. (and won't do any help as it is not supported anymore) Got 1.6 from EPEL7 repository a few days after reporting the bug. No complaints from anyone on the server since then. Commonly used modules like 'simple_away', 'stickychan', 'autoop', 'autovoice', 'perform', etc. are active.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#484