search for: cjtibbett

The longer our samba runs the more delayed the responses become. Samba has been running for 5 months but this new development was noticed 2 weeks ago. The first major sign of the issue was a new DC was trying to join and failed due to timeout errors. At close look we see performance degradation within a few hours or when we try to join a new DC. smb.conf # Global parameters [global]

On Thu, Dec 18, 2014 at 3:51 PM, Cj Tibbetts < cjtibbetts at heritageacademyaz.com> wrote: > > Thank you Ricky for responding. I am still new to linux and samba so I am > struggling with where to start. I will answer your questions the best that > I can. For memory use I see only a small increase over time. I used vmstat > after reboot...

Here is the information requested it took 3 days before results came samba-tool dbcheck finished with this error root at ham1:/usr/local/samba/bin# time ./samba-tool dbcheck --cross-ncs Checking 212687 objects ERROR(<type 'exceptions.MemoryError'>): uncaught exception - File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py", line 175, in _run

New to linux and new to Samba so any direction in troubleshooting would be helpful. Here is what I have so far. Within a half an hour of a reboot of the server my cpu reaches high numbers and becomes slow to respond on all actions. With my limited understanding I have used vmstat to observe the system. I noticed is that the numbers of forks grows from 1-2k to 43k within 30 minutes after reboot. I