+- Snakeoil Forums (https://forums.snakeoil-os.net)
+-- Forum: Snakeoil Topics (https://forums.snakeoil-os.net/Forum-Snakeoil-Topics)
+--- Forum: Support & Troubleshooting (https://forums.snakeoil-os.net/Forum-Support-Troubleshooting)
+--- Thread: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) (/Thread-split-Problem-starting-API-server-1-4-1-Missing-qsqlite3-lib)
Pages:
1
2
RE: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) - agent_kith - 22-Mar-2025
(22-Mar-2025, 09:59 AM)clark8888 Wrote: file sent by emailThere's a bug and the file I want isn't included in the diagnostics file
. This will be fixed in 1.4.2can you send me /var/www/config/snakeoil.db directly instead? thanks
RE: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) - agent_kith - 23-Mar-2025
Unfortunately I cannot recreate this problem in my test environments as the API server still start up fine.
Will need more information so I can better understand the problem.
@clark8888 @jetski when you can, please run the following via SSH:
Code:
sudo systemctl stop snakeoil-rest
QT_PLUGIN_PATH=/usr/local/lib/plugins/ snakeoil-rest --verbosity 10If everything works, you should see this:
Code:
[5] Snakeoil API Listening to requests at: 127.0.0.1:30511 [helper/rest_server.cpp:58|rest_server_c::listen()]Wait about 30 seconds and see if it crashes, and then go to the WebApp and see if it's working. You wouldn't see a 503 error if you see the above line.
RE: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) - clark8888 - 24-Mar-2025
(23-Mar-2025, 08:14 AM)agent_kith Wrote: Unfortunately I cannot recreate this problem in my test environments as the API server still start up fine.
Will need more information so I can better understand the problem.
@clark8888 @jetski when you can, please run the following via SSH:
Code:sudo systemctl stop snakeoil-rest
QT_PLUGIN_PATH=/usr/local/lib/plugins/ snakeoil-rest --verbosity 10
If everything works, you should see this:
Code:[5] Snakeoil API Listening to requests at: 127.0.0.1:30511 [helper/rest_server.cpp:58|rest_server_c::listen()]
Wait about 30 seconds and see if it crashes, and then go to the WebApp and see if it's working. You wouldn't see a 503 error if you see the above line.
[7] Register API endpoint: /api/browse/ Routes: 7 [api/base.cpp:63|base_c:
etup_routes()][5] Snakeoil API Listening to requests at: 127.0.0.1:30511 [helper/rest_server.cpp:58|rest_server_c::listen()]
[3] Statement: INSERT OR REPLACE INTO settings (KEY, VALUE) values ("last_check", "Mon Mar 24 06:43:07 2025") Code: [service/database.cpp:186|database_c::_run_query()]
[5] Query failure: SELECT VALUE FROM settings WHERE key = 'cpuset_config' [service/database.cpp:89|database_c::_get_single_value()]
[5] Query failure: SELECT VALUE FROM settings WHERE key = 'cpuset_shield' [service/database.cpp:89|database_c::_get_single_value()]
[5] Query failure: SELECT VALUE FROM settings WHERE key = 'ramdisk_size' [service/database.cpp:89|database_c::_get_single_value()]
[5] Query failure: SELECT VALUE FROM settings WHERE key = 'ramdisk_type' [service/database.cpp:89|database_c::_get_single_value()]
[5] Query failure: SELECT VALUE FROM settings WHERE key = 'ramdisk_enable' [service/database.cpp:89|database_c::_get_single_value()]
[5] Query failure: SELECT VALUE FROM settings WHERE key = 'uhubctl_enable' [service/database.cpp:89|database_c::_get_single_value()]
[5] Query failure: SELECT VALUE FROM settings WHERE key = 'player_basic_mode' [service/database.cpp:89|database_c::_get_single_value()]
[4] Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
- Exception caught: bad file: /etc/netplan/50-cloud-init.yaml [helper/entry_point.cpp:155|entry_point_c::run()]
During 30s waiting, GUI is back and fine. But 10s later bad again. I have to email you picture, as failed at this site.
https://ibb.co/QFYQh3JW
https://ibb.co/mV0hwHcM
RE: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) - agent_kith - 24-Mar-2025
(24-Mar-2025, 03:01 PM)clark8888 Wrote: [4] Qt has caught an exception thrown from an event handler. ThrowingThat's the problem.
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
- Exception caught: bad file: /etc/netplan/50-cloud-init.yaml [helper/entry_point.cpp:155|entry_point_c::run()]
Can you send this file to my email address please? thanks.
Code:
/etc/netplan/50-cloud-init.yaml1.4.2 will roll out and fix this issue (hopefully) when I get this file. Unsure if I still have time today but hopefully can get the fix out tomorrow or the day after.
thanks.
RE: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) - clark8888 - 25-Mar-2025
(24-Mar-2025, 03:28 PM)agent_kith Wrote:(24-Mar-2025, 03:01 PM)clark8888 Wrote: [4] Qt has caught an exception thrown from an event handler. ThrowingThat's the problem.
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
- Exception caught: bad file: /etc/netplan/50-cloud-init.yaml [helper/entry_point.cpp:155|entry_point_c::run()]
Can you send this file to my email address please? thanks.
Code:/etc/netplan/50-cloud-init.yaml
1.4.2 will roll out and fix this issue (hopefully) when I get this file. Unsure if I still have time today but hopefully can get the fix out tomorrow or the day after.
thanks.
file emailed. not hurry for me
RE: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) - agent_kith - 25-Mar-2025
(25-Mar-2025, 09:20 AM)clark8888 Wrote: file emailed. not hurry for meGot the file thanks. The syntax in the file is correct and is not a bad file. File loads up properly in my test environment with no "bad file" error. Something is very weird here.
Because I still don't fully understand the reason for this error, and it seems to affect different people differently (e.g. 503 error in dashboard page), for now I have no other choice but to let the code be a lot more defensive...
In 1.4.2 there will be a new layer of protection against this. Unfortunately this new layer is pretty much at the core of application so it might affect performance, but in most cases I don't think it's going to be an issue at all. Will see how it goes.. Hopefully can release 1.4.2 out soon. just need to work out some extra issues.
RE: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) - agent_kith - 25-Mar-2025
Guys with this problem, please try 1.4.2 and see if it's any better.
RE: [split] Problem starting API server 1.4.1 (Missing qsqlite3 lib) - clark8888 - 26-Mar-2025
(25-Mar-2025, 12:09 PM)agent_kith Wrote: Guys with this problem, please try 1.4.2 and see if it's any better.
GUI is back. Thanks!