Search Criteria
Package Details: rasdaemon 0.6.8-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: | GPL2 |
Submitter: | grawity |
Maintainer: | eta-carinae |
Last Packager: | eta-carinae |
Votes: | 35 |
Popularity: | 1.05 |
First Submitted: | 2017-05-04 06:49 (UTC) |
Last Updated: | 2022-06-02 12:12 (UTC) |
Latest Comments
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.
yochananmarqos commented on 2020-07-04 16:45 (UTC)
The url() should be https://pagure.io/rasdaemon
BStrauss3 commented on 2020-06-19 21:58 (UTC)
@eta-carinae : Just built it for a new machine - smooth... THANKS!!!!!
If anybody is having problems with the periodic block_rq_complete 'errors' that aren't errors, there was a thread on GitHub in the last couple days:
https://github.com/mchehab/rasdaemon/issues/17#issuecomment-646455597
At least for some machines, it's each empty slot in a card reader (SD, etc.) and the 7th message down has the command to make it STFU.
-----Burton
eta-carinae commented on 2020-05-26 16:44 (UTC)
Removed --enable-abrt-report as requested. Got a little too aggressive with experimental flags I guess. :)
BStrauss3 commented on 2020-05-24 15:53 (UTC)
Why is this package being built with
There is no abrt daemon for Arch, so this generates an "error" about 5 per minute. I've built it with this removed and we're down to a heartbeat every 3 seconds or so.
-----Burton
pancho commented on 2020-05-16 11:55 (UTC)
Stellar! ;-)
eta-carinae commented on 2020-05-16 09:55 (UTC)
pancho,
Thanks for the heads-up. I added your workaround and will report the problem upstream.
pancho commented on 2020-05-16 06:51 (UTC) (edited on 2020-05-16 06:51 (UTC) by pancho)
Hi there.
It seems that we've been hit by a change¹ in GCC 10. See the topic² for more details. It also affects
pam_ssh
, so I've managed to easily workaround it² by adding:This just reverts GCC to the pre-10 behavior.
Hope that it helps.
¹: https://gcc.gnu.org/gcc-10/porting_to.html
²: https://bbs.archlinux.org/viewtopic.php?id=255727
³: https://aur.archlinux.org/cgit/aur.git/commit/?h=pam_ssh&id=cb4ed823ece6b3316a7b4103135dec8d1711473c
eta-carinae commented on 2019-10-12 12:45 (UTC)
I get some of those disk errors, though not nearly as many. Also don't see any corresponding problems or errors outside of rasdaemon, so I'm not sure what to make of them. If they're causing people problems, I can disable the disk error feature in the PKGBUILD, but I think reporting this upstream is the best answer.
Ropid commented on 2019-10-12 08:50 (UTC)
Those new "experimental features" don't seem to be working right for me here. On certain boots, I get hundreds of the following errors recorded in
ras-mc-ctl --errors
:This does not happen on every boot, it only happens every three days or so.
While those errors are getting recorded by rasdaemon, I can't find any strange messages in
journalctl
ordmesg
. The log messages there look fine with no errors or warnings.eta-carinae commented on 2018-09-03 23:16 (UTC)
Because this was an orphaned package I took over and I didn't notice the change because I was using my own custom unit :). Fixed.
amezin commented on 2018-09-03 18:04 (UTC)
Why are you removing "-r" from ExecStart in rasdaemon.service? Without "-r" it doesn't record anything,
journalctl -u rasdaemon
output is nearly useless when MCE occurs:grawity commented on 2018-02-07 20:33 (UTC)
automake and autoconf are in base-devel.
OdinEidolon commented on 2018-02-07 20:27 (UTC)
automake and autoconf are needed to build this package.
manuel commented on 2017-10-18 23:14 (UTC)
ckujau commented on 2017-10-15 21:40 (UTC)
adfjjv commented on 2017-09-17 09:59 (UTC) (edited on 2017-09-17 10:00 (UTC) by adfjjv)