Greyhole UI Server never activating

[mjaw]

Greyhole UI Server is never activating. I manually turn it on and hit refresh and it is turned off. I Installed it from the app store, then added my hdd's, formated ext4 i believe, added shares to greyhole, and as far as I can tell it is not making the second copy of the share I had set up. I have the Disk Stats app installed and it shows all my shares data sitting on my OS hdd under the "/". It shows my 2 other hdd's as emty and shows my greyhole setup as "/var/spool/greyhole/mem 4 MB".

WHy is greyhole not duplicating my shares. I setup my hda using amahi instructions and download data.
Help please

extra what is better using Amahi's Plex app of installing it manually. I have done it manually before.

[bigfoot65]

WHy is greyhole not duplicating my shares.

First of all, let's make sure it's running. Do the following via command line:

Code: Select all

sudo systemctl status amahi-greyhole

Post the output here please.
If it's not running, you can start it by:

Code: Select all

sudo systemctl start amahi-greyhole

Next, need to check the contents of /etc/greyhole.conf.

Code: Select all

sudo cat /etc/greyhole.conf

Post them here.

Did you add your new drives to the Greyhole storage pool via the greyhole-ui App? To ensure you get multiple copies, I always set my shares to max copies.

You also might want to check /var/log/greyhole.log file for activity:

Code: Select all

tail -f /var/log/greyhole.log

extra what is better using Amahi's Plex app of installing it manually.

If you install the plex-media-server App manually, we cannot provide any support.

[mjaw]

Thankyou for responding


sudo systemctl status amahi-greyhole

● amahi-greyhole.service - Greyhole for Amahi
Loaded: loaded (/usr/lib/systemd/system/amahi-greyhole.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit-hit) since Fri 2017-09-29 22:13:06 EDT; 11s ago
Process: 8469 ExecStopPost=/bin/rm -f /run/amahi-greyhole.pid (code=exited, status=0/SUCCESS)
Process: 8466 ExecStop=/usr/bin/kill $MAINPID (code=exited, status=1/FAILURE)
Process: 8434 ExecStart=/usr/bin/amahi-greyhole (code=exited, status=0/SUCCESS)
Main PID: 8435 (code=exited, status=1/FAILURE)

Sep 29 22:13:06 HTPC systemd[1]: amahi-greyhole.service: Unit entered failed state.
Sep 29 22:13:06 HTPC systemd[1]: amahi-greyhole.service: Failed with result 'exit-code'.
Sep 29 22:13:06 HTPC systemd[1]: amahi-greyhole.service: Service hold-off time over, scheduling restart.
Sep 29 22:13:06 HTPC systemd[1]: Stopped Greyhole for Amahi.
Sep 29 22:13:06 HTPC systemd[1]: amahi-greyhole.service: Start request repeated too quickly.
Sep 29 22:13:06 HTPC systemd[1]: Failed to start Greyhole for Amahi.
Sep 29 22:13:06 HTPC systemd[1]: amahi-greyhole.service: Unit entered failed state.
Sep 29 22:13:06 HTPC systemd[1]: amahi-greyhole.service: Failed with result 'start-limit-hit'.

sudo cat /etc/greyhole.conf

# This file is automatically generated by Amahi on 2017-09-28 22:45:31 -0400
# Any manual changes WILL BE OVERWRITTEN!
# Set the defaults (carefully) in /var/hda/platform/html/config/greyhole.yml
db_engine = mysql
db_host = localhost
db_user = greyhole
db_pass = greyhole
db_name = greyhole
sticky_files = Music/
# add any group of other settings
# here in multiple lines

delete_moves_to_trash = yes
modified_moves_to_trash = no
email_to = root
drive_selection_algorithm = most_available_space

greyhole_log_file = /var/log/greyhole.log
df_cache_time = 15
log_memory_usage = no
check_for_open_files = yes
ignored_files = (\..*\.[0-9a-zA-Z]{6}|[0-9A-F]{8}\.tmp|\.cprestoretmp.*)
ignored_folders = .*/_UNPACK_.*
log_level = INFO

storage_pool_drive = /var/hda/files/drives/Data 2/gh, min_free: 10gb
storage_pool_drive = /var/hda/files/drives/Data 1/gh, min_free: 10gb
num_copies[Clients] = max
num_copies[Raw Photography] = max

Did you add your new drives to the Greyhole storage pool via the greyhole-ui App? To ensure you get multiple copies, I always set my shares to max copies.


I am using the Amahi grehole-ui app that I paid for from the app store. The shares are set to max copies.


tail -f /var/log/greyhole.log Repeating continously

Sep 29 22:30:13 INFO daemon: Greyhole (version 0.10.13) daemon started.
Sep 29 22:30:13 INFO daemon: Optimizing MySQL tables...
Sep 29 22:30:13 CRITICAL daemon: ERROR: The following storage pool drives are on the same partition: /var/hda/files/drives/Data 2/gh, /var/hda/files/drives/Data 1/gh. The Greyhole
daemon will now stop.

[bigfoot65]

storage_pool_drive = /var/hda/files/drives/Data 2/gh, min_free: 10gb
storage_pool_drive = /var/hda/files/drives/Data 1/gh, min_free: 10gb

I see two drives for the storage pool. One potential issue is the use of spaces in the mount point. Recommend you unmount the drives, then remount them without the space. For example, Data 1 should be data1. No need to use capitalization. Linux is finicky about spaces.

Based on your output of the log and the status command, Greyhole is not running. Making these changes will likely correct the issue. You should remove them from the Greyhole storage pool first, then redo the mount points.

BTW, using Greyhole is for advanced users so you pleas understand you need to have some Linux command line experience when attempting such tasks.

Basically you need to start over with the Greyhole portion and go from there.