Forum Discussion
Configuration SMB Monitors
- Mar 13, 2014
It seems as though the issue was due to a missing directory. The message below which was seen in the logs was due to the local directory not being present.
file.txt was not transferred: No such file or directory
The monitoring uses /var/run/monitors as a default directory. This appears to be hardcoded. The get commands are successful and the files are being placed in /var/run as indicated by the preceding lines in the logs.
smbclient //longweb03sandbo/share mypassword -I 10.200.8.28 -p 445 -c cd .; cd; get file.txt file.txt.18261 -U myuser dirstring: Current directory is \ Domain=[LONGWEB03SANDBO] OS=[Unix] Server=[Samba 3.0.33-3.39.el5_8] getting file \file.txt of size 2 as file.txt.18261 (0.5 kb/s) (average 0.5 kb/s) Recvd: 'Current directory is \
Creating /var/run/monitors directory resolved the issue. We now get:
smbclient //longweb03sandbox/share mypassword -I 10.200.8.28 -p 445 -c cd .; cd; get damian.txt damian.txt.24691 -U 101135 dirstring: Current directory is \ Domain=[LONGWEB03SANDBO] OS=[Unix] Server=[Samba 3.0.33-3.39.el5_8] getting file \damian.txt of size 6 as damian.txt.24691 (1.5 kb/s) (average 1.5 kb/s) Recvd: 'Current directory is \ ' up
I'll ask an obvious question. Have you checked the permissions on the CIFS server for the LTM to be able to access the file?
- damian_19221Mar 11, 2014NimbostratusGood call... I hadn't tested that, but I just mounted the share from another host with the same credentials I'm using on the LTM and can read the file ok. I've not seen it documented anywhere, but what is supposed to go in the "Path / Filename" field in the monitor? If my file is in the top level directory of my share, then it should just be the file name?
- Cory_50405Mar 11, 2014NoctilucentI believe so, because the location is relative to the service. If you are dropped into /share, then it should be right there. Have you tried capturing traffic on the LTM using tcpdump and saving to a file to view with Wireshark? I wonder if the capture would yield any useful information about the reason for failure.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com