Search Criteria
Package Details: rasdaemon 0.8.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/rasdaemon.git (read-only, click to copy) |
---|---|
Package Base: | rasdaemon |
Description: | Logging daemon for Platform Reliability, Availability and Serviceability (RAS), replacing mcelog |
Upstream URL: | https://github.com/mchehab/rasdaemon |
Licenses: | GPL-2.0-or-later |
Submitter: | grawity |
Maintainer: | eta-carinae |
Last Packager: | eta-carinae |
Votes: | 42 |
Popularity: | 0.128944 |
First Submitted: | 2017-05-04 06:49 (UTC) |
Last Updated: | 2024-11-25 15:54 (UTC) |
Dependencies (5)
- dmidecode (dmidecode-gitAUR)
- libtraceevent
- perl (perl-gitAUR)
- perl-dbd-sqlite
- sqlite (sqlite-fossilAUR)
Latest Comments
« First ‹ Previous 1 2 3 4 Next › Last »
zerophase commented on 2021-06-02 18:05 (UTC)
@eta-carinae thanks
eta-carinae commented on 2021-06-02 16:02 (UTC)
zerophase,
There's an error in this command called by configure to test gcc:
gcc -march=native -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2, D_GLIBCXX_ASSERTIONS -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.c
The problem is with this section:
-Wp,-D_FORTIFY_SOURCE=2, D_GLIBCXX_ASSERTIONS
This should read:
-Wp,-D_FORTIFY_SOURCE=2,-D_GLIBCXX_ASSERTIONS
This is probably coming from your /etc/makepkg.conf. The -D_GLIBCXX_ASSERTIONS portion was moved in the latest pacman upgrade, so maybe there was a problem when you merged the new version of makepkg.conf?
zerophase commented on 2021-06-02 15:02 (UTC)
https://pastebin.com/7iyDqdeF
eta-carinae commented on 2021-06-02 02:19 (UTC)
zerophase,
Can you post the config.log from your build directory? configure spits out that error message anytime gcc fails, and the log should have the underlying error message. Often it's a missing library or header file, but it could be a lot of things.
zerophase commented on 2021-06-02 02:07 (UTC) (edited on 2021-06-02 02:07 (UTC) by zerophase)
I'm getting
configure: error: in /tmp/makepkg/rasdaemon/src/rasdaemon-0.6.7: configure: error: C compiler cannot create executables
with the 0.6.7-2 update.eta-carinae commented on 2021-06-01 15:00 (UTC)
0.6.7-2 fixes the location of the rasdaemon config file. It's now back at /etc/sysconfig/rasdaemon. It briefly moved to /rasdaemon in version 0.6.7-1!
webdawg commented on 2021-02-12 00:54 (UTC) (edited on 2021-02-12 00:54 (UTC) by webdawg)
How is this package in the aur?
How else is someone supposed to explore mce issues?
eta-carinae commented on 2020-08-11 02:14 (UTC)
@Kodehawa, I remember encountering this error, too. I meant to file a bug report upstream but must have forgotten.
I believe the mc_event table is where rasdaemon records memory-corrected error data, which is new in 0.6.6. If you've been using rasdaemon for a while, you already have a database which doesn't have this table, and the new version fails to create it if it doesn't exist, hence the error.
You could stop rasdaemon, rename the existing database in /var/lib/rasdaemon to something else, then restart rasdaemon. It should create a new database with the correct tables. You'd lose all your history, however.
The other option is to use a sqlite tool to add the missing table manually to your existing database. The SQL statement is:
CREATE TABLE mc_event (id INTEGER PRIMARY KEY, timestamp TEXT, err_count INTEGER, err_type TEXT, err_msg TEXT, label TEXT, mc INTEGER, top_layer INTEGER, middle_layer INTEGER, lower_layer INTEGER, address INTEGER, grain INTEGER, syndrome INTEGER, driver_detail TEXT);
I'll file this upstream when I have a chance to downgrade and verify the problem with a fresh database.
Kodehawa commented on 2020-08-11 01:03 (UTC)
Hello. I keep getting
I've ran rasdaemon --record at least 10 times. I'll attach an image: https://i.imgur.com/gIFyRLT.png
Pretty lost really. Can't find much on the internet. Any ideas?
eta-carinae commented on 2020-07-21 14:30 (UTC)
rasdaemon 0.6.6 adds support for memory corrected error PFA, and I enabled it in the PKGBUILD. If it causes any problems for anyone, let me know and I'll disable it until it's had more testing.
« First ‹ Previous 1 2 3 4 Next › Last »