Error When Trying To Autoexpire
Post #1 of 4 (655 views) Permalink ERROR when trying to autoexpire file I keep getting this message in the backend log and my backend got totally hosed where I had to restart it right after it hit this problem. The file does not exist. Searching google gave me no solution, but I did find people with the same problem. AutoExpire: ERROR when trying to autoexpire file: /mythtv/recordings/1065_20061001135623.mpg. File doesn't exist. Database metadata will not be removed. How can I clean this up? Thanks, James _______________________________________________ mythtv-users mailing list mythtv-users [at] mythtv http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users lynchmv at gmail Oct10,2006,8:20AM Post #2 of 4 (627 views) Permalink Re: ERROR when trying to autoexpire file [In reply to] On 10/10/06, James Pifer <jep [at] obrien-pifer> wrote: > I keep getting this message in the backend log and my backend got > totally hosed where I had to restart it right after it hit this problem. > The file does not exist. Searching google gave me no solution, but I did > find people with the same problem. > > AutoExpire: ERROR when trying to autoexpire file: /mythtv/recordings/1065_20061001135623.mpg. File doesn't exist. Database metadata will not be removed. > > How can I clean this up? > > Thanks, > James > I've cleared up similar problems by just touching the file it's looking for. Try touch /mythtv/recordings/1065_20061001135623.mpg _______________________________________________ mythtv-users mailing list mythtv-users [at] mythtv http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users mtdean at thirdcontact Oct10,2006,8:23AM Post #3 of 4 (630 views) Permalink Re: ERROR when trying to autoexpire file [In reply to] On 10/10/06 11:16, James Pifer wrote: >I keep getting this message in the backend log and my backend got >totally hosed where I had to
too many problems. But something happened recently and I'm not sure what to remove to free up space. When I use df in the command line, I get this: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 9843276 9840156 0 100% / varrun 517748 212 517536 1% /var/run varlock 517748 0 517748 0% /var/lock udev 517748 92 517656 1% /dev devshm 517748 0 517748 0% /dev/shm lrm 517748 34696 483052 7% /lib/modules/2.6.22-14-generic/volatile /dev/sda2 720516512 659277092 61239420 92% http://www.gossamer-threads.com/lists/mythtv/users/230319 /var/lib overflow 1024 16 1008 2% /tmp I know I need to remove a few shows from sda2, but I thought the only thing on sda1 was the OS. But it looks like something else is on there. I could have sworn I had 5GB free on sda1 back in Feb, and the only thing running on this https://ubuntuforums.org/archive/index.php/t-866445.html computer is MythTV. What can I do to free up some disk space, as it is keeping mysql from running MythTV. Thanks. tgm4883July 22nd, 2008, 01:33 AMcheck /var/log/mythtv You might have something producing super huge logs nickroutJuly 22nd, 2008, 02:11 AMcheck /var/log/mythtv You might have something producing super huge logs The other thing is that when you update the .deb files go in /var/cache/apt/archive. To clean it up use: apt-get clean or apt-get autoclean from the man page: clean clean clears out the local repository of retrieved package files. It removes everything but the lock file from /var/cache/apt/archives/ and /var/cache/apt/archives/partial/. When APT is used as a dselect(8) method, clean is run automatically. Those who do not use dselect will likely want to run apt-get clean from time to time to free up disk space. autoclean Like clean, autoclean clears out the local repository of retrieved package files. The difference is that it only removes package files that can no longer be downloaded, and are largely useless. This allows a cache to be
an hd-5500 card which I'm planning on using in a new HTPC. I thought it made sense to check it out first by putting it in my existing https://ubuntuforums.org/archive/index.php/t-654157.html Ubuntu desktop and installing Mythbunu over the top. However I'm really struggling to get anything working and I'm not sure if my problem is the Myth configuration or the tuner card. https://devot-ee.com/add-ons/support/auto-expire/viewthread/607 There is more detail over here, http://pchdtv.com/forum/viewtopic.php?p=19432#19432 I think the backend sets up ok and I can scan and find 5 or 6 channels ok however when I start the frontend error when I can never see any channels. I don't think the quide is picking up any info (I'm scanning OTA ATSC broadcasts) but I don't really know how that works. Anyway, when I run mythfrontend in a terminal I noticed the following: X Error: BadDevice, invalid or uninitialized input device 158 Major opcode: 146 Minor opcode: 3 Resource id: 0x0 Failed to open error when trying device X Error: BadDevice, invalid or uninitialized input device 158 Major opcode: 146 Minor opcode: 3 Resource id: 0x0 Failed to open device Anyone have any idea what that might mean? The frontend continues to start but I can't watch any of the channels. I'm stumped. newlinuxDecember 31st, 2007, 03:51 AMYou can ignore those errors. They are bug with Xorg and wacom: https://launchpad.net/ubuntu/+source/xorg/+bug/42553 What happens when you try to watch liveTV? Have you look at your frontend and backend logs in /var/log/mythtv/ jonnoDecember 31st, 2007, 04:33 AMWhen I run mythbackend from a terminal I see: 2007-12-30 21:29:21.559 Using runtime prefix = /usr 2007-12-30 21:29:21.580 New DB connection, total: 1 2007-12-30 21:29:21.586 Connected to database 'mythconverg' at host: localhost 2007-12-30 21:29:21.592 Current Schema Version: 1160 Starting up as the master server. 2007-12-30 21:29:21.601 New DB connection, total: 2 2007-12-30 21:29:21.602 Connected to database 'mythconverg' at host: localhost 2007-12-30 21:29:21.604 EITHelper: localtime offset -6:00:00 2007-12-30 21:29:21.608 TVRec(1) Error: Start channel invalid, setting to '18' on input Television instead. 2007-12-30 21:29:21.613 New DB connection, total: 3 2007-12-30 21:29:21.613 Connected to database 'mythconverg' at host: localhost 2007-12-30 21:29:21.61
Fieldtypes Modules Plugins Submit an Add-on Extras Articles Buy Store Credit Hooks AcademEE Awards Developers EE Config Variables For a more accurate search, use quotation marks. Add-ons (All) Add-ons (All) Add-ons (EE2) Add-ons (EE3) Everything Articles/News Hooks search Extension Developer Supported Auto Expire ExpressionEngine 1.x, ExpressionEngine 2 Back to this add-on's main page View Other Add-ons From Wouter Vervloet Auto Expire>Thread You must be logged in to post. Back tracking old entries? Feature Request Biggles Posted: 07 February 2011 05:13 PM Hi, I've just installed, enabled and configured your extension so it auto-expires "News" channel entries after 2 weeks. I have about 1 years worth of old news stories i'd like to mass expire, e.g. if older than 2 weeks - set expire… which I thought your plugin would do… Does it only work on new entries? As it seems to, or am i missing something? Thanks Wouter Vervloet Posted: 07 February 2011 05:18 PM # 1 Developer Hi Biggles, At the moment Auto Expire only sets expiration dates for newly added or edited entries, but I am toying with the idea of adding a big red button to also apply one to old entries. Just one question: how would you like to see this implemented? In my opinion there are 3 ways of doing this: 1. Set an expiration date for ALL entries in a channel 2. Set an expiration date for all entries BEFORE A CERTAIN DATE. 3. MANUALLY select which entries to set it for. Which one has your preference? Greetz, Wouter Biggles Posted: 07 February 2011 05:20 PM # 2 Hi, Wow, quick reply! Excellent, so pleased you're toying with this idea, ok. Logical one seems #2 - as you can be 100% specific of what entries will go (Say you actually might want to remove them all up until the point you install your extension) When I say "remove them all" I mean change the status. To what date to should you alter statu