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
Hi, it doesn't seem to make a difference whether I use longweb03sandbo or longweb03sandbox - both test OK from my PC and both fail on the LTM monitor. I think the protocol just truncates the last character anyway.
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