Tickets :: Comment on [#12906] Horde doesn't work on NFS

* Your Email Address
* Spam protection	Enter the letters below: .___. .. ..__.._. [__ \| \|\|__\|\| \| \| [___\|/\\|\| \|\|__\|_\|_
Comment	> I've a recently upgraded Horde from FreeBSD packages. The server runs > from a read only NFS server, so every directory and file are on NFS > and are read only. > When I log into Horde, I get the following error: > [08-Jan-2014 09:46:44 Europe/Budapest] PHP Fatal error: Call to > undefined method PEAR_Error::getName() in > /usr/local/share/pear/Horde/Core/Db/Migration.php on line 93 > > Placing two debug log statements around that line: > -----------------------------------8<----------------------------------- > foreach (glob($pear->get('data_dir') . '/*/migration') as $dir) { > Horde::log("XXX ".$dir, Horde_Log::ERR); > Horde::log("XXX > ".$registry->getPackage(basename(dirname($dir)), > 'pear.horde.org'), Horde_Log::ERR); > $app = $registry->getPackage( > -----------------------------------8<----------------------------------- > revealed the following: > Jan 8 09:46:44 [imp] XXX > /usr/local/share/pear/data/Horde_ActiveSync/migration [pid 2333 on > line 90 of "/usr/local/share/pear/Horde/Core/Db/Migration.php"] > Jan 8 09:46:44 [imp] XXX could not acquire shared lock > (/usr/local/share/pear/.lock) [pid 2333 on line 91 of > "/usr/local/share/pear/Horde/Core/Db/Migration.php"] > > Doing a ktrace on the php process gives: > 2333 php-fpm CALL open(0x810f64348,0<O_RDONLY>,<unused>0) > 2333 php-fpm NAMI "/usr/local/share/pear/.lock" > 2333 php-fpm RET open 16/0x10 > 2333 php-fpm CALL fstat(0x10,0x8112bc540) > 2333 php-fpm STRU struct stat {dev=973143809, ino=3195588, > mode=-rw-r--r-- , nlink=1, uid=0, gid=0, rdev=42672, > atime=1389170490.846139742, stime=1389170490.846139742, > ctime=1389170490.846139742, birthtime=-1, size=0, blksize=4096, > blocks=1, flags=0x0 } > 2333 php-fpm RET fstat 0 > 2333 php-fpm CALL lseek(0x10,0,SEEK_CUR) > 2333 php-fpm RET lseek 0 > 2333 php-fpm CALL flock(0x10,0x1<LOCK_SH>) > 2333 php-fpm RET flock -1 errno 45 Operation not supported > > which makes sense, flock over NFS doesn't work. Last year this setup > worked. What has changed since then? > Could you please correct, or work around this to make Horde runnable > over NFS again?
Attachment
Watch this ticket

Saved Queries