Highlighted
Absent Member.
Absent Member.
1915 views

File not found

Hi I have installed Filr and it works great to the first few hours after that no one can download or upload and files. on my android device I get file not found (500) even though it is there. if I restart the appliance it is fine again.

the windows server is Windows 2012 if that affects anything. Has anyone else seen this?

thanks in advanced
0 Likes
9 Replies
Highlighted
Absent Member.
Absent Member.

Re: File not found

ckazzi wrote:

>
> Hi I have installed Filr and it works great to the first few hours
> after that no one can download or upload and files. on my android
> device I get file not found (500) even though it is there. if I
> restart the appliance it is fine again.
>
> the windows server is Windows 2012 if that affects anything. Has
> anyone else seen this?


Sounds like the famtd service may be dying. The next time this
happens, please try the following command on the appliance.

rcnovell-famtd status

If it's not running, try starting it up using this command

rcnovell-famtd start

Then see if things start working. If that gets it going again we'll
need to take a look at the famtd.log to try and determine why the
service is dying.

--
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: File not found

Hi thanks for getting back so quickly. Yes that was the problem. Where is the log file located?

jmarton;2261919 wrote:
ckazzi wrote:

>
> Hi I have installed Filr and it works great to the first few hours
> after that no one can download or upload and files. on my android
> device I get file not found (500) even though it is there. if I
> restart the appliance it is fine again.
>
> the windows server is Windows 2012 if that affects anything. Has
> anyone else seen this?


Sounds like the famtd service may be dying. The next time this
happens, please try the following command on the appliance.

rcnovell-famtd status

If it's not running, try starting it up using this command

rcnovell-famtd start

Then see if things start working. If that gets it going again we'll
need to take a look at the famtd.log to try and determine why the
service is dying.

--
Your world is on the move. Novell. Because Your World is on the Move.
We know what your world looks like. Novell. Because we know what your world looks like.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: File not found

ckazzi wrote:

> Hi thanks for getting back so quickly. Yes that was the problem. Where
> is the log file located?


/var/opt/novell/filr/log/famtd.log

--
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: File not found

Cheers. I had a look at the log file and it looks like its a rights issue. I didn't give the proxy full rights to the share and the file permissions. Hopefully this should resolve the issue.

ckazzi;2261916 wrote:
Hi I have installed Filr and it works great to the first few hours after that no one can download or upload and files. on my android device I get file not found (500) even though it is there. if I restart the appliance it is fine again.

the windows server is Windows 2012 if that affects anything. Has anyone else seen this?

thanks in advanced
0 Likes
Absent Member.
Absent Member.

Re: File not found

Hi,

I am still having the problem. I am getting a lot of these errors.

May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees:PopulateTrusteeList: Could not get attributes for [smb://name of server/name of file] 110: Connection timed out
May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees:PopulateTrusteeList: ret = -1, the_acl = system.nt_sec_desc.*, value =
May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees::GetFirstTrustee: Trustee List is not populated

Thanks in advanced.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: File not found

ckazzi wrote:

> May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees:PopulateTrusteeList:
> Could not get attributes for [smb://name of server/name of file] 110:
> Connection timed out
> May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees:PopulateTrusteeList:
> ret = -1, the_acl = system.nt_sec_desc.*, value =
> May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees::GetFirstTrustee:
> Trustee List is not populated


The connection timed out error likely indicates that famtd has died
again. Have you tried increasing the amount of RAM this VM has? When
doing so, make sure you also increase the JVM heap size (in the
appliance config).

--
Your world is on the move. http://www.novell.com/mobility/
We know what your world looks like. http://www.novell.com/yourworld/

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: File not found

Thanks. I will increase the heap size to 8G and test. Thanks.

jmarton;2263442 wrote:
ckazzi wrote:

> May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees:PopulateTrusteeList:
> Could not get attributes for [smb://name of server/name of file] 110:
> Connection timed out
> May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees:PopulateTrusteeList:
> ret = -1, the_acl = system.nt_sec_desc.*, value =
> May 9 12:53:13 kazflr01 [XTCOM]: ERROR:Trustees::GetFirstTrustee:
> Trustee List is not populated


The connection timed out error likely indicates that famtd has died
again. Have you tried increasing the amount of RAM this VM has? When
doing so, make sure you also increase the JVM heap size (in the
appliance config).

--
Your world is on the move. Novell. Because Your World is on the Move.
We know what your world looks like. Novell. Because we know what your world looks like.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: File not found

On 14/05/2013 06:26, ckazzi wrote:

> Thanks. I will increase the heap size to 8G and test. Thanks.


Don't just increase the JVM Heap Size without also adjusting the amount
of virtual memory assigned to the appliance VM - JVM Heap Size should be
half the virtual memory. If you're going to increase the JVM Heap Size
to 8g you should increase the amount of virtual memory to 16GB.

HTH.
--
Simon
Novell Knowledge Partner

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Technology Transfer
Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: File not found

Thanks for that. I increased the VM to 16GB and the JVM to 8GB. It is still crashing. It lasts about 4 hours than dies.

The last set of errors I am seeing is

May 15 02:10:08 servername [XTCOM]: ERROR:FAMTOperations::ProceeRequest failed unc: //servername/name of file identity: domain\username session: tcpesZGtEv+gkzfoxPWZqw==
May 15 02:10:08 servername [XTCOM]: ERROR:thread_handler: request processing failed
May 15 02:10:08 servername [XTCOM]: ERROR:sendStatus: sending status ret: -15
May 15 02:10:11 servername [XTCOM]: ERROR:CIFSOperations::FAMT_GetOwner: SMBC_Getxattr: failed: 110 path: //servername/name of file
May 15 02:10:11 servername [XTCOM]: ERROR:FAMTOperations::ProceeRequest failed unc: //servername/name of file identity: domain\username session: tcpesZGtEv+gkzfoxPWZqw==
May 15 02:10:11 servername [XTCOM]: ERROR:thread_handler: request processing failed
May 15 02:10:11 servername [XTCOM]: ERROR:sendStatus: sending status ret: -1
May 15 02:10:17 servername [XTCOM]: ERROR:CIFSOperations::FAMT_GetOwner: SMBC_Getxattr: failed: 110 path: //servername/name of file
May 15 02:10:17 servername [XTCOM]: ERROR:FAMTOperations::ProceeRequest failed unc: //servername/name of file identity: domain\username session: tcpesZGtEv+gkzfoxPWZqw==
May 15 02:10:17 servername [XTCOM]: ERROR:thread_handler: request processing failed
May 15 02:10:17 servername [XTCOM]: ERROR:sendStatus: sending status ret: -1
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.