** Description changed: It is a known issue within the rasdaemon package where `ras-mc-ctl --errors` fails due to a database schema mismatch. This issue is already tracked upstream in rasdaemon GitHub issue #237. - Upstream Issue: https://github.com/mchehab/rasdaemon/issues/237 - [Expected Behavior] Running `sudo ras-mc-ctl --errors` should complete successfully and display all hardware error categories without any script crashes. [Actual Behavior] The script terminates prematurely with the following Perl database errors: "DBD::SQLite::db prepare failed: no such column: signal at /usr/sbin/ras-mc-ctl line 2404." "Can't call method "execute" on an undefined value at /usr/sbin/ras-mc-ctl line 2405." - [Steps to Reproduce] 1. Install rasdaemon (0.8.4) on Ubuntu 26.04: - $ sudo apt update - $ sudo apt install rasdaemon + $ sudo apt update + $ sudo apt install rasdaemon 2. Initialize and start the rasdaemon service: - $ sudo systemctl enable --now rasdaemon + $ sudo systemctl enable --now rasdaemon 3. Execute the query tool with the errors flag: - $ sudo ras-mc-ctl --errors + $ sudo ras-mc-ctl --errors …error shows DBD::SQLite::db prepare failed: no such column: signal at /usr/sbin/ras-mc-ctl line 2405. Can't call method "execute" on an undefined value at /usr/sbin/ras-mc-ctl line 2406. + + --- + SRU addendum + + [Impact] + Running `ras-mc-ctl --summary` or `ras-mc-ctl --errors` fails when querying signal events with: + DBD::SQLite::db prepare failed: no such column: signal at /usr/sbin/ras-mc-ctl line 2404. + Can't call method "execute" on an undefined value at /usr/sbin/ras-mc-ctl line 2405. + + This prevents admins on systems recording hardware RAS events from + viewing error summaries properly. + + [Test Plan] + 1. Install rasdaemon: + sudo apt install rasdaemon + 2. Ensure the daemon is running and database initialized: + sudo systemctl start rasdaemon + 3. Run the commands: + sudo ras-mc-ctl --errors + 4. Verification: + - Without fix: Script fails with "no such column: signal". + - With fix: Command finishes cleanly and prints SIGNAL summary and events full SIGNAL events without any SQL errors. + + [Where problems could occur] + The patch only modifies the column name in the `signal_event` SQL SELECT query within `ras-mc-ctl` from `signal` to `sig`. + - Low risk: It does not affect daemon event gathering, tracepoints, or kernel interfacing. + - Potential regression: If an older DB schema used `signal`, it could break that specific legacy schema; however, the signal_event table has always used `sig` column name since being introduced https://github.com/mchehab/rasdaemon/commit/69a4535eb1c356320cefd56f8aaf907a72a2c57d#diff-ce5e89890021db64ca28bbc34c2203ddab990127d00d916d7507bc7857c2815eR1149 + + [Other Info] + Upstream fix reference: + - Issue: https://github.com/mchehab/rasdaemon/issues/237 + - GitHub PR: https://github.com/mchehab/rasdaemon/pull/246 + - Commit: https://github.com/mchehab/rasdaemon/commit/3d0c4ba5f3d9b83e3c11789022a514c027fa6935
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2154809 Title: [ubuntu 26.04]ras-mc-ctl fails with "no such column: signal" when running with --errors flag in rasdaemon 0.8.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/2154809/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
