Greyhole 0.9.64 Update
- Adding support for Samba 4.3
- Add compiled vfs module for x86-64
- Merge pull request #143 from Sparticuz/samba43
- New VFS module for Samba 4.3 (i386, x86_64, armhf)
- When installing either the RPM or DEB packages, show a warning if logrotate is not installed.
- New --balance-status command to monitor the progress of --balance
#2 Updated by bigfoot65 over 4 years ago
Tested by installing RPM prior to Greyhole UI. Received the following error message:
error: Failed dependencies: lsof is needed by amahi-greyhole-0.9.64-0.x86_64 php-intl is needed by amahi-greyhole-0.9.64-0.x86_64 php-mbstring is needed by amahi-greyhole-0.9.64-0.x86_64 sysstat is needed by amahi-greyhole-0.9.64-0.x86_64
I then tested installing Greyhole UI first, then the RPM. I added a single drive to the storage pool and Docs share. Saw this error message prior to running FCSK:
Feb 27 10:05:28 WARN initialize: PHP Warning : Invalid argument supplied for foreach() in /usr/bin/greyhole on line 510; BT: greyhole[L3285] processCommandLine() => greyhole[L3058] getRunner() => greyhole[L3094] process_config() => greyhole[L6058] parse() => greyhole[L147] init() => greyhole[L360] getShares() Feb 27 10:05:28 WARN initialize: PHP Warning : Invalid argument supplied for foreach() in /usr/bin/greyhole on line 510; BT: greyhole[L3285] processCommandLine() => greyhole[L3058] getRunner() => greyhole[L3094] process_config() => greyhole[L6058] parse() => greyhole[L147] init() => greyhole[L401] getShares() Feb 27 10:05:28 WARN initialize: The storage pool drive '/var/hda/files/drives/drive1/gh' is not part of any drive_selection_algorithm definition, and will thus never be used to receive any files.
Once FCSK ran, everything seemed to settle down.
Next using the amahi-greyhole test checkist (https://wiki.amahi.org/index.php/Web_App_Packaging_Notes#Amahi_Greyhole), I discovered the following issues:
a. After adding files, FCSK did not run automatically to pick up the files. I then tried to force it (greyhole -f) and still nothing. A reboot was required for it to see the files added.
b. Deleted a file and no action taken by Greyhole. A reboot was required for it to delete the file.
Not sure what is going on, but something is not right. I have heard of a few users having issues, but they seemed to clear up over time.
The test was done on a VM with no updates and the latest Amahi 8 platform. This machine is the one you currently have access to for debugging.
All checklist items passed with the exception of what I have noted above.
#3 Updated by bigfoot65 over 4 years ago
So after leaving it set for about 10 minutes (I timed it), Greyhole finally saw the changes to the share and deleted/added files.
Seems like there is something off on the timing. It should sense file changes more frequently, then react accordingly in my opinion.
Will continue to explore the source and see what changed.
#4 Updated by cpg over 4 years ago
i think we should instlall the deps first. probably what happened here i think is that the existing GH installed, then the new one i assume you install via upgrade and at that point you did not get any install warnings?
as for the rest -- it's good to hear things stabilized, but it's a little worrying. so we may have to sit this one out a bit past the point of amahi 9 install, just because we have a lot going on
Also available in: Atom