amette_: left #tikiwiki
joined #tikiwiki
left #tikiwiki
wikifan: https://demo.tiki.org/17x/ is down ? getting ERR_TOO_MANY_REDIRECTS
https://doc.tiki.org/Documentation -> System error. The following error message was returned: Got error 28 from storage engine
k that's up now but the search on that page still doesn't work, just returns a blank page
not_a_robot: joined #tikiwiki
amette_: joined #tikiwiki
fp: joined #tikiwiki
amette_: polom
fp: hi, i am running a tiki 15.5 installation. the one issue i do have is that i am not happy with the search results. even if my searchstring matches around 60% of a complete tiki article this article is somewhere random in my search-results
all search results have the same relevance of 1
is that supposed to be like that?
even if i enter the complete article name to my search the article in question is not number 1 in the search result list
amette_: Hi fp, I assume you use MySQL full-text-search? The results of that are sadly quite arcane... they get better by using either the Lucene PHP implementation or (much better) by using an additional/external elasticsearch server. Both these things are configurable from Admin->Control Panels->Search.
fp: hi amette_ . yes i am pretty sure we currently do use the mysql search
thanks for the pointers
amette_: np, yw
fp: mh, interesting. the paket elasticsearch is installed on that server and in 'Control Panel' -> 'Search' the unified search index is set to Elasticsearch as well
*package elasticsearch*
amette_: That sounds pretty good then. Time to get into tuning... ;)
Usually though the search results with elasticsearch out-of-the-box are amazingly good.
fp: but i dont see a cronjob to rebuild a search index
amette_: I'm not sure, if putting 60% of the article into the search field is a good test... but usually, with two/three keywords, it gives me pretty much exactly what I want.
yes, that one would be beneficial *nod* ;)
fp: is there a way to check the age of a search index (elasticsearch)
amette_: And you can set additionally to update the index incrementally.ä
it should be mentioned on the Admin Search page
fp: most likely in the advanced settings/view right?
Your index was last fully rebuilt on Friday, 08. July 2016 08:40:53 UTC. ;)
amette_: Aha! ;)
fp: how often would you recommend to optimize and/or rebuild the index?
RadoS: joined #tikiwiki
amette_: I usually have it to incrementally update and then do an additional rebuild it via cron nightly (when there are no/little users on the site).
If you have ginormous amounts of data, you could even do it just once per week or so.
fp: hopefully my last question then: i do know how to rebuild it, but how to incrementally update it?
amette_: Optimization, etc. depends a lot on your data, how often it is updated, etc.
Admin -> Search: Activate "Advanced" features, then check "Incremental Index Update"
fp: ok. created a daily crontab to rebuild on a daily basis. icremental index update is/was already activated
amette_: Cool. Then happy searching! :)
fp: to be honest- the results dont look that much better so far ;)
amette_: lol :D
sorry, but hmmm... didn't expect that.
fp: maybe i am assuming wrong that if my searchstring is part of an article it should have a higher relevancy
article-title
amette_: maybe you need to tweak the weights in Admin Search (never really used those myself, but they are for making these knids of adjustments)
fp: lets see what i can find
xavi: joined #tikiwiki
polom
amette_: moloq xavi
xavi: doc.t.o yields error 500
amette_: oops, ok, I'm on it
xavi: hi amette
thks :-)
and dev.t.o shows db connection lost
:-/
amette_: That was just temporary, when restarting MySQL for doc.
xavi: ok, dev.t.o is up now, doc.t.o shows error 500 still
amette_: doc.t.o will take a while
can the table tiki_rss_feeds be truncated? It's over 2GB in size.
ok, no, optimize did just fine, table is now 10MB
xavi: no idea, sorry. I reckon, if that is the source of the problem (is it really?), a better solution for all tikis out there should be found
ah, ok. I wonder how a table of 10Mb can get 2Gb in size
amette_: It's not the table data itself, it's the binary log (logging changes).
xavi: amette : fyi, see also this: https://irc.tiki.org/irclogger_log/tikiwiki?date=2017-10-18,Wed&sel=6#l2
amette_: ^
amette_: yep, same thing, error 28 is no space left
fp: ok - more questions regarding the search: Assuming title & textarea is set as heigh weight-wise for search - should an article which features my search-string several times have a higher relevancy then an article which features the text only once?
using elasticsearch which rebuilded index
luciash: polom
arildb: joined #tikiwiki
Bsfez: joined #tikiwiki
fp: sidenote: my 15.5 install points for more details on elasticsearch to https://doc.tiki.org/ElasticSearch - which throws a 404
amette_: xavi, luciash, fp : doc is back
luciash: amette_: thanks! so do we need to buy more disk space?
Bsfez: Thanks Amette !
amette_: What happened? tiki_rss_feeds binary logs filled up the disk, then the automatic svn up broke a PHP file, which made php throw a 500.
luciash : no
xavi: thanks amette_
how can we make things (server-side) less fragile?
luciash: can we have cron warning sent to your mail when disk space becomes critically low?
amette_: I need to change the setup of the machine. Let me explain it one last time: I had to set it up quickly, because elastichosts was down. I did the normal Debian install, which partitions the disk fully and added a swap area to the end of it. So that's why I can't just resize the disk, but will have to do a more complicated operation.
luciash : yes, there is monitoring for this. I was sleeping though.
luciash: ah, cool
amette_: now https://security.tiki.org please
fp: regarding search: legacy mysql full text search must be enabled for having a search function at all right? even if elasticsearch is configured as unified search engine
luciash: amette_: error 500
amette_: luciash : ok, hang on
luciash : back
xavi: fp: nope, I'm afraid. Only advanced search, and choose your unified search engine. You need to disable Basic Search
at some point, this Basic Search feature should dissapear, to prevent usability issues by new users
imho
fp: see this: https://doc.tiki.org/Admin-Wizard#Set_up_Search . Basic search should be off, and Advanced Search on, which the unified search index engine of your choice. Mysql Full text Search, as unified search index, should be fine also.
Bsfez: +1
default was changed and a message should say it is legacy
xavi: doc.t.o needs updating, then, imho
I'm doing my opart with what I know from a year ago or so
chibaguy: joined #tikiwiki
polom
amette_: moloq chibaguy
chibaguy: hi amette_
fp: xavi thanks for the infos.
xavi: fp np.
hi chibaguy
chibaguy: hi xavi
fp: its getting more and more interessting. if i search via: tiki-searchresults.php the results are pretty "bad" - while searching via tiki-searchindex.php gives really good results.
we always used the search-widget - which seems to use tiki-searchresults.php
therefor the searchresults was disappointing in almost all cases
amette_: fp : that's what xavi meant earlier: searchresults uses the old, old mysql-search, while searchindex uses the newer "unified search index" with one of its three different backend options (Mysql, Lucene, Elasticsearch).
fp: can i force the search widget to use the new search - aka -tiki-searchindex.php?
amette_: Just use the correct module.
xavi: fp: disable the basic search, and it will use the new engine
the same module, afaik
amette_: ah, k, my mistake then
xavi: s/afaik/afair
amette_: (thought there were two, but true, didn't see two of them the last time I configured a Tiki search)
fp: xavi: havent found that setting yet, as your linked screenshot looks totally different then my ui here ;)
still digging
xavi: fp: use the Wizards
https://doc.tiki.org/Wizards
jonnyb: joined #tikiwiki
fp: xavi: i did find and used the wizard to jump to "set up Search". i did disable 'basic search' and 'advanced search' already was enabled. I did finish that step via "Save and continue. Butthe search widget still is using tiki-searchresults.php
ignore that
reloading the wizard had basic search enabled once again. -redid my steps and it seems to work now
guys - big thanks to all of you - the search is now as i would expect a good search. this bumps my wiki
amette_: Cool! Glad to hear that. :)
fp: until now search in our tiki setup was always the ugly-child nobody was loving ;)
amette_: Yeah, I've heard that often. *g*
fp: one final sidenote regarding search: why are you splitting searchstrings on the - character?
amette_: This changes massively though once people start using the elasticsearch based one. ;)
hmm, no idea. What do you mean by splitting them?
fp: i do have articles for each host in our network so i.e.: vm-wsus
if i search for vm-wsus the search is highlightning VM and WSUS as individual search strings in my results
so i do enter 1 searchstring "vm-wsus" but search seems to search for "vm" "wsus"
which works still pretty good with the new search, but i was/and/am wondering why you implemented it that way
amette_: Aaah, good question, no idea. Maybe it's even not us doing it, but elasticsearch. Maybe there's an option for this!?
fp: as it is uncommon at least for me
amette_: if you put vm-wsus in quotes, like so "vm-wsus", when searching, does it still split it up?
fp: even if i really quote "vm-wsus" it is used as 2 strings
amette_: hehe, k
fp: yes ...same idea ;)
amette_: :)
xavi, luciash : I added a cron job to optimize tiki_rss_feeds table every night. It shouldn't hurt performance, but stop the disk from running full.
xavi: thanks amette_
chibaguy: btw, I visited themes.t.o today (after many months of no visit ) and I see a popup in the browser saying: "A problem occurred while detecting JavaScript on this page, click ok to retry." (in both FF and Chromium
)
chibaguy: Yes, xavi, I noticed that, too. I'll try to track it down.
xavi: ok. Clikcing ok in FF did the trick after page reloadē
ah, in Chromium too.
who knows
amette_: left #tikiwiki
joined #tikiwiki
Bsfez: joined #tikiwiki
fp: bye
jonnyb: polom
chibaguy: Hi jonnyb
jonnyb: hi chibaguy - bs4 branch looks good, i see you are starting to modify some tpls, woo! :)
chibaguy: Thanks. Yes, a few as I come across things that are an easy fix.
Bsfez: joined #tikiwiki
chibaguy: Forms aren't looking too bad, but break pretty much when Chosen is activated. I commented out the Chosen CSS temporarily because it created many compile problems.
Same for tablesorter and I think pivottable. They can be addressed later.
luciash: amette_: awesome, cheers
jonnyb: sounds like progress - i think it would be a good idea to keep a note (and diff's) of files you are changing outside of themes, as by the time tiki 19 comes we will get terrible conflicts otherwise i fear...
moqmoq luciash amette_ xavi and all :)
luciash: hello jonny
still good with the hurricane?
(except the yellow sky)
chibaguy: ok
jonnyb: wind seems to have stopped, bit gloomy and dark but not yellow today, thanks luciash :)
Bsfez: joined #tikiwiki
luciash: jonnyb: cool, I hope ppl in the Irelands are safe as well
Jyhem_laptop: joined #tikiwiki
luciash: jonnyb: did you have a look at the H5P in cached wiki pages issue by any chance?
https://dev.tiki.org/item6403
jonnyb: no sorry, critical client issues only so far this week, maybe next week?
Bsfez: joined #tikiwiki
amette_: left #tikiwiki
joined #tikiwiki
xavi: left #tikiwiki
amette_: left #tikiwiki
joined #tikiwiki
trebmuh: joined #tikiwiki
amette_: left #tikiwiki
joined #tikiwiki
Bsfez: joined #tikiwiki
Telesight: joined #tikiwiki
jonnyb: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki
Jyhem_laptop_: joined #tikiwiki
Jyhem_laptop: joined #tikiwiki