Updating Timezone from Europe/Kiev to Europe/Kyiv

Building from Source and Advanced Topics
1

Hi everyone,

Yesterday, I updated to the latest version of GCE. First, I upgraded Ubuntu from 22.04 to Ubuntu 24.04.1, then I updated GCE. After that, I encountered an issue where, after entering my login and password in the web interface, I got the following error in gvmd.log:

md   main:MESSAGE:2025-01-28 13h56.39 utc:3437:    Greenbone Vulnerability Manager version 24.3.1 (DB revision 256)
md manage:WARNING:2025-01-28 13h59.50 utc:3574: sql_exec_internal: PQexec failed: ERROR:  invalid value for parameter "TimeZone": "Europe/Kiev" (7)
md manage:WARNING:2025-01-28 13h59.50 utc:3574: sql_exec_internal: SQL: SET SESSION TIME ZONE 'Europe/Kiev';
md manage:WARNING:2025-01-28 13h59.50 utc:3574: sqlv: sql_exec_internal failed
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(+0x727a0) [0x62f820c847a0]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x45320) [0x7451bfe45320]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11c) [0x7451bfe9eb1c]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x1e) [0x7451bfe4526e]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(abort+0xdf) [0x7451bfe288ff]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(+0x71ed7) [0x62f820c83ed7]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(+0x141b40) [0x62f820d53b40]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x629e7) [0x7451c01aa9e7]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_markup_parse_context_parse+0xd29) [0x7451c01ace99]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(process_gmp_client_input+0x4f) [0x62f820d6219f]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(serve_gmp+0x4c3) [0x62f820c88903]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(+0x72324) [0x62f820c84324]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(+0x729d1) [0x62f820c849d1]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(gvmd+0x1c71) [0x62f820c87a41]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x2a1ca) [0x7451bfe2a1ca]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x8b) [0x7451bfe2a28b]
md   main:MESSAGE:2025-01-28 13h59.50 utc:3574: BACKTRACE: gvmd: Serving client(_start+0x25) [0x62f820c83f85]
md manage:MESSAGE:2025-01-28 13h59.50 utc:3574: Received Aborted signal

I started checking the timezones. The system was using Europe/Kyiv, and PostgreSQL 14 was also set to Europe/Kyiv, so most likely, the issue was with GCE, which still uses Europe/Kiev.

For me, the issue was resolved by simply installing the tzdata-legacy package.

However, would it make sense to update the timezone name in GCE to Europe/Kyiv? This is the more accurate and currently widely used name for the city.

2

It is usually the best to address the responsible development team with such questions / suggestions. Rationale is that the chances are high that it won’t get noticed when positing here (keep in mind this is a user based support forums with a few developers looking into it on a volunteer basis).

On a quick glance i seems the matching repository would be this:

2 Likes
3

Hi, thanks a lot for the hint. I created a PR at Update list of possible timezones by bjoernricks · Pull Request #4309 · greenbone/gsa · GitHub to update the timezones and use the ones from https://momentjs.com/timezone/ instead.

5 Likes