- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: readynas 314
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
An ever haunting problem.
I have a Readynas on my network and have issues with accessing its shares.
readynas 304 lates update 6.6.0 authenticatuion on a domain and importing users okay.
accessed from windows 10 machines.
Until this week everything has been fine after a fresh rebuild in November and all updates applied.
But now the problem of either slow to a none response from browsing shares is back.
All the RN are on a domain and they authenticates ok and imports users fine.
because its only happening on the RN box and not other windows shares im a little lost at how to diagnose this.
they all connect to the windows server for the authentication and import users fine.
There is nothing in my windows server logs to indicate an issue, that i can see.
It seams to happen sporadic for example i can browse fine for a while then it stops and sometime just restarts okay.
the workstation trying to connect event logs shows a failed indexing event eachtime
Microsoft-Windows-Search
[ Guid] {CA4E628D-8567-4896-AB6B-835B221F373F}
[ EventSourceName] Windows Search Service
- EventID 3104
Computer RN1.mydomain.local
- EventData
Details: (HRESULT : 0x80040210) (0x80040210)
The logs on the server show
SYSTEM LOG
Jan 02 13:54:01 HQ-NAS-001 winbindd[13614]: [2017/01/02 13:54:01.749582, 0] ../source3/winbindd/winbindd_dual.c:107(child_write_response)
Jan 02 13:54:01 HQ-NAS-001 winbindd[13614]: Could not write result
and SMBD.log
2017/01/02 12:01:28.105847, 0] ../source3/lib/util_tdb.c:494(tdb_chainlock_with_timeout_internal)
tdb_chainlock_with_timeout_internal: alarm (10) timed out for key d1.mydomain.LOCAL in tdb /var/lock/samba/mutex.tdb
ldb: unable to stat module /usr/lib/x86_64-linux-gnu/samba//ldb : No such file or directory
ldb: unable to stat module /usr/lib/x86_64-linux-gnu/samba//ldb : No such file or directory
This error has maintained it self way to long on my system please help identify the source of the problem.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just to keep everyone posted.
I am still waiting on my logs being looked at to identify the cause and appropriate solution.
In the mean time in the hope to get things running on Thursday night I completed a OS re-install from the boot menu.
The OS reinstall boot mode can be useful when refreshing configuration files. So it seamed a good first choice.
This has worked and everything is running good, after a few restarts.
The RN isn’t prompting about the available upgrade yet, but when it comes available I will install.
The system maybe running the now, but an OS reinstall isn’t a good solution, I need to know what happened, The logs should tell us this.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: readynas 314
Hi Comdiv1,
Could you try disabling the anti-virus on the ReadyNAS.
Then please try sending in your ReadyNAS logs for further checking.
How do I send all logs to ReadyNAS Community moderators?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: readynas 314
Antivirus is disabled by default so its off.
Have sent logs in but not heard back yet.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: readynas 314
It might not be relevant to your logged errors, but if IPv6 is enabled on the RN314 try disabling it.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: readynas 314
thanks ,
IPV6 is also disabled on my network.
Took the bonding off as well, but no difference, even swapped the switch to rule it out.
Everything works fine http services, snapshots and backups. Just seems to be the SMB service that grinds to a halt sporadically.
Logs indicate at network not found. but i have tried both network cards on it, different ip address with static settings. Still no change
I thought it maybe be my 2003 server that I need to replace this year, like everything else, but my other 102 backup NAS works fine with no issues and it’s the exact same network and authentication setup.
THERE was also 4 new HDD in the system after rebuild. So can’t even blame them for messing up system files.
I could try a system restore, but will wait on the guys feedback first, cause am sure it will be something right under my nose.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: readynas 314
Your logs were received. I forwarded them on to FramerV.
Please send follow ups as to whether logs were received via public post or via PM. The logs email is a group email.
Btw we just released ReadyNAS OS 6.6.1 yesterday
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: readynas 314
Hi Comdiv1,
I just would like to verify if you had the chance to try the new firmware?
Link was sent by mdgm.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: readynas 314
@Comdiv1, I was seeing serious access problems on multiple Macs (running 10.2.x). See my recent thread titled, "Sluggish AFP access, Finder hangs: Permissions issues?"
My issues started after a factory reset (which should have cleared up errors, not caused them!) in early December.
Installing 6.6.1 appears to have solved all problems. Over the past few days my 314 has been more responsive via AFP than it's ever been.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: readynas 314
Hi nsne,
Thank you for sharing.
I would be encouraging you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as solution so others can be confident in benefiting from the solution
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just to keep everyone posted.
I am still waiting on my logs being looked at to identify the cause and appropriate solution.
In the mean time in the hope to get things running on Thursday night I completed a OS re-install from the boot menu.
The OS reinstall boot mode can be useful when refreshing configuration files. So it seamed a good first choice.
This has worked and everything is running good, after a few restarts.
The RN isn’t prompting about the available upgrade yet, but when it comes available I will install.
The system maybe running the now, but an OS reinstall isn’t a good solution, I need to know what happened, The logs should tell us this.