Your disk space suggestion was right on the money - thanks! 

Turns out the bacula directory in this server is sym-linked to another on a
partition that was full (not 100% familiar with this server having recently
inherited it).  

The old .db file is working as normal after clearing some space. 

Many thanks,
Kris




Arno Lehmann wrote:
> 
> Hi,
> 
> 07.08.2007 11:43,, Monstad wrote::
>> 
>> Hi there,
>> 
>> For the past day bacula has been unresponsive eg: not mounting tapes, not
>> purging records etc.
>> 
>> Today I got this mail: 
>> 
>> 
>> 
>> 
>> *cacti.poller_output
>> error    : Can't find file: 'poller_output.MYI' (errno: 2)
>> cacti.poller_time
>> warning  : Table is marked as crashed
>> error    : Found key at page 1024 that points to record outside datafile
>> error    : Corrupt
>> syslog.logs
>> warning  : Table is marked as crashed
>> error    : Size of indexfile is: 5218078720        Should be: 5218079744
>> error    : Corrupt
>> 
>>  Improperly closed tables are also reported if clients are accessing
>>  the tables *now*. A list of current connections is below.
>> 
>> +----+------------------+-----------+----+---------+------+-------+------------------+
>> | Id | User             | Host      | db | Command | Time | State | Info     
>>        
>> |
>> +----+------------------+-----------+----+---------+------+-------+------------------+
>> | 52 | debian-sys-maint | localhost |    | Query   | 0    |       | show
>> processlist |
>> +----+------------------+-----------+----+---------+------+-------+------------------+
>> Uptime: 4  Threads: 1  Questions: 379  Slow queries: 0  Opens: 255  Flush
>> tables: 1  Open tables: 64  Queries per second avg: 94.750*
> 
> Your MySQL is databases are broken. MySQL does write a log file where 
> it reports errors, and the system log might also have valuable 
> information. Shut down MySQL and run the related tools to check and 
> repair the databases. There is information in the MySQL manual. One of 
> the more common problems, in my experience, is the infamous "disk 
> full" one, by the way :-)
> 
> As the problem is not directly related to Bacula, I can only recommend 
> to ask for more detailed help in the MySQL-related mailing lists, 
> forums, or newsgroups.
> 
> Once you've got the database running again and checked the 
> Bacula-related ones with dbcheck, I'm sure we can help you restoring 
> your data or getting Bacula running again.
> 
> Arno
> 
> 
>> Can anyone suggest how to repair this? I'm afraid I'm relatively new to
>> bacula (and I apologise if this is a documented problem).
>> 
>> I would be extremely grateful for any advice,
>> 
>> Kris
>> 
>> 
> 
> -- 
> Arno Lehmann
> IT-Service Lehmann
> www.its-lehmann.de
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/bacula-error---poller_output.MYI-tf4229177.html#a12032484
Sent from the Bacula - Users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to