View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 12 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Wed Jul 28, 2010 4:01 pm 
Offline
Joined: Wed Dec 13, 2006 4:29 pm
Posts: 42
Over the last couple of weeks, my /var/log/acpid.log has gotten huge. It's so big that it's filled my entire root partition, making the database unusable. I tried removing the file, which fixes things temporarily, but then it quickly fills up again. What's going on here? And how do I stop it?

Here's a sample of the file:
Code:
Jul 27 18:50:17 mythtv acpid: client connected from 6198[0:0]
Jul 27 18:50:17 mythtv acpid: 1 client rule loaded
Jul 27 18:50:32 mythtv acpid: client connected from 6273[0:0]
Jul 27 18:50:32 mythtv acpid: 1 client rule loaded
Jul 27 18:50:48 mythtv acpid: client connected from 6348[0:0]
Jul 27 18:50:48 mythtv acpid: 1 client rule loaded
Jul 27 18:51:03 mythtv acpid: client connected from 6423[0:0]
Jul 27 18:51:03 mythtv acpid: 1 client rule loaded
Jul 27 18:51:19 mythtv acpid: client connected from 6498[0:0]
Jul 27 18:51:19 mythtv acpid: 1 client rule loaded
Jul 27 18:51:34 mythtv acpid: client connected from 6573[0:0]
Jul 27 18:51:34 mythtv acpid: 1 client rule loaded
Jul 27 18:51:50 mythtv acpid: client connected from 6649[0:0]
Jul 27 18:51:50 mythtv acpid: 1 client rule loaded
Jul 27 18:52:05 mythtv acpid: client connected from 6724[0:0]
Jul 27 18:52:05 mythtv acpid: 1 client rule loaded
Jul 27 18:52:21 mythtv acpid: client connected from 6799[0:0]
Jul 27 18:52:21 mythtv acpid: 1 client rule loaded
Jul 27 18:52:36 mythtv acpid: client connected from 6874[0:0]


I'm using R6.02.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Aug 03, 2010 5:10 pm 
Offline
Joined: Wed Dec 13, 2006 4:29 pm
Posts: 42
Didn't get any suggestions, so here's what I tried. I went to /etc/syslog-ng.conf, and it had a list of processes and the files where the log is written:
Code:
destination kernel { file("/var/log/kernel.log"); };
destination lpr { file("/var/log/lpr.log"); };
destination user { file("/var/log/user.log"); };
destination uucp { file("/var/log/uucp.log"); };
destination mail { file("/var/log/mail.log"); };
destination news { file("/var/log/news.log"); };
destination ppp { file("/var/log/ppp.log"); };
destination debug { file("/var/log/debug.log"); };
destination messages { file("/var/log/messages.log"); };
destination errors { file("/var/log/errors.log"); };
destination everything { file("/var/log/everything.log"); };
destination iptables { file("/var/log/iptables.log"); };
destination acpid { file("/var/log/acpid.log"); };
destination console { usertty("root"); };

I changed acpid.log to /dev/null and rebooted. After that, there was no more problem with the disk filling up. (Though I still don't know why it was doing that in the first place!)

But now I have a new problem that's probably related to my "fix." Although I can still record programs and play them back, mythfilldatabase, commercial detect, transcode, and "backend status" on mythweb all do not work.

My mythbackend log has stuff like this:
Code:
2010-08-03 06:50:33.173 myth_system('/usr/bin/mythbackend --generate-preview 0x0 --chanid 1041 --starttime 20100802233500 '): Error: Can not redirect /dev/null to standard input, failed to open.
            eno: Permission denied (13)

2010-08-03 04:39:16.325 mythfilldatabase still running, skipping checks.
sh: /dev/null: Permission denied

When I click "backend status," I get this error:
Code:
Warning at /data/srv/httpd/htdocs/mythweb/modules/status/handler.php, line 35:
file_get_contents(http://192.168.1.17:6544) [function.file-get-contents]: failed to open stream: HTTP request failed!

I would love to get someone's insight into this.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Oct 27, 2010 9:05 pm 
Offline
Joined: Fri Nov 04, 2005 7:11 am
Posts: 61
I had the same error and wasn't able to figure it out. I had some success by removing acpid


pacman -Rs acpid

So far I haven't had any problems. (I leave my myth box on continuously).

_________________
BE: R8.4, HVR2250, MCE media center remote, GigaByte GA-EP43-UD3L, 2gb ram

FE: Linhes 8.4, Mythbuntu, Linux Mint DE


Top
 Profile  
 
 Post subject:
PostPosted: Wed Oct 27, 2010 9:09 pm 
Offline
Joined: Wed Dec 13, 2006 4:29 pm
Posts: 42
Thanks! I stopped the acpid service and got some temporary relief, but I think I now know the underlying cause. Even though my backend is a backend-only that runs continuously, I had set it to run a frontend. However, with no monitor attached to the machine, mythfrontend was essentially saying, "Where's the monitor? Where's the monitor? Where's the monitor?" over and over again. I stopped running the frontend on the backend, and now acpid doesn't complain.


Top
 Profile  
 
 Post subject:
PostPosted: Mon Nov 08, 2010 4:22 pm 
Offline
Joined: Sun Sep 04, 2005 7:48 pm
Posts: 264
Location: Perth, Australia
Hi there, I have almost exactly the same symptoms, but I dont run the frontend. I changed the combined FE/BE out into the study, and am running XBMC live on a ion330 asrock in the living room.

I use mythwelcome and mythbackend, and like is say, no frontend.

I dont want to disable acpi, as I understand thats what makes the mythwelcome wakeup/shutdown work for me.

Any thoughts as to how to stop the log filling up under there circumstances?

Nathan

_________________
LinHES: R6 | MB: Asus M3N-H/HDMI | CPU: AMD ??Mhz
Capture: 2xHDHR DVB-T
Graphics: Onboard 8300|PSU: Corsair vx450w
Cooling: Zalman cu?,
Display: Benq xx projector


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 08, 2012 11:15 am 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1530
Location: California
On LINHES 6.04 and just noticed I am having the same problem. System is a combined front-end/back-end. Interesting things is that after a reboot a few log entries are placed in acpid.log and then it's quiet. If I then do an "sv restart frontend", the 2 log entries shown below are generated every ~15 seconds.

Any thoughts?

Code:
Feb  8 09:11:14 mythhd acpid: client connected from 8691[0:0]
Feb  8 09:11:14 mythhd acpid: 1 client rule loaded
Feb  8 09:11:29 mythhd acpid: client connected from 8770[0:0]
Feb  8 09:11:29 mythhd acpid: 1 client rule loaded
Feb  8 09:11:44 mythhd acpid: client connected from 8849[0:0]
Feb  8 09:11:44 mythhd acpid: 1 client rule loaded
Feb  8 09:12:00 mythhd acpid: client connected from 8928[0:0]
Feb  8 09:12:00 mythhd acpid: 1 client rule loaded
Feb  8 09:12:15 mythhd acpid: client connected from 9008[0:0]
Feb  8 09:12:15 mythhd acpid: 1 client rule loaded
Feb  8 09:12:30 mythhd acpid: client connected from 9088[0:0]
Feb  8 09:12:30 mythhd acpid: 1 client rule loaded
Feb  8 09:12:45 mythhd acpid: client connected from 9167[0:0]
Feb  8 09:12:45 mythhd acpid: 1 client rule loaded
Feb  8 09:13:01 mythhd acpid: client connected from 9246[0:0]
Feb  8 09:13:01 mythhd acpid: 1 client rule loaded
Feb  8 09:13:16 mythhd acpid: client connected from 9326[0:0]
Feb  8 09:13:16 mythhd acpid: 1 client rule loaded
Feb  8 09:13:31 mythhd acpid: client connected from 9405[0:0]
Feb  8 09:13:31 mythhd acpid: 1 client rule loaded
Feb  8 09:13:47 mythhd acpid: client connected from 9485[0:0]
Feb  8 09:13:47 mythhd acpid: 1 client rule loaded
Feb  8 09:14:02 mythhd acpid: client connected from 9564[0:0]
Feb  8 09:14:02 mythhd acpid: 1 client rule loaded
Feb  8 09:14:17 mythhd acpid: client connected from 9644[0:0]
Feb  8 09:14:17 mythhd acpid: 1 client rule loaded

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 08, 2012 11:20 am 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1530
Location: California
One more piece of info. I tried watching the log file and the output of "top -d 1". Whenever a new pair of lines is written to "acpid.log" the folllowing process pops to the top: "//sbin/fbsplashd.static". Could this be related?

The output of ps auxw shows:

Code:
root      3352  0.0  0.1  37660  3444 tty16    Ssl+ 08:30   0:01 //sbin/fbsplashd.static --theme=linhes --idfile=//lib/splash/cache/daemon.pid --type=bootup

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 08, 2012 11:30 am 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1530
Location: California
OK -- now I have a confirmed factoid. If I do "sv restart frontend" while my TV is turned off, the acpid.log file growth beings. When I turn my TV on, the growth stops and I can turn my TV back off without problems. So the issue seems to be related to restarting the frontend without the TV being connected.

I am connected via HDMI...

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 08, 2012 12:01 pm 
Offline
Joined: Sat Apr 21, 2007 6:55 pm
Posts: 306
Location: CA,USA
I had this some time ago and liked sray I ended up removing apicd.

_________________
Paul O'Flynn


Top
 Profile  
 
 Post subject:
PostPosted: Thu Feb 09, 2012 5:02 am 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1530
Location: California
Updated Feb 11, 2012

Here is a different approach to solving the problem that leaves acpid installed.

In my case the problem is related to restarting the frontend when the TV and the video amp are turned off. My wiring is mythbox -> video_AMP_via_HDMI -> TV_via_HDMI. When I issue "sv restart frontend" with those components off /var/log/Xorg.log shows that X never starts properly. It looks like someone, someplace is trying to restart the frontend every 15 seconds, and that this restart process creates a pair of acpid.log log entries on every attempt.

My solution, which appears to be working, is based on 2 changes to /etc/X11/xorg.conf:

1. Required: In the device section I added the line 'Option "ConnectedMonitor" "DFP"'. Once this change is made, the acpid.log growth problem is solved. This will also enable the "x11vnc" daemon to start properly when the TV is not reachable.

2. Optional: In the monitor section I added the line 'Option "CustomEDID" "DFP-0:/myth/SAVE/config_files/samsung_plasma_edid.bin"' This change is not required to solve the acpid.log growth problem, but it solves another problem that occurs in the situation. When X is not able to communicate with the TV over the HDMI cable during a restart of the frontend, it will default to a very low resolution instead of the optimal resolution, as it is unable to "talk" the the TV and discover what resolutions are available.

I used the nvidia-settings "acquire EDID" button to acquire my TV's EDID and save it to the file "/myth/SAVE/config_files/samsung_plasma_edid.bin"

Now X starts properly even when it cannot communicate with the TV and I am not having the "out of control" acpid.log growth. The resolution is always correct and the "x11vnc" daemon is always running properly.

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Last edited by marc.aronson on Sat Feb 11, 2012 10:55 am, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Feb 11, 2012 1:56 am 
Offline
Joined: Tue Aug 15, 2006 11:14 am
Posts: 1268
Location: Orlando FL
nice hack

_________________
My System


Top
 Profile  
 
 Post subject:
PostPosted: Sat Feb 11, 2012 10:56 am 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1530
Location: California
mattbatt wrote:
nice hack

Thanks. I just updated the entry with a bit more info as only the first step is required. The EDID capture is optional. Also documented that the first step will also solve problems with inability for x11vnc daemon to run.

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 12 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu