Bug #2360
Upgrade to Greyhole 0.10.17
0%
Description
https://github.com/gboudreau/Greyhole/archive/0.10.17.tar.gz
- New: VFS modules for Samba 4.8 & 4.9
- Improvement: check that the required PHP extensions are enabled, before executing (anything)
- Bugfix: Samba VFS module failed to log write operations that occurred asynchronously, triggering VFS' pwrite_send & pwrite_recv instead of pwrite. This resulted in Greyhole not noticing any file write ops, between the file open & close ops.
- Bugfix: folder where we need to put the VFS module symlink might not exist
- Crashfix: Samba 4.5+ would sometimes crash; adding our own pwrite_recv_fn fixed it
History
#5 Updated by modem7 2 months ago
modem7 wrote:
cpg wrote:
here is a build. can you help test it out and provide feedback @modem7 ?
(if so, @bigfoot65 can provide a checklist of things to test out)[...]
Installed now, awaiting any problems. If I don't respond, assume all is going as expected.
Getting the following when attempting to start it:
[~]$ greyhole
PHP Warning: require_once(includes/common.php): failed to open stream: No such file or directory in /usr/bin/greyhole on line 22
PHP Fatal error: require_once(): Failed opening required 'includes/common.php' (include_path='.:/usr/share/pear:/usr/share/php') in /usr/bin/greyhole on line 22
For now, I have gone back to 0.10.15 until resolution
#6 Updated by bigfoot65 about 1 month ago
- Assignee changed from bigfoot65 to cpg
Installed:
[amahi@localhost ~]$ sudo rpm -Uvh http://alpha.amahi.org/tmp/amahi-greyhole-0.10.17-1.x86_64.rpm Retrieving http://alpha.amahi.org/tmp/amahi-greyhole-0.10.17-1.x86_64.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:amahi-greyhole-0.10.17-1 ################################# [100%] Created symlink /etc/systemd/system/multi-user.target.wants/amahi-greyhole.service → /usr/lib/systemd/system/amahi-greyhole.service. Running as unit: run-rf38ff196448a420eaed90b7c5b85023c.service
Service won't start. Get the following:
[amahi@localhost ~]$ sudo systemctl status amahi-greyhole -l ● amahi-greyhole.service - Greyhole for Amahi Loaded: loaded (/usr/lib/systemd/system/amahi-greyhole.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-01-08 21:07:40 CST; 4s ago Process: 2895 ExecStopPost=/bin/rm -f /run/amahi-greyhole.pid (code=exited, status=0/SUCCESS) Process: 2887 ExecStart=/usr/bin/amahi-greyhole (code=exited, status=0/SUCCESS) Main PID: 2888 (code=exited, status=255) Jan 08 21:07:40 localhost.localdomain systemd[1]: amahi-greyhole.service: Failed with result 'exit-code'. Jan 08 21:07:40 localhost.localdomain systemd[1]: amahi-greyhole.service: Service hold-off time over, scheduling restart. Jan 08 21:07:40 localhost.localdomain systemd[1]: Stopped Greyhole for Amahi. Jan 08 21:07:40 localhost.localdomain systemd[1]: amahi-greyhole.service: Start request repeated too quickly. Jan 08 21:07:40 localhost.localdomain systemd[1]: Failed to start Greyhole for Amahi. Jan 08 21:07:40 localhost.localdomain systemd[1]: amahi-greyhole.service: Unit entered failed state. Jan 08 21:07:40 localhost.localdomain systemd[1]: amahi-greyhole.service: Failed with result 'exit-code'. Jan 08 21:07:41 localhost.localdomain systemd[1]: amahi-greyhole.service: Start request repeated too quickly. Jan 08 21:07:41 localhost.localdomain systemd[1]: Failed to start Greyhole for Amahi. Jan 08 21:07:41 localhost.localdomain systemd[1]: amahi-greyhole.service: Failed with result 'exit-code'.
I have Greyhole UI installed and a single drive in the pool along with one share selected.
#7 Updated by cpg 28 days ago
I can reproduce this with a plain configuration (no config settings for ii other than the RPM one). I wonder if it's because there is a bad default GH configuration?
did you have a decent GH config or just the default? did you usually do this and work?
I note that it takes a few seconds to stop (about 25 or 30). the "exit-code" error is in fact strange.
Also available in: Atom