Steps to reproduce:
1. Upgrade the server to 8.0 (or install it fresh) and start it. It inserts the serverid row.
2. Connect any active proxy.
3. Watch zabbix_server.log.

Result:
setting 'serverid' is not found is logged every time the settings are synced, including on each proxy configuration request.

Expected:
No warning. serverid should be in settings_description_table, probably as ZBX_SETTING_TYPE_STR with no proxy flag, like instanceid. Alternatively, the readers should skip it explicitly.

Impact:
Log noise only, as far as observed. The row is skipped and configuration sync completes normally.

 

After upgrading to 8.0, the server log repeatedly shows:

setting 'serverid' is not found

The server creates the serverid setting itself, but the setting isn't in the server's own table of known settings.

1. At startup, zbx_db_check_serverid() (src/libs/zbxdbhigh/db.c, called from src/zabbix_server/server.c) inserts the row if it doesn't exist (added for ZBXNEXT-9109):
insert into settings (name,type,value_str,value_int) values ('serverid',1,'<uuid7>',0)
2. settings_description_table in src/libs/zbxcacheconfig/dbsettings.c has no entry for serverid, unlike instanceid and software_update_checkid.
3. Any code that walks all rows of the settings table then calls zbx_settings_descr_get() for each row. For the serverid row this logs setting '%s' is not found at WARNING level (dbsettings.c). Callers include:
   - setup_entry_table() in dbsettings.c, during the configuration cache sync. Its own CRIT message, Setting '%s' not found, also applies here.
   - the proxy configuration builder in src/zabbix_server/proxyconfigread/proxyconfigread.c, which runs on every proxy configuration sync. With a proxy connected, the warning repeats at every ProxyConfigFrequency.