search

WillyXJ / facileManager

A modular suite of web apps built with the sysadmin in mind.
www.facilemanager.com
GNU General Public License v2.0
87 stars 37 forks source link

[BUG] fmDHCP cannot update config server files #523

Closed teksetter closed 3 years ago

teksetter commented 3 years ago

Good morning, i installed the fmDHCP module but the server configuration (dhcpd.conf file) is not updated. I have verified that the "server_update_config" field of the fm_dhcp_servers table is not updated by the gui.

if I manually force this field of the table, the client correctly retrieves the configuration and writes it to the server configuration file.

Thankyou

Giuseppe

WillyXJ commented 3 years ago

Hello. Would you please fill out the fields in the "New issue" github form (it should have automatically populated the new issue form with the template)? There is a lot of information I need from that form (version, reproduction steps, etc.).

Thanks.

teksetter commented 3 years ago

Hi WillyXJ, sorry if I answer you just now, but I tried to start from scratch with the configuration of easyManager but the problem reoccurs.

Replace everything between stars with current version of your easyManager and module installations: fM Version: 4.0.3 fMDHCP Version: 0.4.6

The fMDHCP client module is installed in cron mode. The insertion of the DHCP records by GUI is done without problems. When I click on the button to update the server configuration files I get the message:

dhcp-svr -> This server will be updated on the next cron run. All updates have been processed.

I wait for the cron daemon to start but the dhcp server configuration is not updated.

In the client logs I find "fmDHCP: No updates found."

I have verified that the "server_update_config" field of the fm_dhcp_servers table is not updated by the gui.

if I manually force to "yes" this field of the table, the client correctly retrieves the configuration and writes it to the server configuration file.

Thankyou

Giuseppe

twildATgmxde commented 3 years ago

Hello Everybody,

I can confirm that behavior absolutely as well the workaround Giuseppe! After the cron Job finished the flag correctly off!

@WillyXJ is there a schedule plane of next release?

Many thanks in advance.

regards Thomas

twildATgmxde commented 3 years ago

Hello Everybody, i found a workaround.

Change the enum structure in table fm_dhcp_servers:

server_update_config | enum('yes', 'no') --> server_update_config | enum('yes', 'no', 'conf')

because the core package handles it as conf and no longer as yes.

regards Thomas
teksetter commented 3 years ago

Great, it works!

WillyXJ commented 3 years ago

This is now fixed in fmDHCP 0.5.0 and later.