similar to: How to implement Spotlight support using ElasticSearch

Hello, yes sadly update 8.9 of elasticsearch broke the samba integration. Seems like 8.10 is still broken. Stay on 8.8 until this is fixed. Ive emailed Ralph B?hme of Sernet already, but hes got no time for it atm. Im not sure about the second part of your bug report though: > There is a bug where when the samba server is running and files are being indexed while samba is running finder

So I have two issues. 1) Using Samba 4.19.2 with spotlight and elasticsearch 8.10.3 doesn?t work. Errors: [2023/10/22 09:04:17, 0] ../../source3/rpc_server/mdssvc/mdssvc_es.c:755(mds_es_search_http_read_done) mds_es_search_http_read_done: json_loadb failed 2) Using Samba 4.19.2 with spotlight and elasticsearch 7.17.10 works. There is a bug where when the samba server is running and files

I?m trying to setup Spotlight with Tracker (2.3 from Ubuntu repo) backend in Ubuntu 20.04 and Samba 4.12.7. I?ve followed the wiki closely but every time I try to search I get this in the logs: [2020/10/02 10:43:42.078242, 0] ../../source3/rpc_server/mdssvc/mdssvc_tracker.c:403(mds_tracker_search_start) mds_tracker_search_start: no connection to Tracker [2020/10/02 10:43:42.079897, 0]

Hi, Is anyone using Spotlight with Elasticsearch in production and what kind of tweaking have you had to do? Certain search types seem to work out of the box, but others not. Perhaps fscrawler and Elasticsearch need some customization that the wiki doesn?t mention. There also seems to be a difference in using the main search box in the Finder window or the more granular options below, even if

Hi Louis, I used your excellent packages but also tried building from source. I?m trying to get Tracker working. Elasticsearch was simpler to get going but it doesn?t really suite the use case due to limitations in fscrawler. I actually created the mdssvc user but also tried directly under root once the dedicated user didn?t work. The problem might be somewhere in D-Bus configuration but I

Hai, Selfcompiles samba? And which one did you use? https://wiki.samba.org/index.php/Spotlight_with_Elasticsearch_Backend Or https://wiki.samba.org/index.php/Spotlight_with_Gnome_Tracker_Backend I think you missed : https://wiki.samba.org/index.php/Spotlight_with_Gnome_Tracker_Backend#Create_a_user_under_which_Tracker_will_run Greetz, Louis > -----Oorspronkelijk bericht----- >

On Wed, Jan 28, 2015 at 04:12:00PM -0800, Jeremy Allison wrote: > On Wed, Jan 28, 2015 at 04:14:15PM -0500, David Thompson wrote: > > > > Hi all, > > > > I have a setup that I'm trying to configure spotlight on samba to > > work with Apples OSX. In the samba wiki it says to use ./configure > > --enable-spotlight sorry, but the code is not shipping yet

Hi Louis, The idea I had with this thread is to just get an honest comparison between Windows and Samba when it comes to file sharing needs in the Windows world, the missing Windows Search capability was just an example to get the discussion going. If I understand your reference correctly, there is a solution, compatible with Apple's Spotlight, to index files on a Samba server using

Hi Pertu, On 6/3/24 10:34 AM, Perttu Aaltonen via samba wrote: > I see a lot of back and forth network traffic when the results are > displayed, so to me it looks like it could be due to fragmentation, > while the native results seem to come back in a big chunk. iirc I recently added fragmentation support to the mdssvc client, but it's still not implemented in the client. Though

Hai Viktor, I dont know or can't tell if this setup can use the windows indexing, i havent looked in to that. I dont use windows indexer. But i do know if you setup as shown and you add a webpage to the server, that makes is also usable for Windows users to search. There was some work done in the area

When comparing to native macOS Spotlight searches, the Samba & elasticsearch combo is much slower, at least for me. Samba takes minutes to return a few hundred results, while native macOS returns thousands of results in a few seconds. This is remotely over a mobile connection, LAN is probably better. Is this due to the missing Spotlight RPC packet fragmentation support mentioned in the

Hai, The latest update is now online. Debian Buster Samba 4.12.5 + extra patches for amd64/i386/armhf. samba (2:4.12.5+dfsg-2.1buster1) buster; urgency=medium * Rebuild from Debian Sid for Debian Buster * d/control, re-added acl as Recommands to samba package * d/control added libicu-dev,add Missing support for Unicode normalisation. * d/patches, fix debian bug #964165 with

Release Announcements --------------------- This is the first stable release of the Samba 4.12 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== Python 3.5 Required ------------------- Samba's minimum runtime requirement for python was raised to Python 3.4 with samba 4.11. Samba 4.12 raises this minimum version to Python

Release Announcements --------------------- This is the first stable release of the Samba 4.12 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== Python 3.5 Required ------------------- Samba's minimum runtime requirement for python was raised to Python 3.4 with samba 4.11. Samba 4.12 raises this minimum version to Python

How could I investigate this further? If I monitor session and system dbus activity with dbus-monitor I can see activity if I do ?tracker search pdf? as the mdssvc user, but nothing if I search through Samba. I only get those two errors below. So seems like Samba dbus connection isn?t working. I?ve followed the wiki very closely so to me it looks like it?s missing a step or the latest versions

I've been working with Samba in an AD domain setting for several years now. Small potatoes, nothing fancy. A few months ago, I came across the limitation of Samba, in comparison to file sharing from a Windows server, that, at the current moment, it doesn't offer an indexing service that is compatible with Windows Search. So, no matter how much I like Samba, if I need this feature, I have

Release Announcements ===================== This is the fourth release candidate of Samba 4.12. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.12 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fourth release candidate of Samba 4.12. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.12 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Hi, this is the error message I do receive: Tracker-Message: 14:15:22.884: Could not get mtime for 'file:///nonexistent/.cache/tracker/meta.db': Error when getting information for file “/nonexistent/.cache/tracker/meta.db”: No such file or directory (process:5229): Tracker-WARNING **: 14:15:22.884: Falling back to bus backend, the direct backend failed to initialize: Could not open

I’m having this exact same issue after upgrading from 4.7.x to 4.9.1. I’ve been using the same set of instructions to setup tracker for a few years without issue. Does anyone have any suggestions? I’m stuck on this and can’t figure out what’s changed. Thanks. Mike Pestorich > Date: Mon May 14 12:31:28 UTC 2018 > From: Dirk Köppen > > Hi, > > this is the error message I do