SOLVED: HDA Stopped

[klauswirn]

Hi,

got an issue with my hda.

It stoppped working and i got following message.

Code: Select all

tail -f /var/log/greyhole.log Jul 03 07:24:36 DEBUG fsck: Storage volume? No Jul 03 07:24:36 DEBUG fsck: Share? Series Jul 03 07:24:36 ERROR fsck: PHP Fatal Error: Uncaught exception 'Exception' with message 'SQLSTATE[HY000]: General error: 1194 Table 'du_stats' is marked as crashed and should be repaired' in /usr/bin/greyhole:595 Stack trace: #0 /usr/bin/greyhole(5042): DB::execute('DELETE FROM du_...', Array) #1 /usr/bin/greyhole(3489): gh_fsck_reset_du('Series', '') #2 /usr/bin/greyhole(3249): execute_next_task() #3 /usr/bin/greyhole(3273): DaemonRunner->run() #4 {main} thrown; BT: greyhole[L595]

my root rans full and i had to delete some log files tot get my server started. after this i ran an fsck on an partition which is the problem why the logs are full. after that server starts and i can work on it.

tried to restart greyhole but i think the issue is in mysql db.
also tried several repair commands to mysql db but everything says its ok. ("mysql -u root -phda -e "repair table settings" greyhole")

can someone help?

thx

[bigfoot65]

Have you tried rebooting the machine since cleaning it up?

Sometimes it just needs a fresh start.

[klauswirn]

Yes,
Done a several restarts.

Is there anything next a can do?

In my opinion the problem is the samba server, but i have no idea what to do....

[bigfoot65]

There are a few things you can do. Try stopping Greyhole, then starting it again. Monitor /var/log/greyhole.log file:

Code: Select all

tail -f /var/log/greyhole.log

If that does not work, then maybe we can look at removing the Table 'du_stats' and re-creating it.

[klauswirn]

I tried to stop and start.

here is the result....

Code: Select all

[root@localhost igor]# service greyhole stop Redirecting to /bin/systemctl stop greyhole.service Failed to issue method call: Unit greyhole.service not loaded. [root@localhost igor]# service greyhole start Redirecting to /bin/systemctl start greyhole.service Failed to issue method call: Unit greyhole.service failed to load: No such file or directory. See system logs and 'systemctl status greyhole.service' for details. [root@localhost igor]# [root@localhost igor]# systemctl status greyhole.service greyhole.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) [root@localhost igor]#

Do you need more infos?
Whats next to do?

[bigfoot65]

The appropriate commands are as root user:

Code: Select all

systemctl stop amahi-greyhole systemctl start amahi-greyhole systemctl status amahi-greyhole

Try those and see what if it helps.

[klauswirn]

Ok my fault...

Done it without result..

Code: Select all

[root@localhost igor]# systemctl stop amahi-greyhole [root@localhost igor]# systemctl start amahi-greyhole [root@localhost igor]# systemctl status amahi-greyhole amahi-greyhole.service - Greyhole for Amahi Loaded: loaded (/usr/lib/systemd/system/amahi-greyhole.service; enabled) Active: failed (Result: start-limit) since Mo 2015-07-06 13:48:13 CEST; 671ms ago Process: 3763 ExecStopPost=/bin/rm -f /run/amahi-greyhole.pid (code=exited, status=0/SUCCESS) Process: 3761 ExecStop=/usr/bin/kill $MAINPID (code=exited, status=1/FAILURE) Process: 3564 ExecStart=/usr/bin/amahi-greyhole (code=exited, status=0/SUCCESS) Main PID: 3565 (code=exited, status=255) CGroup: name=systemd:/system/amahi-greyhole.service Jul 06 13:48:13 localhost.localdomain systemd[1]: Unit amahi-greyhole.service entered failed state. Jul 06 13:48:13 localhost.localdomain systemd[1]: amahi-greyhole.service holdoff time over, scheduling restart. Jul 06 13:48:13 localhost.localdomain systemd[1]: Stopping Greyhole for Amahi... Jul 06 13:48:13 localhost.localdomain systemd[1]: Starting Greyhole for Amahi... Jul 06 13:48:13 localhost.localdomain systemd[1]: amahi-greyhole.service start request repeated too quickly, refusing ...tart. Jul 06 13:48:13 localhost.localdomain systemd[1]: Failed to start Greyhole for Amahi. Jul 06 13:48:13 localhost.localdomain systemd[1]: Unit amahi-greyhole.service entered failed state. [root@localhost igor]# tail -f /var/log/greyhole.log Jul 06 13:48:13 DEBUG fsck: Storage volume? No Jul 06 13:48:13 DEBUG fsck: Share? Series Jul 06 13:48:13 ERROR fsck: PHP Fatal Error: Uncaught exception 'Exception' with message 'SQLSTATE[HY000]: General error: 1194 Table 'du_stats' is marked as crashed and should be repaired' in /usr/bin/greyhole:595 Stack trace: #0 /usr/bin/greyhole(5042): DB::execute('DELETE FROM du_...', Array) #1 /usr/bin/greyhole(3489): gh_fsck_reset_du('Series', '') #2 /usr/bin/greyhole(3249): execute_next_task() #3 /usr/bin/greyhole(3273): DaemonRunner->run() #4 {main} thrown; BT: greyhole[L595]

[bigfoot65]

Ok I see the error for the du_stats table is still the primary issue. What may be necessary is dropping the Greyhole database and then creating it again.

To do that, do the following:

Code: Select all

hda-create-db-and-user -d greyhole hda-create-db-and-user greyhole mysql -uroot -phda greyhole < /usr/share/greyhole/schema-mysql.sql

Once complete, try to start Greyhole and watch the log for errors.

I did notice that the greyhole.log file indicated:

Jul 06 13:48:13 DEBUG fsck: Storage volume? No
Jul 06 13:48:13 DEBUG fsck: Share? Series

Did you add partitions to the storage pool and configure shares for Greyhole? Without those two things configured, there is nothing for Greyhole to do and often it will not start. Check /etc/greyhole.conf to ensure those two items are properly configured or use the Greyhole UI.

Once you have everything set, you can then do as root user:

Code: Select all

greyhole -f

That will get all the shares/files updated in the database for those that are Greyhole enabled.

[klauswirn]

Thx, that fixed it.

Now it works...

Saved my day

[bigfoot65]

Awesome. Happy to assist.