-
Notifications
You must be signed in to change notification settings - Fork 377
SMB crawler not working, share verified working #50
Comments
Maybe you didn't escape correctly some chars in the password? |
Password is just all lower case and kind of like 'heythisismypasswordbutitslongsoicanrememberit'. No special characters. |
Ok, can you please run |
@effnorwood any news? |
Just saw this, will do and get back. Thanks! |
@effnorwood any news? |
No news for 2 weeks. Closing |
I have the same issue. I can ping the SMB host from a freshly installed virtual machine with ubuntu 16.04.
To mount the share with |
@yuergen please share with us your crawler config |
@sochix yes, sure. Here it is:
|
@yuergen host_name should be the name of the pc not the ip address |
I have found a workaround which can be used for testing: Changing the samba-Server's configuration by enabling What is the correct way to supply the samba domain name via the crawler configuration of ambar? |
use domain name in your login, e.g. |
@sochix I will test it as soon as possible and give you feedback if it works. Thank you. |
@sochix, your suggestion works. Thank you! For other users it might be important to know that it is necessary to escape the backslash. This results in a config line similar to |
Installed clean today on clean Ubuntu 16.04 install. Verified I can connect to the share from Windows and Linux using mount -t cifs. Crawler config:
{$)|(\.txt$ )|(\.csv$)|(\.htm[a-z]$)|(\.ppt[a-z]$)|(\.pdf$ )|(\.msg$)|(\.eml$)|(\.rtf$)|(\.md$)|(\.png$)|(\.bmp$)|(\.tif[f]$)|(\.jp[e]g$)|(\.hwp$)",
"id": "data",
"uid": "data_d033e22ae348aeb5660fc2140aec35850c4da997",
"description": "nas crawler",
"type": "smb",
"locations": [
{
"host_name": "nas",
"ip_address": "10.0.0.100",
"location": "data"
}
],
"file_regex": "(\.doc[a-z]$)|(\.xls[a-z]
"credentials": {
"auth_type": "ntlm",
"login": "jes",
"password": "***",
"token": ""
},
"schedule": {
"is_active": true,
"cron_schedule": "/15 * * * *"
},
"max_file_size_bytes": 30000000,
"verbose": true
}
Error:
2017-07-14 11:15:00.688: [info] filecrawler initialized
2017-07-14 11:15:00.695: [error]
2017-07-14 11:15:00.700: [error] error connecting to Smb share on nas
Notice that there is nothing by the error at all.
Also, how do I get to the logs for this system? I looked at docker logs but they said nothing about this issue. Thank you.
The text was updated successfully, but these errors were encountered: