SOLVED: Server has been constantly running for 2 days

[tomtheappraiser]

OK, That was the confusion. That was what I already tried and it didn't work. I thought we were talking about the section titles "Que Still Stuck"

Soooo....so I just do the MySQL part and not stop Greyhole and then restart it? When I followed the thing it didn't work.

[bigfoot65]

I believe it says to stop Greyhole first.

What does the greyhole.log show after doing this procedure and restarting it? Might reboot the machine too for good measure.

BTW is your OS updated?

Code: Select all

sudo dnf update

[tomtheappraiser]

So i went through the process again, made sure the OS was updated, restarted the machine and it is still doing the same thing.

[bigfoot65]

Please attach the latest greyhole.log file so we can take a look.

Also provide the URL for:

Code: Select all

apaste --sysinfo

Want to see the latest stats on your system.

[tomtheappraiser]

https://da.gd/Is8ty -> https://paste.fedoraproject.org/paste/Z ... ivL9gydE=/

[bigfoot65]

Please post the result of:

Code: Select all

echo "select count(*) tasks" | mysql -uroot -phda greyhole

If it's long, then recommend you attach it in a file.

Also something does not look right in the log. It shows Docs//HIlltop Plat 3.jpg as the file with the issue. Should not be two slashes (//) between the share name and file. Is there something custom about your share directory structure?

[tomtheappraiser]

I tried that command and the only that came back was:

Code: Select all

tasks 1

[bigfoot65]

Wonder if this is a permissions issue. Check that all shares are owned by your firstadminuser:users:

Code: Select all

ls -al /var/hda/files

You can ensure they are by doing:

Code: Select all

sudo chown -R firstadminuser:users /var/hda/files

Obviously replace firstadminuser with your actual user name.

Also ensure the correct file permissions are applied to all shares. You can do this from the HDA dashboard via the permissions reset.

I am running out of ideas here.

[tomtheappraiser]

I did that, but it is still running. Here are the results:

Greyhole 2.jpg (152.53 KiB) Viewed 3642 times

I noticed that when I go through the Greyhole Work Que process in the troubleshooter, the Logmon stops showing any activity until I run the fsck. This is after I run:

systemctl start amahi-greyhole.service

But before I run:

greyhole --fsck

However, the server can still be heard running, albeit at a much quieter pace.

Once I run fsck, it goes back up to the loud activity sound and the Logmon shows it starting all over again to try to write these files.

Out of shear desperation, I'm attaching a much longer log of what its been doing before I run through that process. I don't know if it will help.

[bigfoot65]

Try this command and post the results:

Code: Select all

greyhole-dfree